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 2550

Summary: KMail not recognizing renamed/removed mail transport
Product: TDE Reporter: Kristopher <gamrat.kristopher>
Component: tdepimAssignee: Timothy Pearson <kb9vqf>
Status: NEW ---    
Severity: normal CC: bugwatch
Priority: P5    
Version: R14.0.x [Trinity]   
Hardware: Other   
OS: Linux   
Compiler Version: TDE Version String:
Application Version: Application Name:

Description Kristopher 2015-11-25 09:29:05 CST 
When I first setup KMail, I went through the initial setup wizard to setup my GMail account. KMail named both the IMAP and SMTP account as Gmail.com, but I decided to override that and manually rename it to GMail (removing the .com and capitalizing the M). IMAP still works fine, but when trying to send mail, KMail would give me an "Unrecognized transport" message.

To investigate, in KMail's email composer, I clicked View -> Mail Transport to find that it is still trying to use the original Gmail.com transport, despite that being renamed to GMail. I had to manually select the renamed GMail and check the box to "sticky" it to make it remember to use the renamed GMail transport, however the old Gmail.com transport is still there, and un-sticky-ing the renamed GMail transport causes it to revert back to using Gmail.com. Setting the renamed GMail transport as the default in Settings -> Accounts -> Sending removes the need to sticky the GMail transport, but Gmail.com remains.

KMail should recognize when transports are renamed or removed, and should not try sending messages with transports that don't exist.