MSU Listserv


MSUNAG Archives

MSUNAG Archives


MSUNAG@LIST.MSU.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV at MSU

LISTSERV at MSU

MSUNAG Home

MSUNAG Home

MSUNAG  March 2005

MSUNAG March 2005

Subject:

New EHLO SMTP features.

From:

"m. kolb" <[log in to unmask]>

Reply-To:

m. kolb

Date:

Wed, 9 Mar 2005 11:14:53 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (97 lines)

On Saturday March 5th, we implemented some HELO/EHLO checking for
mail.msu.edu's SMTP connection handling.

When a client makes a connection to an SMTP server, that client is
required by the RFC to identify itself.  This is done in the form of
either:
HELO my.hostname
or,
EHLO my.hostname

where my.hostname is the hostname of their computer, so for example if
I were to send mail from bender.cl.msu.edu to [log in to unmask], the start
of my transaction would go like this:

<mail.msu.edu> Connected to mail.msu.edu.
<mail.msu.edu> Escape character is '^]'.
<mail.msu.edu> 220 sys19.mail.msu.edu ESMTP Exim 4.44 Wed, 09 Mar 2005 08:06:29 -0500
<bender> EHLO bender.cl.msu.edu
<mail.msu.edu> 250-sys19.mail.msu.edu Hello bender.cl.msu.edu [35.8.1.192]
<mail.msu.edu> 250-SIZE 52428800
<mail.msu.edu> 250-PIPELINING
<mail.msu.edu> 250-AUTH PLAIN LOGIN
<mail.msu.edu> 250-STARTTLS
<mail.msu.edu> 250 HELP

and then you continue with your SMTP negotiation.  What most virus'
and spammers do, is send a faulty EHLO or HELO line (or no HELO line
at all!).  Sometimes they try to identify themselves as the actual
server they're trying to connect to, sometimes they identify
themselves as localhost, etc etc.  So, what we did was put some rules
in the exim configuration file to deny some of these spams and viruses
before we have to actually scan them.  This has taken quite a load off
of our servers.  Yesterday for example, we rejected ~260k delivery
attempts via ~1.5k independent connections.

Here is a failed negotiation, attempting to use the server's own name:
<mail.msu.edu> Connected to mail.msu.edu.
<mail.msu.edu> Escape character is '^]'.
<mail.msu.edu> 220 sys28.mail.msu.edu ESMTP Exim 4.44 Wed, 09 Mar 2005 08:38:37 -0500
<bender> ehlo sys28.mail.msu.edu
<mail.msu.edu> 550 Invalid HELO. HELO/EHLO with my domain name.


The problems we are seeing is, some older clients (and some newer
ones, unfortunately) are sending invalid HELO/EHLO responses.  These
include:

  * MS Outlook (at least some versions send hostname with dots
    stripped out, e.g. benderclmsuedu)

  * Pegasus (old client, used (afaik) almost exclusively by the physics
    department, does the same thing as outlook, sends hostname w/o dots)

  * Eudora (different versions appear to act differently, but try
    sending their hostname in the form of
    machinename.server.they.connect.to,
    e.g. nibbler.sys19.mail.msu.edu).

We have also had problems with some versions of Apple's Mail.app, and
Netscape 7.1.

In an effort to deal with these broken client responses, we have
slackened up the rules greatly.  We now accept a variety of clearly
illegal ehlo names.  However, we are still doing *some* checking.

Based on some analysis we have done, it appears that this all may root
back to the client not having their hostname set, or not having their
hostnames set correctly.

Greater than 90% of the hosts we blocked had IP addresses which did
not resolve via DNS.  This could be the cause of some clients not
knowing what to do, and thus spoofing their own hostname.  If you guys
are noticing any problems, or having users complain, if you could
collect some data on that, maybe we can setup a solid fix for clients
on their own end.

Q: Can we turn these EHLO rules off?
A: Easily.

Q: Why is it on at all then?
A: Even with our reduced ruleset to allow the junk from the above
   clients, we are still blocking ~260k virus/spams per day
   without the cost of scanning them, or delivering them.  We are
   trying to do better about strictly following RFCs.

If you google for "block on helo" you'll find some more links that
describe what's happening.

If you have questions please feel free to e-mail me directly, or keep
it on list if you feel it is appropriate.  I want the greater MSU
community to know what's going on, and I'd like to get some feedback
as well.

./matt

--
m. kolb  <[log in to unmask]>

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
June 2023
May 2022
April 2022
March 2022
February 2022
December 2021
January 2019
August 2018
June 2018
May 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001

ATOM RSS1 RSS2



LIST.MSU.EDU

CataList Email List Search Powered by the LISTSERV Email List Manager