* Adeodato Simó <asp16@xxxxxxxxx> [2004-08-05 12:43+0200] > I recently hit 'L'ist-reply on a message from a mailing list, saw in the > To field two forms of the list address. Investigating, I found that the > message I replied to had the following headers: > > To: darcs-devel@xxxxxxxxxxxxxxx > List-Post: <mailto:darcs-devel@xxxxxxxxxxxxxxxxxxx> > > My mutt configuration has > > lists darcs-devel@ > > So 'L'ist-reply replied to both the To and List-Post addresses. > > Many lists are aliased by multiple addresses, so I don't think this case > can be written off as a list misconfiguration. However, I don't know > how to resolve it. One idea would be to note that both addresses are > matched by the same lists entry, but I'm not sure that is reliable in > general. > > Supporting the List-Post header sounds admirable, but the overlap with > the existing mailing list features is confusing. Moreover, it is less > powerful than the existing features, since it cannot help with a message > cross-posted to multiple lists (there will be only one List-Post > header). Maybe List-Post should only be used if no mailing lists are > found via the lists and subscribe features? List-Post should only add potential recipients. So it only would harm if it adds garbage. Maybe a quad-option needs to be added about whether List-Post headers should be considered or not when preparing a reply message. This seems to simplest way to deal with this, especially as you can then use hooks to tune the behavior. Cheers, Hugo -- Hugo Haas - http://larve.net/people/hugo/
Attachment:
signature.asc
Description: Digital signature