open https://gitlab.synchro.net/main/sbbs/-/issues/1167

smbchk showed

Missing Message-IDs (!): 3

Digital Man suggested using -e

I have 3 similar reports

Checking /sbbs/data/mail Headers

6% #27367 (025C20) SBBSecho No Message-ID
MSGERR: Header missing Message-ID

message base /sbbs/data/mail
To SYSOP
ToExt 1
Subject FAILED Area Management Request from 1:135/205
Sender SBBSecho
when_written 0184F6E0 C168 Tue Jun 2 15:27:32 2026 CDT
when_imported 6A1F3CB4 C168 Tue Jun 2 15:27:32 2026 CDT
type 0000h
version 0310h
attr 0003h (PRIVATE, READ)
auxattr 00000000h ()
netattr 00000000h ()
header_offset 025C20h
header_fields 4
header_length 155 (calc: 155)
number 27367
thread_id 27367
data_offset 132000h
data_field[0] TEXT_BODY, offset 0, length 208

I'm not sure if that's supposed to be the case?
--- SBBSecho 3.37-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

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)

close https://gitlab.synchro.net/main/sbbs/-/work_items/1167
--- SBBSecho 3.38-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)