The reason for the TOS is because whoever is at the AOL account reported it as spam, and you have setup a feedback loop with AOL. Because of all the extra lines in your logs I can't be sure, but my guess is that the local account got spammed and it was forwarded to AOL who rejected it as spam.
That sad thing is that AOL doesn't include what AOL address rejected the message, it they did it would be much easier for us to track down the origin. What I do is search my log for the sender, then I know who it was sent to. I generally ask the AOL client that it's being forwarded to if they can verify that it wasn't forded to them from their account on our server. I also include a warning that if I keep getting them I will stop forwarding to them to avoid having issues with AOL blocking our server. Once you are on the feedback loop, AOL is way more forgiving, but I still wouldn't want them to get too many of these from our server and test that theory. Ted > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:IMail_Forum- > [EMAIL PROTECTED] On Behalf Of Bill Foresman > Sent: Wednesday, December 15, 2004 3:44 PM > To: [EMAIL PROTECTED] > Subject: Re: [IMail Forum] client TOS notification > > yes, this user forwards their email to their AOL account. > > Matt wrote: > > Bill, > > Look at your IMail server to see if this was sent to either an alias > or an account that was forwarding to AOL. There is no need to speak to > your customer unless you verify the condition and wish to have the > customer stop using it. This is a often reported issue. > > I am near 100% confident that this was sent through your server, and > that it was forwarded by your server to AOL. > > Matt > > > > > Bill Foresman wrote: > > I don't see us having much control over that but I'll speak to > the account holder. > > Bill > > Matt wrote: > > It looks like you might have an account that is being > forwarded to an AOL account. AOL's spam reporting tool is absolutely > blind to this condition, and because they make it so easy for users to > blacklist such a server, you are best off not allowing forwarding to AOL > accounts. If not that, improving your spam detection rates would reduce > the frequency of this happening. > > Matt > > > > Bill Foresman wrote: > > Can someone tell me if my server did something bad > here? > > Thanks, > > Bill > Subject: > Get Cable_Filters Watch Cable_Movies and NFL s8iip33974 > From: > "Rhonda Crawford" <[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED]> > Date: > Wed, 15 Dec 2004 00:42:37 +0200 > To: > <Undisclosed Recipients> > Return-Path: > <[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED]> > Received: > from rly-xh02.mx.aol.com (rly-xh02.mail.aol.com [172.20.115.231]) by air- > xh01.mail.aol.com (v103.7) with ESMTP id MAILINXH11-48d41c0bc1838d; Wed, > 15 Dec 2004 17:35:32 -0500 > Received: > from PINE.MATROSITY.COM (mail.matrosity.com [65.112.155.254]) by rly- > xh02.mx.aol.com (v103.7) with ESMTP id MAILRELAYINXH25-48d41c0bc1838d; > Wed, 15 Dec 2004 17:35:04 -0500 > Received: > from adsl-flat-basic-195.84-47-88.telecom.sk [84.47.88.195] by > PINE.MATROSITY.COM (SMTPD32-8.14) id AB395F50092; Wed, 15 Dec 2004 > 17:31:21 -0500 > Received: > from mr79.bcz.cdchm.com ([34.49.226.228]) by mc88-f20.hotmail.com with > Microsoft SMTPSVC(5.0.2195.18323); Wed, 15 Dec 2004 00:47:37 +0200 > Received: > from mc00.npu.zyzee.com ([162.192.34.160])by mx58.nrm.hevps.com > (8.12.3/8.12.3) with ESMTP id i2E5XSGm029877for > <[EMAIL PROTECTED]> <mailto:[EMAIL PROTECTED]> ; > Wed, 15 Dec 2004 01:45:37 +0300 > X-Message-Info: > VO97Qf6mu4Mu4dzY/4mj1Fv0mwW > MIME-Version: > 1.0 > Content-Type: > multipart/alternative; boundary="--45604635772224988351" > Message-ID: > <[EMAIL PROTECTED]> > <mailto:[EMAIL PROTECTED]> > X-mxGuard-Info: > Processed by pine.matrosity.com using mxGuard v1.5.0 > X-mxGuard-Spool-ID: > bb3805f5009209ed > X-mxGuard-Sender: > [EMAIL PROTECTED] > X-mxGuard-Native-DNSBL: > 1 hit(s) [84.47.88.195] dsbl > X-mxGuard-Native-PTR: > Failed lookup [34.49.226.228] > X-mxGuard-Native-HELO: > Failed lookup [mr79.bcz.cdchm.com] > X-mxGuard-Native-PTR: > Failed lookup [162.192.34.160] > X-mxGuard-Native-RelayCount: > 3 > X-mxGuard-Spam-Score: > 76 > X-mxGuard-Spam-Threshold: > LEVEL10 > X-mxGuard-Spam-Threshold: > LEVEL15 > X-mxGuard-Spam-Threshold: > LEVEL20 > X-mxGuard-Spam-Threshold: > LEVEL25 > X-mxGuard-Spam-Threshold: > LEVEL30 > X-mxGuard-Spam-Threshold: > LEVEL35 > X-mxGuard-Spam-Threshold: > LEVEL40 > X-mxGuard-Spam-Threshold: > LEVEL45 > X-mxGuard-Spam-Threshold: > LEVEL50 > X-mxGuard-Spam-Threshold: > LEVEL55 > X-mxGuard-Spam-Threshold: > LEVEL60 > X-mxGuard-Spam-Threshold: > LEVEL65 > X-mxGuard-Spam-Threshold: > LEVEL70 > X-mxGuard-Spam-Threshold: > LEVEL75 > X-Note: > This message has been scanned for spam and viruses using mxGuard for > Matrosity Hosting > X-AOL-IP: > 65.112.155.254 > X-Mailer: > Unknown (No Version) > > > -- > ===================================================== > MailPure custom filters for Declude JunkMail Pro. > http://www.mailpure.com/software/ > ===================================================== > > > -- > ===================================================== > MailPure custom filters for Declude JunkMail Pro. > http://www.mailpure.com/software/ > ===================================================== To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
