[ZBX-21830] In-Reply-To is not surrounded by "<" and ">". Created: 2022 Oct 28  Updated: 2024 Apr 10  Resolved: 2022 Nov 16

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Server (S)
Affects Version/s: None
Fix Version/s: 6.0.11rc1, 6.2.5rc1, 6.4.0beta4, 6.4 (plan)

Type: Problem report Priority: Trivial
Reporter: Kazuo Ito Assignee: Andrejs Sitals (Inactive)
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Zabbix 6.0.1


Issue Links:
Causes
Team: Team A
Sprint: Sprint 94 (Nov 2022)
Story Points: 0.1

 Description   

In-Reply-To is not surrounded by "<" and ">".

In-Reply-To was not enclosed in '<' and '>', an error occurred on the mail server and the email was not sent.

Below is an excerpt from RFC-5322.

3.6.4. Identification Fields

Though listed as optional in the table in section 3.6, every message
SHOULD have a "Message-ID:" field. Furthermore, reply messages
SHOULD have "In-Reply-To:" and "References:" fields as appropriate
and as described below.

The "Message-ID:" field contains a single unique message identifier.
The "References:" and "In-Reply-To:" fields each contain one or more
unique message identifiers, optionally separated by CFWS.

The message identifier (msg-id) syntax is a limited version of the
addr-spec construct enclosed in the angle bracket characters, "<" and
">". Unlike addr-spec, this syntax only permits the dot-atom-text
form on the left-hand side of the "@" and does not have internal CFWS
anywhere in the message identifier.

https://www.rfc-editor.org/rfc/rfc5322#section-3.6.4



 Comments   
Comment by Andrejs Sitals (Inactive) [ 2022 Nov 09 ]

Fixed in development branch feature/ZBX-21830-6.3

Comment by Andrejs Sitals (Inactive) [ 2022 Nov 16 ]

Available in versions:

Generated at Sat Apr 26 04:00:59 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.