[Mimedefang] md_check_against_smtp_server and md_graphdefang_log

[Tilman Schmidt]

Am 26.03.2013 19:53, schrieb kd6lvw at yahoo.com:
> Extended codes:
> 5.1.1 - No such destination mailbox.
> 5.1.3 - Bad destination mailbox syntax (should have been checked by the current relay MTA but wasn't)
> 5.1.4 - Destination mailbox ambiguous (matches multiple possibilities)
> 5.2.1 - Destination mailbox (valid but) disabled
> 5.2.2 - Destination mailbox full  (also may be tempfailed)
> 5.2.3 - Message too big (if the SIZE parameter is used with MAIL FROM)
> 5.3.1 - Mail system full (usually disk storage full)
> 5.3.4 - Message too big (systemwide limit, as opposed to a per user limit)
> 
> and these which have nothing to do with the recipient:
> 5.1.7 - Bad sending mailbox syntax
> 5.1.8 - Bad sending mailbox's system address
> 5.7.1 - Spam or other similar refusal (mailboxes otherwise valid)
> etc....
> 
> Only the first two indicate a "no valid user," but all of these (and probably others) can occur during such a test.  Can you 100% guarantee that these other error reasons will never occur between your primary and secondaries?  I don't think so....

Welcome to real life, where there are no 100% guarantees, ever.
In fact, there isn't even a 100% guarantee that a mailserver
will return an extended code at all, let alone one that
correspond to the actual reason for the rejection.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <https://lists.mimedefang.org/pipermail/mimedefang_lists.mimedefang.org/attachments/20130327/6693f962/attachment-0003.sig>