Gnus development mailing list
 help / color / mirror / Atom feed
From: dreschs@mpd.tandem.com (Sten Drescher)
Subject: Re: [sgnus 0.18] gnus-summary-resend-message and mail-self-blind
Date: 06 Dec 1995 11:57:24 -0600	[thread overview]
Message-ID: <55ybsqkrcr.fsf@galil.austnsc.tandem.com> (raw)
In-Reply-To: davidk@lysator.liu.se's message of 05 Dec 1995 23:27:07 +0100

davidk@lysator.liu.se (David K}gedal) said:

dreschs@mpd.tandem.com (Sten Drescher) writes:
SD> I have mail-self-blind set, so that I get a BCC: to myself.  Well,
SD> when I use gnus-summary-resend-message, it ends up with a
SD> Resent-BCC: field.  I want the BCC: field either 1) left alone, or
SD> 2) stripped off, since that's the whole point of _B_CC:.  I'd prefer
SD> the first, because with certain resends, it will result in the mail
SD> also going to my other account, but I'll settle for the second.  Any
SD> ideas?

DK> The patch I sent to the list earlier today takes care of not putting
DK> Resent-BCC: in the mail.

	Actually, we may both be taking the wrong tack at this problem.
>From RFC 822:

RFC822> 4.5.  RECEIVER FIELDS

RFC822> 4.5.1.  TO / RESENT-TO

RFC822> This field contains the identity of the primary recipients of
RFC822> the message.

RFC822> 4.5.2.  CC / RESENT-CC

RFC822> This field contains the identity of the secondary
RFC822> (informational) recipients of the message.

RFC822> 4.5.3.  BCC / RESENT-BCC

RFC822> This field contains the identity of additional recipients of the
RFC822> message.  The contents of this field are not included in copies
RFC822> of the message sent to the primary and secondary recipients.
RFC822> Some systems may choose to include the text of the "Bcc" field
RFC822> only in the author(s)'s copy, while others may also include it
RFC822> in the text sent to all those indicated in the "Bcc" list.

	Based on this, I think that Resent-BCC: is appropriate.  Now
what I'm not clear on is _what_ is responsible for handiling the
destination - does Gnus/Emacs call sendmail with explicit delivery
addresses, or does sendmail pick out the Resent- headers and use those?
Looking at the sendmail guide for v8.7, it looks like sendmail _should_
be doing the work, but may not.  Anyone more versed in SMTP
implementation reading this?

		Sten

-- 
#include <disclaimer.h>				/* Sten Drescher */
To get my PGP public key, send me email with your public key and
	Subject: PGP key exchange
Key fingerprint =  90 5F 1D FD A6 7C 84 5E  A9 D3 90 16 B2 44 C4 F3


  reply	other threads:[~1995-12-06 17:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-12-05 21:10 Sten Drescher
1995-12-05 22:27 ` David K}gedal
1995-12-06 17:57   ` Sten Drescher [this message]
1995-12-08  8:10     ` Lars Magne Ingebrigtsen
1995-12-08 17:27       ` Sten Drescher
1995-12-08 20:37       ` Jack Vinson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55ybsqkrcr.fsf@galil.austnsc.tandem.com \
    --to=dreschs@mpd.tandem.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).