This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
when attachments are sent with the message the MIME type multipart/mixed is used. The body text is one part of the message with Content-Type: text/plain. According to RFC 1521 in this case the Content-Type header for the part can be left out, see an example in the RFC page 66. Emacs/Gnus does precisely this. Unfortunately ezmlm cannot handle a part with an empty header section. The end result is that whenever I send a message with an attachment to the list, the message body is lost (it's there in the raw data but not marked as a part anymore, ezmlm destroys the header section of the part). The recipients see only the attachment, no text in the message body. ezmlm violates RFC1521. I attach a test message, twice, once sent directly to me, once through ezmlm.
Created attachment 438 [details] message not sent through ezmlm
Created attachment 439 [details] the same message sent through ezmlm
let him know we're escalating it. I've sent emails to the authors of ezmlm. Brian
This should be fixed with the new ezmlm RPM from releng, which I believe Trung has tested. I'll mark it closed once we're on a system which has that RPM.
Just assigning it to you ed, so that you can look at it and see if it really is fixed when the time comes.
can you confirm ed?
The new RPM hasn't been installed onto netbeans.org, so this is still an issue. I could install that RPM, or wait till we do the next upgrade. Either is fine with me; installing an RPM is fairly painless, but this would be a new version of ezmlm-idx, possibly with some changes besides the bug fix.
I don't think we need to do a new upgrade so close to a major upgrade. But, I'd just like your verbal that you have seen this issue fixed in the newer version (ie. the one that we are working with on SC1.0)
This is fixed in SC, so I am marking the issue resolved later.
re-opening to re-resolve fixed.
re-resolving fixed.
We recently moved out from Collabnet's infrastructure