Hi all!
New user of Ubuntu-Mate. I am having difficulties with getting Evolution to work with my Comcast mail accounts. They worked in my previous install, however! they do not work now. Also, I am unable to edit changes in the account options. Well, I cannot find a way to insert a picture. so I get a message that says “Error resolving “mail.comcast.net”; Temporay failure in name resolutiom.”
https://www.xfinity.com/support/articles/email-client-programs-with-xfinity-email shows you how to configure mail for comcast. I do not see a host named mail.comcast.net (I see imap, pop3, smtp) Try to reconfigure evolution with those settings. I don’t have comcast, just trying to help.
Hi Pavlos,
Thanks for the help but the settings that have worked for years on my old LMDE install are not working. and no matter what the setting I get the same old message:
Error while Fetching mail from “-------------@comcast.net”.
Error resolving “mail.comcast.net”: Temporary failure in name resolution
See launchpad bug 1805027, and add yourself to the “Does this affect me?” list by clicking on the nearby yellow icon. Underlying problem may be bug 1804487. Some terminal programs may show the problem too, right now ping fails, but nslookup works for me. Easy workaround, cut systemd-resolvd out of the lookup by simply redirecting the /etc/resolv.conf link from /run/systemd/resolve/stub-resolv.conf to /run/systemd/resolve/resolv.conf (which in my case changes the nameserver directly to my gateway, 192.168.1.1)
There are other suggestions for adding explicit nameservers, but in the past, the gateway has always been the one I used. My (broken) systemd-resolve --status output show that even my systemd-resolvd is using the gateway for a nameserver, but somehow messing up the request.
Hi Ubufan. here is my resolv.conf:
# This file is managed by man:systemd-resolved(8). Do not edit.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs must not access this file directly, but only through the
# symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a different way,
# replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
/run/systemd/resolve/resolv.conf
nameserver 127.0.0.53
search hsd1.ca.comcast.n
When I use the following resolv.conf from my debian install it works: (Have to copy n paste after each re-boot)
# Generated by NetworkManager
search hsd1.ca.comcast.net
nameserver 75.75.75.75
nameserver 75.75.76.76
nameserver 2001:558:feed::1
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2001:558:feed::2Adding the nameserver (s) directly cuts the systemd-resolved out of the loop, avoiding the error. Another solution is to add the package libnss-resolve, which changes the /etc/nsswitch.conf file to better handle the error. With the package addition, and keeping the original /etc/resove.conf link to the 127.0.0.53, everything works again – ping from the command line, nslookup, evolution mail,…