Re: current_at_ and freebsd-current_at_

On Thursday 01 December 2005 03:28 pm, Matthew D. Fuller wrote:
> On Thu, Dec 01, 2005 at 11:59:41AM -0500 I heard the voice of
>
> Chuck Swiger, and lo! it spake thus:
> > I've asked postmaster_at_ about this, and there are mechanisms in place
> > which are supposed to merge the two names to avoid duplicate
> > postings, but some messages seem to get missed.
>
> Interestingly enough, there seems to be a pattern to it.  All the
> places where somebody starts duplicating happen when somebody (a) is
> using KMail, and (b) replies to a message to 'current_at_' (never to
> freebsd-current_at_), it will set the To: to freebsd-current_at_, and leave
> current_at_ in the CC list.  It doesn't happen every time those
> conditions are met, especially if current_at_ is sandwiched somewhere
> among other headers.  Rather odd; maybe some "list reply" sort of
> feature in KMail?  jhb seems to get bitten by it with some regularity.

Yes, KMail parses the List-XXX headers that mailman sticks in messages to 
figure out that when you reply to a list message it should use the list post 
address for To:.  Unfortunately, there is now way to turn this "feature" off 
and when I submitted a bug report about it to KDE asking for the feature to 
be toggleable the KMail developers basically told me to piss off.  Instead of 
a simple on/off toggle, they supposedly are going to add (though I haven't 
seen it yet) a know so that for any given mailing list you can configure 
alias addresses, but that type of thing doesn't scale well when you have 20+ 
mailing lists and have to duplicate it on N different machines. :(  If only 
Mail.app would do actual trees of message threads.

-- 
John Baldwin <jhb_at_FreeBSD.org>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org