-
-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MultipartRelated Start #124
Comments
From rfc2387, we have this:
Then, in rfc822, it defines
So it looks like Thunderbird is broken. |
In the rfc 822 i can find this: 3.2. The Start Parameter The start parameter, if given, is the content-ID of the compound So in 99 % of cases (including mine), the parameter is not necessary. If the parameter is not specified the message is shown correctly in Thunderbird. |
Yep, I know it's not necessary. That doesn't make it not a bug in Thunderbird, though :-) |
Can you file a bug on https://bugzilla.mozilla.org about the Thunderbird bug? Thanks. |
The bug already exists https://bugzilla.mozilla.org/show_bug.cgi?id=471402 thanks anyway, but in my condition I guess I'll have to edit and recompile the source code of mimekit. |
I've added a work-around to not use a start parameter if it is the first part in the multipart. But shame on Thunderbird for not adhering to the specifications. |
Fantastico! There will be a new version for NuGet with this change? |
Probably not until this weekend when I have time to make a release. |
Ok ... the weekend is a reasonable time. |
Hi...when a new release in nuget? |
Sorry about that, I got distracted this past weekend. There will be a release this weekend for sure. |
Thank you very much! |
I've released MimeKit 1.0.13 with this fix. |
The code line:
ContentType.Parameters["start"] = "<" + value.ContentId + ">";
is right?
Thunderbird with this parameter with the characters < and > shows an empty message!
The text was updated successfully, but these errors were encountered: