* Christian Roessner <c...@roessner-network-solutions.com>: > >> I believe most of the functions are already in place, but the logic and > >> config > >> syntax isn't. In my eyes a structure as noted above would make > >> configuration a > >> lot easier. > > I agree. > > > > amavis is very powerfull. > > But finding the right configuration sytax is sometimes realy hard. > > Well, at the one side I wished it was easier sometimes, but at the other > side I have to say that the more I dive into amavisd the more I love exactly > the way it works. Maybe it is a big difference, if you also love > programming, which I do. So at the end I look into amavisd and the > RELEASE_NOTES and think everything is fine :-)
To me amavis is a programmers toolbox used for administrators. That makes it hard for non-programmers to deal with. > Concerning MTA and amavisd I think this is not so easy, because if using > Postfix, then it makes a difference, if you use smtpd_proxy_filter or > content_filter. It is the fact that the cleanup process is called in first > case after mail returns from amavisd, in second before _and_ after. And that > has consequences in amavisd, too. Because I have to specify different > forward_methods in amavisd. Aha... > I see everything as a big routing plan. I do routing of mails for my > intranet, for foreign remote networks and maybe trusted networks (also from > remote). I do define policies for all these and have full control. If you do that for one domain or domains where everything should be treated the same, you are fine. It becomes messy the moment you need to define different policies for different domains. Doable, but messy. > The only thing that I miss is a complete documentation of basic > configuration parameters. But I guess that makes a lot of work. I even > wouldn't know how to do the documentation structure. The more content is > added to the RELEASE_NOTES the more chance raises up that you miss reading > things and come up with unnecessary questions on the list. Not sure about > that. There are so many and so many old ones overridden by newer ones that got overridden by even newer ones... Like an onion. Its powerful because it is naked Perl. But then Perl is like bike-riding without chain protections. Cool, but it becomes a real mess once you get your pants into that chain... > Ah, finallly forgot one thing concerning policy_banks: If it would be able > to define a policy_bank that can be inherited in others that would be cool > :-) Are you aware amavis can stack policy banks? p...@rick -- All technical questions asked privately will be automatically answered on the list and archived for public access unless privacy is explicitely required and justified. saslfinger (debugging SMTP AUTH): <http://postfix.state-of-mind.de/patrick.koetter/saslfinger/> ------------------------------------------------------------------------------ Learn how Oracle Real Application Clusters (RAC) One Node allows customers to consolidate database storage, standardize their database environment, and, should the need arise, upgrade to a full multi-node Oracle RAC database without downtime or disruption http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user Please visit http://www.ijs.si/software/amavisd/ regularly For administrativa requests please send email to rainer at openantivirus dot org
