Hi!
I´ve been running/clearing Junk and Trash from mailboxes with guide from
docs.mailcow.email Icon Expunge a Users mails - mailcow: dockerized documentation

docs.mailcow.email Icon docs.mailcow.email
Expunge a Users mails - mailcow: dockerized documentation
None
docs.mailcow.email
before but i did run a “./update.sh” 1.5/2 week ago and after that i just get an error (tested with both docker compose (Plugin) and docker-compose (Standalone) same error:

root@mail:/opt/mailcow-dockerized# docker-compose exec dovecot-mailcow doveadm expunge -A mailbox 'Junk' savedbefore 7d
Error: auth-master: userdb list: connect(/run/dovecot/auth-userdb) failed: No such file or directory
Panic: file auth-master.c: line 436 (auth_master_unset_io): assertion failed: (conn->to == NULL)

root@mail:/opt/mailcow-dockerized# docker compose exec dovecot-mailcow doveadm expunge -A mailbox 'Junk' savedbefore 7d
Error: auth-master: userdb list: connect(/run/dovecot/auth-userdb) failed: No such file or directory
Panic: file auth-master.c: line 436 (auth_master_unset_io): assertion failed: (conn->to == NULL)

Any idéas?

Still works for me on an up-to-date mailcow server.

(/run/dovecot/auth-userdb) failed: No such file or directory looks strange – if this file is not available inside the Dovecot container, Dovecot shouldn’t work at all…

What does docker compose exec dovecot-mailcow ls /run/dovecot show?

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

and this is with ls -la

Same for me. Sorry, no idea why your doveadm is complaining, then… 🤔

anyone else got an idéa?

did you try running the doveadm command from inside the container instead of docker compose?
Worth a shot.

No one is typing