By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 2900

Summary: KMail cannot connect to host on CentOS 7
Product: TDE Reporter: Kristopher <gamrat.kristopher>
Component: tdepimAssignee: Timothy Pearson <kb9vqf>
Status: NEW ---    
Severity: major CC: bugwatch
Priority: P5    
Version: R14.0.x [Trinity]   
Hardware: Other   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:
Attachments: Screenshot of this bug

Description Kristopher 2018-05-14 06:22:36 CDT
Created attachment 2845 [details]
Screenshot of this bug

NOTE: This seems to apply to CentOS only, which is not in the OS list.

In CentOS 7, when trying to connect to an IMAP or SMTP host, I get an error message telling me that KMail can't connect to host. In the screenshot, you can see me trying to add an IMAP account then getting an error message, yet ping shows that my system is able to resolve the hostname I gave it. I also see the same thing happen for SMTP. This happens regardless of whether I copy my TDE settings from another system, or start with a fresh setup (by removing ~/.trinity *before* logging in).

/etc/resolv.conf correctly points to my home router as it's nameserver, and the router uses the nameservers from my ISP. As a test, I tried changing resolve.conf to a few others (including OpenDNS and Google): ping is still able to resolve the IMAP server in every case, but I get the same error message from KMail for both IMAP and SMTP.

I see this happen on CentOS 7 only. KMail seems to function normally (i.e. it successfully checks/sends email with no error messages) on CentOS 6, Debian (I've used TDE on Squeeze, Wheezy, and Jessie), and Devuan Jessie. This is on a fresh minimal install of CentOS 7 with a fresh install of TDE. Initially, I tried copying my ~/.trinity profile which had worked fine on CentOS 6 with the same version of TDE (R14.0.4), but as mentioned above, I tried removing it in vain to see if that would change the status of this bug.