Open
Bug 1307071
Opened 8 years ago
Updated 2 years ago
subscribe to new folders automatically
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: harri, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [dupme])
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Steps to reproduce: setup dynamic procmail rules in your account, as described on e.g. https://debian-administration.org/article/400/Handling_Debian_mailing_lists_easily IMAP server is dovecot Actual results: newly generated folders are not shown, even though there were >10 new EMails Expected results: newly generated subfolders should be shown and subscribed to automatically, if the parent is subscribed
Reporter | ||
Updated•8 years ago
|
Summary: subscribe to new folders automaticaly → subscribe to new folders automatically
Comment 1•8 years ago
|
||
Harald, Do they show up on restart? Do you have "show only subscribed folders" enabled? If so, perhaps bug 38943.
Flags: needinfo?(harri)
Reporter | ||
Comment 2•8 years ago
|
||
I saw in another bug report that there might be problems with the nesting level. In my case I have email account --> "debian.org" --> "bugs" --> generated_folders. "show only subscribed folders" is disabled. The new folders don't show up on restart, either. They *do* show up in the folder pane if I collapse and expand the surrounding folder ("bugs"), but it still doesn't show the number of unread messages. The new folders appear to be empty. I have to click on each new folder to make thunderbird look into it. Then the number is shown, too. Maybe I didn't wait long enough here. The subscribe menu shows the new folders after collapse and expand (in the menu! this time), but they are not subscribed, even though the folder pane shows the number of unread messages. BTW, here are the procmail rules to generate the folders: :0: * ^X-Debian-PR-Source:\ *\/[-a-zA-Z0-9]+ $LOGNAME/debian.org/bugs/$MATCH/ :0: * ^X-Debian-PR-Package:\ *\/[-a-zA-Z0-9]+ $LOGNAME/debian.org/bugs/$MATCH/
Flags: needinfo?(harri)
Updated•8 years ago
|
Component: Folder and Message Lists → Networking: IMAP
Product: Thunderbird → MailNews Core
Version: 45 Branch → 45
Comment 3•6 years ago
|
||
this does seem like it would be a duplicate
Flags: needinfo?(gds)
Whiteboard: [dupme]
Comment 4•6 years ago
|
||
Wayne, the part about not seeing the unread count sounds like a recent duplicate. In that bug the user had many gmail folders and server rules to move new message to them and he said tb didn't show the new message count on the folders. I haven't heard any more about that from the reporter. The standard suggestion for this problem is to enable the folder property "When getting new messages on this account, always check this folder". But that didn't help so I last suggested to set mail.imap.use_status_for_biff to false (non-default) and see if that helped, but no response from the reporter. The problem about new folders not appearing sounds new. The folders should be discovered at tb startup and kept after that. Not familiar with "procmail" but I will look closer so keeping the "need info" flag set on this one.
Comment 5•6 years ago
|
||
Bug 1396495 is semi-duplicate.
bug 697363 might also be the same thing.
Comment 7•4 years ago
|
||
I could be wrong but I think that whatever is creating the folders (procmail, dovecot etc) the program can set the folder mode to where the new folders report with the imap list command as "subscribed". Then they appear in tb without the user having to subscribe. That said, something has to occur in tb to trigger an imap list command to "discover" the new folder(s) as subscribed. This always occurs on tb startup and usually when you do a collapse/expand on the accounts folder tree with tb running. Imap has no way to report new folders similar to the way it reports new emails using the idle command that I know of.
Flags: needinfo?(gds)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•