Re: Four questions and three observations

Ed Vazquez <[email protected]>
Newsgroups gmane.mail.mahogany.user
Organization Denver Health & Hospital Authority
Message-ID <[email protected]>
Sorry this took a bit, apparently SF's mail-list has been slow
to cough up the digests...

In reference to VZ on 04Feb2004:

EV> 1 - The Addresses pane does not seem to be implemented
EV> accurately yet.

VZ> Sorry, what do you mean?

Please reference the thread, but in general for (it seems)
everyone except Vadim, adding one's own e-mail addresses to the
slightly obscure area that keeps you from replying to yourself
is a hit-or-miss proposition.  That being said, at least with
the latest wipe and re-install of v0.66 it seems to be working
correctly now.

EV> 2 - Adding a custom filter rule seems a bit cumbersome.  In
EV> reality, do you ever care if you have read your own Sent
EV> e-mails?

VZ> I do... Also, it doesn't make much sense to have to do something special
VZ> (like mark as read) for a sent mail folder, especially if you have
VZ> several of them.

EV>  This is the only MUA I have run across that has this
EV> behaviour by default (some you can change to behave this way),
EV> so it seems logical that it should be configurable to not treat
EV> any messages in the "Sent" folder as unread or new rather than
EV> having to build a custom "one-off" solution each place I install
EV> M.

VZ> I think what you really want is to not show SentMail folder as having VZ> new mail in the tree, don't you? Because otherwise I simply don't
VZ> understand what is the problem with having the messages as unread in it.

We'll have to agree to disagree on that issue.  I have had
issues with M dealing with showing read/unread in the tree.
 Despite folder settings, global settings, etc. it continues to
show.  So, I'll keep my custom filter for the moment.

EV> 3 - Well, generally the "Text Only" viewer displays HTML-only
EV> messages  (a la Outlook created) as:
EV> [Attachment: TEXT/HTML, 32 lines]

VZ> All pure-HTML messages like this go directly to Junk folder here...
VZ> Outlook usually (I do believe that it does it by default) sends
VZ> multipart/alternative messages, i.e. they contain both HTML and text
VZ> parts.
VZ> Sending pure HTML messages is just plain evil and I refuse to do
VZ> anything to support this. Also, you already have the HTML viewer so you VZ> may view them if you really have to. But it would be much better to let VZ> the people sending you crap like this know that they can keep their
VZ> precious HTML while still sending something readable in all mailers.

Gosh, I'm sorry to hear that you feel that way.  Though I
personally don't care for HTML, RichText, or
other-non-plain-text in e-mail, I'm not quite that vehement.
 And part of the issue is that although using the Outlook Client
to send through MS Exchange to the outside world (e.g.: Public
Internet) does create the multi-part message, sending internally
(which is what I'm dealing with) MS _does_not_ allow the
generation of multipart messages to MAPI recipients.  Even if
I'm using the IMAP interface.

In an organization of over 10,000 individuals, run by the State,
it is a tad impractical for me to attempt to mandate that
_everyone_ configure for "Plain Text Only."  I really hope that
you will have mercy and pity on those of us in corporate
environments where we neither control nor can recommend making a
global change of this magnitude.

In the meantime, it (very unfortunately) appears I will have to
again begin researching alternative MUA's so that I can
effectively communicate with my coworkers.

Regretfully,

--
Ed Vazquez


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.