From: "Ryan Sorensen" <[EMAIL PROTECTED]>
> > Mike Jackson wrote:
> >
> >> A couple days ago, I set up AOL's "feedback loop" (though the loop
> >> part is a misnomer, since you can't actually respond to the messages)
> >> so I could monitor complaints against my employer's servers. Looking
> >> through the messages AOL says their members reported as spam, I
> >> noticed that none of them actually originated on my servers; they were
> >> all messages that were sent to addresses at the servers, then
> >> forwarded to AOL accounts, and since AOL records the IPs of all
> >> servers the message touched, I'm tainted by them.
>
>
> I have the same problem. Users will come to my site and inquire on a
> financial listing, and report the response as spam. Often, they will
> report the confirmation emails as spam.
>
> My biggest concern though is messages that come in from spammers, get
> filtered by spam assassin (they have ***SPAM*** tags in the subject) and
> then go on to the AOL forwards. These are defanged messages that still
> get reported as spam. I have to believe that AOL isn't stupid enough to
> blacklist me for relaying the message... i hope?
>
> I have been running like this for a number of months now, and so far
> have not had any trouble. I simply slap the users on my system that send
> messages that could be considered UCE and ignore the rest. I probably
> get 50 - 80 TOS notifications per day, and maybe two or three *a week*
> are legitimate violations. So far I haven't been taken off the whitelist.
You may have to deny forwarding the ***SPAM*** bearing messages. Deflect
them locally to a web mail spam reader application that the users can
check if and when they wish. (Auto-delete in a day or two.) It's a lot
of work and inconvenience. But it can work nicely.
{^_^}
