E x t e n d e d A S C I I d o n o t di s p l a y p r o p e r l y When I exported one of the folders that refuse to display extended ASCII characters properly, after import from Emailer and OE 4.5, I discovered that the chars was set accordingly: 'Content-type: text/plain; charset="x-user-defined" ', It seems this had been set by PM internally as far as I can see and not by OE 4.5 as I first thought. In the exported PM Exchange files, other charsets is displayed under the Content Type header, like for instance UTF-8 and ISO-8859-1.
H e a d e r s v s b o d y In the headers the "X-User-Defined" are visible in text, like in my name: 'Micke Bystr=?x-user-defined?B?mg==?=m', but that doesn't seem to help PowerMail in displaying even the headers properly. Actually, even if I reexport from Emailer, this time with the "Export - Eudora" script and import anew, I can get proper characters, this time with 'charset="iso-8859-1" ' in the *body*, but the headers including the subject line that contains "Subject: =?iso-8859-1?Q?Hall=E5_d=E4r?=" that should display like "Hallå Där", instead is shown as "Hall=E5_d=E4r". This seems like a bug to me. Why isn't ISO-8859-1 applied consistently within a message? This is even more confusing as mailcollected messages with the same header settings *do* display properly. That is, with ISO in both headers and body. How does PowerMail tell imported messages apart from collected ones? What is the problem? E u d o r a f o r m a t I decided to look at the headers in Eudora format in an export from both Emailer and Powermail. I choosed a message with the subjectline "Re: En röst" that happened to have been mailcollected in both Emailer and in Powermail . I discovered that PM adds "charset=x-mac-roman" and "Content-Transfer- Encoding: 8bit" and puts Mac chars in the headers as well (so it looks exactly that I wrote above), when the scripted export from Emailer instead puts ISOcodes directly in the headers as well as keeping that in the charset setting. So in the latter the subject is "Re: En r=?ISO-8859- 1?Q?=f6st" instead of "Re: En röst". P o w e r M a i l E x c h a n g e f o r m a t How does the Emailer exported file display in PowerMail if imported? Well, just as in the first example, the body looks alright, but the headers look faulty with the raw code, sans the ISO designators: "Re: En r=f6st". Maybe Powermail have problems with ISO codes directly in the headers? If we export both these messages, the mailcollected one and the imported from Emailer, into PM exchange format and compare those, we see that beside some returns in the from header, the only thing that separates these are the PMFlags lines: PMFlags : 0 82818 1 8 0 0 3 0 1 3262451987 7200 1 0 0 0 0 0 0 (Collected w PowerMail) PMFlags : 0 83984 3 8 0 0 1 0 3 3262803642 7200 1 0 0 0 0 0 0 (Imported from Emailer) Are what PMFlags are all about in any way related to how to display a message? Or is it just an internal Database header? Anyone can tell? R e i m p o r t i n g t h e E x c h a n g e f o r m a t t e d e x p o r t s OK, so as both these now actually did *have* ISO codes in the headers and had charset set to ISO-8859-1, I reimported them to see how they appeared in PM. Surprisingly they do both now have ISO codes in the headers and still do display correctly both in subject line and other headers and in the body. Hmm. So I try with a whole folder that have been imported from Outlook 4.5, that prior to that gad been imported from Emailer. That didn't work as well of course as the source is different (OE instead of scripted Eudora mailbox). Wh e r e i s t h e l o g i c? Ok, I'm missing the logic in this all. It just doesn't make sense. Can someone from CTM please put these things in order for me? Why does export and reimport jelp in getting proper characters in the above case? The Emailer exports looks standardized to me and the scripts are mentioned in the online help. So why can't Powermail understand the resulting exported files the first time around? What is "X-User-Defined" supposed to mean? Why is this header lacking when importing in PM exchange format as opposed from OE 4.5? I m p o r t a b i l i t y w o r k i n g ? Given that CTM themselves put forward OE 4.5 as a solution for Emailer users, why haven't they found a way to keep proper characters displaying when importing from OE 4.5? What can I do to make this work?
