--- Jared Watkins <[EMAIL PROTECTED]> wrote:
> email builder wrote: > > >>RR > >>lookups in postfix's content_filter. Works fine, kind of.... The amavis > >>servers are used in clumps a few minutes at a time. Turns out, as I was > >>just > >>told on the postfix list, the postfix LMTP client caches its connections, > >>thus negating the whole purpose of having more than one amavis server. > >> > >> I see other people who have tried to do this same thing, but no mention > >>of > >>this issue in the archives (of either list) that I could find. Can > anyone > >>give a pointer? > >> > >> > > > >Update: seems to be that the LMTP client does not shuffle multple response > >records from its lookups, and dnscache, which is what we use for our name > >resolution, seems to shuffle "once in a while" (odd...). So seems that we > >have to consider finding the patch for dnscache that adds round robin > >functionality (that seems to have gone missing from the link on > tinydns.org) > >or use SMTP to connect to amavis instead of LMTP (SMTP client apparently > will > >shuffle the records). > > > >Everyone seems to use LMTP to connect to amavis, but is there a good > reason > >for this? > > > Just as a point of comparison... I have my relays sitting behind an LVS > load balancer with postfix and amavis/clam on each. This way.. I can > positively control how much load each one receives.. and when I need to > do maintenance I can remove one from the pool... then add it back > later. I have a script that polls my ldap server once an hour and > pushes static virtual alias maps and other files config for > postfix/amavis/clam out to each of the relay systems. I also use my own > plugin for squirrelmail (amavisnewsql) to keep all my per user settings > and message quarantines in a shared postgres server. We have our SMTP servers behind LVS too, but (unless I misunderstand you), that means one amavis server gets EVERYTHING that any one SMTP server gets. Usually, that should be A.O.K., however, we want to balance amavis itself, which adds a tiny bit of redundancy, albiet possibly not much (oh, and our architecture is such that the MTAs and amavis servers aren't even on the same machines anyway). Using LVS to balance stuff on the internal eth interface seems like way more trouble than we want to go to, so we are settling on DNS-based balancing, which seems best done if you use smtp between amavis/postfix apparently. Thank you! __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
