On Mon, 18 Nov 2002, Rich Lafferty wrote:
> It looks like you're getting caught by some slightly nonintuitive
> behavior in smtpfront's mailrules parsing.
Whether it's intuitive or not depends on how your intuition works :-)
> The mailrules docs note that
>
> Rules with a recipient pattern of * will be tested when the client
> transmits the sender address. Otherwise rules are be tested when the
> client transmits the recipient address.
>
> so a "*:*" rule will always deny everything, since sender address
> comes before recipient address(es) in the SMTP transaction. It's
> *very* specific about that:
>
> if (r->recipient.pattern.len == 1 && r->recipient.pattern.s[0] ==
> '*') {
> [ apply sender rule ]
> }
>
> In other words, there are "compare to sender" rules and "compare to
> recipient" rules, and the "*" recipient means that that rule is a
> "compare to sender" rule even if "compare to recipient" rules come
> before it in the file.
This actually makes sense if your goal is to reduce bandwidth as much as
possible. If this sender is not permitted to send to anyone, reject them
as soon as we know who they are, rather than waiting to find out who they
want to send mail to.
--
Charlie Brady [EMAIL PROTECTED]
Lead Product Developer
Network Server Solutions Group
Mitel Networks Corporation http://www.mitel.com/smallbusiness
Phone: +1 (613) 592 5660 or 592 2122 Fax: +1 (613) 592 1175
--
Please report bugs to [EMAIL PROTECTED]
Please mail [EMAIL PROTECTED] (only) to discuss security issues
Support for registered customers and partners to [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
