Other / Undefined "Client TOS Notification"

alexn · Joined: 15 Jan 2008 Posts: 11

Well it does exist,

Received: from [66.9.31.65] (66.9.31.65) by kunbox.com with ESMTP
(Eudora Internet Mail Server X 3.2.10) for <drrip04@aol.com>;
Tue, 15 Jan 2008 15:05:18 -0500
Mime-Version: 1.0
Content-Type: text/html;charset=us-ascii
Content-Transfer-Encoding: 7bit
Date: Tue, 15 Jan 2008 15:05:18 -0500

the above is the address needing to get extracted.

stanbusk · Site Admin Joined: 28 Dec 2005 Posts: 2268

This is not the right place to extract an address from actually. It may be right but it may be wrong. Also, this part of the header is extremely complex to handle as it includes all the routing servers. That means you may get several e-mail addresses in case of forwards.

nieK · Joined: 26 Jul 2007 Posts: 19

@alexn:

I don't know if it could hepl you, but we avoid this problem without the Bounce Handler (which really is a great product, but it doesn't solve this problem).

We have an own INBOX for the AOL feedbackloop-mails. Than we wrote a little tool with regular expressions to get the addresses out of the mails.

Then we had the problem that from an certain extent of mailings, the mail-address in the header will be redacted from AOL.

So we always include some kind of UserID or somethink alike in order to find the address in our database. This is easily to automate if you have full control about the mailings and tools.

Greetings