|
From: Bart Schaefer <barton.schaefer <at> gmail.com>
Subject: Re: Procmail not checking all the rules in .procmailrc Newsgroups: gmane.mail.procmail Date: 2004-12-11 23:03:12 GMT (3 years, 31 weeks, 2 days, 17 hours and 53 minutes ago) On Fri, 10 Dec 2004 17:54:13 +0000, NM Public <agorae <at> nm.deflexion.com> wrote: > > Important Warning: Procmail Cannot Reliably Route Users' > Messages in a Virtual Domain > <http://www.ii.com/internet/robots/procmail/qs/#virtualDomain> I hadn't really paid much attention to this before, but I think there's a small problem with terminology there. What this really refers to is not a true "virtual domain" but a local mail system implemented on the downstream side of a single drop box at the provider, e.g., where something like fetchmail picks up all the mail using something akin to POP3, and then attempts to figure out how to route it based on what's left of the envelope in the header. If instead the MTA at the provider is configured to invoke procmail with the -m option, as the "Mprocmail" mailer entry for sendmail does, then procmail DOES have all the necessary sender and recipient information and CAN reliably route users's messages within the (much closer to a true) virtual domain. This could even be combined with the dropbox case, i.e., have procmail at the provider insert the special header information that's recognized by the downstream procmail for local routing. That would, however, mean the dropbox would get one copy of the mail for every downstream recipient rather than one copy for all downstream recipients, so quotas or the bandwidth across POP3 (or whatever it is) might become an issue. |
|
|