Default imap setting: Download Deleted/Trash and Spam/Junk folders when "Get Messages"
Categories
(Thunderbird :: Preferences, enhancement)
Tracking
(Not tracked)
People
(Reporter: ovari123, Unassigned)
References
(Depends on 1 open bug)
Details
Comment 2•7 years ago
|
||
Comment 4•7 years ago
|
||
Comment 5•7 years ago
|
||
Comment 6•7 years ago
|
||
Comment 8•7 years ago
|
||
Comment 9•6 years ago
|
||
It could well be that a decision was made to not enable sync for these folders because Gloda does not index messages from these folders (if I remmeber correctly).
duplicate bug 1520921 ?
Comment 11•6 years ago
|
||
Looks like Matt decided for me.
Anyway, I learned something new yesterday and hope it helps with this bug and 1520921.
Comment 12•4 years ago
|
||
Too bad you decided not to change the way that Thunderbird download emails just like every other mail client. They all download for offline use the Trash and Spam folder.
Now I am stuck after every installation of Thunderbird, for every account: Settings / Synchronization / Advanced and manually check everything so that Thunderbird has a normal behavior.
Thunderbird is unique.
Comment 13•4 years ago
|
||
What is the logic to closing this bug Óvári I realise it has been sitting here unconfirmed for years, but the failure to download all mail from all folders is becoming an oft commented issue in support. So this wontfix feels wrong to me.
Comment 14•4 years ago
•
|
||
Check my issue bug 1520921 which is the same. It has been confirmed.
Reporter | ||
Comment 15•4 years ago
|
||
(In reply to Matt from comment #13)
What is the logic to closing this bug Óvári I realise it has been sitting here unconfirmed for years, but the failure to download all mail from all folders is becoming an oft commented issue in support. So this wontfix feels wrong to me.
When people ask for help with this issue, could you ask them to cc themselves to this issue? Could this provide better exposure of this issue to the Thunderbird steering committee and core developers?
(In reply to Zurd from comment #14)
Check my issue bug 1520921 which is the same. It has been confirmed.
It looks like your issue has never confirmed only marked as resolved as a duplicate of this issue.
Description
•