On 08/14/02 at 11:40, Rick Osgood wrote:
> >>I get a great deal of spam from domains in .CZ and .RU. As the
> >>likelihood of my ever getting legitimate email from Rumania is
> >>extremely remote, I'd like to find a way to ban those domains.
>
> Well, pardon me. I don't really give a flippin' ".RU" what the
> suffix stands for, I just would like to hear from someone who can
> please tell me how to setup the router to either ignore or ban these.
You can't do this with the router unless the spam's return-path has a .ru
domain. Unfortunately, they mostly don't. The relay server may be a .ru,
but the return path will often be something entirely different. For those
relays, you need to blacklist them by IP address.
> I've tried using the = NULL setting in the router, but it seems to
> require a full domain name, the asterisk doesn't appear to work after
> the @ symbol.
That's correct. In a local alias address in the router --
<[EMAIL PROTECTED]> -- you can only use a wildcard in the 'user' part.
> According to the manual, it appears that a setting like this should
> cause the server to ignore the email: * @*.RU = NULL
Another limitation of the router is that you can only use one wildcard in a
given entry. So that would have to be either
<*@some.specific.domain.ru> = null
which will catch all messages from that specific domain, or
*.ru = null
which will catch all messages from any .ru domain. But, again, these router
entries will only work on return-path addresses, and only if you've got
'Verify Return-Paths' enabled (which you should). (BTW, the first line is
equivalent to 'some.specific.domain.ru = null' so it doesn't really require
a wildcard.)
Also, it's arguably a little better to route 'naughty' return paths to
'error' rather than to 'null'. Messages routed to 'error' generate a bounce
message back to the sender, while messages routed to 'null' just disappear
into the void with no bounce.
> Of course, as usual, I am probably completely misunderstanding the
> manual, which seems to be written for someone with a different
> mindset than mine. This changeover to SIMS from EIMS has been a real
> pain. A couple of people here have been a big help in getting us
> running at all.
SIMS' router does have a somewhat steep learning curve, and the manual does
assume a certain level of prior knowledge. Once you grok it, though, the
router is a very powerful tool.
--
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]>
