<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:large">Looks like I missed the forum discussion of the comcast/systemd-resolve problem:<br></div><div class="gmail_default" style="font-size:large"><a href="https://ubuntuforums.org/showthread.php?t=2406399">https://ubuntuforums.org/showthread.php?t=2406399</a></div><div class="gmail_default" style="font-size:large">Launchpad bug 1805027 (and maybe 1804487).</div><div class="gmail_default" style="font-size:large">Ken<br></div></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 15, 2018 at 8:34 PM Ken Shaffer <<a href="mailto:kenshaffer80@gmail.com">kenshaffer80@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-size:large"><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Sat, Dec 15, 2018 at 8:56 AM Akkana Peck <<a href="mailto:akkana@shallowsky.com" target="_blank">akkana@shallowsky.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Ken Shaffer writes:<br>
> Anyone else having email problems? Last month, systemd on my Ubuntu 18.04<br>
> stopped resolving <a href="http://mail.comcast.net" rel="noreferrer" target="_blank">mail.comcast.net</a>. No known changes on my part, not even<br>
> an update, it just stopped working, but none of the other sites I visit had<br>
<br>
Comcast apparently recently changed the name of the server people<br>
need to use for email. I haven't been paying strict attention (even<br>
if I had Comcast service, they've caused enough email problems with<br>
things like bogus spam rejection that I wouldn't use them for my own<br>
email -- seems like I'm always dealing with issues like "I'm not<br>
getting email from the XYZ list to my Comcast address"); but my<br>
impression is that the preferred hostnames to use for mail changed<br>
at some point (perhaps long ago) and the grandfathered older server<br>
people have been using up to now is being gradually retired,<br>
starting with not renewing its cert.<br>
<br>
This thread might have some helpful information:<br>
<br>
<a href="http://lists.nmglug.org/pipermail/nmglug-nmglug.org/2018-December/004909.html" rel="noreferrer" target="_blank">http://lists.nmglug.org/pipermail/nmglug-nmglug.org/2018-December/004909.html</a><br>
<br>
and in particular these messages:<br>
<a href="http://lists.nmglug.org/pipermail/nmglug-nmglug.org/2018-December/004924.html" rel="noreferrer" target="_blank">http://lists.nmglug.org/pipermail/nmglug-nmglug.org/2018-December/004924.html</a><br>
<a href="http://lists.nmglug.org/pipermail/nmglug-nmglug.org/2018-December/004926.html" rel="noreferrer" target="_blank">http://lists.nmglug.org/pipermail/nmglug-nmglug.org/2018-December/004926.html</a><br>
<br>
but read the whole thread since there might be other relevant info.<br>
<br>
...Akkana<br></blockquote><div><span class="gmail_default" style="font-size:large">Thanks Akkana,</span></div><div><span class="gmail_default" style="font-size:large">Your third link had a link to the current comcast recommendations, which include using <a href="http://pop3.comcast.net" target="_blank">pop3.comcast.net</a> instead of <a href="http://mail.comcast.net" target="_blank">mail.comcast.net</a>,</span></div><div><span class="gmail_default" style="font-size:large">and port 587 instead of the alternate 465 for smtp. I tend to just copy the old setup, and after a few years, things do change, so checking back to the source is recommended.<br></span></div><div><span class="gmail_default" style="font-size:large"> Not that the existing server/port setup didn't work in evolution when using the /run/systemd/resolve/resolv.conf link for /etc/resolv.conf. Or that the changes fixed anything in getting the 127.0.0.3 nameserver to work (from the /run/systemd/resolve/stub-resolv.conf link).</span></div></div><div class="gmail_quote"><br></div><div class="gmail_quote"><div style="font-size:large" class="gmail_default">The error from evolution when trying to get/send mail was:</div><div style="font-size:large" class="gmail_default"> Error while Fetching mail from ...@<a href="http://comcast.net" target="_blank">comcast.net</a><br> Error resolving "<a href="http://mail.comcast.net" target="_blank">mail.comcast.net</a>": Name or service not known<br></div><div style="font-size:large" class="gmail_default">In a big orange banner across the evolution window<br></div></div><div class="gmail_quote"><br></div><div class="gmail_quote"><div style="font-size:large" class="gmail_default">(Well, after the changes, the error was ..."<a href="http://pop3.comcast.net" target="_blank">pop3.comcast.net</a>"... )</div><div style="font-size:large" class="gmail_default"><br></div><div style="font-size:large" class="gmail_default">I didn't notice anything odd running nslookup or systemd-resolve when I reset the /etc/resolv.conf to the stub-resolv.conf.</div><div style="font-size:large" class="gmail_default">Anyway, redirecting the link works for me, as a minimal change to the system -- a solution which is frequently suggested on google for dns problems. <br></div><div style="font-size:large" class="gmail_default">Ken<br></div><br><div style="font-size:large" class="gmail_default"><br></div><div style="font-size:large" class="gmail_default"></div><br></div><div class="gmail_quote"><br></div></div></div></div></div>
</blockquote></div>