Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Earthlink bouncing Greylisted messages

2008-01-11 by Bill Levering

Earthlink is causing problems (again).

 From what I gather, it is bouncing messages back to the sender as  
undeliverable.

My guess is that there are multiple servers trying to send the  
message, and none of them get auto-whitelisted.

Does anyone know what outgoing server they use? netblock? any other  
ideas.. I just don't want to whitelist earthlink.net.

As someone once said:
There is a shitload of zombied/trojaned/proxied spam machines using  
both their domains as return addesses on the spam.

Thanx,
Bill

>> ------ Forwarded Message
>> From: Mail Delivery System
>> <Mailer-Daemon@...>
>> Date: Fri, 11 Jan 2008 11:36:07 -0500
>> To: <audra@...>
>> Subject: Mail delivery failed: returning message to sender
>>
>> This message was created automatically by mail delivery software.
>>
>> A message that you sent could not be delivered to one or more of its
>> recipients. This is a permanent error. The following address(es)  
>> failed:
>>
>> ed@...
>>   SMTP error from remote mailer after RCPT TO:<ed@...>:
>>   host mail.siriuslink.com [128.121.50.164]: 451 4.7.1 Greylisting in
>> action, please come back later:
>>   retry timeout exceeded
>>
>> ------ This is a copy of the message, including all the headers.  
>> ------
>>
>> Return-path: <audra@...>
>> Received: from [75.172.57.67] (helo=[192.168.0.11])
>> by elasmtp-mealy.atl.sa.earthlink.net with asmtp (Exim 4.34)
>> id 1JDMrR-0000tk-8u; Fri, 11 Jan 2008 11:36:01 -0500
>> User-Agent: Microsoft-Entourage/11.3.3.061214
>> Date: Fri, 11 Jan 2008 08:35:44 -0800
>> Subject: Re: New Associate
>> From: Audra Brown <audra@...>
>> To: Ed Kelly <ed@...>
>> CC: Crystal Rude <Crystal@...>
>> Message-ID: <C3ACDAE0.DD7E%audra@...>
>> Thread-Topic: New Associate
>> Thread-Index: AchUcALLQVSb38BjEdy7FgAX8gIvqg==
>> In-Reply-To: <22912DE3-2AF7-4E5A-A3FF-F2B209B6CAB9@...>
>> Mime-version: 1.0
>> Content-type: multipart/related;
>> boundary="B_3282885346_20349590"
>

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.