LuKreme:
> Feb 12 17:37:18 mail postfix/smtpd[25585]: 8BB71118AD62:
> client=mail-fx0-f228.google.com[209.85.220.228]
> Feb 12 17:37:18 mail postfix/cleanup[25539]: 8BB71118AD62:
> message-id=<e4c7e27d1002121637u50074bc2ud09e1df33b4b4...@mail.gmail.com>
> Feb 12 17:38:29 mail postfix/smtpd[25585]: warning: 8BB71118AD62: queue file
> size limit exceeded
...
> $ postconf message_size_limit
> message_size_limit = 15728640
First of all, the MESSAGE size is not the ATTACHMENT size.
The message is some 30% larger than the attached file itself,
because the content is encoded. This encoding was defined in RFC
1341, published in 1992, and updated with a few later RFCs.
Second, the Postfix SMTP server replies with a 552 status code when
the message exceeds the server's size limit:
552 5.3.4 Error: message file too big
This 552 status code is defined in RFC 1427 (SMTP Size Declaration),
published in 1993, and updated with a few later RFCs.
Once Postfix replies with 552, it is up to the remote host to send
a non-delivery notification to the message sender. This is sufficient
to inform the sender that they need to look for an alternative
solution.
Third, unlike the detailed logging of blocked spam (which may be
blocked due to false positives), Postfix does not log all those
details for non-spam delivery errors, because there is no risk
of blocking mail due to false positives.
If people claim that Google is inventing its own SMTP status code, then
a) They are shooting the messenger (Google reports an error response
from a Postfix SMTP server).
b) They are not aware that the 552 SMTP status code was defined in
RFCs almost 20 years ago.
Wietse
