laravel mail facade queue function sends mail to wrong mailhost - laravel

I use laravel version 5.8.
To send non-blocking mails through queues I use the mail facade as described in the documents.
In development I use mailtrap.io to attest the mails are send, in production I use the actual smtp server.
Using the Mail::send method sends the mail through the actual smtp server. Using the Mail::queue method the mail is still send with the mailtrap.io server although I flushed the configuration cache.
The only reference of mailtrap.io in the files I can find is in my development .env file which I don't use in production.
I can't figure out why mail is send to mailtrap.io server using queue instead of to the smtp server as is done using send on the mail facade.

Found it. The threads started with php artisan queue:work keep the old configuration until they are stopped (and restarted).
I have supervisor running on the system to start the threads. I did so when in maintenance mode and with a temporarily development environment. This kept the mailtrap.io reference for the queue.
After stopping and restarting supervisor the threads now use the production environment and thus the right smtp server.

Related

failed to authenticate on smtp server in laravel

when i am trying to send mails using smtp in laravel application i am having this error
error
i thought the error is is app but when i upload app on another server the mails are going good.
but on the centos server which is having cpanel is facing this error while sending mail. even i have disabled smtp restrictions in whm.
i am using a laravel application to send email . to sending mails i amd adding smtp server. when i start sending mail 2000 mails get sent but after that all mails gets blocked and are not sent out of the server
Did you consider using queue?
Try to change your mail driver from smtp to mail

Laravel 5.2 Mail cannot be sent outside domain

So when I try to send mails with Laravel's mail facade, I can only send within our company domain, when trying to send E-mails to either gmail or outlook, the mail never gets deliviered, but if I use outlook, the mail is delivered instantly.
I have turned everything upside down to figure out what it can be, but I cant find anything that cause this issue, not even a single trace of my app sending "non-internal" mails in the exchange logs.
Our company uses an Exchange 2003 server, I have checked the logs, no trace of (Out of company) mails are there
Im on a 20 hour streak, sorry for any confusion
/Tarre
The issue was that our Exchange SMTP relay didnt have the correct connectors and configuration.
To use exchange with SMTP.
Add a Connector bridge between your Exchange server and the Virtual SMTP server.
Configure "trusted" IP's.
Everything is done in the Exchange Server Management part.

Laravel 5.1 Mail Queue not working after upgrading driver from sync to redis

I recently setup my Redis server and configured laravel to use it. Everything is going fine, sessions are working cache is working. I set the queue driver to redis in env as well and tried Mail::queue function, apparently I am not getting any error but I don't see any mail in my inbox. When driver was set to sync I was getting emails. Is there something else I need to configure?
Items in the queue (mail and otherwise) sit there until processed by the queue listener.

Send email with Ruby without SMTP server installed/running?

On Mac, I can send email from command line using the command mail, but definitely I don't have SMTP server installed on my MacBookPro.
So, it is possible to send email with Ruby without an SMTP server? I don't care about the speed, I just want a way to send email without additional software needed.
You could just call the mail command from within your Ruby code. Use system or backticks or something more sophisticated like open3 to interact with system commands... Here is a nice overview over the different methods: http://mentalized.net/journal/2010/03/08/5_ways_to_run_commands_from_ruby/
About mail and sendmail
I don't know much about mail, but results from a quick search on Google seem to indicate that it uses postfix, which is the default SMTP server that is installed on Macs. In other words, you have installed and are running a SMTP server on your Macbook Pro.
About Ruby
So, it is possible to send email with Ruby without an SMTP server?
Yes and No. You don't need to have a SMTP server running on the same machine as your Ruby process. In fact, you don't even need to run your own SMTP server. However, you need a SMTP server somewhere to send your email.
About SMTP
This article on howstuffworks gives a good explanation of what SMTP does. Essentially, you need a SMTP server somewhere that accepts your email, talks to other SMTP servers, and passes your email on for delivery. With Ruby, you can configure Net::SMTP to connect to a SMTP server of your choice.
About What You Are Trying To Do
If you want to write and execute a script that will deliver a small number of email messages, create a fake email account on Gmail/Live and use their SMTP servers for sending email.
If you want to build and launch an app that will deliver emails to your users, use Mandrill, MailGun, or SendGrid. Mandrill has a free tier for you to get started.
I don't recommend running your own SMTP server for most use cases, because your emails will likely be marked as spam. (Comcast might also think that you have malware on your network.) Professional services like Mandrill will help you setup SPF and DKIM records to authenticate your emails and improve sending reputation.
(If you just want to test email in dev mode, use MailCatcher.)
Conclusion
Sign up for a Mandrill account, then use Net::SMTP in Ruby to connect to their SMTP servers. No additional software is required.
If your mail command is working, then you can send mail from within
ruby. And if your mail command is working on your mac already, then
you also already have an SMTP server working on your mac, since by
default it uses postfix which comes installed. The mail command
defaults to using /usr/sbin/sendmail, which is in this case an
interface to postfix. (Try man sendmail from the Terminal.)
Now, that said, you will probably experience something like this when trying to use Net::SMTP locally:
[3] pry(main)> smtp = Net::SMTP.start('localhost',25)
Errno::ECONNREFUSED: Connection refused - connect(2)
This means that you need to do something to tell your mac that it can
accept connections on port 25. Another alternative is to use that
sendmail program as a transport access method, which might actually be the
better option. The port 25 access is turned off so that no one else
can use your mac as a mail relay. Having to go through the sendmail
command means that only programs on your mac can send mail (go
figure).
My suggestion here would be to use the mail gem (or pony if you
prefer) and configure it to use sendmail. From the mail README
file:
Sending via sendmail can be done like so:
mail = Mail.new do
from 'me#test.lindsaar.net'
to 'you#test.lindsaar.net'
subject 'Here is the image you wanted'
body File.read('body.txt')
add_file :filename => 'somefile.png', :content => File.read('/somefile.png')
end
mail.delivery_method :sendmail
mail.deliver
Likewise, if you're using ActionMailer you can configure it to use
sendmail as well.
Have you tried the Pony gem? It provides a really simple interface to sendmail, which should already be installed on your Mac.
Is your goal to write and send email from the CLI?
There's a number of mailer gems, including mail. You could probably also play directly with Ruby's Net::SMTP and get something working, depending on what you are trying to do.
You don't have to have an SMTP server, you just need to know where one is that you can connect to.
See Net::SMTP. It's part of Ruby.
If you used mail or /usr/sbin/sendmail command and your mail delivered successfully, then there was an MTA (Mail/Message transfer Agent eg. postfix, sendmail or whatever) running on your machine.
when you use your mail command to send a mail to guser#gmail.com,your mail command will submit the mail to local SMTP server.
(local) SMTP server will do the following tasks.
SMTP server(MTA) will do MX lookup for gmail.com
Connect to port 25 of MX server and hand over the mail by talking SMTP (HELO, MAIL FROM,RCPT TO,DATA commands)
Mx server will deliver the mail to the corresponding mailbox (guser).
The above answers suggest you to use Net::SMTP where you will connect to some SMTP server and hand over the mail to that SMTP server, which will again do the above tasks (of local SMTP server above) to perform the delivery.
So to send mail, u need an SMTP server. or you will have to code yourself/use some library to perform MX lookup and hand over the mail to the MX server by talking SMTP commands as per RFC 2821.

trouble sending mail with free smtp

I am trying to send mail from a local iis app using localhost as my smtp server after installing free smtp but I am getting the following error:
Mailbox unavailable. The server response was: Invalid
recipient: 'validAddress'#hotmail.com
Any idea what the problem could be?
it sounds like your free (3rd party) smtp app is not leaving your network and might be trying to see if it has that mailbox itself. Try and see if there is a setting to allow the smtp server to access external connections, etc. What is the name of the free smtp app, btw?
Alternatively, can u use the built in SMTP mail provider, built into iis? do you know how to use that, instead of this 3rd party app.
It looks more like the SMTP service needs to be configured to "Relay" email... Usually this involves telling it what YOUR mail domain is, and then any mail destin for a domain other than it's own will cause it to go out to the world, and try to relay the message to the real server.
But, be careful! This is how spammers exploit email servers. They look for SMTP listeners that will relay for them. You want to make sure yours will only accept relay mail from "localhost", or whatever machine will be connecting to it to do the sending.
A more secure way is to block port 25 inbound at your firewall to this box, so this SMTP server is not visible to the outside world.
Write and test a simple smtp sender in C. It needs 3 minutes with RFC
Use Wireshark to see what comes on the wire between your application and the SMTP server.

Resources