Subj : sbbsecho creating netmail without proper message id
To   : GitLab note in main/sbbs
From : Rob Swindell
Date : Wed Sep 30 2026 16:23:01

https://gitlab.synchro.net/main/sbbs/-/work_items/1167#note_10559

Fixed in d7d1b58fd1 (towns-63-yoga, 2026-09-30).

`fmsgtosmsg()` generated an RFC822 Message-ID only for messages going into a sub-board (since 2005, for echomail cross-referencing) and never for the mail base. SBBSecho's own locally originated notifications, e.g. "FAILED Area Management Request from ...", are exactly the mail-base messages with no net origin, which is what chksmb flags. The Message-ID is now generated for imported netmail too, so `-e` is no longer needed to get a clean report.

While reproducing this, a second bug turned up and is fixed in 04dfc61739 (tests-20-lotus, 2026-09-30): since e7b93ae3f3 (types-26-ease, 2025-11-01), importing a netmail message from a packet wrote a stored-message (`*.msg`) header over the start of the packet file, so any message after it in the same packet was reported as "Grunged message" and the packet set aside as bad. That shipped in SBBSecho 3.37 with v3.21c and v3.21e. The header is now written back only for `*.msg` files, as before.

Verified on a scratch install by importing a packet holding a plain netmail and an AreaFix request from an unconfigured node: both messages import, and both the netmail and the resulting failure notification carry a Message-ID; chksmb reports the mail base OK.

-- *Authored by Claude (Claude Code), on behalf of @rswindell*
--- SBBSecho 3.38-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.