Double Header Message-ID in outbound email causing email failure

Created on 26 May 2011, about 13 years ago
Updated 29 March 2023, over 1 year ago

I just attempted to upgrade Support Ticketing to 6.x-1.4 and also tried 6.x-1.x-dev (May 18, 2011) from 6.x-1.3. Both of these upgrades causes a failure in the sending of Support Ticketing emails from my website. Reverting back to 6.x-1.3 allows for the outbound emails to work as normal.

The website is being hosted on OpenSuse 11.3 with PostFix 2.7.1 and Amavisd-New 2.6.4. The log files show that the outbound Support Ticketing emails are being blocked due to the following error.
X-Amavis-Alert: BAD HEADER SECTION Duplicate header field: "Message-ID"

Checking the outbound file, it does show that with Support Ticketing 6.x-1.4 there are two fields listed in the HEADER with almost the same name. The second line is being generated by Support Ticketing, I found the second line description on line 932 of the SUPPORT.MODULE with the lowercase "d"
Message-ID: <9680caa8e4d205b1630927c08a437015@xxx.xxx.xxx.34>
Message-Id: <2226.2047@xxx.xxx.xxx.34>

Changing the Message-Id to Message-ID does get rid of the Duplicate Header field error, but AMAVISD still reports that the headers being generated by SUPPORT TICKETING 6.x-1.4 are still bad and are being quarantined. The format that is shown in the first Message-ID above is the correct format when there is no errors.

I am continuing to look for any possible solutions with changes to AMAVISD config, but with 6.x-1.3, there are no Bad Header errors being generated.

What other information can I supply to assist?

πŸ’¬ Support request
Status

Closed: outdated

Version

1.8

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States leevester

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.69.0 2024