[private]

> > Note too that if you have a different type font selected for displaying
> > messages and creating new ones (the former seems "stuck" on Arial--ugh!)
> > then editing any line which contains old text (so that line now contains
> > two different fonts) will make Exchange generate WINMAIL.DAT regardless
> > of how your options are set.  My advice: use Pegasus mailer (I don't have
> > the URL handy, but AltaVista should find it no prob).  I switched and have
> > never looked back.
>
> Yuk, I knew there was a reason I was avoiding micro$oft mailers...

Yeah... both of those behaviorisms are truly befuddling IMHO.  It's not as
though Internet mail is exactly a "new thing".

On the other hand, I'll admit that Pegasus' editor is also at times annoy-
ing.  For example, I've been trying to figure out a good way to:

-1- Disable line-wrap for certain lines, or at least manage to create lines
    longer than the line-wrap limit.  While I generally like to keep my
    mails less than 76 char's/line, sometimes tables and such really do need
    the full 79.  Can't do it under Pegasus, though.

-2- Cut and paste text with leading tabs.  Pegasus seems to convert them to
    spaces (for code fragments, tabs are much more convenient than spaces;
    I'm generally careful to format my code so tab stops of either 4 or 8
    will work decently).

-3- Handle decently lines with varying margins, such as this four-point list.
    Pegasus seems to wrap things all over the place; PC-Write 2.5 did much
    better (later versions of PC-Write allow you to embed ruler lines within
    the text; earlier ones would try to judge the left margin by the text that
    was there.  Right margin still had to be set by hand but could be changed
    very easily).

-4- Use two spaces after periods without having to worry about whether Pegasus
    will wrap an extra space onto the next line.  PC-Write will simply let
    extra spaces remain at the end of the previous line (which seems to work
    pretty well).

Any good workarounds for those that you know of?

> Humm, I just set up procmail to send any messages with font
> extensions to /dev/null ! - And that also goes for messages sent in
> HTML, or worse (but only just) messages sent as plain text and HTML.

Do you go after full-body HTML ones, or anything with embedded HTML?  I know
some people like to use pseudo-HTML to emphasise text in otherwise non-HTML
documents (personally, I prefer /italic/, *BOLD*, ~superscript~, and
_underlined_ but that's just my taste.)