Topic: SMTP AUTH extension not supported by server.

[mophilly]

A commercial application has a feature to send email to a designated address if certain conditions occur on the app server. The host machine is running OS X, is on the LAN behind SME, and the target mail server is SME 7.5.x. SME is up to date, and no other mail clients on the LAN are having trouble. In fact, the mail app installed on the OS X box can send and receive email using the very same SME user account used in the config of the commercial app.

The support rep is asking me to test against gmail or similar, which is fine as far as it goes. Still, it feels like a bit of runaround given that this needs to work with SME. So I am posting this note here, with reservations as it is off topic, in hopes someone might offer a helpful tip.

Here is the traceback on the error:

Code: [Select]

Traceback (most recent call last):
File "/Library/Application Support/Daylite Server/Daylite Server.bundle/Contents/Frameworks/MCMailer.framework/Resources/MCMailer.py", line 65, in <module>
smtp.login(strUser, strPass)
File "/System/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/smtplib.py", line 552, in login
raise SMTPException("SMTP AUTH extension not supported by server.")
smtplib.SMTPException: SMTP AUTH extension not supported by server.
I have read some of the threads here that discuss enabling/disabling qpsmtp proxy and such, but I prefer to avoid customizing the mail service in SME unless it is absolutely necessary.

Does anyone know of issues with the python 2.6 smtplib interacting with SME 7.5 mail service?

[cactus]

A exception is raised in your code because the library you are using seems use a AUTH method that is not supported by the server, you will somehow need to find out which AUTH method is used by the library and what SME Server wants.

[CharlieBrady]

IIRC, AUTH is not enabled unless TLS is negotated first. Have your application send STARTTLS before trying AUTH, or switch your application to use SMTPS on port 465.

[mophilly]

Thank you, Charlie and cactus.

I will ask the support tech at the other company about the methods they employ; perhaps a new idea will emerge.

For the record, I have attempted the test with SSL enabled, password authentication enabled, and verified the user account and password. The app appears to hang when attempting to communication via port 465 under this circumstance.

Here is a snippet from the log sqpsmtpd/current:

Code: [Select]

2011-04-09 14:29:15.886475500 18003 Accepted connection 1/10 from 192.168.181.10 / files.mydomain.com
2011-04-09 14:29:15.886729500 18003 Connection from files.mydomain.com [192.168.181.10]
2011-04-09 14:29:15.892072500 18003 tls plugin (init): ciphers: ALL:!aNULL:!ADH:!eNULL:!LOW:!EXP:RC4+RSA:+HIGH:+MEDIUM
Regards,

 - Mark