Matus UHLAR - fantomas wrote:
Message-ID: <20210712140000.horde.zzzzzzz...@example.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36
(KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36
meta FORGED_MUA_MOZILLA (__MOZILLA_MUA && !__UNUSABLE_MSGID &&
!__MOZILLA_MSGID)
header __MOZILLA_MUA User-Agent =~ /^mozilla\b/i
header __MOZILLA_MSGID MESSAGEID =~
/^<(?:[a-f\d]{8}-(?:[a-f\d]{4}-){3}[a-f\d]{12}|[A-F\d]{8}\.[A-F1-9][A-F\d]{0,7})\@\S+>$/m
meta __UNUSABLE_MSGID (__LYRIS_EZLM_REMAILER ||
__GATED_THROUGH_RCVD_REMOVER || __WACKY_SENDMAIL_VERSION ||
__IPLANET_MESSAGING_SERVER || __HOTMAIL_BAYDAV_MSGID ||
__SYMPATICO_MSGID && __GROUPSIO_GATED)
This IS a forged Mozilla MUA header. The User-Agent field in your
"Email" is from a Web Browser, not a Mail User-Agent.
If Horde wants to retain Web Browser headers, they can do so and wrap
them up in a References Email header.
Doesn't sound like Horde. Maybe more like a misconfiguration issue?
The only Mozilla MUA I know of is Thunderbird, and I regex on that
personally. The spin-off SeaMonkey doesn't set a User-Agent field.
It's not a Mozilla MSGID.
Only question I'd have is on MSGID.
$0.02,
-- Jared Hall
