Bug#320316: amavis-ng-milter-helper security issues

2005-07-28 Thread Don Armstrong
severity 320316 wishlist retitle 320316 Add option to not rewrite bugs that are bounced to the -B address tag 320316 -moreinfo thanks On Fri, 29 Jul 2005, Evan Harris wrote: > Since the mail is bounced with the -r 7 option, the spamkeeper > address is the only one that gets it, and is also exactly

Bug#320316: amavis-ng-milter-helper security issues

2005-07-28 Thread Evan Harris
Since the mail is bounced with the -r 7 option, the spamkeeper address is the only one that gets it, and is also exactly the one that I want not to be marked up. If there were another way to keep a copy of the message for later analysis while still bouncing it at the MTA level, that would be fine

Bug#320316: amavis-ng-milter-helper security issues

2005-07-28 Thread Don Armstrong
On Thu, 28 Jul 2005, Evan Harris wrote: > /etc/default/spamass-milter: > > OPTIONS="-i 127.0.0.1 -r 7 -m -B spamkeeper -- -u amavis" What you're showing below is a message sent to the spamkeeper address, which gets the output of spamassassin, not what is actually sent through the system. The -m a

Bug#320316: amavis-ng-milter-helper security issues

2005-07-28 Thread Evan Harris
> The -m just disables changes to Subject: Content-Type: and the body of > the message. That's it. It'll still add the various X-Spam headers. I realize that, the problem is it is still doing the body mods. The subject mods and Content-Type are both disabled globally, and appear to be working pr

Bug#320316: amavis-ng-milter-helper security issues

2005-07-28 Thread Don Armstrong
tag 320316 moreinfo thanks On Thu, 28 Jul 2005, Evan Harris wrote: > When using -m to prevent modification of the message, this setting > appears to be ignored. Markup still happens, unless the default > spamassassin prefs disable it. Unfortunately, I do not want to > disable it for local users, j

Bug#320316: amavis-ng-milter-helper security issues

2005-07-28 Thread Evan Harris
Package: spamass-milter Version: 0.3.0-1 When using -m to prevent modification of the message, this setting appears to be ignored. Markup still happens, unless the default spamassassin prefs disable it. Unfortunately, I do not want to disable it for local users, just for mail that may be "passi