On Wed, 8 Feb 2006, John Peacock wrote:
frank wrote:
Here's my take: Ever met an MTA/MUA that _changed_ it's HELO name
mid-stride when you refused the first one? I didn't think so.
My copy uses DENY_DISCONNECT :)
You made the choice to be non-RFC compliant; I don't think that is
necessarily appropriate for the project as a whole. Technically speaking,
the client (remote MTA) is expected to send QUIT when it receives a 5xx
message and the server (local MTA) is not permitted to just drop the
connection.
[Quoting RFC 2821]
An SMTP server MUST NOT intentionally close the connection except:
- After receiving a QUIT command and responding with a 221 reply.
- After detecting the need to shut down the SMTP service and
returning a 421 response code. This response code can be issued
after the server receives any command or, if necessary,
asynchronously from command receipt (on the assumption that the
client will receive it after the next command is issued).
OK, so looks like DENYSOFT_DISCONNECT would be more appropriate - and just
as effective.
