similar to: dovecot-2.0-pigeonhole/ManageSieve: wrong service name

Hello! Upgrading manual tells that authdb [NSS module was removed][1] some time ago. [1]: https://wiki2.dovecot.org/Upgrading/2.3#line-100 > userdb nss was removed. Use userdb passwd instead. Can this change be reverted? I'd like to use only libnss_sss.so.2 as dovecot userdb source. It's also essential for me to enable files backend in nsswitch.conf so the system could use local

Hello dovecot users, I have finally updated the MANAGESIEVE patch to fix the currently known small problems with the protocol implementation. Also, I included a proxy implementation based on imap-proxy.c. This patch is designed for dovecot release 1.0.2 and it will not apply cleanly to the 1.1 versions yet. Change Log V5 ------------- - Applied patch by Uldis Pakuls to fix

I use LDAP right now, but local cached sssd queries are much faster and reliable. On July 15, 2019 6:49:18 AM GMT+03:00, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > >On 15/07/2019 02:54 Eugene via dovecot < dovecot at dovecot.org> wrote: > > > >Hello! > > >Upgrading manual tells that authdb [NSS module was removed][1] some >time ago. >

Hi, I've enabled client certificate authentication for imap and managesieve. When I use Thunderbird with the sieve plugin it tries to login, but times out. Initially I reported this to the sieve plugin, but we came to the conclusion that it managesieve is misbehaving. https://github.com/thsmi/sieve/issues/94 Thunderbird (win10-64) 52.4.0 (32bit) Sieve 0.2.3k Dovecot (Ubuntu 16.04.3 LTS)

Hello, I'm currently packaging dovecot 2.0.3 under Mandriva Linux. It has been using LDFLAGS="-Wl,--as-needed -Wl,--no-undefined" for shared libraries for over two years[1]. And I've found there are lots of linking problems with dovecot 2.0.3. After some investigation, I've made small patch regarding dovecot 2.0.3, posted here:

Hi all, ok, I am running version v2.0.beta6 and the latest pigeonhole build to run managesieve and the sieve delivery filters... I am getting the following response from the managesieve port when connecting : Escape character is '^]'. "IMPLEMENTATION" "Dovecot" "SIEVE" "" "SASL" "PLAIN" "STARTTLS" "VERSION"

Hi, Curtis (and the group), I tried setting up Dovecot's auth default section as you described, with both authdb and userdb set to 'passwd.' It let the authenticated session start on the POP side, but I got consistent authentication failures on the client side that the passwords didn't match. I don't have any more time to mess with it this morning, but I will make it a

Hi! I'm still fighting with lost mails and what I think is a locking problem. As I've lost some pretty important mails already, I decided to mitigate my troubles by moving to maildir format, which should not be susceptible to these problems. I read the docs and wanted to test on my account, before I mess with all the others and possibly break something. The way to do it seems to be to

Gedalya-san Thank you for the information. It seems to be difficult... morikawa -----Original Message----- From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Gedalya Sent: Thursday, October 29, 2020 1:17 PM To: dovecot at dovecot.org Subject: Re: dovecot quota-warning detection mail Aha. Then it's not a straightforward case of just adding the domain name to the same

Hello, does anybody knows what managesieve addon sets in SERVICE env when autentificating to checkpassword? thanks Pete

Hi there, I run a system that has a lot of virtual users. We invoke deliver from exim and pass the directory to deliver into using the HOME environment variable, so deliver doesn't do any database lookups during the delivery process. The exim pipe environment is described at http://exim.org/exim-html-current/doc/html/spec_html/index.html#toc0239, but basically I'd like to know the domain

Couple questions about running doveadm with multiple instances... I have Dovecot 2.2.13 on RHEL6 running across 3 boxes, each with a director and main instance running. When I try to lookup something on the main instance (which is handling user auth) via its auth-userdb socket directly, I get an error: # doveadm auth lookup -a /var/run/dovecot-main/auth-userdb myuser doveadm(root): Error: passdb

I got around to trying the 0.2.2 managesieve listener and it's not working for me. As soon as the client authenticates, the connection is closed and the following is logged on the server: > Dec 13 11:48:30 managesieve(xx at yy.com): Error: user xx at yy.com: Initialization failed: Namespace 'Mobile/': Unknown mail storage driver virtual > Dec 13 11:48:30 managesieve(xx at

Hello, list! I am in the midst of configuring a new Dovecot IMAP server, and I'm preparing to setup shard mailboxes as part of the ocnfiguration. In order to get these setup the way I want, I've figured out that I'm going to have to setup an acl_shared_dict. This is where things start to get confusing for me, as I have had difficulty finding thorough explanations of dictionary

Hi, due to compatibility issues with mail clients I think I have to use plain text authentication. In order to secure the passwords during their transport I'll use SSL encryption. After reading some documentation I think that I'll have to store the passwords as plain text in the authdb. That is something I dislike very much as it is a (imho) good tradition for unix to store only

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

Hello Dovecot users, Due to personal matters I haven't had time to do anything in the last few weeks. Before that I provided some pre-releases and since nobody indicated problems with those, I release them definitively now. I hope the shit storm has blown over, so that I can dedicate more of my time towards Pigeonhole development. The Sieve release involves a large architectural change,

OK. "passdb/userdb" Setting part $ dovecot -n (Excerpt from change) ---------------------------------------------------------------------------- --------------------- passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users.auth driver = passwd-file } userdb { args = username_format=%u /etc/dovecot/users.auth driver = passwd-file } protocol lmtp { info_log_path =

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 15/07/2019 02:54 Eugene via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div> <div>

Line 33: #process_count = 1024 Probably you mean process_limit