| From: | Greg Stark <stark(at)mit(dot)edu> |
|---|---|
| To: | José Luis Tallón <jltallon(at)adv-solutions(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Kevin Grittner <kgrittn(at)gmail(dot)com> |
| Subject: | Re: New email address |
| Date: | 2015-11-26 23:24:07 |
| Message-ID: | CAM-w4HMCWBZGKTE9rZUw28c6Tb7esiP8MrLNpVa7tzyhxAZ5Dg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 26, 2015 at 11:13 PM, José Luis Tallón
<jltallon(at)adv-solutions(dot)net> wrote:
> From DMARC.org's Wiki:
> <<< 2 Add an "Original Authentication Results" header to indicate you have
> performed the authentication and you are validating it
> 3 Take ownership of the email, by removing the DKIM signature and putting
> your own
> as well as changing the from header in the email to contain an email address
> within your mailing list domain. >>>
But you missed option #1:
1. Operate strictly as a "forwarder," where the RFC5321.RcptTo field
is changed to send the message to list members, but the RFC5322
message headers and body are not altered.
Pros: Receiving systems can validate the DKIM signature of the message
author, if one was present.
Cons: Senders that depend solely on SPF for authentication will still
fail. Precludes many customary features of mailing lists, such as
"Subject:" tags, list footers/disclaimers, etc.
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-11-26 23:26:14 | Re: New email address |
| Previous Message | José Luis Tallón | 2015-11-26 23:13:45 | Re: New email address |