Support forum

Interesting. Diafaan SMS Server should not use APOP with your POP server and I am not sure why it does try APOP instead of a plain login.

However, I see in the log that your POP server supports SASL PLAIN and this will be supported in the next version in addition to DIGEST-MD5, CRAM-MD5 and NTLM. In the new version, Diafaan SMS Server will use plain login for your server instead of APOP. Please let me know if you are still interested in testing it out with your POP server.

Regards, Henk

I had another look at how Diafaan SMS Server handles a POP server that does not support APOP. Contrary to what I said in the previous reply, Diafaan SMS Server should not use APOP when the POP server does not give an indication in the header that this feature is supported. I have tested it with a local POP server that only supports plain login and that works as expected.

I would appreciate it if you can send the log of the POP server test in the Email Connector setup wizard, maybe I can find out if Diafaan SMS Server does not correctly to your POP server.

Regards, Henk

Hello Ole,

The POP client in Diafaan SMS Server tries APOP first to log in and if that does not succeed, it will try to login with plain user name and password. Encrypted login procedures like CRAM-MD5 are not supported but it is possible to use a secure SSL connection and the STARTTLS command, to start encryption, is also supported.

It is probably possible to add support for CRAM-MD5 and DIGEST-MD5 to the POP client. If you are willing to try it out, please send an e-mail to dms@diafaan.com with the login procedures that your POP server supports and if it is possible to add it to the POP client, I will send you a plugin to test it out.

Regards, Henk