On Sat, Jun 3, 2017 at 3:32 AM, Ken O'Driscoll
wrote:
> Not to mention, the irony of the official DMARC mailing list discouraging
> postings from DMARC protected domains due to compatibility issues!
>
Not long ago there was some advice circulated that DMARC is really
In article <1496485938.3555.19.ca...@wemonitoremail.com> you write:
>MailMan has supported DMARC domains for ages through a simple address re-
>writing mechanism. It works quite well. The version running this list
>(2.1.22) definitely supports it, it just needs to be enabled.
The IETF has a
Replying from my personal account as requested:
On Fri, Jun 2, 2017 at 8:08 AM, Barry Leiba wrote:
> The valimail.com domain appears to have recently (it looks like it
> started 1 June) set a restrictive DMARC policy, and that's caused a
>
valimail.com has been at
Oh, and I've reset the disabled bits for everyone who was disabled due
to bounces. But that doesn't scale, and I don't have the time to keep
doing that.
Barry
On Fri, Jun 2, 2017 at 11:08 AM, Barry Leiba wrote:
> The valimail.com domain appears to have recently (it
The valimail.com domain appears to have recently (it looks like it
started 1 June) set a restrictive DMARC policy, and that's caused a
boatload of disabled subscriptions. Basically, whenever Seth (or any
other valimail.com user, but recently that's been Seth) sends a
message to the list now,