Path: csiph.com!usenet.pasdenom.info!aioe.org!.POSTED!not-for-mail From: Mail Man Newsgroups: comp.mail.misc Subject: Re: Would your SMTP server accept -> ehlo MAPI1.0 ??? Date: Sat, 03 Nov 2012 09:56:32 -0400 Organization: Aioe.org NNTP Server Lines: 17 Message-ID: <50952290.6E3D7C18@Man.com> References: <5078AD79.AADEC93F@Man.com> <508C78EE.EAD2B0E9@Man.com> <5093C266.B4193524@Man.com> <50951FB7.D87E73F2@Man.com> NNTP-Posting-Host: j00MYSoEYuGlIbYp6y1sZw.user.speranza.aioe.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@aioe.org X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en X-Notice: Filtered by postfilter v. 0.8.2 Xref: csiph.com comp.mail.misc:347 Mail Man wrote: > And as pointless as it is, my 12-year-old Post.Office SMTP server > software is correctly terminating the session with a "501 Invalid > domain syntax" error. That might explain the some-what common sightings of SMTP connect and immediate SMTP close entries in my server's log files. I see maybe a dozen of those on any given day. The source might just be trojanized windoze PC's that are being used as spam relays (zombies) that impliment a half-ass set of SMTP rules and methods when they send their spam - one of which is the construction of a malformed (non-compliant) HELO/EHLO greeting. So it's probably a good thing that my server is adhering closely to RFC 821.