mouss, > I suggest having a config parameter that allows using the "current" mode > or the following new mode: > - keep SA headers untouched > - add X-Amavisd-* headers > > People who activate the latter mode would need to addapt their delievry > config/scripts to use these headers (This is why a config param to > enable this mode is needed). > This way, if people configure new headers in their SA config, they will > get them.
Fetching headers or changed mail as prepared by SpamAssassin would involve two actions: SA needs to be told to prepare a rewritten message (currently this step is skipped, saving SA the work), and the prepared rewrite would need to be parsed in order to extract changes (in a milter setup for example only header edits and additions are fed to MTA, not a complete mail). On top of it, SA is called by amavisd only once per message, but mail header modification controls apply per-recipient, so amavisd needs to do its own header editing. I know it would be useful for some purposes to use the modified mail as prepared by SA, but this is quite impractical the way it works now. If one needs such functionality badly, spam checking from amavisd-new should be turned off and spamc/spamd invoked at a later stage. Mark ------------------------------------------------------------------------- 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 [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/
