[exim] AOL onus when sender verify fails?

Top Page
Delete this message
Reply to this message
Author: Simon Hobbs
Date:  
To: exim users
Old-Topics: Re: [exim] Router decline locally generated messages
Subject: [exim] AOL onus when sender verify fails?
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
(envelope-sender
<owner-THEATRE-SOUND?joesmith??EXAMPLE?-COM@???>)

On good days
(envelope-sender <owner-THEATRE-SOUND@???>

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 user
as to why the responsibility should rest with AOL.

I tried googling, since AOL have a bad reputation, but I got a lot of
noise.

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
<owner-THEATRE-SOUND*joesmith**EXAMPLE*-COM@???>: response
to "RCPT
TO:<owner-THEATRE-SOUND*joesmith**EXAMPLE*-COM@???>" from
listserv.aol.com [152.163.210.183] was: 550 5.1.1
<owner-THEATRE-SOUND*joesmith**EXAMPLE*-COM@???>... User
unknown

2007-08-26 14:00:59 H=lsvsm-m01.elist.aol.com [64.12.187.199]
F=<owner-THEATRE-SOUND*joesmith**EXAMPLE*-COM@???> rejected
RCPT <joesmith@???>: Sender verify failed

Thanks for your time
Simon