Bug 477512

Summary: Kmail crashes when it cannot resolve domain
Product: [Fedora] Fedora Reporter: Nicolas Troncoso Carrere <ntroncos>
Component: kdepimAssignee: Lorenzo Villani <lorenzo>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 10CC: jreznik, kevin, lorenzo, ltinkl, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-07-22 14:23:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Traceback
none
Aditional Trace back when reproducing. none

Description Nicolas Troncoso Carrere 2008-12-21 13:06:17 UTC
Created attachment 327576 [details]
Traceback

Description of problem:
If kmail is unable to resolve a domain (mail.foo.bar) because the authoritative dns for foo.bar is no where to be found, it displays the unknown host mail.foo.bar message. Then after a minute or so it crashed.
My setting with mail.foo.bar is imaps. Interval check of 2 minutes.

Version-Release number of selected component (if applicable):
kdepim-4.1.3-1.fc10.i386

How reproducible:
Always

Steps to Reproduce:
1. Configure an imap account in a foo server
2. Nuke the resolver for the foo server
3. check your mail
  
Actual results:
Kmail displays the unknown host message and crashed.

Expected results:
Kamil displays the unknown host message

Additional info:
I attach a traceback

Comment 1 Nicolas Troncoso Carrere 2008-12-21 13:07:22 UTC
Created attachment 327577 [details]
Aditional Trace back when reproducing.

Comment 2 Lorenzo Villani 2009-07-22 13:39:43 UTC
Cannot reproduce here (w/ kdepim 4.2.96).
Can you provide more information or test a newer package kdepim version? Going to close as WORKSFORME if no further problems are reported in two weeks.

Comment 3 Nicolas Troncoso Carrere 2009-07-22 14:08:46 UTC
I tried to reproduce the problem. This seems to have been fixed in some version since 4.1.

Go ahead and Close the ticket.

Comment 4 Lorenzo Villani 2009-07-22 14:51:41 UTC
Thanks for testing again.