>>>>> "OX" == Oliver Xymoron <oxymoron@waste.org> writes:
OX> Not true in general - imagine a subject marker "foo" - shall we remove
OX> that from all subject lines?
Duh, now I see what you mean. Yes, that is a problem, but it's mostly
solved by making the prefix odd enough. How often does "[Prefix]:" appear
on a regular message when it's not really the prefix? (And even if it did
appear, I probably wouldn't mind having it stripped anyway.)
OX> Hmmm... bouncing is one solution, but the solution of modifying the
OX> headers is probably preferable sometimes.
If I send a message somewhere and it does somewhere else (or at least, to
some places and not others) and I'm not informed about it, I'm going to get
pissed. But that's just me; I generally try to make sure I know where I'm
sending messages. Lots of people don't.
OX> The problem arises when user-b only on list-2 replies without editing
OX> the header, and leaves the list-1 owner to decide whether to approve
OX> it, if the list bounces non-member submissions.
Were I such a list owner, I would simply send to the bit bucket (using an
access rule, of course) any crossposted message to my closed list.
However, I can see the utility for something like this and I'd be
interested to know what you come up with.
One first approximation to this is to add To: and CC: to skip_headers
(which is now a per-list config variable instead of a hardcoded string in
resend) and add To: list-name to message_headers. Of course, this removes
legitimate CC's, perhaps to people who aren't members. It does have some
utility, however.
- J<
Follow-Ups:
References:
|
|
