On 23/08/25, aholiveira--- via dovecot ([email protected]) wrote:
> I've recently upgraded to debian 13 (trixie), from debian 12 (bookworm).

> In bookworm I had the following setup working like perfection:
> - All mail is sorted to some mailbox folder through sieve (either a 
> "specialized" one, or a generic folder under the inbox name like year.month - 
> 2025.08). 
> - No email whatsoever was ever reaching the inbox.
> - Then I had a virtual inbox which would get me all the "unread" or "flagged" 
> messages
> 
> This way I had all my email sorted out from the delivery and my inbox cleared 
> itself once I had read an email.

This seems like a really cool setup.

> ... but dovecot refuses to list the emails in my INBOX folder

> mail_driver = maildir
> mail_inbox_path = ~/Maildir
> mail_path = ~/Maildir
> mail_plugins {
>   notify = yes
>   mail_log = yes
>   virtual = yes
> }
...

Is the separator below correct?
According to 
https://doc.dovecot.org/2.4.1/developers/design/mail_namespace.html#hierarchy-separators-and-namespace-prefixes
 it's (only?) Maildir++ which uses the dot separator.

...
> namespace inbox {
>   inbox = yes
>   prefix =       # can remove
>   separator = .  # try without this setting?
>   subscriptions = yes
>   mailbox Drafts {
>     special_use = "\\Drafts"
>   }
>   mailbox Junk {
>     special_use = "\\Junk"
>   }
>   mailbox Trash {
>     special_use = "\\Trash"
>   }
>   mailbox Sent {
>     special_use = "\\Sent"
>   }
>   mailbox "Sent Messages" {
>     special_use = "\\Sent"
>   }
> }

The only other thing I can think of is a permissions issue.

I'd suggest trying with a minimal dovecot.conf just to try and get the inbox 
working and work from there. A good way of doing this is with the dovecot 
docker image and a sample of your inbox contents, then run it with verbose 
logging. See https://github.com/rorycl/dovecot-config/blob/main/README.md for 
an example invocation.

_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to