k...@rice.edu:
> On Tue, May 15, 2012 at 03:08:45PM -0400, Wietse Venema wrote:
> > k...@rice.edu:
> > > Dear Postfix users,
> > >
> > > I am having mail bounce from a Exim 4.77 system with the following
> > > error:
> > >
> > > <x...@citykitchencatering.com>: Protocol error: host
> > > citykitchencatering.com[74.50.1.185] said: 250 Accepted (in reply to DATA
> > > command)
> >
> > Does this affect all mail or just some?
> >
>
> It affects all Email sent to the system. This only started today and
> mail to the same system and addresses worked yesterday.
That server is busted.
Maybe they installed a "security" "firewall" that mis-implements
SMTP PIPELINING.
Evidence:
1 May 15 15:29:18 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 220-roland.lunarservers.com ESMTP Exim
4.77 #2 Tue, 15 May 2012 12:29:18 -0700
2 May 15 15:29:18 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 220-We do not authorize the use of
this system to transport unsolicited,
3 May 15 15:29:18 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 220 and/or bulk e-mail.
4 May 15 15:29:18 spike postfix/smtp[37016]: >
citykitchencatering.com[74.50.1.185]:25: EHLO spike.porcupine.org
5 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250-roland.lunarservers.com Hello
spike.porcupine.org [168.100.189.2]
6 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250-SIZE 52428800
7 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250-PIPELINING
8 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250-AUTH PLAIN LOGIN
9 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250-STARTTLS
10 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250 HELP
11 May 15 15:29:19 spike postfix/smtp[37016]: >
citykitchencatering.com[74.50.1.185]:25: MAIL FROM:<wie...@porcupine.org>
12 May 15 15:29:19 spike postfix/smtp[37016]: >
citykitchencatering.com[74.50.1.185]:25: RCPT
TO:<postmas...@citykitchencatering.com>
13 May 15 15:29:19 spike postfix/smtp[37016]: >
citykitchencatering.com[74.50.1.185]:25: RSET
14 May 15 15:29:19 spike postfix/smtp[37016]: >
citykitchencatering.com[74.50.1.185]:25: QUIT
15 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250 OK
16 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 250 OK
17 May 15 15:29:19 spike postfix/smtp[37016]: <
citykitchencatering.com[74.50.1.185]:25: 550 No Such User Here
Line 15: the server replies with "250 OK"; by the rules of SMTP,
this is the reply to "MAIL FROM".
Line 16: the server replies with "250 OK"; by the rules of SMTP,
this is the reply to "RCPT TO".
Line 17: the server replies with "550 No Such User Here". Clearly
the server has gotten out-of-sync with the client.
You can dumb down Postfix with
/etc/postfix/main.cf:
smtp_discard_ehlo_keyword_address_maps = hash:/etc/postfix/busted-servers
/etc/postfix/busted-servers:
74.50.1.185 pipelining
Do "postmap /etc/postfix/busted-servers" and "postfix reload".
Wietse
