If you don't compact your folders regularly, performance can slow to a crawl, you can't store new messages anymore, start losing parts of messages or have deleted messages resurrected. Compacting a folder frees wasted space but the main reason to do it regularly is because it's a type of preventative maintenance. Compressing/zipping only changes how data is stored compacting changes the actual data. "Compacting" a folder has nothing to do with compressing or zipping a file. When you empty the trash it physically removes (expunges) the messages in the Trash folder. Messages in a Trash folder aren't actually deleted messages, when you delete a message in a POP account it copies the message to the Trash folder and then deletes the original. This is a tradeoff done to improve performance in large folders. They are not physically removed until you "compact" the folder. Instead they are marked for deletion and hidden from view. Even emptying the Trash does not get rid of them. When you delete messages in an email client such as Thunderbird they aren't physically deleted. Mariusz, I was wondering what reference you have for this being an illegal way to encode the attachment? Not that it helps with proprietary email clients that encode in this fashion, but it may be helpful if something needs to be changed in Django.This article was written for Thunderbird but also applies to Mozilla Suite / SeaMonkey (though some menu sequences may differ). I've filed a similar bug on the Gnome Bugzilla: Viewing the source of the email in Thunderbird shows the base64 blob in tact. Often company firewalls or antivirus programs will destroy attachments.""" Please check with the person who sent this. I've added a couple more test cases which caused problems for me, the 8bit encoded email works fine, but the base64 one does not (despite it having identical content inside). I've been able to replicate the issue with Evolution as well (although the examples given do not even load in Evolution at all), but messages encoded like this work fine in mutt and Apple Mail. Django seems to encode attached emails in this fashion, which causes some problems! EML file with ThunderbirdĢ) Either nothing is displayed inline for the attachment (first case) or raw base64 data is displayed inlineĥ) The attachment is displayed inline (an HTML with some small embedded images)ħ) The saved EML is nothing but raw base64Ģ) The attached message is displayed inlineħ) The saved EML is displayed like a messageĪ base64-encoded attached email that doesn't work. EML file in the attachment pane andħ) Open the saved. This is reproduceableĢ) Open either of the messages attached to this bug with ThunderbirdĤ) Forward the message (or just Send Later) to any convenient addressĥ) View the forward in the Sent (or Unsent) folderĦ) In the original message, select the. It had been decoded back to plain text during TB's compose/send. Interestingly: the reporter originally forwarded me the message inline - and that forwarded version displayed the attachment as expected. Please check your file name and try again later." I'm unable to reproduce this with the message as sent. Reporter also had a problem with saving the attachment, getting the error "Unable to save the attachment. I reduced the data into the following testcases. The message window (with Display Attachments Inline turned on). In the version I received (the reporter's original message, forwarded-as-attachment to me using TB 1.5), the base64 text appeared *as* base64 text in One of those clients took the attachment and converted it to base64. The message was part of a forward-chain of "funny photos." Someone had forwarded as attachment, and three subsequent people had forwarded inline. I got a copy of that failing message, and was able to distill the problem to a simple testcase. Someone in was complaining about not being able to see images in a forwarded message.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |