This:
On 7/21/20 12:29 PM, Joseph Brennan wrote:
>
> My understanding of DMARC's purpose was to protect transactional
> messages from sources like banks, credit card issuers, online shopping
> venues, and the like. It supposed that those messages should pass only
> directly from the source to the
On Wed, Jul 22, 2020 at 6:38 PM Jesse Thompson wrote:
> On 7/22/20 12:05 PM, John Levine wrote:
> > I don't believe we have a charter to tell mailing list operators what
> > to do, even if we believed, against all experience, that they would
> > take our advice.
>
> https://cyber.dhs.gov/bod/18-0
On 7/22/20 12:05 PM, John Levine wrote:
> I don't believe we have a charter to tell mailing list operators what
> to do, even if we believed, against all experience, that they would
> take our advice.
https://cyber.dhs.gov/bod/18-01/ references
https://dmarc.org/wiki/FAQ#I_operate_a_mailing_list_
In article <002201d6602d$8b87dca0$a29795e0$@bayviewphysicians.com> you write:
>Since the conflict between DMARC and Mailing Lists is related to the changes
>that Mailing List apply
>to a received message, it may be useful to review the purposes that each of
>those changes serve, with
>a goal of e
Since the conflict between DMARC and Mailing Lists is related to the changes
that Mailing List apply to a received message, it may be useful to review the
purposes that each of those changes serve, with a goal of eliminating
unnecessary changes.
Specifically, this list adds a footer to every me
On 7/21/2020 1:08 AM, Laura Atkins wrote:
When we’re basing a protocol on “what the user sees” and “what the
user can trust” then I think we have to. DMARC says “users can trust
that mail from @domain.example is really from @domain.example” but if
the user never sees that, how do they know?
