Re: Upcoming Release: feature Request

2016-02-18 Thread Mark Martinec
Mark Martinec: AuthServID by itself is not good enough, such header field must also belong to a set of trusted fields. SpamAssassin solves the problem of determining which header fields can be trusted by settings trusted_networks / internal_networks / msa_networks. Patrick Ben Koetter: How wou

Re: Upcoming Release: feature Request

2016-02-17 Thread A. Schulze
Mark Martinec: AuthServID by itself is not good enough don't agree... A-R header are defined by RFC7001 there is also a section about "Remove Existing Header Fields": http://tools.ietf.org/html/rfc7001#section-5 replace "conforming MTA" by "conforming MILTER" while reading :-) Andreas

Re: Upcoming Release: feature Request

2016-02-16 Thread Patrick Ben Koetter
* Mark Martinec : > >@lbutlr: > >>How does amavis know if you removed the spammer headers and > >>added your own? > > Andreas Schulze wrote: > >It has to trust the administrator does a good job :-) > > > >Each A-R header include an AuthServID (a hostname generating the > >A-R header) > >Any A-R he

Re: Upcoming Release: feature Request

2016-02-16 Thread Mark Martinec
@lbutlr: How does amavis know if you removed the spammer headers and added your own? Andreas Schulze wrote: It has to trust the administrator does a good job :-) Each A-R header include an AuthServID (a hostname generating the A-R header) Any A-R header consumer must know these "TrustedAuth

Re: Upcoming Release: feature Request

2016-02-16 Thread A. Schulze
@lbutlr: How does amavis know if you removed the spammer headers and added your own? It has to trust the administrator does a good job :-) Each A-R header include an AuthServID (a hostname generating the A-R header) Any A-R header consumer must know these "TrustedAuthServIDs" and trust thes

Re: Upcoming Release: feature Request

2016-02-16 Thread @lbutlr
On Feb 16, 2016, at 3:31 AM, Patrick Ben Koetter wrote: > * @lbutlr : >> On Feb 15, 2016, at 1:53 PM, A. Schulze wrote: >>> Feature Request: Amavisd-new should recognise A-R header and use/trust them. >>> Assumption: the A-R header aren't present in an incoming message but really >>> added by a

Re: Upcoming Release: feature Request

2016-02-16 Thread Patrick Ben Koetter
* @lbutlr : > On Feb 15, 2016, at 1:53 PM, A. Schulze wrote: > > Feature Request: Amavisd-new should recognise A-R header and use/trust them. > > Assumption: the A-R header aren't present in an incoming message but really > > added by a local milter. > > How would amavis know if the headers were

Re: Upcoming Release: feature Request

2016-02-16 Thread @lbutlr
On Feb 15, 2016, at 1:53 PM, A. Schulze wrote: > Feature Request: Amavisd-new should recognise A-R header and use/trust them. > Assumption: the A-R header aren't present in an incoming message but really > added by a local milter. How would amavis know if the headers were added by the local serv

Re: Upcoming Release: feature Request

2016-02-15 Thread Patrick Ben Koetter
* A. Schulze : > > Hello Mark, > > I'm a little uncomfortable with the DKIM check implemented in amavis. > For unrelated reasons we use an spf-milter and opendkim-milter in > front of amavisd-milter. > > So in the moment amavisd-milter get the message there are already > two A-R Header present.

Upcoming Release: feature Request

2016-02-15 Thread A. Schulze
Hello Mark, I'm a little uncomfortable with the DKIM check implemented in amavis. For unrelated reasons we use an spf-milter and opendkim-milter in front of amavisd-milter. So in the moment amavisd-milter get the message there are already two A-R Header present. Unfortunately amavisd-new c