?

Log in

No account? Create an account

fanf

ENHANCEDSTATUSCODES FAIL

« previous entry | next entry »
30th Oct 2009 | 13:09

I sort of expect an SMTP server that claims to support enhanced status codes to, y'know, put enhanced status codes in its responses...

220 bill.internal.[redacted] ESMTP Symantec Mail Security
EHLO ppsw-0.csi.cam.ac.uk
250-bill.internal.[redacted] says EHLO to 10.0.64.17:58126
250-ENHANCEDSTATUSCODES
250-PIPELINING
250 8BITMIME
MAIL FROM:<dot@dotat.at>
250 MAIL FROM accepted
RCPT TO:<asldkja@sjkfsajhg>
554 Recipient address rejected: User unknown
RSET
250 RSET OK
QUIT
221 bill.internal.[redacted] closing connection

| Leave a comment | Share

Comments {2}

Simon Tatham

from: simont
date: 30th Oct 2009 16:06 (UTC)

I wonder if "Symantec Mail Security", whatever that might be, is acting as a wrapper (SAUCE-style) on the real SMTP server, and passing through the EHLO unmodified but rewriting the subsequent responses...

Reply | Thread

Tony Finch

from: fanf
date: 30th Oct 2009 16:13 (UTC)

The back-end mail server is MS Exchange whose EHLO response is much longer than the one from Symantec Mail Security.

Reply | Parent | Thread