[Outages-discussion] [outages] Level 3 blip

[Jared Mauch]

It's more of a sendmail & mailman issue. My patch to workaround sendmail was not applied properly to mailman. When you end up with people on broken name servers and mail servers it delays others messages unnecessarily. Instead of 500 per I use 10. I also sort by domain prior to handing to the mta to further optimize all the gmail in a single transaction. 

The grey list config I will discuss with others privately, but if you see delays from that, I would be shocked. 

Jared Mauch

On Nov 7, 2011, at 7:20 PM, Jeremy Chadwick <outages at jdc.parodius.com> wrote:

> The delays are likely due to greylisting, but every X-Greylist header I
> see from puck.nether.net indicates greylisting delays aren't happening.
> 
>> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.6
>>    (puck.nether.net [204.42.254.5]); Mon, 07 Nov 2011 14:49:58 -0500 (EST)
>> X-Greylist: Recipient e-mail whitelisted, not delayed by milter-greylist-4.2.6
>>    (puck.nether.net [204.42.254.5]); Mon, 07 Nov 2011 10:07:53 -0500 (EST)
> 
> Of course one will need to review the headers for every Email sent, but
> I can confirm the delays.
> 
> People who deploy use of greylisting often forget one key/important
> fact: the retry interval of delivery is entirely dependent upon the mail
> server attempting the delivery, not the server doing the greylisting.
> That interval could be 5 minutes, or it could be 4 hours.  It's entirely
> up to the system administrator to decide.  And that downside to
> greylisting is exactly why so many people choose not to use it any more
> (read: users expect mail to be delivered quickly).
> 
> -- 
> | Jeremy Chadwick                                jdc at parodius.com |
> | Parodius Networking                       http://www.parodius.com/ |
> | UNIX Systems Administrator                   Mountain View, CA, US |
> | Making life hard for others since 1977.               PGP 4BD6C0CB |
> 
> On Mon, Nov 07, 2011 at 02:55:44PM -0500, Wallace Keith wrote:
>> Maybe this should be on discussion ,   but the posts here are so far delayed, the board is not even useful.
>> If you want info on this am's craziness, check NANOG.
>> -Keith
>> 
>> From: outages-bounces at outages.org [mailto:outages-bounces at outages.org] On Behalf Of Adam Greene
>> Sent: Monday, November 07, 2011 9:45 AM
>> To: outages at outages.org
>> Subject: Re: [outages] Level 3 blip
>> 
>> Another announcement:
>> 
>> -------- Original Message --------
>> Subject:
>> 
>> FW: NYC TIME WARNER OUTAGE
>> 
>> Date:
>> 
>> Mon, 7 Nov 2011 09:41:00 -0500
>> 
>> 
>> Hi All,
>> 
>> TW Outage Should be Resolved at this time( Fiber Backhaul Issue) - Please advise if any of your clients  are still experiencing issues with Their TW Services
>> 
>> 
>> On 11/7/2011 9:36 AM, Adam Greene wrote:
>> Hmm ... just received this as well from a Time Warner agent ... Time Warner is 12271 in one of the AS-PATHs below.
>> 
>> -------- Original Message --------
>> Subject:
>> 
>> NYC TIME WARNER OUTAGE
>> 
>> Date:
>> 
>> Mon, 7 Nov 2011 09:26:15 -0500
>> 
>> 
>> Hi All,
>> 
>> TW is Currently Experiencing a Large Scale TW Outage in NYC- Please Advise your clients if they call you directly
>> 
>> 
>> 
>> On 11/7/2011 9:32 AM, Adam Greene wrote:
>> I think Level 3 just had a major burp in the NY area.
>> 
>> Both ASN 20208 and ASN 11579 were dead in the water from about 9:12am - 9:19am EST.
>> 
>> These are the paths in question:
>> 
>> 20208 12271 7843 3356
>> 11579 3356
>> 
>> Just a heads up ...
>> 
>> thanks,
>> Adam
>> 
> 
>> _______________________________________________
>> Outages mailing list
>> Outages at outages.org
>> https://puck.nether.net/mailman/listinfo/outages
> 
> _______________________________________________
> Outages-discussion mailing list
> Outages-discussion at outages.org
> https://puck.nether.net/mailman/listinfo/outages-discussion