On 9/23/07 10:49 PM, "Thomas Hochstein" <[EMAIL PROTECTED]> wrote:
> "John W. Baxter" schrieb:
>
>> 4. It's not clear, however, why AOL would fail sender verification callouts
>> with their VERPed addresses. They do want those bounces (those are the more
>> useful ones to a mailing list system)
"John W. Baxter" schrieb:
> 4. It's not clear, however, why AOL would fail sender verification callouts
> with their VERPed addresses. They do want those bounces (those are the more
> useful ones to a mailing list system).
Perhaps their VERP procedure is broken, generating the VERPed
messages,
John W. Baxter wrote:
>On 9/13/07 4:00 AM, "Simon Hobbs" <[EMAIL PROTECTED]> wrote:
>
>
>>Assuming I *should not* whitelist AOL, that I should put the onus
>>squarely back on AOL, how should I word this message and who should I
>>send it to? If I can understand the issue better, I can inform my
On 9/13/07 4:00 AM, "Simon Hobbs" <[EMAIL PROTECTED]> wrote:
> One of my users receives mail from an AOL listserver. The digest fails
> to reach him on every second day. To investigate the issue, I subscribed
> for a while via an unrelated mail server which doesn't do sender
> verification. The di
Simon Hobbs wrote:
>
> Here are some relevant log file messages:
>
> 2007-08-26 14:00:59 H=lsvsm-m01.elist.aol.com [64.12.187.199] sender
> verify fail for
> <[EMAIL PROTECTED]>: response
> to "RCPT
> TO:<[EMAIL PROTECTED]>" from
> listserv.aol.com [152.163.210.183] was: 550 5.1.1
> <[EMAIL
Hi there
One of my users receives mail from an AOL listserver. The digest fails
to reach him on every second day. To investigate the issue, I subscribed
for a while via an unrelated mail server which doesn't do sender
verification. The difference in the headers was fairly obvious:
On bad days