evolution imap with comcast

ping imap.comcast.net

Pinging imap.g.comcast.net [68.87.20.10] with 32 bytes of data:
Reply from 68.87.20.10: bytes=32 time=96ms TTL=53
Reply from 68.87.20.10: bytes=32 time=95ms TTL=53
Reply from 68.87.20.10: bytes=32 time=95ms TTL=53
Reply from 68.87.20.10: bytes=32 time=95ms TTL=53

Can you ping that IP?

I can ping both imap.comcast.net and imap.g.comcast.net with the ping utility. However, that is not the topic of this question/bug. It is that evolution reports an error. Is this a problem or a bogey?

Further, I can ping 68.87.20.10 directly with the ping utility. However, when I ping either imap.comcast.net or imap.g.comcast.net, the replies come from imap.po.sys.comcast.net (96.114.157.78).

Have you contacted Comcast to verify the settings to use?

Yes, see the following:

To configure an email client to use Comcast email (@comcast.net), the following settings should be used
for sending and receiving email:
Recommended
Only If Needed
Incoming Mail
Server - imap.comcast.net imap.comcast.net
Name
Incoming Mail
Server - Port 993 with SSL ON 143 with SSL ON
Number
Outgoing Mail
Server -
smtp.comcast.net smtp.comcast.net
Name
Outgoing Mail
Server - Port
Number
SSL
Encryption
587 (SMTP) 465 (SMTPS)
checked checked
Authentication Comcast ID and Password required

Sorry if this seems cryptic but this window would not preserve the tabular nature of the content. See
http://customer.comcast.com/help-and-support/internet/email-client-programs-with-xfinity-email/
for more details.

There was a similar problem by someone else https://answers.launchpad.net/ubuntu/+source/evolution/+question/233857
Changing the DNS server to the Google one seems to have helped in that case.

I am a bit astonished to read that actionparsnip gets a reply from 68.87.20.10 when he pings imap.comcast.net, but you get a reply from 96.114.157.78?

Mr Hampl,

Thank you, but I want to know more before I fiddle with system files.
First of all, why does adding "nameserver 8.8.8.8" to /etc/resolv.conf change the DNS server to Google. Is 8.8.8.8 some special IP belonging to Google?
Second, the way I interpret it, /etc/resolvconf/resolv.conf.d/head contains the system default for DNS, while /etc/resolv.conf contains the current default, correct?
Third, where can I go to find out more about DNS handling under ubuntu and/or linux in general?
Since the post you cite is old, I have put these questions in this post, which has been more lately monitored.

I have again tried the various pings, confirming my previous report of IPs in all respects. Might this have something to do with the fact that I use comcast/xfinity as my ISP, as well as, mail server?

8.8.8.8 is the IP of Google's primary public DNS service. 8.8.4.4 is their secondary.

The head file contains the text saying "don't modify this file" and is added to the top of /etc/resolv.conf when it is generated. You can edit the file but if DHCP is ran, the changes will be lost. By putting lines in the head file it will add the nameserver line, even if DHCP is used.

I am still getting the message from evolution, but it doesn't seem to be affecting email fetching, so I guess that it IS a bogey.

A search for "evolution ping" reveals that this problem is not unique to comcast nor to this questioner:

Answered 6709 Can I switch off evolution imap server ping? 2007-05-16 Stephan Elsner — Answered
Answered 1858 Need to ping server before send or receiving using POP3 2006-09-22 rjhutt — Answered
Solved 268423 evolution imap with comcast 2015-06-22 Phil Norisez — Solved
Answered 118 Timout error in evolution 2005-11-11 Philip Graetz — Answered
Solved 83263 Evolution with 1and1.com 2009-09-19 richnvel — Solved
Solved 3965 Send/Receive grayed out in evolution 2.9.92 2007-03-01 |Fred Krogh — Solved
Solved 233857 connection timing out 2013-08-11 David Danforth — Solved
Solved 68498 Error while Fetching Mail. (Evolution, Jaunty) 2009-04-24 Larry Vogler — Solved
Solved 120667 Noob ?: Evolution "Login Failure" when attempting Send/Receive 2010-08-11 Popeye.Tom — Solved

I have added this information to the referenced bug report.

This seems to have gone away in more recent versions of ubuntu/evolution/comcast, so setting this post to solved.