Re: [cobalt-users] raq3 catch-all alias problems (& solution)

[Chris Adams <cmadams@xxxxxxxxxx>]

Once upon a time, Jeff Lasman <jblists@xxxxxxxxxxxxx> said:
> At 02:41 PM 2/16/00 -0600, you wrote:
> >Second, sendmail's search rules go like this (in order):
> >
> >1) If you have user@xxxxxxxxxx and domain.com is in the list of virtual
> >domains, then lookup user@xxxxxxxxxxx  If you get a match, you are done.
> >2) If you have user+extra@xxxxxxxxxx, lookup user+*@domain.com.  If you
> >get a match, you are done.
> >3) If you have user+extra@xxxxxxxxxx, lookup user@xxxxxxxxxxx  If you
> >get a match, you are done.
> >4) If you have user@xxxxxxxxxx, lookup @domain.com, possibly replacing a
> >"%1" in the result with the original user.  If you get a match, you are
> >done.
> 
> I believe this, but I've never been able to find it.  I've always used 
> "sendmail", the O'Reilly book, as Sendmail documentation.  After all, it's 
> written by the same man who wrote the software.

Well, he helped (Brian Costales wrote the book, but he asked Eric Allman
lots of questions :-) ).

> Note that it all I've been able to find about FEATURE(virtusertable) is on 
> page 274, and it does NOT say all this.  However, I agree that it IS how it 
> seems to work.

If you can read sendmail rules, see lines 633-638 in /etc/sendmail.cf,
part of the Parse1 (aka 198) ruleset.

> >This set of rules is run repeatedly until none of the rules match.
> >Rules 2 and 3 let you have "extra" stuff on the user part of an address
> >and just strip it off to look up the virtual user entry.  After that, if
> >user exists as a local user on the RaQ (even if they are not part of
> >domain.com), the email would be delivered to them.
> >
> >The way Cobalt sets things up, virtual users are always setup only for
> >@host.domain.com, not plain @domain.com.  If you check the "Accept email
> >for domain" box, then a special entry like:
> >
> >@domain.com %1@xxxxxxxxxxxxxxx
> 
> This appears to automatically happen on the RaQ2; I don't remember setting 
> up anything for it.

It happens if you check the "Accept email for domain" box (on both the
RaQ2 and RaQ3).
-- 
Chris Adams <cmadams@xxxxxxxxxx>
Systems and Network Administrator - HiWAAY Information Services
I don't speak for anybody but myself - that's enough trouble.