>>>>> "RS" == Russell Steinthal <rms39@columbia.edu> writes:
RS> Notifications (when a user subscribes, unsubscribes, etc.) are sent To:
RS> list-owner@domain and From: mj2@domain.
RS> Confirmation requests are sent From: list-owner@domain and don't
RS> contain a To: header.
That would be a bug, then. Everything sent to the list owner should show
To: list-owner@domain (or a CC, perhaps, but I'm not sure there's anything
there that needs it). If it doesn't, it should be fixed. Feel free to
point these out when they happen.
The From: may vary, depending on where a reply is supposed to go, I think.
It's actually not completely clear what should be in the headers. Should
CONFIRM and CONSULT messages come from mj2@domain or mj2-owner@domain? Can
we trust Reply-To: in the latter case to properly direct the reply?
But this is from the code that generates the confirmation requests:
$ent = build MIME::Entity
(
Path => $file,
Type => $file{'c_type'},
Charset => $file{'charset'},
Encoding => $file{'c_t_encoding'},
Filename => undef,
To => "$victim",
-From => $mj_addr,
'-Reply-To' => $mj_addr,
-Subject => "$token : $desc",
'Content-Language:' => $file{'language'},
);
so they do indeed have To: headers. List owner consultations don't,
though, and should more closely match what's above.
RS> I realize I could use separate regexes for each of those types of mail,
RS> but I'm curious if there's about the rationale for the difference?
RS> Backwards compatability? An RFC? Jason's whim? :)
Random chance; some code was just written to work. You'll find that the
confirmation stuff was written very early on and is thus most likely to
leave something out.
- J<
Follow-Ups:
References:
|
|
