From: Andy Smith <andy@strugglers.net>
To: notmuch@notmuchmail.org
Subject: What to do about message/rfc822 attachments?
Date: Thu, 29 Jun 2023 14:14:25 +0000 [thread overview]
Message-ID: <ZJ2RwSlVMtZLXDoV@use> (raw)
Hi,
In this age of DKIM and DMARC, some mailing lists have decided to
wrap the original message into a message/rfc822 attachment before
sending it out to subscribers.
Some do this unconditionally, for every message received. Some do it
conditionally, for example only when the poster's domain has a DMARC
policy of "reject".
Popular mailing list software such as Mailman (both v2 and v3) offer
both of those modes of operation. I am on multiple mailing lists
that use both methods, though it is still a minority.
What this means is that I see a message that looks like this:
From: Joe Bloggs via somelist <somelist@lists.example.com>
Message-ID: <whatever@lists.example.com>
Subject: Joe's original subject
References: (from Joe's post)
In-Reply-To: (from Joe's post)
That then contains a message/rfc822 attachment that contains the
full original copy of Joe's post, with all its headers intact.
I am a relatively new notmuch user. Am I correct in thinking that
notmuch will look inside message/rfc822 containers and find the
text/plain (and/or text/html) parts within and index them for full
text search just as it would the message body in a conventional
message?
The threading should also work as intended too because the
References/In-Reply-To are retained.
So really I think the only wrinkle is that I need to remember that
searching by a person's email address is not going to find all
messages by them, because ones they send to such a list will not
actually appear to notmuch to be from them, but instead from the
lists's address.
That is already an issue with mailing lists that rewrite the From:
address (again for DKIM/DMARC reasons), but I was wondering if there
were anything that people do with notmuch to improve matters given
that all the info does actually exist in these wrapped messages. Is
it somehow possible, or would be a worthwhile idea to, look for
From: addresses and other useful headers also inside message/rfc822
containers?
Thanks,
Andy
next reply other threads:[~2023-06-29 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 14:14 Andy Smith [this message]
2023-07-22 18:37 ` What to do about message/rfc822 attachments? David Bremner
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZJ2RwSlVMtZLXDoV@use \
--to=andy@strugglers.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).