Thus said Richard Hipp on Sat, 21 Feb 2015 13:07:46 -0500: > Yes. We moved the mailing list server to a different IP address > (because it wants to use Apache and we are running a different web > server on port 80 of the machine that was hosting the mailing list.) > This involved giving it a new domain name.
The new configuration has introduced another unforseen anomaly. Some MUAs are sending replies to two mailing lists, which results in two deliveries of the same message (though not identical because they have different headers from different mailing lists) to subscribers. Mutt, for example, is sending a copy to both fossil-dev@mailinglists.sqlite.org and fossil-...@lists.fossil-scm.org. Your response to which I am currently responding was delivered to my server 2 times. I'm not sure why, but it's possible that it is picking up one from the To header and one from the Reply-to header (and they are different). I don't know if Mutt will look at the List-post header. So here is a typical concoction of headers that come from a message sent to the list: List-post: <mailto:fossil-dev@mailinglists.sqlite.org> To: fossil-...@lists.fossil-scm.org Reply-to: fossil-dev@mailinglists.sqlite.org Reply-to-all to this will result in a recipient list that includes both fossil-...@lists.fossil-scm.org and fossil-dev@mailinglists.sqlite.org. Anyway, just thought I would bring it to your attention. Andy -- TAI64 timestamp: 4000000054eeac82 _______________________________________________ fossil-dev mailing list fossil-dev@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev
