Hmm, weird what's setting content transfer encoding? it shouldn't ever be set blank unless something lese is going wrong right? Z On 10 Jun 2001 18:29:20 -0400, Jeffrey Stedfast wrote: > I think at least part of this brokenness is known about but I'm not sure > about all of it. > > Since I'm away on vacation using pine, some of the brokeness is clearly > apparent. I've been receiving a lot of messages in the past few days on > the mailing lists that pine shows me nothing and tells me to view a single > text/PLAIN part as an attachment. > > I took a look at the headers and I see that Evolution *is* only sending a > single part and not a multipart which pine seems to think. However, there > is an empty Content-Transfer-Encoding header which should probably be set > to 7bit in this case (or, possibly not even be there in the first place?). > > The other part, which I know people are aware of is the charset being set > to something weird and incorrect when 7bit ascii is being sent. > > Fixing the second one might fix the first problem I mentioned - just > wanted to bring it to everyone's attention to keep an eye out for. > > If problem #2 has been fixed in CVS, maybe someone using CVS can email me > and I can see how it displays in pine? > > Btw, JPR's most recent messages to evolution@ have the display problem I'm > describing. > > Jeff > > > _______________________________________________ > evolution-hackers maillist - [EMAIL PROTECTED] > http://lists.helixcode.com/mailman/listinfo/evolution-hackers _______________________________________________ evolution-hackers maillist - [EMAIL PROTECTED] http://lists.helixcode.com/mailman/listinfo/evolution-hackers
