View Issue Details

IDProjectCategoryView StatusLast Update
0001563Community.cacert.orgmiscpublic2024-09-21 09:30
Reporterdops Assigned Tojandd  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformDefaultOSanyOS Versionany
Summary0001563: Invalid Message-ID in board voting system notifications
DescriptionImpact:
- notifications get a big penalty in Spamassassin (4.7 INVALID_MSGID=1.167,MSGID_NOFQDN1=2.899) and maybe other spam protection mechanisms, so at risk to be filtered and not seen by recipients
- potential interoperability problems with mail user agents

Sample:
   Message-ID: <m20240606.1>

According to https://www.rfc-editor.org/rfc/rfc5322#page-25 the format is
    msg-id = [CFWS] "<" id-left "@" id-right ">" [CFWS]

So this part is missing:
   @" id-right "
Typically a domain or a "domain-like" identifier is chosen and must be unique, not necessarily a valid hostname, e. g.
   Message-ID: <m20240606.1@voting.cacert.org>
Steps To ReproduceSubscribe to the CAcert board mailing list and receive a notification from the CAcert board voting system
TagsNo tags attached.

Activities

jandd

2024-06-07 09:21

administrator   ~0006225

Thanks for the high-quality bug report. I filed in issue in the issue tracker of the affected code at https://code.cacert.org/cacert/cacert-boardvoting/issues/1

jandd

2024-06-08 11:09

administrator   ~0006227

I implemented the necessary code change in https://code.cacert.org/cacert/cacert-boardvoting/commit/3d16034c449a96b25a12d9b1dfb2f0a5b1635d00 contained in https://code.cacert.org/cacert/cacert-boardvoting/releases/tag/0.8.3

I'm waiting for the current pending votes to finish before deploying the release that contains this commit on the production system.

jandd

2024-09-21 09:30

administrator   ~0006247

the fix has been deployed on the production system

Issue History

Date Modified Username Field Change
2024-06-07 07:22 dops New Issue
2024-06-07 09:21 jandd Note Added: 0006225
2024-06-07 09:22 jandd Assigned To => jandd
2024-06-07 09:22 jandd Status new => needs work
2024-06-08 11:09 jandd Status needs work => fix available
2024-06-08 11:09 jandd Note Added: 0006227
2024-09-21 09:30 jandd Status fix available => closed
2024-09-21 09:30 jandd Resolution open => fixed
2024-09-21 09:30 jandd Note Added: 0006247