-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "LM" == Leslie Mikesell <les@Mcs.Net> writes:
LM> In this case the message is clearly not the original author's
LM> submission and the headers can/should be modified.
If the moderator becomes the originator then his mailbox belongs in the
- From header, and what was originally there should be moved to the
Resent-From (I think) header. Regardless, *MAJORDOMO* is not the
originator, it is the agent responsible for final submission of the message
to the network.
[...]
LM> And to reverse your argument, if majordomo (as an agent of the list
LM> manager) isn't the reason I have this message, what is it?
Who Majordomo is accting for does not change the fact that it is acting for
someone. It clearly is not the originator of any list traffic and
therefore should not be doing anything with originator headers.
LM> You wouldn't have sent something to me were it not for the list so why
LM> shouldn't my reply be guided back the same way? However, this is silly
LM> semantics -
So RFC822 is nothing more than silly semantics?
LM> the real issue is where a 'normal' reply should go and I believe this
LM> depends on the nature of the list and the intent of it's manager.
No, a 'normal' reply goes to wherever the composer of that reply wishes.
Only he knows whether or not the message he is composing is relevant to the
list, and only he is in a position to do anything about where that message
is addressed.
LM> If it takes a modification of the message body and message ID to
LM> convince purists that a modification to the header is legal, so be it.
LM> Consider it a digest form where the digest is composed on every single
LM> message.
A digest is a new message, and if you note carefully Majordomo puts one of
its mailboxes in the originator header when it sends out a digest.
LM> There are lists that work this way, and from an end user viewpoint I
LM> prefer them at least for technical topics where you are unlikely to
LM> send something personal to the list by mistake. The question is, how
LM> do those lists avoid problems with mail loops caused by forwarding
LM> through transports that only understand a single return address?
Because the mailbox in question is the list owner's mailbox (alias), not
the list itself.
-----BEGIN PGP SIGNATURE-----
Version: 4.0 Business Edition
Charset: noconv
iQCVAwUBM5LUep6VRH7BJMxHAQF5vgP+L52Iw3qgN4hJwuu+QP6yvIx9AFWXYk/F
SzTAlst6c928pQZX5J+Z6S0xKYZNuXFuGpeL8Cxdunw7QDc2XRyQN/Uvhun8cood
gbjKLdXRvs52+uTiHJyhHYDfMOXsJND8lWFjCGbjGfEh5Po0cJ/QlIiTs2ZsIOlU
cxibOU92RZw=
=n1uV
-----END PGP SIGNATURE-----
--
Rich Pieri <rich.pieri@prescienttech.com> | Happy Fun Ball contains a liquid
Prescient Technologies, Inc. | core, which, if exposed due to
A Stone & Webster Company | rupture, should not be touched,
I speak for myself, not PTI or SWEC | inhaled, or looked at.
Follow-Ups:
References:
|
|
