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  October 2007

MSUNAG October 2007

Subject:

Re: E-mail Issues

From:

"Kwiatkowski, Nicholas" <[log in to unmask]>

Reply-To:

Kwiatkowski, Nicholas

Date:

Wed, 24 Oct 2007 09:51:28 -0400

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (133 lines)

The grey-listing method that MSU has implemented fully implements the
RFC for SMTP E-Mail.  There should be no blockage of legitimate email,
only possible delays of up to 4 hours.  Mail servers are required to
re-try sending the email every 4 hours until the message goes through,
up to 24 hours (although the 24 hour mark can be configured to be
longer).  Because most spam is generated from 'spam-bots' which often do
not implement the RFC spec of email, this is a very effective way to
block spam and other malformed email from entering our system.

Most corporations and commercial email providers (including Gmail and
Yahoo) have implemented greylisting as a form of spam protection.  

(I might be speaking without authority on this, but... )The way that MSU
has implemented Greylisting is system-wide.  They greylisting happens
before it actually hits our mail-servers, and cannot be opted-out of.

If you are having so many difficulties, there is always the option to
run your own mail server, or have AIS host an Exchange instance for
you...

-Nick Kwiatkowski
 MSU Telecom Systems


-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Laurence Bates
Sent: Wednesday, October 24, 2007 9:30 AM
To: [log in to unmask]
Subject: Re: [MSUNAG] E-mail Issues

I am not convinced that blocking the first instance of an email until a
second arrives from the same source within four hours reflects the best
interests of doing business on campus.  It is trivial for a spammer to
send
multiple emails from the same source within a four hour period but
almost
impossible to get legitimate email sources to do the same thing.  I
really
think that this practice should be thought through in conjunction with
administrative units on campus since it affects their operations in very
significant ways.  Quite frankly, now that I know how this spam filter
works, I don't see how I can justify using my MSU email address to do
MSU
business and will need to migrate to some form of alternate.  Is there a
way
of option out of this portion of the spam filter?

-----Original Message-----
From: Edward R Kryda [mailto:[log in to unmask]] 
Sent: Tuesday, October 23, 2007 10:20 PM
To: [log in to unmask]
Subject: Re: [MSUNAG] E-mail Issues

John Valenti writes: 

> 
> On October 23, at 5:18 PM October 23, Laurence Bates wrote: 
> 
>> In addition, I regularly have problems getting security codes for  
>> software that I purchase off the Internet and need to use
immediately.
> 
> Laurence, this is probably from the greylisting... email from a new  
> sender is automatically rejected the first (few?) times, just to help

> make sure it is a valid smtp server. 
> 
> I have noticed this issue too, but felt that it was a worthwhile
tradeoff

> to reject more spam using this method. 
> 
> As I recall, a second message from the same sender goes thru
immediately.

> So if there is some means of getting the remote end to  send any sort
of 
> message to you first, the important message should  come thru right
away.

> Maybe someone from the mail team could comment  on this?

After the second attempt at delivery, in under a 4 hour time period, the

server is then trusted for approximately 36 days. (The process must be 
repeated afterwards) 

Unfortunately there are web apps which don't use an email server to send
out

confirmations, etc from their pages. They attempt at sending only 1
message 
without worrying about delivery errors. 

Please submit a problem ticket with the ACNS Help Desk at 
http://help.msu.edu if you're having an issue like this. If possible we
try 
to see if a sending host is able to be RFC complaint with retrying
delivery.

If this fails and the server doesn't appear to be a potential large
source 
of spam, then we can add its IP address to an exception list. 

>  
> 
>> I don't blame ACNS for the email delays since they are clearly
related 
>> to the SPAM spikes that we typically get just before Fall  and Spring

>> breaks.
> 
> Not sure where you are getting the spam spikes related to breaks?  I  
> thought it was 24x7 problem, about 97% of messages are spam.

Yeah, Spammers unfortunately don't rest. We do see overall system spikes

that correspond to the University academic schedule. (I'm sure many
other 
services do as well) Today's performance issues aren't related to Spam,
but 
due to our issues with performing backups. More information is posted
at: 
http://servicestatus.list.msu.edu 

 -Ed


__________ NOD32 2611 (20071023) Information __________

This message was checked by NOD32 antivirus system.
http://www.eset.com

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