On 20.09.11 18:45, Jason White wrote:
I just realized (too late, unfortunately) that Mutt's reply to list feature is now generating a "To" field like this: luv-main@lists.luv.asn.au, luv-main@luv.asn.au
I think the cause may be this header in messages distributed via the list: List-Post: <mailto:luv-main@lists.luv.asn.au> whereas the "To" header gives luv-main@luv.asn.au as the address.
But isn't that just due to an OP to the old list domain being accepted? If the list server is using different domains in the two headers, then this post, to the new domain only, will incur the effect. Let's see. Still, it's only harmless untidiness, since only one copy of the post appears on the list. Erik -- ... implementations should follow a general principle of robustness: be conservative in what you do, be liberal in what you accept from others. -Jon Postel, RFC 761