On Thursday, October 03, 2002 7:10 PM, Bill Michell wrote:
> Alexei Batyr' writes:
>
>> On Thursday, October 03, 2002 4:48 PM, Bill Michell wrote:
>>
>>> Currently, for domains listed in locals, you *never* append the
>>> domain, for all other domains, you *always* append it. Simple.
>>
>> Simple idea: strip local domain part _after_ looking up alias
>> database instead of doing it _before_.
> But why?
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.
However in some cases I need to make difference between domains, e.g. alias
"news" should exist for all my domains but messages to [EMAIL PROTECTED] and
[EMAIL PROTECTED] should be redirected to the different real mailboxes. Now
instead of simply using alias database entries
[EMAIL PROTECTED]: user1
[EMAIL PROTECTED]: user2
...
I need to use following sysconfdir/aliasdir/courier-news file:
|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?
--
Alexei.
-------------------------------------------------------
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
