Sam Varshavchik wrote: > Alessandro Vesely writes: >> sensible information, coordinating mail filters, et cetera. Besides >> properly setting the Return-Path, a policy might need to mandate a >> specific outgoing IP, a smart relay, some kind of authorization token, >> or other features. >> >> Would it be worth to plan such a general solution for Courier? > > That's what maildrop is for. Once a decision is made to forward mail, > there's no substantial difference between what maildrop does and what > Courier does. Courier invokes submit, while maildrop invokes sendmail > which invokes submit.
I guess you're right. I shall get rid of naive .courier forwarding and reserve .courier files for very specific tasks, such as, e.g., mailing lists. (A mailing list _is a_ type of forwarding.) BTW, sendmail is invoked through a maildrop variable, which provides an additional way for setting up whatever policy, orthogonally across all forwarding recipes, except .courier driven ones. Thank you for the tip ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
