Bug 15296 - The Busybox sendmail command does not add a Message-ID
Summary: The Busybox sendmail command does not add a Message-ID
Status: NEW
Alias: None
Product: Busybox
Classification: Unclassified
Component: Other (show other bugs)
Version: 1.35.x
Hardware: All Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-01-27 09:08 UTC by Sven Kirmess
Modified: 2023-01-27 11:04 UTC (History)
2 users (show)

See Also:
Host:
Target:
Build:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sven Kirmess 2023-01-27 09:08:10 UTC 
The following command run on illumos with the real sendmail gets sendmail to add a Message-Id header.

    echo "To: me@example.net\nSubject: test" | sendmail -ti

If I run this command (on Alpine Linux) with the Busybox sendmail it does not add a Message-Id header.
(BusyBox v1.35.0 (2022-11-19 10:13:10 UTC) multi-call binary.)

    echo -e "To: me@example.net\nSubject: test"  | sendmail -ti

Unfortunately, gmail does reject mails without a Message-Id. And, although the RFC violation seems to be with Google, I would suggest that the Message-Id header is added as it would increase compatibility with real sendmail and serve better for the intended purpose (sending mails as easy as possible).
Comment 1 Sven Kirmess 2023-01-27 11:04:06 UTC 
I just noticed that msmpt added the same feature request recently

https://github.com/marlam/msmtp-mirror/issues/82