Re: [courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
On Mon, Sep 29, 2003 at 06:22:56PM -0400, Sam Varshavchik wrote: Courier User writes: Assume that I have an email user on my system whose address is [EMAIL PROTECTED] I know I can use .courier and .courier-default in that user's HOME directory to control the delivery of email not only to [EMAIL PROTECTED], but also to all possible variants of the following form: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc. But as a sysadmin, I would like to control this outside of the users' HOME directories, so that I can force certain mail processing for all users. Is there any way to configure Courier so that all these random variant addresses can be handled for each given user without the use of ~/.courier, ~/.courier-default, and their cousins? You can create a script that creates a soft link from every account's .courier-foo file to a global default file. What about creating a .courier-default file specifying maildrop as MDA and having a centralized maildroprc in /etc/courier/maildroprc? Sth. like: --- SHELL=/bin/ash DEFAULT=./Maildir ALL_LIST=$DEFAULT.MessagesForAll if (/^To:[EMAIL PROTECTED]/) to $ALL_LIST/ to $DEFAULT --- Regards Mirko --- 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
Re: [courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
On Mon, Sep 29, 2003 at 06:22:56PM -0400, Sam Varshavchik wrote: Courier User writes: Assume that I have an email user on my system whose address is [EMAIL PROTECTED] I know I can use .courier and .courier-default in that user's HOME directory to control the delivery of email not only to [EMAIL PROTECTED], but also to all possible variants of the following form: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc. But as a sysadmin, I would like to control this outside of the users' HOME directories, so that I can force certain mail processing for all users. Is there any way to configure Courier so that all these random variant addresses can be handled for each given user without the use of ~/.courier, ~/.courier-default, and their cousins? You can create a script that creates a soft link from every account's .courier-foo file to a global default file. Yes, I know I can do that, but I was hoping that I didn't have to. Oh well ... -- Courier User [EMAIL PROTECTED] --- 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
Re: [courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
On Tue, Sep 30, 2003 at 08:40:20AM +0200, Mirko Zeibig wrote: On Mon, Sep 29, 2003 at 06:22:56PM -0400, Sam Varshavchik wrote: Courier User writes: [ ... ] But as a sysadmin, I would like to control this outside of the users' HOME directories, so that I can force certain mail processing for all users. Is there any way to configure Courier so that all these random variant addresses can be handled for each given user without the use of ~/.courier, ~/.courier-default, and their cousins? You can create a script that creates a soft link from every account's .courier-foo file to a global default file. What about creating a .courier-default file specifying maildrop as MDA and having a centralized maildroprc in /etc/courier/maildroprc? Thank you. Where would this .courier-default file reside? Would it be a soft link from every account's HOME directory to a central location? If so, I already have something like this in place. I'm trying to avoid putting all those links in the users' HOME directories, if at all possible. Sth. like: --- SHELL=/bin/ash DEFAULT=./Maildir ALL_LIST=$DEFAULT.MessagesForAll if (/^To:[EMAIL PROTECTED]/) to $ALL_LIST/ to $DEFAULT -- Courier User [EMAIL PROTECTED] --- 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
Re: [courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
On Tue, Sep 30, 2003 at 05:22:51AM -0400, Courier User wrote: On Mon, Sep 29, 2003 at 06:22:56PM -0400, Sam Varshavchik wrote: Courier User writes: Assume that I have an email user on my system whose address is [EMAIL PROTECTED] I know I can use .courier and .courier-default in that user's HOME directory to control the delivery of email not only to [EMAIL PROTECTED], but also to all possible variants of the following form: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc. But as a sysadmin, I would like to control this outside of the users' HOME directories, so that I can force certain mail processing for all users. Is there any way to configure Courier so that all these random variant addresses can be handled for each given user without the use of ~/.courier, ~/.courier-default, and their cousins? You can create a script that creates a soft link from every account's .courier-foo file to a global default file. I thought of another possibility, but it didn't work for me. I created this file and put delivery instructions in it: COURIERHOME/etc/aliasdir/[EMAIL PROTECTED]:com I ran makealiases, and I even restarted Courier, but addresses of the following forms did not get recognized: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc. What did I do wrong? -- Courier User [EMAIL PROTECTED] --- 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
[courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
Courier User writes: On Tue, Sep 30, 2003 at 05:22:51AM -0400, Courier User wrote: On Mon, Sep 29, 2003 at 06:22:56PM -0400, Sam Varshavchik wrote: Courier User writes: Assume that I have an email user on my system whose address is [EMAIL PROTECTED] I know I can use .courier and .courier-default in that user's HOME directory to control the delivery of email not only to [EMAIL PROTECTED], but also to all possible variants of the following form: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc. But as a sysadmin, I would like to control this outside of the users' HOME directories, so that I can force certain mail processing for all users. Is there any way to configure Courier so that all these random variant addresses can be handled for each given user without the use of ~/.courier, ~/.courier-default, and their cousins? You can create a script that creates a soft link from every account's .courier-foo file to a global default file. I thought of another possibility, but it didn't work for me. I created this file and put delivery instructions in it: COURIERHOME/etc/aliasdir/[EMAIL PROTECTED]:com I ran makealiases, and I even restarted Courier, but addresses of the following forms did not get recognized: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc. What did I do wrong? An aliasdir/[EMAIL PROTECTED]:com would only be in play for a literal address [EMAIL PROTECTED]. pgp0.pgp Description: PGP signature
Re: [courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
Courier User wrote: On Tue, Sep 30, 2003 at 08:40:20AM +0200, Mirko Zeibig wrote: What about creating a .courier-default file specifying maildrop as MDA and having a centralized maildroprc in /etc/courier/maildroprc? Where would this .courier-default file reside? Would it be a soft link from every account's HOME directory to a central location? If so, I already have something like this in place. I'm trying to avoid putting all those links in the users' HOME directories, if at all possible. If you want to use maildrop as the delivery agent, change the setting for DEFAULTDELIVERY in /etc/courier/courierd. --- 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
Re: [courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
On Tue, Sep 30, 2003 at 07:14:32AM -0700, Gordon Messmer wrote: Courier User wrote: On Tue, Sep 30, 2003 at 08:40:20AM +0200, Mirko Zeibig wrote: What about creating a .courier-default file specifying maildrop as MDA and having a centralized maildroprc in /etc/courier/maildroprc? Where would this .courier-default file reside? Would it be a soft link from every account's HOME directory to a central location? If so, I already have something like this in place. I'm trying to avoid putting all those links in the users' HOME directories, if at all possible. If you want to use maildrop as the delivery agent, change the setting for DEFAULTDELIVERY in /etc/courier/courierd. I already have DEFAULTDELIVERY set exactly in that manner. The problem is that I need to accept mail not only for [EMAIL PROTECTED], but also, for [EMAIL PROTECTED]. In order to do that, I need to put .courier-default into the HOME directory for user, and as far as I know, if [EMAIL PROTECTED] is to be processed in exactly the same manner as [EMAIL PROTECTED], .courier-default must contain the following line: |preline maildrop I know that I can have a central version of .courier-default and then have a symbolic link for this in each user's HOME directory, but the purpose of my starting this thread is to ask if there's a way to allow [EMAIL PROTECTED] to be handled the same as [EMAIL PROTECTED] _without_ having to create these links in each and every HOME directory. -- Courier User [EMAIL PROTECTED] --- 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
Re: [courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
Courier User wrote: On Tue, Sep 30, 2003 at 07:14:32AM -0700, Gordon Messmer wrote: If you want to use maildrop as the delivery agent, change the setting for DEFAULTDELIVERY in /etc/courier/courierd. I already have DEFAULTDELIVERY set exactly in that manner. The problem is that I need to accept mail not only for [EMAIL PROTECTED], but also, for [EMAIL PROTECTED]. I keep telling myself to stop answering email in the morning... --- 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
[courier-users] Re: To user@domain.com and user-whatever@domain.com without dot-courier?
Courier User writes: Assume that I have an email user on my system whose address is [EMAIL PROTECTED] I know I can use .courier and .courier-default in that user's HOME directory to control the delivery of email not only to [EMAIL PROTECTED], but also to all possible variants of the following form: [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] etc. But as a sysadmin, I would like to control this outside of the users' HOME directories, so that I can force certain mail processing for all users. Is there any way to configure Courier so that all these random variant addresses can be handled for each given user without the use of ~/.courier, ~/.courier-default, and their cousins? You can create a script that creates a soft link from every account's .courier-foo file to a global default file. pgp0.pgp Description: PGP signature
