From: Gregory Heytings via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: FW: Describe keymap
Date: Mon, 14 Dec 2020 10:05:49 +0000 [thread overview]
Message-ID: <alpine.NEB.2.22.394.2012141102480453.15479@sdf.lonestar.org> (raw)
In-Reply-To: <87lfe0d81w.fsf@gmail.com>
>>> Because you have Reply-To set (and Mail-Followup-To, but I think
>>> Drew's MUA ignores that)
>>
>> Thanks, that's exactly right, they are
>>
>> Reply-To: Emanuel Berg <moasenwood@zoho.eu>
>> Mail-Followup-To: help-gnu-emacs@gnu.org
>>
>> I don't remember configuring that, but again there has been so much
>> configuration...
>
> Itʼs possible that itʼs the mailing list putting those in for you, since
> itʼs rewriting your From header as well (I assume youʼre sending to the
> mailing list)
>
Yes, it's the mailing list, because the domain name Emanuel uses (zoho.eu)
has a strict DMARC policy:
$ dig +short -t txt _dmarc.zoho.eu
"v=DMARC1; p=reject; sp=reject; fo=0; rua=mailto:dmarc.reports.eu@zoho.eu; ruf=mailto:dmarc.reports.eu@zoho.eu"
The two "reject" means that the policy is strict. Compare this to, for
instance:
$ dig +short -t txt _dmarc.gmail.com
"v=DMARC1; p=none; sp=quarantine; rua=mailto:mailauth-reports@google.com"
$ dig +short -t txt _dmarc.gnu.org
"v=DMARC1; p=none; rua=mailto:dmarc-rua@fsf.org"
next prev parent reply other threads:[~2020-12-14 10:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201213195427.jyn4vwkayqujbnwh.ref@Ergus>
2020-12-13 19:54 ` Describe keymap Ergus
2020-12-13 20:01 ` Drew Adams
2020-12-13 20:14 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-13 23:18 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 1:31 ` FW: " Drew Adams
2020-12-14 2:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 8:46 ` Robert Pluim
2020-12-14 9:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 9:57 ` Robert Pluim
2020-12-14 10:05 ` Gregory Heytings via Users list for the GNU Emacs text editor [this message]
2020-12-14 10:30 ` Robert Pluim
2020-12-14 13:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 17:08 ` Robert Pluim
2020-12-14 18:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-15 10:18 ` Robert Pluim
2020-12-15 20:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 13:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-12-14 1:31 ` Drew Adams
2020-12-14 2:33 ` Michael Heerdegen
2020-12-14 2:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.NEB.2.22.394.2012141102480453.15479@sdf.lonestar.org \
--to=help-gnu-emacs@gnu.org \
--cc=ghe@sdf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).