nmh-workers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Nmh-workers] Re: 1.3 release and Dcc/Bcc behaviour


From: Bill Wohler
Subject: [Nmh-workers] Re: 1.3 release and Dcc/Bcc behaviour
Date: Sun, 08 Apr 2007 21:01:02 -0700
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.97 (gnu/linux)

Peter Maydell <address@hidden> writes:

> Robert Elz wrote:
>>    From:        Joel Reicher <address@hidden>
>>  | I get the feeling this might be catching many people, and my preference
>>  | would be to put "-msgid" in the defaults for "send".
>>
>>I might too (see below for possibly why not), if MH were just being released
>>now - but this kind of change to default options is a really annoying thing
>>to have happen.
>
> I agree with this point -- by now almost the only people who are using
> nmh will be long-time users, I expect, and it would be rude to break their
> existing setups like this. I think the best thing we could do would be to
> document a sort of "best practice" configuration, and perhaps arrange
> for install-mh to set new users up that way.

My view is that not having a Message-Id in your +outbox messages is a
lot more broken than having a sub-optimal Message-Id. The chance of it
being broken (being non-unique) is non-zero, but damn near. So,
"breaking existing user's setups" is a bit strong.

While having install-mh add a send: -msgid component is a good idea,
it isn't enough. It doesn't help the folks like me that ran install-mh
back in 1985 and only found out on 2003-04-23 about the -msgid option,
cursing the absence of a Message-Id in my outbox all the while.

One thought is to roll out a version 2 and document it loudly.

-- 
Bill Wohler <address@hidden>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD





reply via email to

[Prev in Thread] Current Thread [Next in Thread]