On Mon, Aug 01, 2005 at 07:33:03PM -0500, David Champion wrote:
> A totally different workaround I considered was to add a tiny chunk of
> code to parse.c:mutt_read_rfc822_header(), right before the RFC2047
> parsing.
>
> diff -ru mutt-1.3.8-dist/parse.c mutt-1.3.8/parse.c
> --- mutt-1.3.8-dist/parse.c Tue Aug 22 16:26:25 2000
> +++ mutt-1.3.8/parse.c Sun Sep 10 23:38:50 2000
> @@ -1288,6 +1288,9 @@
>
> FREE (&line);
>
> + if (!e->to && !e->cc)
> + e->to = rfc822_parse_adrlist(NULL, "Undisclosed-recipients:;");
> +
> if (hdr)
> {
> hdr->content->hdr_offset = hdr->offset;
>
> This would ensure that messages with no To: or Cc: ever occur, and suits
> me fine for display purposes. I was never sure how comfortable I was
> with modifying the messages for write-back, though.
I'm very much in favor. I frequently want to send mail to a gaggle of
people without everyone being able to see everyone else's e-mail
address. My current work-around has been to just send it to myself...
but that's just annoying.
--
Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02
-=-=-=-=-
This message is posted from an invalid address. Replying to it will result in
undeliverable mail. Sorry for the inconvenience. Thank the spammers.
Attachment:
pgpKEnujhGl3V.pgp
Description: PGP signature