On Tue, 29 Jun 2004, Tony Nelson wrote: > I hope someone noticed, but the relay server for this mailling list is > blocked in SPEWS. I believe it is in incorrect network entry in SPEWS, > but for right now I have to manually remove the block in my lists > (yesterday and today so far) as our sendmail is just plain blocking the > message. > > Jun 29 11:50:32 mail sm-mta[8094]: i5TFoR5n008094: ruleset=check_rcpt, > arg1=<[EMAIL PROTECTED]>, relay=hermes.apache.org [209.237.227.199], > reject=553 5.0.0 <[EMAIL PROTECTED]>... SPEWS [1] Global Media, see > http://spews.org/ask.cgi?S3056 > Jun 29 11:50:33 mail sm-mta[8094]: i5TFoR5n008094: > from=<[EMAIL PROTECTED]>, > size=0, class=0, nrcpts=0, proto=SMTP, daemon=MTA, relay=hermes.apache.org > [209.237.227.199] > > Is there any way to get this fixed?
Have unitedlayer.com boot their spam-supporting customer at [209.237.227.178]? I don't think this listing is a mistake, or even that it's unwarranted. My guess is that SPEWS expanded their listing to block the entire /24 due to unitedlayer.com's inaction in reining in that customer, thus making [209.237.227.199] collateral damage. The answer is not getting SPEWS to 'fix' their listing and grant us an exception, the answer is to make [209.237.227.178] go dark until its owners decide to stop supporting spammers. Only unitedlayer.com can do that. -- Bob
