Re: Use X-Amavis-Alert header to influence Spam Assassin Scoring

I think that re-factoring amavis into smaller chunks so that spamassassin can «use» those modules will reduce the duplicated code, if not the duplicated effort. What is the benefit of having all of the 71 packages in the same file? This will make it difficult to write and exercise unit tests. If

Re: Use X-Amavis-Alert header to influence Spam Assassin Scoring

On 7 Mar 2016, at 12:13, Josh Hamell wrote: > > Amavis headers are injected in immediately before delivery, and > therefore aren't available for SA to analyze. This is my understanding, amavis headers aren't there until after SA -- This is my signature. There are many like

Use X-Amavis-Alert header to influence Spam Assassin Scoring

Hi, There was a similar post here in 2014: > http://lists.amavis.org/pipermail/amavis-users/2014-September/003143.html Basic request: * For banned attachments, we strip attachments + PASS (and rewrite header/inject disclaimer) * Vast, vast majority of this is unsolicited email * I would like