On Fri, 15 Nov 2019 at 21:17, Kevin A. McGrail wrote:
> Good idea. This is done.
>
> On 11/15/2019 11:49 AM, David Jones wrote:
> > Perhaps it needs to be named KAM_DMARC_REJECT to make it obvious that it
> > came from the KAM.cf and have a default score of 0.001?
>
I believe only the renaming
On Nov 15, 2019, at 4:35 PM, RW wrote:
>
> DKIM_VALID_AU is too strict for DMARC as it requires strict alignment.
Indeed, although I wonder if DKIM_VALID_AU is itself too strict? In
particular, one sender that triggers this issue is coming from a .gov 3rd-level
subdomain where the valid DKIM
On 2019-11-16 00:35, RW wrote:
meta DMARC_REJECT !(DKIM_VALID_AU || SPF_PASS) && __DMARC_POLICY_REJECT
this is when not aligned and domain owner want to reject
adding another meta with MAILING_LIST_MULTI included does not harm imho
On Fri, 15 Nov 2019 10:02:48 -0700
Amir Caspi wrote:
> On Nov 15, 2019, at 9:50 AM, David Jones wrote:
> >
> > If SA is being run post MTA (i.e. inside Thunderbird) then any
> > filtering can change the content to remove potentially bad
> > attachments, add an "EXTERNAL" warning to the Subject o
Good idea. This is done.
On 11/15/2019 11:49 AM, David Jones wrote:
> Perhaps it needs to be named KAM_DMARC_REJECT to make it obvious that it
> came from the KAM.cf and have a default score of 0.001?
--
Kevin A. McGrail
kmcgr...@apache.org
Member, Apache Software Foundation
Chair Emeritus Ap
On Nov 15, 2019, at 9:50 AM, David Jones wrote:
>
> If SA is being run post MTA (i.e. inside Thunderbird) then any filtering
> can change the content to remove potentially bad attachments, add an
> "EXTERNAL" warning to the Subject or body, etc. which will break DKIM
> signing.
I believe this
On 11/15/19 12:35 AM, Kevin A. McGrail wrote:
> The DMARC Reject rule is about whether a domain has failed DKIM and has
> a DMARC reject policy. I will add descriptions to these rules ASAP.
> Thanks.
>
> We have encapsulated the rules in a check for DKIM and SPF.
>
> Best to report issues with K
On 11/15/19 1:02 AM, Kevin A. McGrail wrote:
>
>> how more longer will it take to make 3.4.3 realease by looking ? :=)
>
> Right now, I'm working through bugs found by myself and my staff to make
> sure the release is up to snuff.
>
> The biggest delay is a lack of feedback and testing. Please
If you don't want to hit it at all for some recipient, you can try
redefining the whole UNWANTED_LANGUAGE_BODY rule into a meta.
body __UNWANTED_LANGUAGE_BODY eval:check_language()
header __UNWANTED_LANGUAGE_SKIP X-Envelope-To =~ /\@foo\.com>/i
meta UNWANTED_LANGUAGE_BODY __UNWANTED_LANGUAGE_BOD
On 15.11.19 11:51, KADAM, SIDDHESH wrote:
I have multiple domains which are running after Spamassassin server.
I want to bypass one specific Spamassassin rule ie TextCat(Unwanted
Language) for one recipient domain.
how do you run spamassassin? with spamass-milter you can use per-recipient
ok_
10 matches
Mail list logo