Bug 151136 - External references warning in kmail reappears in the opened email if it already accepted by clicking on it in the bottom pane
Summary: External references warning in kmail reappears in the opened email if it alre...
Status: RESOLVED DUPLICATE of bug 53178
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.9.7
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2007-10-21 14:44 UTC by Ralph
Modified: 2010-01-11 00:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralph 2007-10-21 14:44:45 UTC
Version:           1.9.7 (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
OS:                Linux

Basically, when viewing the email messages in a pane in Kmail (i.e. no extra windows open except for the main kmail one), you can click on the "external references" warning to allow kmail to download the images in an HTML email. 

Now, when you double click the message to view it in a new window, the "external references" warning reappears!!! Why? There is no need for this as you've already accepted to load external references for that email.

To correct this, kmail should automatically load external references (from a cache ideally) once the warning message has been clicked. 


Alternatively, have 3 options for each message with external references; one option always loads external references, one option to never load external references, and one option to ask each time that perticular email is viewed.

Thanks.
Comment 1 Ruchir Brahmbhatt 2009-04-24 15:27:18 UTC
I can confirm this on trunk revision 958061 but not sure if this should be implemented.
Comment 2 Ralph 2009-04-24 17:43:26 UTC
Why should it not be implemented?

Do you suspect that yet another option for configuring Kmail would confuse users?

Regards.
Comment 3 Björn Ruberg 2010-01-11 00:48:20 UTC

*** This bug has been marked as a duplicate of bug 53178 ***