From: Ralph Seichter <ralph@ml.seichter.de>
To: notmuch@notmuchmail.org
Subject: Re: Dealing with Missing Date Headers
Date: Tue, 18 Jan 2022 20:16:02 +0100 [thread overview]
Message-ID: <87y23cx3bh.fsf@ra.horus-it.com> (raw)
In-Reply-To: <87bl0aysvl.fsf@kevinjfoley.me>
* Kevin Foley:
> Has anyone ever dealt with missing "Date" headers? My emails from Etrade
> in particular are missing them for whatever reason.
Amazing, and not in a good way. There are only two required email
headers, and Etrade manages to screw this up? Quoting RFC 5322
https://datatracker.ietf.org/doc/html/rfc5322#section-3.6 :
The only required header fields are the origination date field and the
originator address field(s). All other header fields are syntactically
optional.
This is something the message sender has to fix.
-Ralph
prev parent reply other threads:[~2022-01-18 19:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 21:06 Dealing with Missing Date Headers Kevin Foley
2022-01-18 13:35 ` David Bremner
2022-01-18 19:16 ` Ralph Seichter [this message]
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=87y23cx3bh.fsf@ra.horus-it.com \
--to=ralph@ml.seichter.de \
--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).