similar to: analysing of dmarc report

This caused a crash on a 2.6.10-1.12_FC2smp kernel May 19 09:56:35 spf1 kernel: Assertion failure in log_do_checkpoint() at fs/jbd/checkpoint.c:361: "drop_count != 0 || cleanup_ret != 0" May 19 09:56:35 spf1 kernel: ------------[ cut here ]------------ May 19 09:56:37 spf1 kernel: kernel BUG at fs/jbd/checkpoint.c:361! May 19 09:56:37 spf1 kernel: invalid operand: 0000 [#1] May 19

On Fri, Jan 2, 2015 at 3:43 PM, Geert Stappers <stappers at stappers.nl> wrote: > On Sat, Dec 27, 2014 at 05:07:04PM +0100, Geert Stappers wrote: >> On Mon, Dec 22, 2014 at 11:06:58AM +0200, Ady wrote: >> > > On Sun, Dec 21, 2014 at 12:21:32PM -0800, Patrick Masotta wrote: >> > > > [ ... Failed to build gnu-efi. ... ] >> > >> > For some

On Sat, Jan 3, 2015 at 12:53 PM, John 'Warthog9' Hawley <warthog19 at eaglescrag.net> wrote: > On 01/03/2015 08:56 AM, Gene Cumm wrote: >> On Fri, Jan 2, 2015 at 3:43 PM, Geert Stappers <stappers at stappers.nl> wrote: >>> On Sat, Dec 27, 2014 at 05:07:04PM +0100, Geert Stappers wrote: >>>> On Mon, Dec 22, 2014 at 11:06:58AM +0200, Ady wrote:

On 01/03/2015 08:56 AM, Gene Cumm wrote: > On Fri, Jan 2, 2015 at 3:43 PM, Geert Stappers <stappers at stappers.nl> wrote: >> On Sat, Dec 27, 2014 at 05:07:04PM +0100, Geert Stappers wrote: >>> On Mon, Dec 22, 2014 at 11:06:58AM +0200, Ady wrote: >>>>> On Sun, Dec 21, 2014 at 12:21:32PM -0800, Patrick Masotta wrote: >>>>>> [ ... Failed to

Hello Everyone, I am used to messing with bind zones directly. With samba 4, I cannot do that. Is the following the correct way to add a TXT record for SPF to the zone using samba-tool? /usr/local/samba/bin/samba-tool dns add s4server.example.org example.org example.org TXT "v=spf1 mx -all" I am not sure it is because it is showing up with dig as "v=spf1" "mx"

Test from Yahoo via Android --Gene

On Sun, Jan 4, 2015 at 9:27 AM, gene.cumm at yahoo.com <gene.cumm at yahoo.com> wrote: > Test from Yahoo via Android > > --Gene > _______________________________________________ > Syslinux mailing list > Submissions to Syslinux at zytor.com > Unsubscribe or set options at: > http://www.zytor.com/mailman/listinfo/syslinux As some users may already be aware, my test

On Sun, Jan 04, 2015 at 07:37:44PM +0100, Geert Stappers wrote: > On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: <snip/> > > As far as I can tell, GMail does process the SPF/DKIM/DMARC properties > > but ignores Yahoo!'s DMARC policy to reject on failure. > > The Syslinux ML should now be ready for DMARC p=reject > > We shall see how

On 2/9/19 10:48 AM, Juri Haberland via dovecot wrote: > On 09/02/2019 10:44, Aki Tuomi via dovecot wrote: >> For some reason mailman failed to "munge from" for senders with dmarc policy ;( >> >> It's now configured to always munge to avoid this again. > > I'd say, let Mailman throw all people off the list that have enabled DMARC > checking without

Hi! It seems we accidentically had a high amount of subscribers temporarily disabled due to DMARC on some sender's host. We have now taken actions to prevent this in the future and all temporarily disabled members have been restored. Aki

I get about a half dozen rejection messages from various servers when I post to this list. Is there something I need to configure differently in my DMARC record to be better compliant? Daniel

On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: > On Sun, Jan 4, 2015 at 9:27 AM, gene.cumm at yahoo.com <gene.cumm at yahoo.com> wrote: > > Test from Yahoo via Android > > > > --Gene > > _______________________________________________ > > Syslinux mailing list > > Submissions to Syslinux at zytor.com > > Unsubscribe or set options at:

In the same vein, I am receiving forensic DMARC reports from mx01.nausch.org. Whenever I send a message to the mailing list or when my server sends a DMARC report, I'm getting a DMARC Forensic report. It's odd, because the actual report tells me both DKIM and SPF (in the the of a DMARC report) pass... Here is what I am getting : This is an authentication failure report for an email

> On Saturday, January 17, 2015 9:34 AM, Gene Cumm <gene.cumm at yahoo.com> wrote: > > On Saturday, January 17, 2015 1:48 AM, Geert Stappers <stappers at stappers.nl> wrote: > > > > > > On Sun, Jan 04, 2015 at 07:37:44PM +0100, Geert Stappers wrote: > > > On Sun, Jan 04, 2015 at 12:14:51PM -0500, Gene Cumm wrote: > > <snip/>

All, Within the last year, Yahoo has published some strict DMARC filtering policies, and Gmail is dutifully rejecting emails that fail the DMARC policies. Unfortunately, this has some negative consequences for other list members, even those without a Yahoo address (in particular, Gmail bounces messages that fail the DMARC checks, and after a certain number of bounces, Mailman unsubscribes the

All, Within the last year, Yahoo has published some strict DMARC filtering policies, and Gmail is dutifully rejecting emails that fail the DMARC policies. Unfortunately, this has some negative consequences for other list members, even those without a Yahoo address (in particular, Gmail bounces messages that fail the DMARC checks, and after a certain number of bounces, Mailman unsubscribes the

Just reading up on DMARC, toying with setting it up to auth against incoming emails. (but not configure my domain to use dmarc, or at least not yet) ran into an article about opendmarc, which is available on epel. but when I took a look at the opendmarc website and the git pages it doesn't appear to have been updated in several years. while I see that it is still available from epel, I

Maurizio Caloro: > Please i have new following Error, from DMARC Report, if i check my domain > on example mxtoolbox i dont see any problems. > > Any from you know this Eror report, what i need to do to fix this issue? I guess, the reports are about messages you sent to the list: https://dovecot.org/pipermail/dovecot/2017-August/109097.html are you *really* sure you signed the

so... I've got some mailman lists running on centos 6. apparently c6 has mailman 2.1.12, which is far too old to have the dmarc patches (introduced in 2.1.16 and updated in 2.1.??, so of course, I'm having ongoing issues with yahoo/sbc/att/aol/etc subscribers and bouncing messages ending up causing 30%+ of my subscribers not to be able to get mail. These are mostly non-technical

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 09 February 2019 at 20:48 Juri Haberland via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>