Google generating it's own reject codes?
in [Postfix]
|
From: LuKreme on 13 Feb 2010 05:36 I got the following from a user (email obfuscated). The user has an email address on a domain hosted with me, but all emails are redirected to her gmail account. THis has been working without issue for a long time. > ---------- Forwarded message ---------- > From: Mail Delivery Subsystem <mailer-daemon(a)googlemail.com> > Date: Fri, Feb 12, 2010 at 5:38 PM > Subject: Delivery Status Notification (Failure) > To: user23(a)gmail.com > > > Delivery to the following recipient failed permanently: > > user22(a)domain.tld > > Technical details of permanent failure: > Google tried to deliver your message, but it was rejected by the > recipient domain. We recommend contacting the other email provider for > further information about the cause of this error. The error that the > other server returned was: 552 552 5.3.4 Error: message file too big > (state 18). > > ----- Original message ----- > > MIME-Version: 1.0 > Sender: mbutler18(a)gmail.com > Received: by 10.103.80.32 with SMTP id h32mr1451173mul.59.1266021434616; Fri, > 12 Feb 2010 16:37:14 -0800 (PST) > Date: Fri, 12 Feb 2010 17:37:11 -0700 > X-Google-Sender-Auth: bd3d7d6438b928a4 > Message-ID: <e4c7e27d1002121637u50074bc2ud09e1df33b4b40d6(a)mail.gmail.com> > Subject: St C's Keith, Niels > From: Bess Smith <user22(a)domain.tld> > To: Bess <user22(a)domain.tld> > Content-Type: multipart/mixed; boundary=0016e65b6230e3dc14047f709572 This is an email that the user sent to herself and Google sent her a NDN. However, looking through my logs, this is what I see: $ bzgrep 8BB71118AD62 /var/log/maillog.0.bz2 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=<e4c7e27d1002121637u50074bc2ud09e1df33b4b40d6(a)mail.gmail.com> Feb 12 17:38:29 mail postfix/smtpd[25585]: warning: 8BB71118AD62: queue file size limit exceeded A warning. No error, no failure, no reject. This is everything logged for 8BB71118AD62 with no obfuscation. I have $ postconf message_size_limit message_size_limit = 15728640 in postconf, but I do not know if this message was too large. I doubt it. -- The voice of the majority is no proof of justice.
From: Wietse Venema on 13 Feb 2010 09:35 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=<e4c7e27d1002121637u50074bc2ud09e1df33b4b40d6(a)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
From: LuKreme on 13 Feb 2010 13:13 On 13-Feb-2010, at 07:35, Wietse Venema wrote: > > Second, the Postfix SMTP server replies with a 552 status code when > the message exceeds the server's size limit: I was surprised to see a 552 from google when there wasn't a 552 in the postfix logs, that's what I meant; I did not mean to imply that I thought 552 was invalid in anyway, only that I wasn't seeing that error on my end. -- Tina... homecoming is spelled c *O* m
From: Wietse Venema on 13 Feb 2010 17:15 LuKreme: > On 13-Feb-2010, at 07:35, Wietse Venema wrote: > > > > Second, the Postfix SMTP server replies with a 552 status code when > > the message exceeds the server's size limit: > > I was surprised to see a 552 from google when there wasn't a 552 > in the postfix logs, that's what I meant; I did not mean to imply > that I thought 552 was invalid in anyway, only that I wasn't seeing > that error on my end. You missed a whole paragraph in my response: 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. I guess some people lose the attention span after two. Wietse
From: LuKreme on 13 Feb 2010 23:16 On 13-Feb-2010, at 15:15, Wietse Venema wrote: > > You missed a whole paragraph in my response: No, I just didn't respond to it as there didn't seem to be any need. -- Naked blonde walks into a bar with a poodle under one arm, and two-foot salami under the other. The bartender says, I guess you won't be needing a drink. Naked lady says
|
Next
|
Last
Pages: 1 2 Prev: does using a hash map for an alias file extend rec len? Next: Restrictions on localhost |