Done
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Gabriele BulfonGabriele BulfonReporter
Luca GaspariniLuca GaspariniFix Branch
releaseFix Version
5.14.5Release Version
wt-5.16.3WAR ##
0509Components
Priority
Medium
Details
Details
Assignee
Gabriele Bulfon
Gabriele BulfonReporter
Luca Gasparini
Luca GaspariniFix Branch
release
Fix Version
5.14.5
Release Version
wt-5.16.3
WAR ##
0509
Components
Priority
Created April 7, 2022 at 1:28 PM
Updated April 14, 2022 at 2:11 PM
Resolved April 13, 2022 at 10:29 AM
In some emails, most likely generated by Microsoft clients, there are references that look like this:
References: <460779217.325675.1647264140642@posta.domain.net>\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ ..............
By forwarding or replying to these messages in some cases you will receive an NDR with this error message:
Invalid MIME Content: Single text value size (33000) exceeded allowed maximum (32768) for the 'References' header
You can think of cleaning up this kind of References as suggested by what IceWarp does: https://esupport.icewarp.com/index.php?/Knowledgebase/Article/View/590/106/fix-oversize-references-header-lines-that-cause-error-554
Thanks to Emiliano Vavassori (Ticket #146944)