Alexei Batyr' writes:
> Let's look at practical example: in my installation there is approx. 10
> local domains for different publications of our publishing house. All users
> are real mail server users. Some of them work for several magazines, so they
> want messages addressed to, e.g., [EMAIL PROTECTED], [EMAIL PROTECTED] and [EMAIL PROTECTED] to
> go to the same mailbox. That's why I'm using "unidomain" scheme, where all
> hosted domains are local and everybody can use any domain part of his
> address.
And that's the broken part. You _should_ be using hosteddomains here, and
use aliases for the shared accounts.
> |case "${HOST}" in \
> "pcmag.ru") sendmail -t -f "$SENDER" user1 ;; \
> "crn.ru") sendmail -t -f "$SENDER" user2 ;; \
> ...
> *) sendmail -t -f "$SENDER" userX ;; \
> esac
>
> Not very simple and straightforward, isn't it?
Of course not. Aliases -- when properly implemented -- are much simpler.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
