Dear Mark, The thing is, that we have a big farm of amavisd-new machines connected by CARP in one AV/AS cluster (about 30 boxes, and growing), and it serves for many, many smtp boxes. With this patch we found it very useful and easy to manage what does amavisd-new do with the mail received from particular server. For example, there are group of servers, which mail messages should be delivered by other group of servers (due to postfix unability to use procmail as delivery agent for virtual users). Also, there are group of servers (CARP`ed too) that need to get their mail back, to send it away. All this, with mixtures of some other smaller issues made us to write this patch, so we could do all of this in very easy and very clean way.
Now, is there any chance to see this functionality in amavisd-new official release, or not? Maybe, if the code quality doesent satisfy you, we could fix any issues you see? And if the code is OK, then why to not add such functionality? Kind regards, Bartek Rutkowski > > I can see what the patch does, but what is the underlying problem > it is trying to solve? > > I see two issues there: > > - any sending host can let his HELO command show any string he wants, > so any decision based on such information must not have any important > consequence; load balancing and logging could perhaps be a valid reason, > but more than that certainy not; > > - if there are not too many different relay destinations (like > [10.10.3.13]:10025 in your example), the same effect can be achieved > by Postfix check_helo_access, which can map HELO names to FILTER > settings, where each distinct FILTER can route mail to a dedicated > TCP port of amavisd, where policy banks can take care of each > individual forwarding destination. Letting Net::Server listen > on a couple of TCP ports (a dozen or two) should not represent > any additional burden. > > See Example 3 at: > http://www.ijs.si/software/amavisd/amavisd-new-docs.html#pbanks-ex > > Mark > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > 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/ -- Bartłomiej Rutkowski <[EMAIL PROTECTED]> ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ 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/
