#22 — Issues with Content-ID header of image parts in MIME messages
by
Hans Aschauer
—
last modified
Apr 06, 2011 09:34 PM
| State | Unconfirmed |
|---|---|
| Version: | |
| Area | Functionality |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Hans Aschauer |
| Submitted on | Apr 06, 2011 |
| Responsible |
—
|
| Target release: |
—
|
According to RFC2392, chapter 2, the content id in the MIME header is included in angle brackets. So in content/ENLIssue.py the line
image["Content-ID"] = "image_%s" % image_number
should be something like
image["Content-ID"] = "<image_%s>" % image_number
Btw. AFAIK the content id should be something more random -- so that it is unique even if many newsletters are forwarded in multiple attachements of a single mail.
This bug is actually in 2.5.10a2
image["Content-ID"] = "image_%s" % image_number
should be something like
image["Content-ID"] = "<image_%s>" % image_number
Btw. AFAIK the content id should be something more random -- so that it is unique even if many newsletters are forwarded in multiple attachements of a single mail.
This bug is actually in 2.5.10a2
No responses can be added.
If you can, please log in before submitting a reaction.