Heinz Ulrich Stille wrote: > My only (small) gripe against dspam is that it insists on delivering > one message to each receiver separately (via LMTP) instead of handing > it over to the next filter step "as is".
It depends on the parameters used to call DSPAM. If you are using --stdout, DSPAM won't deliver anything but prints the message to stdout. > Which gets me back to the original question of integrating dspam into > amavisd: Don't - I at least prefer to know what dspam is doing, so I > run it as a separate LMTP server. For developers there is another option: Use my experimental DSPAM patches for amavisd-new. With these, you can DSPAM and disable SpamAssassin in amavisd-new. It uses the stdout option so no delivery "under the hood" will happen. But beware: there are some bugs left in, the current implementation is only alpha and multiple recipients with different DSPAM profiles (which requires multiple messages for the output) are not implemented yet. fs ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
