Bug 63842
Summary: | Subject line mangling is turned on by default. | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | David Woodhouse <dwmw2> |
Component: | mailman | Assignee: | John Dennis <jdennis> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.2 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-03-13 23:05:27 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
David Woodhouse
2002-04-19 11:45:47 UTC
Defaults are in the realm of religion, some people like the default the way it is. My general inclination as a package maintainer is not to change the upstream sources unless there is a compelling reason and the upstream sources have this on by default. Given that it is trival to change the default in mm_cfg.py to your own individual preference its hard for me to see the choice of a default as a bug. As it turns out I'm in your camp, I happen not to care for this default either, its just that this isn't a bug IMHO. BTW, mailman now adds List-Id to the headers which is an excellent way for users to filter. I'll accept the argument that we shouldn't change the default, albeit grumpily -- leaving it on by default means that admins who _don't_ think about it will leave it on, rather than only those who are dim enough to actually think it's a good idea. But I certainly wouldn't advocate filtering on List-ID. That has false positives when a mail _originally_ sent via a list is received via other means -- either by _another_ list which doesn't add its own List-ID or more likely if an important mail is bounced _directly_ to a recipient known not to be paying much attention to the list at the moment. If I know you're on vacation and you're going to read the list with the 'd' key on your return, and I see a mail on the list and hit 'b' in pine to bounce it to you so it ends up in your inbox and you actually _see_ it... Does it end up in your inbox and actually get read, or does it hit a false positive because you're filtering on List-ID: and still end up in the list folder with the original? The only reliable filtering method that I've found is the SMTP reverse-path, usually in a 'Return-Path:' header of the delivered mail. |