On Thu, 13 Jul 2017, Marc Haber wrote: > On Wed, Jul 12, 2017 at 10:59:22PM +0200, Alexander Wirt wrote: > > On Sun, 04 Jan 2015, Andreas Metzler wrote: > > > On 2015-01-04 Rainer Dorsch <m...@bokomoko.de> wrote: > > > > Package: exim4 > > > > Version: 4.84-6 > > > > Severity: wishlist > > > > Tags: patch > > > > > > > Dear Maintainer, > > > > > > > I am running exim since a few years and scanned incoming and > > > > outgoing mails for spam, where outgoing does not make a lot of sense > > > > or even hurts. > > > [...] > > > > > > I tend to disagree here. - Scanning outgoing mails to avoid spreading > > > viruses sent by infectected users makes sense. > > jftr, it dies hurt to add the spamassassin report to outgoing mails. Those > > mails does are rfc2822 conform any more. Debian listserver will discard such > > mails. SA Report should not get added to mail leaving the server. > > In which point does the adding of X-Headers violate RFC822? > > Additionally, the patch given in this bug report will not help in the > case where a message is accepted by exim as a relay from a permitted IP > range as it will only exempt authenticated mail. > > So, the question is, how do we determine that a message is "outgoing" > not from exim's point of view, but from the _site's_ point of view. > > In addition, the headers in question seem to be added by Amavis, not by > exim, right? I am talking about the report: X-Amavis-Alert: BAD HEADER SECTION, Improper folded header field made up entirely of whitespace (char 20 hex): X-Spam_report: ...T_ADDRESS@@ for details. Content previ[...]
This does not belong to outgoing mail. Alex
