|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Andras Galos (galosa
netinform.hu)
Date: Tue Feb 12 2008 - 18:31:52 CST
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wietse Venema wrote:
> Andras Galos:
>> Wietse Venema wrote:
>>> And what evidence do you have that hanging up without reply would
>>> result in different remote SMTP client behavior than sending a 421
>>> reply and hanging up?
>> I'm rather afraid of. 421 means try again, while hangup says this is a
>> bad MX, try another one.
>
> That is not evidence of actual client behavior. That's speculation.
Yes it is. Can I reject everybody with 4xx on the fake MX? No sender
will see this error message, but the one from the primary MX in case of
any error report, delay report, or so? It could be something like "421
MX unavalaible" or similar, but this message should not appear in
senders' mailboxes in any cases. I'm afraid it's an 'answer' that the
client receives and this is something that could be misunderstood by the
client. While a hangup is not an 'answer'. There is no need an answer at
all on a fake MX. The answer is an unnecessary point of failure here.
If you really say 4xx, I'll do that.
Best regards,
Andras Galos
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]