> On Dec 4, 2017, at 8:05 AM, Derek Atkins <[email protected]> wrote: > > John Ralls <[email protected]> writes: > >> I've got a better and even weirder reason to prefer >> [email protected]: When I send mail to >> [email protected] and route the mail through comcast.net >> (my ISP) the mail bounces because the terminal comcast >> mail server won't talk to lists.gnucash.org. It's perfectly happy to >> talk to gnucash.org even though it's the same computer (the one we >> fondly refer to as "code"). That means I always have to check the CC >> when I reply-all to make sure it's the right address. > > This is weird. I see no reason why this would be the case. In fact, > gnucash.org has an MX record pointing to lists.gnucash.org, which > implies it's sending to the same machine either way. > > I suppose we could try adding an MX for lists pointing to itself?
Yeah, no argument that it’s weird. Sending this to lists.gnucash.org <http://lists.gnucash.org/> to make sure and to capture the error. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
