Akkana wrote:
> Here's why this happens: The Netscape emphasis has
> been on html mail, for good or ill. (If it's wrong, no one has managed
> to convince them why plaintext mail should be an important corporate
> goal). This means that plaintext work for developers inside
> Netscape is a spare-time thing (and there are only a few of us who
> care enough). This also means that QA doesn't test plaintext mail
> much -- e.g. it's not a regular part of the daily acceptance tests.
While I know that plaintext mail is not a pripority for Netscape, this
extreme surprises even me.
Not having the ability *at all* to send as plaintext would be
unbelieveably foolish - both for the app Netscape Mailnews and the
internet, because Netscape Mailnews and users of countless UAs (these
users still make up some considerably portion - I hope, I don't have to
argue about that) wouldn't be able to communicate at all.
> So to get plaintext mail working solidly, we either need someone to
> convince Netscape that it should be an important corporate goal (and
> rest assured you're not going to do that by posting to these lists,
> since the people you'd need to convince don't read developer groups)
Who are they?
If I find the time to write that, I'll try to stay very rational. :)
