ietf-822
[Top] [All Lists]

Re: best name for followups?

1997-07-15 08:44:50
On Tue, 15 Jul 1997 11:03:05 +0200, Keld J|rn Simonsen said:
Of cause you cannot do it in that case, but if you see 
for example my address on the explicit From: or To: list, and later 
see the same address in the list data, you can avoid sending the latter.

Hmm.. I see Keld, I see Bart, I see Keith, I see some guy named ietf-822.
I certainly don't see 'keld' *inside* the ietf-822 list, since I don't expand
it.

On Tue, 15 Jul 1997 10:42:56 +0200, Keld J|rn Simonsen said:
What if the author isn't a subscriber? Now you've eliminated him from
the recipient list. What if he wanted to receive a copy?
Then you use the reply-all

This doesn't work if you don't have a *clue* who is on the list.  Citing
the mail for ietf-822 in the last few days (or rather, some that's in that
folder), I know I'm on the list, I can be pretty sure that Keld Simonsen,
D.J. Bernstein, and Keith Moore are on the list.  However, I posted a note
last week about "some vendors just don't get it", and I have *no* idea if
Doug Strauss and Larry Osterman (both of Microsoft(*))  are on the list, or
were merely forwarded a copy of my mail.

In any case, there's something that everybody has overlooked (perhaps
intentionally as a "we don't need to bother", or intentionally because
it's a can of worms, or just oversight ;)

What is the desired behavior if person A posts to a mailing list, and person
B follows up, etc etc - and then person G replies to F, trims out persons
A through E, and does a *BCC:* to the mailing list? (or vice versa - sending
to the list, and a bcc: to the author because his list membership is unknown)

                                Valdis Kletnieks
                                Computer Systems Senior Engineer
                                Virginia Tech

(*) Incidentally, the people at Microsoft were quite helpful in tracking
down when/how the bug I commented on originated, and I assume that it
is being chased down by their software teams.

Attachment: pgpcAB3Dxup0s.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>