On 05/09/02 at 10:35, Mark S. Strom wrote:
> Two days ago, they were coming from IP addreses in the 62.150.189
> range (which resolved to ones owned by qwest.net). After a couple of
> emails to [EMAIL PROTECTED] went unanswered, I entered this block in
> the blacklist. Today they returned, same names on their mail servers
> (mail03.ums01.com and mail04.ums01.com) but from addresses in the
> 63.150.189 range! So I've BL'd these too. However, is there
> something I can put in the router for a spamtrap? When I try to add:
>
> <*@*.ums01.com> = spamtrap
>
> I get
>
> <*@*.ums01.com*ERROR*> = spamtrap
The router only allows one wildcard in an address. Also, you would only
route a recipient address to 'spamtrap'. IOW, routing ums01.com addresses
to spamtrap only works if messages are being sent TO those addresses. If
ums01.com is showing up on the Return-Path header line of the spam
messages, then you can route it to 'error':
ums01.com = error
*.ums01.com = error
If the domain name is somewhere other than in the Return-Path, then your
stuck with blacklisting IP addresses only, at least with SIMS.
--
Christopher Bort | [EMAIL PROTECTED]
Webmaster, Global Homes | [EMAIL PROTECTED]
<http://www.globalhomes.com/>
#############################################################
This message is sent to you because you are subscribed to
the mailing list <[EMAIL PROTECTED]>.
To unsubscribe, E-mail to: <[EMAIL PROTECTED]>
To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]>
To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]>
Send administrative queries to <[EMAIL PROTECTED]>
