>When I use Bcc with exmh, the recipient receives a *text* copy of my
>entire message -- including all headers, MIME parts, and attachments.
>Most are completely dumbfounded by this and unable to make sense of
>the message. I would think that the only difference that should occur
>between a Bcc and an original is that the recipient's address not
>appear in the message headers and be used only for the SMTP operation.
>Am I missing something?

This is more of a (n)mh thing, as opposed to a exmh thing.

For reasons I am NOT completely clear on, the authors of MH decided
a long time ago that sending what the rest of the world knows as a
Bcc was The Worst Thing Ever.  Okay, I'm exaggerating a bit, but they
were really dead set against it.  Their main objection, as far as I
can tell, is that when you send a "traditional" Bcc the Bcc recipient
doesn't necessarily know that they received a Bcc and could reply to
it and reveal that they received a copy.  That's why the MH Bcc sends
you a separate copy of the entire message, so someone that hits "reply"
won't reply to everyone.  This all originated in a pre-MIME universe, so
nowadays the odds are it's not so useful.

Now, solutions?  There are two obvious ones.  First, if you add the
-mime switch to send, you will use MIME encapsulation instead of the
default encapsulation (it will send someone a message/digest which
contains the original message as a message/rfc822).  This preserves the
original message MIME structure, and a compliant MIME mailer should
be able to handle this just fine.  Secondly, you can always use "Dcc"
instead of "Bcc", which will behave like the Bcc the rest of the world
uses.  Both of these things are actually documented, but are not widely
known (Dcc got added late in MH's life, and it seems like the author of
MH at the time added it only grudgingly).  In nmh we've just brought the
MH behavior forward.

We've occasionally talked about turning Bcc into Dcc, but there are some
people who prefer the original behavior, and changing functionality like
this in a non-backwards compatible way is hard.

--Ken


_______________________________________________
Exmh-users mailing list
Exmh-users@redhat.com
https://www.redhat.com/mailman/listinfo/exmh-users

Reply via email to