On Thu, Nov 29, 2012 at 01:06:30PM -0800, Michael Elkins wrote:
> On Thu, Nov 29, 2012 at 04:37:23PM +0000, Chris Green wrote:
> >On Thu, Nov 29, 2012 at 11:23:56AM -0500, Patrick Shanahan wrote:
> >>* Chris Green <[email protected]> [11-29-12 11:08]:
> >>> I have been trying to work out for a while why I sometimes send two
> >>> copies of some messages to mailing lists.  I finally worked out why, the
> >>> L[ist reply] command will send to any address which is like:-
> >>>
> >>>     List-Post: <mailto:[email protected]>
> >>>
> >>> *as well as* any message that matches the name found in the subscribe
> >>> and/or lists commands in muttrc.
> >>>
> >>> Is there any way to disable the use of the List-Post: entry, or any way
> >>> to prevent mutt from sending to two addresses?
> 
> List-Post is always used when the list-reply function is invoked.
> There is not configuration option to disable that.
> 
> >It's not my .muttrc, it's just one list that I subscribe to which has
> >two addresses.  Only one address ever appears in List-Post: but the
> >alternative address sometimes appears in To: or Cc: headers, thus there
> >can be messages with the following:-
> >
> >   List-Post: <mailto:[email protected]>
> >   Cc: [email protected]
> >
> >Since I have [email protected] in 'subscribes' and 'lists' mutt will
> >reply to *both* [email protected] and [email protected]
> >when I hit L[ist reply].
> 
> Mutt doesn't have any way for the user to let it know about mailing
> list aliases, so when you invoke list-reply it pulls out all
> addresses which match, along with List-Post.
> 
> >I *think* I may be able to fix the problem by removing [email protected]
> >from subscribe/lists but it's not ideal because I also need to know that
> >messages sent to [email protected] are messages to the list.
> >
> >What I was really complaining about was that mutt uses the List-Post:
> >header and that this *isn't* as documented.
> 
> http://dev.mutt.org/trac/ticket/3599

Thanks for that, it at least shows I'm not completely silly! :-)

-- 
Chris Green

Reply via email to