09-12-2007 10:33 PM
This is mainly addressed to the IronPort employees who hang out here.
I found this thread on a discussion board while searching for something else. The bottom line is that AsyncOS does not follow RFC 2034 in its use of enhanced SMTP status codes because it precedes them with a "#", like this:
550 #5.1.0 Address rejected.
550 5.1.0 Address rejected.
09-13-2007 11:37 AM
Heya,
That is kinda right, but we never announce after the EHLO that we do follow the advanced status codes.
Cheers,
Mark
09-13-2007 01:52 PM
[quote:1903d3ddb0="Mark [CSE]"]That is kinda right, but we never announce after the EHLO that we do follow the advanced status codes.
Yes I know. That's what I said:
AsyncOS doesn't advertise the ENHANCEDSTATUSCODES capability, so it isn't actually breaking the rules.
09-13-2007 05:47 PM
You could call tech support and ask them to open a formal feature request. Product Management does look at them.
If they can determine that removing the # sign won't really break anything, it might not be that hard to implement.
09-13-2007 07:26 PM
I will file a feature request, and I can't imagine how removing the "#" will hurt anything. But I am curious to know why they chose to do it that way in the first place.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide