Patrick, > > As far as amavisd is concerned, you may increase $logline_maxlen > > arbirtarily. What happens with long log lines then depends on your > > syslog. The default maxlen just fits a standard syslog syscall with its > > syslogd daemon that comes with FreeBSD systems (and likely others). > > Check your logging daemon to see what are its limits. > > Thanks Mark. In our case rsyslog provides a setting ($MaxMessageSize) that > corresponds to amavis' $logline_maxlen. We bumped both parameters up to a > size that gives us what we need.
Good. Just make sure to test it with long lines (try setting $log_template to a long string). There are some intermediate layers (like the: perl module Unix::Syslog, SYSLOG(3) service, UDP protocol, and the logging daemon at the end), each of these may impose its restrictions. > Performancewise it seems to be better to have amavis send one line instead > of the log file analyzer splice the lines back. But that's "seems". I am > not the one working on this part of the project. Sure. Just make sure it works as expected. Programs can be made arbitrarily fast if correctness is not required. Mark ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ AMaViS-user mailing list [email protected] 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
