With some editing (mostly order, unnecessary parts of the header and an intervening step at Comcast):
Date: Mon, 5 Nov 2018 16:26:52 -0600 (CST)
X-Received by resomta-ch2-14v.sys.comcast.net with ESMTPS; Mon, 05 Nov 2018 22:26:52 +0000
X-Received by mta4002.groups.mail.bf1.yahoo.com with SMTPS; Mon, 05 Nov 2018 22:26:53 +0000
X-Received by mtaq6.grp.bf1.yahoo.com with SMTP; 5 Nov 2018 22:26:53 -0000
X-Received by m11.grp.bf1.yahoo.com with SMTP; 5 Nov 2018 22:28:07 -0000
So, it took about one second to get from Comcast to Yahoo, then a little over a minute to get to that next step there, and then...
Received: from sonic.gate.mail.ne1.yahoo.com by sonic324.consmr.mail.gq1.yahoo.com with HTTP; Tue, 6 Nov 2018 01:44:03 +0000
.... over three hours to get to the mail gateway? Then another two minutes *exactly* (which makes me wonder if one or the other's clocks are just off that way) to get back to Comcast. Well, you know what my vote's likely to be. Or will in three hours...
Then again, there's the old adage, you get what you pay for. Yahoo may have been capable of dealing with mailflow two decades and who-knows-how-many companies ago, but maybe they just can't anymore.
>On November 5, 2018 at 4:26 PM Joel Fischoff wrote:
>>if this group does move, please leave instruction to people like me that
>>may not know how to get to the new location.
>It's been a while since I transferred a group to groups.io, but if I
>remember correctly, it will transfer the entire mailing list, with the
>possible exception of anyone who is currently bouncing. So long as
>you're not bouncing, you should just start getting messages from the
>new list.
>That said, it would probably just require updating the various web
>presences with the new address.
Posted by: Joel Fischoff <petrukio@comcast.net>
| Reply via web post | • | Reply to sender | • | Reply to group | • | Start a New Topic | • | Messages in this topic (25) |
No comments:
Post a Comment