jmfs's avatar
Level 6

SwiftMailer error: Expected response code 250 but got code "", with message ""

I have supervisord running 8 Laravel queue worker instances. I just upgraded our server to PHP7.0 and L5.4, but now I'm getting this error when queuing messages:

Expected response code 250 but got code "", with message ""

frequently during peak traffic times. It doesn't appear our SMTP server is even getting these requests - no throttling or spam blocking is being shown.

Any idea what this error is telling me? Is my SMTP at fault or something in the PHP/Apache setup?

0 likes
5 replies
jmfs's avatar
Level 6

I restarted supervisor service and it seems to fix the issue for a while... is there a setting that could be not releasing a resource or something? I also see this new error:

fwrite(): send of 8192 bytes failed with errno=11 Resource temporarily unavailable

jmfs's avatar
Level 6

running php artisan queue:restart seems to have the same effect and fixes it for a while - can can anyone recommend something that will help?

jmfs's avatar
Level 6

I added --memory=32 and haven't gotten the error since. We'll see if that continues.

(hopefully this will help someone else. This is on a CentOS 7 server)

1 like
jmfs's avatar
Level 6

still getting the error, i'm trying running queue:restart 2x per day.

it seems even overnight when load is low this just compounds once it starts happening. I have the queue set to retry 5 times and am still getting this error.

jmfs's avatar
jmfs
OP
Best Answer
Level 6

Solution! Apparently one of our Cisco routers had Esmtp Inspection turned on, which was messing with the detecting of the connection close. I still get "Connection to X timed out", but I think that's the SMTP connection closing after 2 minutes.

1 like

Please or to participate in this conversation.