Skip Menu |

Preferred bug tracker

Please visit the preferred bug tracker to report your issue.

This queue is for tickets about the Email-MIME CPAN distribution.

Report information
The Basics
Id: 13236
Status: resolved
Priority: 0/
Queue: Email-MIME

People
Owner: Nobody in particular
Requestors: JRED [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 1.81
Fixed in: (no value)



Subject: No MIME-Version header field set, but RFC 1521 requires it
When building MIME mails, e.g. Content-type: multipart/alternative for Text+HTML mails, no "MIME-Version: 1.0" header is added automatically, which is required by RFC1521. Some mail/groupware servers are not able to process such mails correctly, e.g. if they their policy forbids HTML content. The user then gets the pure MIME encoded content, with all delimiters, applied quoted printable encoding etc., rendering the mail unreadable.
On Tue Jun 14 04:08:23 2005, guest wrote: Show quoted text
> When building MIME mails, e.g. Content-type: multipart/alternative for > Text+HTML mails, no "MIME-Version: 1.0" header is added > automatically, which is required by RFC1521.
I can not verify this bug. Perhaps it was fixed in the last year.
Can't reproduce. -- rjbs