Re: [Mailman-Developers] How to remove X-Confirm-Reading requests from mail headers distributed by Mailman?
If you want something done, and there isn't anyone who has the time, skills or inclination to do it for you, then you either knuckle down and
And how could I know that there isn't anyone, huh?
do it yourself, or forget about it. You don't keep hounding someone else to do it.
You are rude. Look what you've just written. You seem to have contempt for users of the program, and that's a very bad thing. Is the mailman for the users or the users for the mailman? There are developers, and users, users can make their wishlist, and developers could see what they can do. If someone can do a patch himself, that's good, but if someone cannot, then telling him to shut up, because he cannot do it himself is just rude and silly.
ak
Guys --
Can we please drop this? It's been beaten into the ground. I don't think the mailman development crew has shown itself well here, either, especially Brad, who seems to be grumpy beyond the needs of the discussion for some reason. I don't think we as a team managing an open source project look good right now, it wasn't handled particularly professionally, IMHO.
and for the record, I tend to disagree with Brad -- I definitely see it as useful to be able to strip out headers that cause systems to auto-reply with a return receipt. but since those headers aren't really standardized, it's not as simply as flipping a switch. what I might do, stepping back a couple of steps and looking at it somewhat objectively, is to consider an option that simply strips all non-RFC headers from a message.
But I'm rather surprised to see us blowing off someone's privacy concerns here in the heat of whatever grumpiness people brought to the discussion the last couple of days, and especially doing it as members of the Mailman team the way we did. All of the points made are relevant, the way they were made was, well, IMHO less than optimal.
so maybe we should all shut up and let this cool off. Maybe reconsider the idea once the emotion's drained a bit. But right now, we're not doing anyone any good on anything.
On Apr 4, 2004, at 2:01 PM, Chuq Von Rospach wrote:
Can we please drop this? It's been beaten into the ground. I don't think the mailman development crew has shown itself well here, either, especially Brad, who seems to be grumpy beyond the needs of the discussion for some reason. I don't think we as a team managing an open source project look good right now, it wasn't handled particularly professionally, IMHO.
so maybe we should all shut up and let this cool off. Maybe reconsider the idea once the emotion's drained a bit. But right now, we're not doing anyone any good on anything.
Thank you Chuq. That's pretty much what I was thinking.
*I* think stripping headers could be a useful feature, and I can even see in my head how I'd go about putting that into the admin interface. But since I think writing more documentation is more useful, that's where my time's going to go. (Even though writing that code is more fun to me than writing admin documentation.)
Now that the idea's out there (it has been put into the wiki, right?), it'll be implemented if someone interested has the time, inclination, and expertise, and it'll be accepted if the patch is appropriate. No point in trying to force people to volunteer their time if they're not ready yet, and no point in shoving the idea into the ground when it's clearly useful to someone, and might be useful to more people in the future. Who knows -- a few months from now, we may find out that flocks of people want it, and then more people will be willing to put the time into implementation. Or a few months from now, no one else will have wanted it in Mailman because they'll have found something else better suits their needs, and the idea will die.
Terri
On 2004-04-04 at 11:01:22-07 Chuq Von Rospach <chuqui@plaidworks.com> wrote:
I definitely see it as useful to be able to strip out headers that cause systems to auto-reply with a return receipt.
IMHO, this statement can be shortened to "I definitely think it would be useful to strip out arbitrary headers."
Case in point: we use SpamAssassin to analyze and tag incoming email (meaning, email received from external sites). All scanned messages receive an "X-Spam-Status" header; messages which scored as probable spam also receive an "X-Spam-Level" header. This permits mailing list owners to add this bounce_matching_headers rule:
x-spam-level: \.But we'd like to have these headers removed when the message is distributed to the members of the list.
While I can strip those headers at the MTA level (the combination of sendmail + MIMEDefang is a wonderful thing), it can be tricky to do it correctly. I think it would be cleaner to strip them from within Mailman.
If, at some point in the future, I feel that my Python skills are up to the task, I'll probably take a crack at implementing something like this. But until then (or until someone else beats me to it), I think it's definitely a good idea.
-- James Ralston, Information Technology Software Engineering Institute Carnegie Mellon University, Pittsburgh, PA, USA
On Wed, 2004-04-28 at 12:23, James Ralston wrote:
On 2004-04-04 at 11:01:22-07 Chuq Von Rospach <chuqui@plaidworks.com> wrote:
I definitely see it as useful to be able to strip out headers that cause systems to auto-reply with a return receipt. IMHO, this statement can be shortened to "I definitely think it would be useful to strip out arbitrary headers."
I agree too, so here's a patch for my first attempt at it:
https://sourceforge.net/tracker/index.php?func=detail&aid=957054&group_id=103&atid=300103
-- Colin Palmer <mailmandev@waikato.ac.nz> University of Waikato
participants (5)
-
Andrzej Kasperowicz -
Chuq Von Rospach -
Colin Palmer -
James Ralston -
Terri Oda