I'm trying to allow relaying from mynetworks and sasl authenticated
clients, it works fine when:
* client is in mynetworks and not set to use smtp authentication
* client is not in mynetworks and is set to use smtp
authentication... so sasl auth is working
However when the client is both in mynetworks and they are
configured to use smtp authentication I get "lost connection after
EHLO".
I've posted the logs below but it doesn't realy help me in
determining the cause of this error.
I'm a bit stumped on this one as I have the same configuration
working on another site.
Suggestions much appreciated.
I've figured out why the connection is getting dropped but could
still do with some help.
It seems that somewhere along the line things are getting garbled.
From certain clients the 250-STARTTLS command and others are ending
up as XXXXXs
Here's an example for both ends of one conversation.
telnet from client to mail server:
220 mx.mymx.com ESMTP Postfix
EHLO kananga.mydomin.com
250-mx.mymx.com
250-PIPELINING
250-SIZE 10240000
250-XXXA
250-ETRN
250-XXXXXXXB
250-AUTH PLAIN
250-XXXXXXXXXC
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
STARTTLS
502 5.5.2 Error: command not recognized
QUIT
221 2.0.0 Bye
Here is a wireshark capture on the server end for the same connection:
220 mx.mymx.com ESMTP Postfix
EHLO kananga.mydomin.com
250-mx.mymx.com
250-PIPELINING
250-SIZE 10240000
250-VRFY
250-ETRN
250-STARTTLS
250-AUTH PLAIN
250-AUTH=PLAIN
250-ENHANCEDSTATUSCODES
250-8BITMIME
250 DSN
XXXXXXXX
502 5.5.2 Error: command not recognized
QUIT
221 2.0.0 Bye
Any ideas what is going on and has anybody ever come across this before?
-Phill
| 