[Dovecot] How the does "new" autocreate method works?
Hi,
I'm trying to migrate from the deprecated autocreate plugin to the mailbox { auto }setting without success. What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the folders other than the inbox itself.
doveconf -n
2.2.2: /usr/local/etc/dovecot/dovecot.conf
OS: FreeBSD 9.1-STABLE amd64
auth_cache_negative_ttl = 0 auth_cache_size = 100 M default_process_limit = 1000 default_vsz_limit = 1 G disable_plaintext_auth = no import_environment = LD_PRELOAD info_log_path = syslog lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes lmtp_save_to_detail_mailbox = yes log_path = /var/log/dovecot-errors.log mail_gid = 999 mail_location = maildir:~/Maildir mail_plugins = " quota" mail_temp_dir = /data/tmp mail_uid = 999 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } passdb { args = /usr/local/etc/dovecot/master-users driver = passwd-file master = yes pass = yes } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { mail_log_events = delete mailbox_delete mail_log_fields = uid box msgid size flags vsize from subject quota = maildir:User quota quota_warning = storage=95%% quota-warning 95 %h quota_warning2 = storage=80%% quota-warning 80 %h recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = pop3 imap lmtp service auth { unix_listener auth-userdb { mode = 0600 user = qmailldap } } service lmtp { inet_listener lmtp { port = 24 } user = qmailldap } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/local/quota-warning/quota-warning.sh unix_listener quota-warning { user = qmailldap } user = qmailldap } ssl = no userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = /usr/local/etc/dovecot/dovecot-ldap-catchall.conf.ext driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = " quota mail_log notify sieve" } protocol imap { mail_plugins = " quota imap_quota mail_log notify" }
Thanks,
On 23.5.2013, at 14.26, Attila Nagy <bra@fsn.hu> wrote:
I'm trying to migrate from the deprecated autocreate plugin to the mailbox { auto }setting without success. What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the folders other than the inbox itself.
The new method is creating the folders lazily to disk. They will be visible in IMAP session, but they won't be actually created to disk until the folder is opened.
Your config looks correct to me.
On 05/23/13 14:01, Timo Sirainen wrote:
On 23.5.2013, at 14.26, Attila Nagy <bra@fsn.hu> wrote:
I'm trying to migrate from the deprecated autocreate plugin to the mailbox { auto }setting without success. What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the folders other than the inbox itself. The new method is creating the folders lazily to disk. They will be visible in IMAP session, but they won't be actually created to disk until the folder is opened.
Your config looks correct to me.
Exactly what I see, but I thought this was an error. Could you please clarify this somewhere appropriate? BTW, this is a problem for us, because we have a custom software accessing the maildir, which won't see these until created. Would it be possible to set the laziness of this process and provide the possibility to create the folders on disk?
Thanks!
On 23.5.2013, at 15.06, Attila Nagy <bra@fsn.hu> wrote:
On 05/23/13 14:01, Timo Sirainen wrote:
On 23.5.2013, at 14.26, Attila Nagy <bra@fsn.hu> wrote:
I'm trying to migrate from the deprecated autocreate plugin to the mailbox { auto }setting without success. What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the folders other than the inbox itself. The new method is creating the folders lazily to disk. They will be visible in IMAP session, but they won't be actually created to disk until the folder is opened.
Your config looks correct to me.
Exactly what I see, but I thought this was an error. Could you please clarify this somewhere appropriate? BTW, this is a problem for us, because we have a custom software accessing the maildir, which won't see these until created. Would it be possible to set the laziness of this process and provide the possibility to create the folders on disk?
This changed, because the previous behavior was unnecessarily accessing the disk all the time at each login. I wasn't really planning on adding the old behavior back anymore. Maybe you could create the folders when the user is created?
On 05/23/13 14:08, Timo Sirainen wrote:
On 23.5.2013, at 15.06, Attila Nagy <bra@fsn.hu> wrote:
On 05/23/13 14:01, Timo Sirainen wrote:
On 23.5.2013, at 14.26, Attila Nagy <bra@fsn.hu> wrote:
I'm trying to migrate from the deprecated autocreate plugin to the mailbox { auto }setting without success. What do I forget, or misunderstand?
I deliver mails via LMTP and log in on IMAP, neither of them create the folders other than the inbox itself. The new method is creating the folders lazily to disk. They will be visible in IMAP session, but they won't be actually created to disk until the folder is opened.
Your config looks correct to me.
Exactly what I see, but I thought this was an error. Could you please clarify this somewhere appropriate? BTW, this is a problem for us, because we have a custom software accessing the maildir, which won't see these until created. Would it be possible to set the laziness of this process and provide the possibility to create the folders on disk? This changed, because the previous behavior was unnecessarily accessing the disk all the time at each login. I wasn't really planning on adding the old behavior back anymore. Maybe you could create the folders when the user is created?
Very good point, will do.
Thanks.
participants (2)
-
Attila Nagy
-
Timo Sirainen