--Edwin Culp wrote on 22.02.2002 08:10 -0800: > Thanks, Roland. This is great. You've given us several different > solutions to test.
Caveats with maildrop/xfilter: a) xfilter can be a real cpu-hog and kill your server. dcc-client and anomy piped though xfilter, concurrent incoming connections and local delivery set both to 4 (only!) caused an average load of >8 for some time on my old p200/scsi testbox while processing ~1000 incoming bounces with 2..3k each. b) the filter get executed _after_ the message has been received and acknowledged. Bounce after accepting the message is the worst one can do and will actually increase the spamload. Filters at this stage may only add headers or deliver identified spew to /dev/null. The same for filters in .courier-dotfiles. The daemonized localfilter/perlfilter will be invoked before any mail is accepted, but cant add/change headers on the fly (yet...) Roland _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
