Bowie Bailey wrote: > Jay Lee wrote: >> > Is this functionally any different from an alias? (besides using >> > maildrop for forwarding) >> >> Technically yes since Courier accepts the message and starts delivery >> instructions instead of just re-queueing it to the alias. So for >> instance, if he runs spam filtering via a maildrop call to spamc, he >> could just put this code underneath the spamc call and his user's >> spam filters would stay in place. > > Well, that's what I meant by "besides using maildrop". Maildrop gives > you some flexibility to do other operations before forwarding, but if > all you want to do is send the mail along to another server, the end > result is exactly the same.
Hm... in one case you get one more Received/Delivered-To pair. And what about the envelope sender? In general, maildrop allows to plug any forwarding policy that may be relevant, e.g. spam-filter before forwarding, required DNSBLs, SPF checks, et cetera. See also: "Looped DSNs when empty sender and broken user's forward" Fri, 04 Jul 2008 15:23:58 -0700 http://www.mail-archive.com/[email protected]/msg31988.html Apparently, those issues are less relevant when configuring two or more synchronized servers, e.g. using courierldapaliasd and IMAP/POP3 aggregator proxy. In such cases, any "forwarding" should probably be considered just a delivery mechanism. However, I'm not sure what happens if a message forwarded to multiple users hits quota limits for just some of the recipients. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
