Subject:
|
Re: Lugnet.robotics and the Robotics List
|
Newsgroups:
|
lugnet.admin.general
|
Date:
|
Thu, 17 Dec 1998 18:50:17 GMT
|
Viewed:
|
888 times
|
| |
|
|
Alex Wetmore <alex@phred.org> writes:
> [...]
> Finally, I would like to use this time to bring up one oddity in the way
> that lugnet had the lugnet.robotics group setup. It puts Reply-To headers
> into the messages, while the lego-robotics list does not. This is annoying,
> because if one isn't paying attention then they'll find private emails going
> back to the group. I would like it to at least be consistent with the
> mailing list, and in the best case I'd like to see the Reply-To's not put in
> there by lugnet. Is there a reason why they are there?
Hmm, perhaps in the case of gatewayed messages going out (i.e., gatewayed
out of the lugnet.robotics newsgroup into the lego-robotics mailing list,
or out of the lugnet.loc.us.ca.sf newsgroup into the ba-lego mailing list),
the Reply-To field could be set to the original From field before the From
field is munged. For example, the NNTP headers
Newsgroups: lugnet.robotics
From: Rutherford Snickerfritz <rsnicker@foofoo.com>
could become the SMTP headers
To: lego-robotics@crynwr.com
From: lugnet.robotics@lugnet.com (Rutherford Snickerfritz)
Original-From: Rutherford Snickerfritz <rsnicker@foofoo.com>
Reply-To: Rutherford Snickerfritz <rsnicker@foofoo.com>
Bcc: lego-robotics@crynwr.com
Would that be better?
(Currently, only To, From, and Original-From are set as shown above, while
Reply-To is currently always set to the address of the mailing list.)
Note that if Reply-To isn't set, the default action will be to reply to
lugnet.robotics@lugnet.com, which is worse than explicitly setting the reply
to go to lego-robotics@crynwr.com for people subscribing via lego-robotics.
Also note that the From field has to be munged so that it shows the message
as coming from lugnet.robotics@lugnet.com with the user's name in SMTP
header comments (parens), otherwise the lego-robotics listserver will reject
messages from people it doesn't recognize.
--
The reason the Reply-To field is ever set at all is because the news-by-mail
gateways which convert news to mail and vice versa have been carefully set
up to mimic newsgroup interactions as closely as possible -- meaning that
the NNTP Followup-To header is maps to the SMTP Reply-To header.
For example, the NNTP headers
Newsgroups: lugnet.announce
Followup-To: lugnet.general
From: Rutherford Snickerfritz <rsnicker@foofoo.com>
become the SMTP headers
To: lugnet.announce@lugnet.com
From: lugnet.announce@lugnet.com (Rutherford Snickerfritz)
Original-From: Rutherford Snickerfritz <rsnicker@foofoo.com>
Reply-To: lugnet.general@lugnet.com
Bcc: ...recipient...
Bcc: ...recipient...
Bcc: ...recipient...
In other words, the Reply-To field is set to lugnet.general so that someone
receiving by mail and replying to a message posted to lugnet.announce will
properly send that reply to lugnet.general and not to lugnet.announce.
So that's the rationale of Reply-To in the lugnet.* news-to-mail gateways.
It could certainly be tailored differently/specially for messages going out
to external mailing lists like lego-robotics and ba-lego without changing
the core dynamics for regular direct news-by-mail subscribers.
--Todd
|
|
Message has 1 Reply:
 | | Re: Lugnet.robotics and the Robotics List
|
| Todd Lehman wrote in message <36794b80.31897794@l...et.com>... (...) I'd have to experiment and see what happens if a user does a reply to all in that case. If it sends to the people in the Reply-To header as well as the To header then it would work (...) (26 years ago, 17-Dec-98, to lugnet.admin.general)
|
Message is in Reply To:
| | Re: Lugnet.robotics and the Robotics List
|
| Linc Smith wrote in message ... (...) list (...) I read via the mailing list instead of via lugnet for a couple of reasons: 1) My email comes in via IMAP, where my news doesn't. IMAP keeps my read/unread status on the server, which means that I can (...) (26 years ago, 17-Dec-98, to lugnet.admin.general)
|
8 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
