Am 04.12.19 um 10:14 schrieb Petter Reinholdtsen: > [Matthias Andree 2014-05-20] > While it sure is optional according to RFC5322, it is considered best > practice to include in in emails. What is the reason the fetchmail > developers do not want to include Message-ID into these notification? > I currently use fetchmail+procmail to receive emails from IMAP servers, > and the IMAP servers seem to make sure Message-ID is present. The > issue at hand here are emails not originating from the IMAP servers, > unfortunatly.
What is the reason people use inferior software and then only to a small stretch of its possibilities, and then try to put convenience features into other packages? What is the new argument that could sway the original decision? Or think that the fetchmail developers would have to answer such questions at all? If the issue is with procmail + notmuch not generating that header, or coping without, then fix that. So? If you must use that unmaintained piece from the museum of anti-designs called "procmail", you can as well rig it to pipe all ingress mail through "formail -a Message-ID" if notmuch still fails without such a header. formail is part of the procmail package. Or you could use reformail from the maildrop package. Other options might exist.
