Hello,

 

We've identified an issue with emails sent by the Nexus Support system in the latest version which causes two Message-ID headers to be sent and the emails to be rejected.

 

When adding a unique Message-ID header in the following locations, "Message-Id" was used as the header key rather than "Message-ID"; this causes SMTP::_send to fail its check for the header and add an additional one due to the difference in casing ("Message-Id" is used in Nexus, "Message-ID" is required by _send):

• /applications/nexus/sources/Support/Reply.php - line 467
• /applications/nexus/extensions/IncomingEmail/Support.php - line 411
• /applications/nexus/tasks/supportAutoresolve.php - line 73

 

The relevant check for the header in SMTP::_send is at /system/Email/Outgoing/Smtp.php - line 200.

 

An example of a bad SMTP log resulting from this behavior is below:
 

[redacted authentication]
> MAIL FROM:<noreply@...>
250 Ok
> RCPT TO:<...@gmail.com>
250 Ok
> DATA
354 End data with <CR><LF>.<CR><LF>
> MIME-Version: 1.0
To: ...@gmail.com
From: ... <noreply@...>
Subject: ...
Date: Sat, 30 Nov 2024 11:03:37 +0000
Auto-Submitted: auto-generated
Content-Type: multipart/alternative; boundary="--==_mimepart_24b8bb3600bde6b440df029b69cccd0d"; charset=UTF-8
Content-Transfer-Encoding: 8bit
Message-Id: <IPS-0-SR00000.AB1-noreply@...>
Message-ID: eilo88vhvpk404sgc0gg0ko0@...


----==_mimepart_24b8bb3600bde6b440df029b69cccd0d
Content-Type: text/plain; charset=UTF-8




[email contents]



554 Transaction failed: Duplicate header 'Message-ID'.

 

Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.