The following are the message traffic trends on the Summit Internet Services Mail Server.

Incoming Spam Trend [summitinternetservices.com]
Date Range: 2/15/2009 to 2/21/2009

Greylisting Trend [summitinternetservices.com]
Date Range: 2/15/2009 to 2/21/2009

Message Traffic Trend [summitinternetservices.com]
Date Range: 2/15/2009 to 2/21/2009

Abuse Detection Trend [summitinternetservices.com]
Date Range: 2/15/2009 to 2/21/2009

Blacklist / Whitelist Trend [summitinternetservices.com]
Date Range: 2/15/2009 to 2/21/2009

This report generated by SmarterMail 5.5.3315.Copyright© 2003-2009 SmarterTools Inc. All Rights Reserved
Sun, 22 Feb 2009 07:09:51 GMT

Posted via email from Summit Internet Services

The following are the message traffic trends on the Summit Internet Services Mail Server.

Incoming Spam Trend [summitinternetservices.com]
Date Range: 2/8/2009 to 2/14/2009

Greylisting Trend [summitinternetservices.com]
Date Range: 2/8/2009 to 2/14/2009

Message Traffic Trend [summitinternetservices.com]
Date Range: 2/8/2009 to 2/14/2009

Abuse Detection Trend [summitinternetservices.com]
Date Range: 2/8/2009 to 2/14/2009

Blacklist / Whitelist Trend [summitinternetservices.com]
Date Range: 2/8/2009 to 2/14/2009

This report generated by SmarterMail 5.5.3315.Copyright© 2003-2009 SmarterTools Inc. All Rights Reserved
Sun, 15 Feb 2009 07:14:27 GMT

Posted via email from Summit Internet Services

When a sending mail server gets a retry order (in this case a 451 grey-listing response) they should requeue and resend their mail at a reasonable time frame.

The published Internet Standard for retrying to send mail is 30 minutes after the first delivery failure.

http://www.rfc.net/rfc2821.html

“…The sender MUST delay retrying a particular destination after one attempt has failed.  In general, the retry interval SHOULD be at least 30 minutes; however, more sophisticated and variable strategies will be beneficial when the SMTP client can determine the reason for non-delivery…Experience suggests that failures are typically transient (the target system or its connection has crashed), favoring a policy of two connection attempts in the first hour the message is in the queue, and then backing off to one every two or three hours.”

Sometimes the sender is using a Microsoft Exchange Server which has a documented problem with this standard.  Microsoft documents the issue and provides a Registry fix

http://technet.microsoft.com/en-us/library/aa998772.aspx

The following are the message traffic trends on the Summit Internet Services Mail Server.

Incoming Spam Trend [summitinternetservices.com]
Date Range: 2/1/2009 to 2/7/2009

Greylisting Trend [summitinternetservices.com]
Date Range: 2/1/2009 to 2/7/2009

Message Traffic Trend [summitinternetservices.com]
Date Range: 2/1/2009 to 2/7/2009

Abuse Detection Trend [summitinternetservices.com]
Date Range: 2/1/2009 to 2/7/2009

Blacklist / Whitelist Trend [summitinternetservices.com]
Date Range: 2/1/2009 to 2/7/2009

This report generated by SmarterMail 5.5.3315.Copyright© 2003-2009 SmarterTools Inc. All Rights Reserved
Sun, 08 Feb 2009 07:14:11 GMT

Posted via email from Summit Internet Services

The following are the message traffic trends on the Summit Internet Services Mail Server.

Incoming Spam TrendData for summitinternetservices.com

Greylisting TrendData for summitinternetservices.com

Message Traffic TrendData for summitinternetservices.com

Abuse Detection TrendData for summitinternetservices.com

Blacklist / Whitelist TrendData for summitinternetservices.com

This report generated by SmarterMail 5.5.3315.Copyright© 2003-2009 SmarterTools Inc. All Rights Reserved
Thu, 05 Feb 2009 16:25:29 GMT

Posted via email from Summit Internet Services