[Dovecot] dovecot 2.1.8 still tries to touch any mountpoint

[Timo Sirainen]

On 17.7.2012, at 15.12, Reindl Harald wrote:

>> v2.1.9+ log message will point to http://wiki2.dovecot.org/Mountpoints
> 
> Dovecot already internally filters out many mountpoints and filesystems that
> are pretty much guaranteed not to contain any emails
> 
> i bet /sys/fs/cgroup will never contain any mail :-)

v2.1.7+ won't add any mounts from /sys by default. But you had already run an older Dovecot version that had added those mountpoints, so v2.1.8 will still complain about them until you remove them. But they won't get added again even if you don't add an ignore for them.

> the bug is taht it also adds fuse-mountpoints where the dovecot
> suer never ever has any access permissions and whines later
> if they are unmounted

It's not easy for Dovecot to know this. Other installations are using FUSE mountpoints to store mails.

> i see no reason for such magic
> 
> why does a mailserver touch any mountpoint where it is not
> explicit configured to store mails?

Because Dovecot doesn't know where mails can be stored (userdb lookups can override the defaults).

The other possibility would have been to require you to explicitly list all the mountpoints that can contain mails/indexes and have Dovecot refuse to access the mails outside that list. But that would have broken all the existing installations.

> Jul 17 14:10:17 srv-rhsoft dovecot: master: Warning: /var/run/vmblock-fuse is no longer mounted. If this is
> intentional, remove it with doveadm mount

I guess /var/run and /run could be added to the default ignore list.