50.6 Folder Issues
50.6.1 Overview ¶
When accessing email folders, various problems can arise - the folder no longer exists (renamed, deleted, permissions revoked) or the server returns temporary errors. The program absorbs such situations automatically and maintains a list of unreachable folders, in which you can curate affected entries as needed.
50.6.2 List of Unreachable Folders ¶
If a folder cannot be reached multiple times, the program enters it automatically into an internal list. Consequences:
- The affected folder is skipped on subsequent runs - other folders of the same account continue to be processed
- A notice appears in the log area Issues
- The status bar shows a warning symbol with the number of affected folders
This keeps the program operational even if a single folder is disrupted.
50.6.3 Correction Flow ¶
In the area Log -> Issues (or via the status bar) you can see the list of unreachable folders. Three actions are available per entry:
| Action |
Effect |
| Correct... |
Opens a folder selection dialog - you choose the correct folder from the current server structure. All profiles that referenced the original folder are switched to the new path |
| Retry |
Marks the folder as "to be checked again" - the next processing run picks it up again. Useful for temporary problems (server maintenance) |
| Ignore |
Leaves the entry in the list but does not affect processing further |
Once a folder is reachable again, it is removed from the list.
50.6.4 Typical Triggers ¶
- Folder was renamed or moved - the profile points to the old name
- Folder was deleted - e.g. a test folder that was removed later
- Permissions revoked - the account no longer has access
- Server error on multiple attempts - quota exceeded, maintenance, hardware problems
50.6.5 Automatic Path Correction ¶
Some IMAP servers write subfolders with the prefix INBOX. - in the Outlook web interface the folder is called e.g. "Inbox/Invoices", but on the server side it is INBOX.Rechnungen. If the program does not find a folder at the originally configured path and the server returns a matching hint, it corrects the path automatically and remembers the change in the profile.
This correction runs in the background - you notice it at most by the fact that the path in the profile looks slightly different after the first successful run than originally entered.
50.6.6 Shared Mailbox Without Subfolders ¶
If the folder dialog shows only the top level for a shared Microsoft 365 mailbox (an account with a filled-in Mailbox address, see chapter 50.2.6) although Outlook shows subfolders under the inbox or the archive, the cause is almost always a permission. Microsoft 365 returns to a delegate only the folders the delegate is permitted to see. If sharing was granted per folder in Outlook, it does not apply to the subfolders of that folder. The program detects this situation and shows a notice in the folder dialog.
First check in the account editor whether the correct sign-in account is entered under Email address. If a different account signed in during sign-in, for example an administrator account for the approval, the program asks which mailbox to monitor (see chapter 50.2.3). If the desired mailbox has its own sign-in, the simplest way is to sign the account in with that mailbox directly and leave the Mailbox address field empty.
If the delegate is to keep the access, grant it full access:
- Check the finding in Outlook on the web: Sign in with the sign-in account and open the shared mailbox via
https://outlook.office.com/mail/<mailbox address>. If the subfolders are missing there as well, full access is missing.
- Grant the sign-in account full access to the mailbox in the Exchange admin center: Recipients, Mailboxes, open the mailbox, tab Delegation, Read and manage (Full Access). Full access covers all folders, including subfolders created later.
- Wait up to one hour until Microsoft 365 has applied the change everywhere.
- Click Refresh in the folder dialog. The subfolders appear, restarting the program is not necessary.
Note: If the shared mailbox really has no subfolders, the notice appears as well. It is then without consequence.
50.6.7 Use Case ¶
Server Migration with Renamed Folders
After a migration from hoster A to hoster B, all folder paths are invalid. They show up in the Log -> Issues area - click Correct... once per folder, choose the new path, and all affected profiles are updated at the same time.