When I download an attachment, Kmail freeze and I can't interact with the UI. All the click I made during this time are queued, and released when download finish (which is pretty annoying if you click on buttons or messages on the list). But worse, if the user downloads a very big attachment (it's possible to send several giga of data in one email), the user can't use Kmail during a very very long time (at least with my bad Internet connexion :D). Reproducible: Always Steps to Reproduce: 1. Send an email with a big attachment or find one in your existing email 2. Download the attachment 3. Try to use Kmail… Actual Results: Kmail is blocked during the download of attachments. Expected Results: Kmail must be usable during this time.
In KDE 4.11.0, Kmail seems to download the attachments _before_ displaying the email which is worse than the previous behavior. Kmail should: 1. Display the email at soon as possible. 2. If we request so, downloading the attachment in the background. 3. Display the attachment download progression in the status bar (like when we fetch emails).
"Kmail seems to download the attachments _before_ displaying" it always did it. We have not an emails and in other place attachment it's in email. So we can't do it. But send 1Go attachment... too bad.
> We have not an emails and in other place attachment it's in email. So we can't do it. How other email clients do that? Thunderbird do that, K9-mail do that. And it’s a pain in the ass that when someone send me an attachment of 20Mo, I need to wait 1m30 to see the text. With Hotmail, you can send 10Go. It takes me more than 1h to download 1Go. And think about other countries where Internet bandwith is very low.
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.
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.