On 05/29/02 at 12:05, Neil Herber wrote:
> It is rumored that on or about 2002-05-29 10:46 AM -0400, Paul List
> Hess wrote as follows:
> >Could somebody tell me what's wrong with this line in my router?
> >Is it the double-wildcard or does it have something to do with the
> >brackets? I am trying to block mail whose Return-Path header shows
> >up as from [EMAIL PROTECTED]
> >
> ><*@*hinet.net> = error ; Klez virus'd 0205+ and various spams
> >
> >Thanks in advance for any help!
>
> Paul
>
> I am pretty sure that you can only have one wild card on either side
> of a router rule.
That and you can only use wild cards in the local part of a foreign alias
address.
> >At 10:54 AM -0400 5/29/02, Neil Herber wrote:
> >>To do what you want, the following should work:
> >>
> >>hinet.net = error
> >>
> >>or
> >>
> >>*.hinet.net = error
> >
> >Thanks Neil!
> >
> >Would I need both of those entries to cover (for instance)
> >mail123.hinet.net as well as just hinet.net?
> >
> >Also, noting that you removed the brackets, would I still use
> >brackets for individual return-path entries I want to block, such as:
> >
> > <[EMAIL PROTECTED]> = error ; virus'd 020516+
> >
> > - Paul
>
> Paul
>
> My experience with the router is "mixed" at best, so I would
> recommend testing any of my solutions. ;->
>
> That warning aside, I think you would need both "hinet" entries to
> catch addresses with just the simple domain as well as those with
> subdomains. I have never tried an entry like "*hinet.net", but it
> might catch both, assuming that the wild card can also represent a
> period.
Yes, the wild card will match dots (.). The problem with an entry like
'*hinet.net' is that, because it does match dots, it may also match other
second level domains that end in 'hinet' -- e.g. 'chinet.net', etc. It may
not be very likely in any particular instance, but to avoid the ambiguity,
it's probably best to use two entries, one for 'hinet.net' to catch the
main domain and one for '*.hinet.net' to catch sub-domains:
hinet.net = error
*.hinet.net = error
> The <brackets> are usually used to indicate a local address or an
> address that you want to treat as local.
A.k.a 'local aliasing' and 'foreign aliasing'.
> However, in the SIMS docs, it shows antispam error routing in exactly
> the form you have specified above, so it should work.
The behavior is consistent, really. The error routing is an example of
foreign aliasing. What's special about it is that 'error' is treated
differently than 'normal' local accounts, and that it is intended to be
applied to return-paths rather than recipient addresses.
--
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]>
