Gmail and RFC 2821
Just a Guy
(host gmail-smtp-in.l.google.com[72.14.205.27] said: 451 4.5.0 SMTP
protocol violation, see RFC 2821
I am using postfix-2.0.16-3 on redhat ES 2.1. The MUA in question is
Outlook 2007, and Thunderbird. I have also tried to mail from the
command line. It appears it is something postifx is doing that isn't
well liked by Gmail's servers.
Is there anything that I should be tweaking to get around this issue?
Martin Gregorie
> I have recently been getting mail blocked by gmail with the error
>
> (host gmail-smtp-in.l.google.com[72.14.205.27] said: 451 4.5.0 SMTP
> protocol violation, see RFC 2821
>
Possibilities:
> Is there anything that I should be tweaking to get around this issue?
>
I assume you have read RFC 2821 section 4.5. If not, do so now: GIYF.
Leaving out any deficiencies in Postfix, there are violations of the RFC
that you may have configured in:
- do you have a 'postmaster mailbox?
- have you reduced the maximum mail size (headers+body) below 64 KB?
- have you diddled with any SMTP timeouts?
- is there any program between Postfix and the Internet that could by
causing RFC2821 violations
There are a number of other possibilities that you might have set up by
not setting your configuration correctly. These include:
- not setting mydomain when the hostname isn't an FQDN (Fully Qualified
Domain Name) that matches your external domain name.
- not setting myorigin if the domain name used inside your LAN doesn't
match your external domain name and you haven't set mydomain correctly.
Read section 4.5 of RFC2821 and make quite sure that you haven't
misconfigured anything in Postfix that could be causing the problem.
Ditto for MUAs - check the ones that originated the rejected mail.
Hint: Use always_bcc to capture all mail passing through Postfix so you
can look at the messages that caused the rejections.
--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |
Jack Raats
Matheus Lima:
> Recently, withou any changing in my configurations, the e-mail send to any
> gmail accounts are getting deferred:
>
> Nov 5 18:00:38 tampa postfix/smtp[5687]: 88D6A48F2:
> to=<guim...@gmail.com>,
> relay=gmail-smtp-in.l.google.com[72.14.205.27]:25, delay=2189,
> delays=2186/0.01/2.6/0.54, dsn=4.5.0, status=deferred (host
> gmail-smtp-in.l.google.com[72.14.205.27] said: 451 4.5.0 SMTP protocol
> violation, see RFC 2821 k27si638904qba.10 (in reply to end of DATA
> command))
>
> The problem is only with gmail.
Try:
# postconf -e smtp_discard_ehlo_keywords=pipelining
# postfix reload
If this solves the problem, Google has screwed up their support
for RFC 2920 command pipelining.
Wietse
> PS.: My server receive any e-mail from any gmail account, the problem is
> olny sending. The most fucking issue is that two e-mails that a sended
> among
> various, surprisinly were sent:
>
> one of them is:
> Nov 5 17:40:40 tampa postfix/smtp[4601]: D2E7448D4:
> to=<guim...@gmail.com>,
> relay=gmail-smtp-in.l.google.com[72.14.205.27]:25, delay=1753,
> delays=1748/3.1/0.79/0.99, dsn=2.0.0, status=sent (250 2.0.0 OK 1225914048
> k8si588760qba.5)
>
> WFT?
Just a Guy
> Try:
>
> # postconf -e smtp_discard_ehlo_keywords=pipelining
> # postfix reload
>
> If this solves the problem, Google has screwed up their support
> for RFC 2920 command pipelining.
>
> Wietse
Thanks, I believe you were on... interestingly enough, just as I went
to make the change to my postfix configuration, I noticed a duplicate
(read old) e-mail in my gmail inbox, so I took that as a sign that
they were monkying with things. I sent a few test e-mails and the
problem seems to have solved itself.
Mik