C. A. Niemiec suggested: > >1. view plain text portion >2. view HTML portion >3. view HTML portion scrubbed to plain text > >#3 is HTML part minus tags. Links reduced to PowerMail's usual angle- >bracketed plain text style.
The 3rd alternative is usually possible with PM since some time, if there is no pure text part. If there is a pure text part, usually it makes sense to default to that. I'd consider it feature though to be able to view any HTML-message to text only, even if there was a pure text part. However, some HTML-messages end up as attachments only, which is a big problem IMHO. Some problems with this: ? The PM built-search index won't contain the data as it's only available in an external file. Thus, information in these attached files won't turn up in any searches. ? The information is fragile. If the external file is moved or deleted only an empty message will be what's left. ? The information can only be read, copied and treated in the web browser, which is quite inconvenient. ? It's likely that forwards or redirects will keep the message as attachment only, which will expand the problem to users of other more HTML-capable email clients. >Friends (sic), family, co-workers all get their HTML mail via the client >of their choice. PowerMail users can send back plain text replies. >PowerMail users with a grudge against HTML mail can send back plain text >with maniacal glee. Hehe, this sounds nice. >Would this really take more than some regex? Why? It's much better to let an HTML interpreter do its stuff and use the result, which is text after all (and media obviously, but that would have to be scrapped I think). Which is what PM does now. Mikael Technoids: PM 5.6.5 build 4509 sv / SpamSieve 2.7.1 sv | OS X 10.4.8 | Powerbook G4/400 | 1GB / 80GB
