Jean-Christophe Boggio writes: > Le 23/01/2012 12:54, Sam Varshavchik wrote : > > That's what it always does. With a local recipient's address of "user- > extension", > > Courier will deliver to ~user/.courier-extension, and fail with "No such > recipient" > > otherwise (if no other alternative delivery destination, like .courier- > default, and a few others, exist). > > Yes I know but I don't see the connection between "john" and "mylist".
There's really nothing here to see. After installing a $HOME/.courier- extension, no further action is required. Courier does not need to be "told" that you did that. Each time it gets an address of the form user-extension, it checks if $HOME/.courie-extension exists, automatically, and if so it accepts the receipient's address, otherwise it's rejected as unknown. Here, $HOME/.courier-extension gets installed as part of couriermlm, but that's irrelevant. > In aliases definitions, if I declare : > mary: john > Courier will deliver the mail to john-mary No – this is a simple alias, to "m...@example.com" gets delivered to "j...@example.com". > If I declare : > @virtualdomain.com: john > Courier will deliver <originalrecipient>@virtualdomain.com to john- > <originalrecipient> > > But this is stored in /etc/courier/aliases/* and "compiled" by makealiases > in /etc/courier/aliases.dat Sort of, but yes. > I wonder where courier stores the "uncompiled" form that connects > myl...@mydomain.com to /home/john/mylist > when I create the list with couriermlm create /home/john/mylist > ADDRESS=myl...@mydomain.com Some other steps must be taken for that. couriermlm, by itself, wouldn't create a deliverable mail address. If you use that in conjunction with a virtual domain definition of "@mydomain.com: john", then the email address of "l...@mydomain.com" becomes "john-list", at which point the regular mail delivery rules apply: if john's $HOME/.courier-list exists, mail gets delivered there. If that .courier file happens to execute couriermlm, then so be it. The connection here, if any, is that the virtual domain's rewriting rules happen to produce a rewritten name that's consistent with the naming convention for local mail delivery rules. > Put the other way round, if I decide to change the list's "owner" from > "john" to "paul" > where/how do I have to make the change (apart from moving all .courier- > mylist* files from > /home/john to /home/paul) ? If you change the virtual domain alias, move all the files, change the userid and groupid that owns the .courier file, and the couriermlm directory, then no further action is necessary. ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
