Problem with AUTH=LOGIN |
Post Reply |
Author | |
atifghaffar
Senior Member Joined: 31 May 2006 Location: Switzerland Status: Offline Points: 104 |
Post Options
Thanks(0)
Posted: 22 August 2006 at 9:26am |
Hello,
We started using the SMTP AUTH feature. Thanks. It works great. Just a small problem with some email clients and email servers. They expect AUTH=LOGIN instead of AUTH LOGIN. The spamfilter just gives AUTH LOGIN and confuses these clients. (1) 250-AUTH LOGIN (1) 250-8BITMIME (1) 250 HELP (1) Provider does not support "AUTH=LOGIN" extension The postfix server we have works around this by giving out both responses.. eg: 250-PIPELINING 250-SIZE 50120000 250-VRFY 250-ETRN 250-AUTH LOGIN PLAIN 250-AUTH=LOGIN PLAIN 250 8BITMIME Would it be possible to have this work-around in the next release. Thanks in advance |
|
best regards
Atif |
|
BigDog
Newbie Joined: 26 January 2005 Location: United States Status: Offline Points: 11 |
Post Options
Thanks(0)
|
I agree, MS OE works but I just had a user with a Palm Treo complain that it doesn't work for him and that user is a techy who then telnet'ed into the spamfilter box and told me the very same as atifghaffar described.
|
|
BigDog
Newbie Joined: 26 January 2005 Location: United States Status: Offline Points: 11 |
Post Options
Thanks(0)
|
Retract my prior..... Seems that my Cisco Pix firewall is doing this, certain elements are being filtered by it; right now my firewall guy is working on how to make exceptions for the mapping that SpamFilter had though the firewall inorder to correct this. By the way LogSat, EXCELLANT feature upgrade with LDAP authentication !!! Kudos and thanks!!!!
Cisco Pix changes complete and now it appears that all is working properly from the outside. Edited by BigDog |
|
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
|
Atif,
Is your problem also related to the Cisco PIX? If not, can you please provide some references to documentation that requires the syntax "AUTH=LOGIN"? That syntax is in theory incorrect, as per RFC 2821 the ehlo keywords and its parameters must be separated by a space, the "=" is not allowed: Normally, the response to EHLO will be a multiline reply. Each line There is a bug in some older email clients that caused the softwares to require the incorrect syntax "AUTH=LOGIN", but that is a bug in those apps. While we could add the buggy syntax, we're hesitant to do so as we can't predict what will happen to legitimate clients. |
|
atifghaffar
Senior Member Joined: 31 May 2006 Location: Switzerland Status: Offline Points: 104 |
Post Options
Thanks(0)
|
Hello Roberto,
No my problem is not related to PIX. I understand that it is a broken behaviour in the CLIENT and some Servers that act as a CLIENT for us. Postfix server has made a configuration parameter that allows you to accept this broken behaviour (Its difficult for me to justify to our clients that it is THEIR program which is broken when the same program was working fine until the move). Here is the excerpt from the postfix manual, perhaps you can give the same option which when set to yes|1, does what the broken clients want in addition to what the un-broken clients want. Parameter: broken_sasl_auth_clients |
|
best regards
Atif |
|
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
|
Atif,
We uploaded build 3.1.3.598 in the registered user area. The only difference from build 597 is the availability of a new parameter in the SpamFilter.ini file: ;Some older email clients have a bug that requires them to see "AUTH=LOGIN" in the EHLo response rather than "AUTH LOGIN". Set this to 1 to add the incorrect syntax to the EHLO output AddIncorrectAUTHLOGINEHLOEntry=0 Please let us know if this helps. |
|
atifghaffar
Senior Member Joined: 31 May 2006 Location: Switzerland Status: Offline Points: 104 |
Post Options
Thanks(0)
|
Roberto, Thankyou very very much. I have more feature requests but will bug you with that at a later time and in a different thread.
|
|
best regards
Atif |
|
Desperado
Senior Member Joined: 27 January 2005 Location: United States Status: Offline Points: 1143 |
Post Options
Thanks(0)
|
Roberto, It fixed my issue with Stupid ... ooops, I mean "Smart Phones" manufactured by Samsung for Verizon! |
|
The Desperado
Dan Seligmann. Work: http://www.mags.net Personal: http://www.desperado.com |
|
LogSat
Admin Group Joined: 25 January 2005 Location: United States Status: Offline Points: 4104 |
Post Options
Thanks(0)
|
Geez... that bug is years old, thought they'd have fixed it by now...
Well... Thank Atif! he did most of the work |
|
Desperado
Senior Member Joined: 27 January 2005 Location: United States Status: Offline Points: 1143 |
Post Options
Thanks(0)
|
BTW ... I does not seem to have broken the other clients that are using SMTP auth ... or at least I am not seeing any issues. |
|
The Desperado
Dan Seligmann. Work: http://www.mags.net Personal: http://www.desperado.com |
|
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
This page was generated in 0.156 seconds.