On 16.01.16 20:37, Russell Coker wrote:
On Sat, 16 Jan 2016 08:00:49 PM Erik Christiansen via luv-main wrote:
If that is the goal, do we not evilly abuse it by using it to ensure that list members _cannot_ have a genuine From: field? The reason that mutt's ~(~P) pattern no longer identifies my posts is that the header munge munges them as authored by the list server. Faking the From: field is what spammers do, innit?
The user visible From field is to tell the user where the message came from. In this case it came from a mailing list. The list server verifies the message it receives, processes it, and sends a new message out. One could argue that Mailman should create a new Message-ID when doing so, but it is convenient to have the same Message-ID through the process.
One can argue any kind of nonsense. The need to rationalise an unpopular and broken munge is understandable motivation. I know of no other list which inflicts similar pain on list members - and certainly do not experience such disservice on other lists. It is irrational to pretend that my posts come from the list server - an internet host which is merely one of several servers through which our posts flow. In properly administered servers, the flow is more transparent. If you screwed with the Message-ID too, I think it would be time to unsubscribe. I suggest that you have lost the plot. You have still not informed us why you insist on denying list members a genuine From: field, merely to grant the same to others. (My understanding is that it is because you have not found a workable solution to some other minor issue, so you've created a bigger problem.) Erik