On Thursday 14,April,2011 03:56 AM, Sam Varshavchik wrote: > But, aside from that, Courier creates separate connections for different > domains, without considering esmtproutes. If the mail queue does contain > multiple messages for the same domain, and they're scheduled to be > delivered, Courier will reuse an existing connection to the recipient's > domain, if it's available.
Several years ago I wrote a patch to "batch" all the messages through a smarthost. So you end up with one connection to the smarthost instead of one per email domain. You can find the patch here: http://phantom.dragonsdawn.net/~gordon/courier-patches/batch-through-smarthost.patch I haven't used it in years because I don't need it anymore. I don't even know if it will apply cleanly to the code today. But as you can see from the patch, it's pretty easy to do. The only problem with this approach is you incur the overhead of an second lookup in the esmtproutes file for each message. Jeff Jansen ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
