Re: filtering locally submitted emails / tidying up the config

On 02 May 2020, at 10:56, Patrick Proniewski wrote: > milter-greylist You might want to read the list archives for recent (last five years?) threads on greylisting. -- Well, if crime fighters fight crime and fire fighters fight fire, what do freedom fighters fight? They never

Re: filtering locally submitted emails / tidying up the config

Bob Proulx: > > but won't add: > > > > X-Spam-Score: -3.714 > > X-Spam-Flag: NO > > X-Spam-Level: > > X-Spam-Status: No, score=-3.714 tagged_above=-6 required=3 > > tests=[ALL_TRUSTED=-1, ... > > That milter configuration for SpamAssassin appears to have a problem > then. If

Re: filtering locally submitted emails / tidying up the config

Ok, my tests were not well done. I've re-tested and I see that everything is indeed correct. pure milter for amavisd-milter (no forwarding to after-queue smtp), and Amavisd tags are present in headers. My test messages were "too clean" and would not trigger insertion of X-Spam-* headers. My

Re: filtering locally submitted emails / tidying up the config

On 02 mai 2020, at 19:25, Matus UHLAR - fantomas wrote: > > On 02.05.20 17:46, Patrick Proniewski wrote: >> well in fact I've tried the default settings first ("client" as per >> ), >> the milter works as expected but

Re: filtering locally submitted emails / tidying up the config

Patrick Proniewski: It negates the benefit you were writing about as amavisd-milter will drop the message on the milter interface (postfix/cleanup[26401]: 87E5316135: milter-discard: END-OF-MESSAGE from localhost[127.0.0.1]: milter triggers DISCARD action) and re-inject it in an after-queue SMTP

Re: filtering locally submitted emails / tidying up the config

> On 02 mai 2020, at 18:09, Bob Proulx wrote: > >> Unfortunately I've discovered that Amavisd is unable to add headers >> I want as it would do as an smtp proxy filter. >> It will properly add: >> >> X-Virus-Scanned: my custom tag >> X-Crm114-Status: UNSURE ( 6.79 ) > > Those two

Re: filtering locally submitted emails / tidying up the config

Patrick Proniewski wrote: > In mean time I've changed my all setup to use only > milters (more readable config). Seems reasonable to me. > Unfortunately I've discovered that Amavisd is unable to add headers > I want as it would do as an smtp proxy filter. > It will properly add: > >

Re: filtering locally submitted emails / tidying up the config

On 02 mai 2020, at 15:13, Bastian Blank wrote: > > On Sat, May 02, 2020 at 11:40:52AM +0200, Patrick Proniewski wrote: >> It negates the benefit you were writing about as amavisd-milter will drop >> the message on the milter interface (postfix/cleanup[26401]: 87E5316135: >> milter-discard:

Re: filtering locally submitted emails / tidying up the config

On 02 mai 2020, at 14:19, Wietse Venema wrote: > > Patrick Proniewski: >> It negates the benefit you were writing about as amavisd-milter >> will drop the message on the milter interface (postfix/cleanup[26401]: >> 87E5316135: milter-discard: END-OF-MESSAGE from localhost[127.0.0.1]: >> milter

Re: filtering locally submitted emails / tidying up the config

On Sat, May 02, 2020 at 11:40:52AM +0200, Patrick Proniewski wrote: > It negates the benefit you were writing about as amavisd-milter will drop the > message on the milter interface (postfix/cleanup[26401]: 87E5316135: > milter-discard: END-OF-MESSAGE from localhost[127.0.0.1]: milter triggers

Re: filtering locally submitted emails / tidying up the config

Patrick Proniewski: > It negates the benefit you were writing about as amavisd-milter > will drop the message on the milter interface (postfix/cleanup[26401]: > 87E5316135: milter-discard: END-OF-MESSAGE from localhost[127.0.0.1]: > milter triggers DISCARD action) and re-inject it in an

Re: filtering locally submitted emails / tidying up the config

On 01 mai 2020, at 18:28, Wietse Venema wrote: >> >> would there be a performance/functionality penalty switching from >> smtpd_proxy_filter to smtpd_milters/non_smtpd_milters? > > It will be faster, because it avoids the need to deliver the whole > message outside of Postfix, and then to

Re: filtering locally submitted emails / tidying up the config

Patrick Proniewski: > Thanks Wietse, > > > On 01 mai 2020, at 15:37, Wietse Venema wrote: > > > > Patrick Proniewski: > >> I really feel like my setup needs some cleanup and I'm not sure were to > >> start. Some of you have suggested to me, in the past, that I could move to > >>

Re: filtering locally submitted emails / tidying up the config

Thanks Wietse, > On 01 mai 2020, at 15:37, Wietse Venema wrote: > > Patrick Proniewski: >> I really feel like my setup needs some cleanup and I'm not sure were to >> start. Some of you have suggested to me, in the past, that I could move to >> amavisd-milter instead of smtpd_proxy_filter for

Re: filtering locally submitted emails / tidying up the config

Patrick Proniewski: > I really feel like my setup needs some cleanup and I'm not sure were to > start. Some of you have suggested to me, in the past, that I could move to > amavisd-milter instead of smtpd_proxy_filter for antispam/antivirus > filtering. It might be the way but I don't know if

filtering locally submitted emails / tidying up the config

Hello, I've been using postfix with great success and delight for many years now, but my config has become quite messy over time, with additions like dkim/spf/dmarc and various filtering options. I'm currently having a problem with some locally generated emails (eg. sendmail command). I would