Thread

This question may be related to a resolved thread.

When trying to send mail from EE Communicate tab, I’m recieving the following error message:

Unable to send email at this time.
Debugging Message
220 utter.chaos.org.uk ESMTP Exim 4.34 Thu, 14 May 2009 07:37:46 +0000

hello: 250-utter.chaos.org.uk Hello ec2-174-129-125-84.compute-1.amazonaws.com [174.129.125.84]
250-SIZE 52428800
250-PIPELINING
250-STARTTLS
250 HELP

Failed to send AUTH LOGIN command. Error: 503 AUTH command used when not advertised

from: 250 OK

to: 550 relay not permitted

Failed to Send Command. Error: 550 relay not permitted

data: 503 valid RCPT command must precede DATA

Failed to Send Command. Error: 503 valid RCPT command must precede DATA
500 unrecognized command
Failed to send SMTP email. Error: 500 unrecognized command
Unable to send email using SMTP

It almost makes sense, but I’m not sure what it means.

In the related thread, I was using a different SMTP server and received a similar message (though slightly different) and thought it was related to being blacklisted by that server, but now I’m not so sure.

Just to update this issue, I have, on the same servers, an installation of Invision IP board and a php software suite called Cliphouse. Both Cliphouse and IPBoard successfully send emails using the same SMTP server accounts, so it does seem to be something specific to Expression Engine.

What that specific thing might be is a mystery.

Any help gratefully appreciated.

I found this thread that discusses something similar.

And, of course, there’s this one: http://ellislab.com/forums/viewthread/114309/

Which was me using a different server and getting a similar but different message.

I’m totally at a loss as to what to do about it.

Are you still being blocked?

Actually, I think that very well may have been it, Sue. I managed to “borrow” an SMTP server account that accepts plain logins and it sent the mail no problem. I can only assume that the other two applications send encrypted logins.

The odd thing is that one and one were accepting plain logins for the last year or so, then mysteriously stopped again.

So this is, for the moment, resolved. Ish.

OK, so the final resolution is to ensure you use an SMTP server account that accepts plain logins. Don’t hesitate to post again as needed.