similar to: How the does "new" autocreate method works?

Hi, I try to deliver into specific folders with the "plus addressing", namely: rcpt to:<userid+folder at domain> This works only if the folder exists. If it does not, I get the following error: rcpt to:<userid+Spam at domain> 501 5.5.4 Unsupported options example-config/conf.d/20-lmtp.conf says: # When recipient address includes the detail (e.g. user+detail), try to save #

Hi, I've recently seen the following issue. A user logs in with pop3, and sees zero e-mails. The maildir contains emails both in cur and new. The mail delivery is done with qmail, and this user have had no logins before, so it has only the inbox, trash and sent (while dovecot is configured to create drafts and spam folders too). Because of this, the user doesn't have any dovecot

Hi, This is a capture from an imapc client session (which is triggered by a message, received via LMTP): * OK [CAPABILITY IMAP4rev1 NAMESPACE] Ready 2 LOGIN "uid" "pass" 2 OK LOGIN succeeded 1 LIST "" "" * LIST (\Noselect) "/" "" 1 OK LIST completed 3 APPEND "INBOX" {568} + Ready for 568 octets of data [...] 3 OK APPEND

Hi, On 05/04/15 10:59, Timo Sirainen wrote: > On 28 Apr 2015, at 23:49, Nagy, Attila <bra at fsn.hu> wrote: >> Hi, >> >> imapc does a lot of UID FETCH $UID (BODY.PEEK[]), which is nice, because it works even with the dumbest IMAP server, altough it really kills performance, especially on high latency lines. >> >> I wonder: if IMAP servers can effectively

I have a new installation of Dovecot 2.1.12 and cannot select the Inbox without getting this error: c select inbox c NO [SERVERBUG] Internal error occurred. Refer to server log for more information. [2013-01-16 18:22:13] Here's the server log: dovecot[15643]: imap(u1): Error: Failed to autocreate mailbox INBOX: Mailbox already exists Auto create settings are currently set to 'no' --

On 08 Feb 2016, at 12:56, Nagy, Attila <bra at fsn.hu> wrote: > > On 02/08/16 11:16, Timo Sirainen wrote: >> Oh, you were thinking about ability to provide IMAP/etc support for other random servers, and have Dovecot act as kind of a middleware and translate the requests. Maybe the answer is still jmap though? It would require jmap lib-storage backend similar to imapc, which

On 09/11/2017 10:42 AM, Sami Ketola wrote: >> On 11 Sep 2017, at 11.24, Nagy, Attila <bra at fsn.hu> wrote: >> I use dovecot with a broken IMAP server (which doesn't properly implement command pipelining amongst others) as an imapc backend. >> Dovecot issues the above command sequence (SELECT and UID FETCH pipelined), which doesn't work with this server. >>

Hi, imapc does a lot of UID FETCH $UID (BODY.PEEK[]), which is nice, because it works even with the dumbest IMAP server, altough it really kills performance, especially on high latency lines. I wonder: if IMAP servers can effectively handle boundless fetches (like a list with all wanted UIDs, or simply 1:* if all are needed), do you see this as a good addition to develop? This could be a

Hi, Nearly every popular programming language has an LMTP/POP/IMAP implementation, most of them suck in many different ways. I don't know any server or library which provides a well-established, compatible protocol frontend with an open backend API, which could be used to easily make a custom storage backend for the LMTP/POP/IMAP frontend in any language, in any programming paradigm,

On 09/11/2017 09:17 AM, Aki Tuomi wrote: > > On 08.09.2017 15:29, Nagy, Attila wrote: >> On 09/08/2017 01:53 PM, Aki Tuomi wrote: >>> On 08.09.2017 14:50, Nagy, Attila wrote: >>>> Hi, >>>> >>>> I've a broken IMAP server, which doesn't support pipelining and fails >>>> on dovecot's attempt to do this ([C] is

> On 08 Feb 2016, at 11:59, Timo Sirainen <tss at iki.fi> wrote: > > On 08 Feb 2016, at 11:01, Nagy, Attila <bra at fsn.hu> wrote: >> >> Hi, >> >> Nearly every popular programming language has an LMTP/POP/IMAP implementation, most of them suck in many different ways. >> I don't know any server or library which provides a well-established,

Hi, all I've recently upgraded to 2.1.16 and found my self in deep .... There are 4 accounts in my setup that need to be accessed simultaneously by 5-6 PCs on a local lan. The thing is if a user A updates, deletes, flags mail messages in the imap folders the changes don't get propagated to the other mail clients. To state this clearly, PC (A) thunderbird has an account SALES, Maildir

thanks for the feedback! Userdb would be an option, however we would need to extend our LDAP Schema with an additional "autocreate flag". Modifying the LDAP import scripts, this is quite a task. Another option we were thinking of is creating the special folders by a script right after user creation. By far the best and easiest solution would be a flag to auto-create the special folders

You could also use welcome plugin to execute a custom script on first login. Aki On 15.03.2017 09:28, plataleas wrote: > thanks for the feedback! > > Userdb would be an option, however we would need to extend our LDAP > Schema with an additional "autocreate flag". Modifying the LDAP import > scripts, this is quite a task. Another option we were thinking of is >

welcome plugin is already present in 2.2.24, so in that sense, no need to upgrade. Other than that, it should be rather straightforward upgrade. Aki On 15.03.2017 13:07, plataleas wrote: > Thanks Aki!! > > The welcome plugin sounds like the best workaround. To implement this we > would need to upgrade our Dovecot installation: > > dovecot-core: > Installed:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 14 Mar 2017, plataleas wrote: > We are currently migrating accounts to Dovecot. The existing accounts do > have special folders with different names. (i.e. sent, sent-mail) > > The autocreate-function of "special folders" is useful. However we need > this feature ONLY for new users. The existing accounts have a

Hi, I figured out that Dovecot does not honer secondary groups with auth/auth-worker (??), if doing LDAP/TLS stuff. I had to use file system acls to add the user "vmail" to /etc/ssl/private and to the corresponding key file: doveconf -n # 2.1.3: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-40-generic-pae i686 Ubuntu 10.04.4 LTS auth_master_user_separator = * auth_mechanisms = plain

Thanks Aki!! The welcome plugin sounds like the best workaround. To implement this we would need to upgrade our Dovecot installation: dovecot-core: Installed: 1:2.2.24-1~bpo8+1 Candidate: 1:2.2.27-2~bpo8+1 Are there special recommendations for the upgrade process (in addition to the Dovecot NEWS file)? Any special steps we should be aware of during the upgrade? Is it that simple

W dniu 13.01.2015 o 13:53, Lazy pisze: > I can't reproduce this with redis dict. > > Could You provide us with a doveconf -n ? > Does this also happen with other dict engines ? Working configuration: auth_cache_size = 64 k auth_cache_ttl = 10 mins auth_master_user_separator = * auth_mechanisms = plain login deliver_log_format = msgid=%m: from=%f: phys=%p: virt=%w %$ dict {

I have old dovecot server: (# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.14.15-3.el7xen.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) and new dovecot server: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 4.14.47-5.el7xen.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) I try