On 4/5/2016 9:17 AM, jaso...@mail-central.com wrote: > On 04/05/2016 07:08 AM, Wietse Venema wrote:>> I'm not exactly sure why I'm > getting one CONNECT and 2 REJECTs. >> >> The client sent two RCPT TO commands. Why did it try the same >> recipient twice? No idea, I didn't write the client code. > > I was just looking to make sure I'm not doing something wrong. > > Not surprised that some spammer's client is doing something weird! > > It didn't dawn on me that a client can send 2 identical commands in a single > connection, and still be a legit SMTP transaction. > > Thanks. > > Jason >
I think this particular instance is because you've set the non-default non-recommended "smtpd_delay_reject = no". > Apr 4 19:55:45 mail01 postfix/psint/smtpd[7450]: NOQUEUE: reject: EHLO > from g87d686d.darrylloves.science[74.63.250.84]: 554 5.7.1 > <g87d686d.darrylloves.science>: Helo command rejected: TLD; proto=SMTP > helo=<g87d686d.darrylloves.science> > Apr 4 19:55:45 mail01 postfix/psint/smtpd[7450]: NOQUEUE: reject: HELO > from g87d686d.darrylloves.science[74.63.250.84]: 554 5.7.1 > <g87d686d.darrylloves.science>: Helo command rejected: TLD; proto=SMTP > helo=<g87d686d.darrylloves.science> First the client's EHLO is rejected, then the client retries with HELO. You may notice other oddities when you use "smtpd_delay_reject = no", including clients that treat an early reject as temporary failures and keep retrying. -- Noel Jones
