In TB 52.6.0, my remote content exceptions list gets erased on exit because mail.ab_remote_content.migrated is set to 1
Hi there!
Since updating to TB 52.6.0 (Linux x64/openSUSE Leap 42.3) I've noticed that my remote content exceptions list is now empty every time I start TB. None of the exceptions i used to have have survived and when I add new exceptions, they too disappear after a restart of TB.
Can you help?
Thanks!
Gewysig op deur Wayne Mery
All Replies (4)
I had someone (walt) test this (not on SUSE) and he was unable to reproduce)
Hi!
I've been otherwise busy lately, so I didn't have time to dive into this further. Today, I got updated to TB 52.7.0 and decided to take another look at the problem.
Here's what I've found: If I reset the mail.ab_remote_content.migrated (which was set to "1") and restart TB, I can add exceptions again. When I exit and restart again, the preference is set back to "1" and all my exceptions are gone, and again my newly added exceptions don't survive a program exit.
So, I guess the next question is, where are the remote content prefs migrated to and could there be a permission related problem?
Thanks for your help,
BB
suggestions from someone else...
"try with a new test profile, selecting a few test emails and see what happens, or safe mode.
I don't see how it could be a permissions problem. Like him I don't know where that list is stored.
Maybe "network.jar.block-remote-files". The default is set to "true" for me.
That is probably in omni.ja in the installation folder. I have Read + Write permissions for that file. Possibly he should check the permissions on that file."