Bug 308064

Summary: "Load external references" setting on a folder is not completely evaluated
Product: [Applications] kmail2 Reporter: Mathias Homann <Mathias.Homann>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: montel
Priority: NOR    
Version: 4.9.2   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Mathias Homann 2012-10-08 10:29:22 UTC 
I have one folder where I allow HTML mails, and external references. Therefor I set the flags for those two settings in the "Folder" menu accordingly.

Since KDE 4.9.2, the HTML flag still works, but the "load external references" flag doesn't, I get mails displayed with placeholders. What's more, when I switch that flag off, and back on, I get to see the external images, but I still get the "Click here to enable external references" header displayed on top of the email.

Reproducible: Always

Steps to Reproduce:
1. Set up a folder for HTML mail with external refs
2. put somesuch mails in there
3. set the folder flags in the folder menu
4. open a mail in that folder, observe the external references not being loaded, or being loaded but in either case you always see the "Click here to enable external references" headerbox.
Actual Results:  
see steps

Expected Results:  
I would expect the "click here to..." to go away after I enable external references. I would also expect the feature to work right away after starting kontact.
Comment 1 Laurent Montel 2012-10-08 11:14:05 UTC 
Works fine here.
Comment 2 Denis Kurz 2016-09-24 18:13:06 UTC 
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 3 Denis Kurz 2017-01-07 22:38:48 UTC 
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.