>Also we need to check that the cache size preferences don't have any funny values. In tb's config editor, check to make sure these are default (not bold and the values are as shown): ``` browser.cache.memory.capacity 200000 browser.cache.memory.enable true browser.cache.memory.max_entry_size 25000 ``` Since you made a new profile it is doubtful that these have changed from default. However, if the attachment is larger than 25M bytes there may be issues. See https://wiki.mozilla.org/MailNews:Logging for info on generating a log file. It doesn't mention how-to for freebsd but I assume it is similar to macos or linux, e.g, in a terminal do.: ``` export MOZ_LOG=IMAP:5,timestamp,IMAPCache:5 export MOZ_LOG_FILE=/tmp/imap.log thunderbird ``` I've added IMAPCache as Jorg suggested. Before running tb with the env vars set, I would suggest creating a folder with just a problem email in it, then shutdown tb and restart with env vars set and access the problem email and try to open the problem attachment. Then shut down tb and attach the log using the "Attach file" link above. This may tell us something.
Bug 1576584 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
>Also we need to check that the cache size preferences don't have any funny values. In tb's config editor, check to make sure these are default (not bold and the values are as shown): ``` browser.cache.memory.capacity 200000 browser.cache.memory.enable true browser.cache.memory.max_entry_size 25000 ``` Since you made a new profile it is doubtful that these have changed from default. However, if the attachment is larger than 25M bytes there may be issues. See https://wiki.mozilla.org/MailNews:Logging for info on generating a log file. It doesn't mention how-to for freebsd but I assume it is similar to macos or linux, e.g, in a terminal do.: ``` export MOZ_LOG=IMAP:5,timestamp,IMAPCache:5 export MOZ_LOG_FILE=/tmp/imap.log thunderbird ``` I've added IMAPCache as Jorg suggested. Before running tb with the env vars set, I would suggest creating a **not sync'd** folder with just a problem email in it, then shutdown tb and restart with env vars set and access the problem email and try to open the problem attachment. Then shut down tb and attach the log using the "Attach file" link above. This may tell us something.