Hello,

In looking through my logs I see some from aol, and they really are from 
aol.  This spam catcher address is embedded in HTML comment tags on some 
pages the customer has.  I verified the IP and it is aol.

We've been getting a lot of spam from aol lately, it seems that anyone 
can just open up a free email account and start blasting.

27 15:55:52[391892:-1227486320] Rejected 64.12.143.152 
HIDDEN@irl247@aol.com> <xxxxxxxxxxxx@xxxxxxxxxxxx.net> 0  "Rcpt found in 
g_black_to so you will be blocked for a period of time - correct mailing 
list"


My attitude with this is if aol isn't going to control the automated 
spamming that comes from page scrapers where the spam trap email is 
inside comment tags, then they deserve to be banned for short intervals. 
  I have no problems telling my customers that aol has spam problems and 
it causes short interruptions and there's basically little we can do 
about it until they clean up their act.

--Ed

On 03/29/2011 08:41 PM, Jake Steidl wrote:
> On 3/29/11 4:44 PM, "VinnyHIDDEN@@Dell.com" <Vinny_Abello@Dell.com> wrote:
>
>     Hi everyone,
>
>     I have more problems with the above error blocking legitimate
>     servers� particularly large servers like AOL, Apple and others. I
>     don�t believe anyone is sending to the address I defined in
>     G_BLACK_TO at all from those servers. In addition, I don�t use
>     g_black_isspam. That is disabled. The only remaining thing is
>     nbadrcpt which I find is a very poor description compared to the
>     usually helpful error messages in Surgemail. I cannot find what this
>     is referring to anywhere. I suspected it was perhaps what is
>     controlled by g_max_bad_ip. I currently have that set to 100 and it
>     still happens. Anyone have suggestions about what causes this and
>     what knobs to look at to help fix it? It�s literally the only
>     problem that causes complaints on our servers. I don�t think I had
>     this issue until I applied several of the recommended settings many
>     months ago. I�ve been trying to chase it down for a while. Everytime
>     I think I have it fixed through whitelisting, it pops up again with
>     a different sending server.
>
>     Thanks!
>
>     -Vinny
>
> I myself am running into this issue as well. Would love to find the
> answer to it as well.
>
> Thanks,
>
> Jake

-- 
-----------------------------------------------------------
EAS Enterprises LLC
World Class Web and Email Hosting Solutions
www.easent.net