[ https://issues.jboss.org/browse/JBWS-4064?page=com.atlassian.jira.plugin.... ] Radovan Netuka commented on JBWS-4064: -------------------------------------- This one is curious. According to [RFC-2392|https://tools.ietf.org/html/rfc2392]: "A *cid* URL is converted to the corresponding Content-ID message header [MIME] by removing the *cid:* prefix, _converting the % encoded character to their equivalent US-ASCII characters_, and enclosing the remaining parts with an angle bracket pair, *<* and *>*... Reversing the process and _converting URL special characters to their % encodings_ produces the original cid." But few lines later, they provide an example that contradicts the provided information: "For example, *cid:foo4%25foo1@bar.net* corresponds to *Content-ID: <foo4%25foo1(a)bar.net&gt;*&quot; The same RFC document clearly says, that *cid:...* element _must_ be encoded. I wasn't able to find any information on Content-ID however. For me, the only possible solution is not to fix the cid element not to be encoded (as suggested upstream), but to fix the Content-ID header _to be encoded_. -- This message was sent by Atlassian JIRA (v7.5.0#75005)