similar to: Tracing a server problem

Hi, I am using dovecot 2.1.3 on centos 5.7. It was working fine but last few days I need to restart or reload dovecot service because at that time users are not able to login. Each time I am getting information from doveco.log is as : Jun 04 11:52:54 auth: Error: BUG: Authentication client gave a PID 17564 of existing connection Jun 04 11:52:54 auth: Error: BUG: Authentication client gave a PID

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Alexey.Petruchik has submitted a cmake build file for libogg. https://github.com/xiph/ogg/pull/6 I'm curious how many people here would find this useful, particularly Visual Studio users. I don't object in principle, but I'm wary of adding yet another build description which would need to be maintained. -r -----BEGIN PGP

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're

up until a week or so ago, I had no problem using IMAP logging into a server running Fedora Core (I think 4 or 5 ) with dovecot 1.0. Had used squirrelmail and other mail agents using IMAP with no problem. as of 2 days ago, I get a squirrelmail error "ERROR: Connection dropped by IMAP server. Query: CAPABILITY" and turning on dovecot debugging shows the following:

Hello, I am using the latest dovecot 1.1.2 with postfix, and using doveco deliver command for LDA. I really love dovecot, and how it has progressed over the years. However I have noticed that if I put a TAB character in the dovecot.conf file, it sometimes does not parse the file correctlty, and complains about missing postmaster_address etc, even though they are there. So I reformated my

I have 2.2 installation on Centos 7, and, I'm trying to setup a new server, and, 'clone' existing setup: Dovecot/Postfix/Mysql on new Centos 7 installed from RPM 2.3.4.1 (3c0b8769e) I then copied/overwrote from old to new /etc/dovecot/*.conf (but not conf.d files), created self certs in place of old server certs and, started Dovecot is that totally dumb, and, how should I do this,

Just a heads up. I recently built a new (XPSP2) image with the Kaspersky 6.0.3.837 on it. I had issues joining the domain with the AV running. Had to disable. (A domain controller for domain ABC could not be contacted.....) I didn't have AV on my previous image, so I don't know if version 5 did the same. I don't recall seeing this on the list, so I thought I would throw it out....

In https://wiki.dovecot.org/HowTo/Fail2Ban, for a current (I know for a fact in 2.2.36) I believe it should be filter = dovecot instead of filter = dovecot-pop3imap [root at mail ~]# ls -l /etc/fail2ban/filter.d/doveco* -rw-r--r-- 1 root root 1875 May 11 2017 /etc/fail2ban/filter.d/dovecot.conf [root at mail ~]#

If i try to connect as root (dovecto 1.0) with wrong password doveco exit with an auth error robyt:~# telnet dns pop3 Trying x.x.x.x Connected to dns. Escape character is '^]'. +OK Dovecot ready. user root +OK pass [wrong] -ERR Authentication failed. but if the password is correct dovecot exit but with another error: user root +OK pass [correct] -ERR [IN-USE] Internal login failure.

Hi all! Os : Fedora 6 Dovecot version : 1.0-0.1.rc7 Dovecot-sieve version: 1.0.2-6 (this is a problem?) Config : # dovecot -n # /etc/dovecot.conf protocols: imaps pop3s disable_plaintext_auth: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3):

Hello, I am trying to run exim 4.68 and dovecot 1.0.13 on Solaris 10 x86 5/08 using dovecot lda and sieve with virtual users and domains, tls and ssl. At the moment certificates are from my internal CA Exim and Dovecot, dovecot lda and dovecot sieve were downloaded and installed from Blastwave. Mail delivery (ie from Exim to dovecot via dovecot lda) is working correctly but when I try

Yes please. CMake support is somehow mandatory for any C/C++ project nowadays. Death to autotools! But that's just my ignorance speaking :-) I have also commented on that pull request. Cheers, Cristian. On Wed, May 27, 2015 at 2:07 AM, Ralph Giles <giles at thaumas.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > Alexey.Petruchik has submitted a cmake

Hey, I had trouble this morning creating a folder to contain sub-folders. I am using the mbox format. Turns out that the .imap directory in the new folder (directory) was not being created. Anytime I tried to view a sub-folder (using Thunderbird) dovecot would dump. Once I manually created the .imap directory, it works fine. dovecot --version -> 2.0.9 dovecot -n # 2.0.9:

> 11:30:12 auth-worker(32307): Warning: sqlpool(mysql): Query failed, > retrying: Unknown column 'mailbox.enableimaptls' in 'where clause' > Mar 03 11:30:12 auth-worker(32307): Error: > sql(voytek at sbt.net.au,110.175.246.167,<xBk6viWDzrRur/an>): User query > failed: Unknown column 'mailbox.enableimaptls' in 'where clause' I've found a

I'm on dovecot 2.3.3 (dcead646b). Output of `dovecot -n`: # 2.3.3 (dcead646b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.3 (f018bbab) doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No matches doveconf: Error: managesieve-login: dump-capability process returned 89 doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 98: No

Further investigation shows that `doveconf` called `/usr/lib/dovecot/managesieve` which in return calls `doveconf` again, but with another uid (possible? I'm not sure) and a few extra arguments, which causes a call to `glob` in `src/config/config-parser.c:settings_include` to fail with `GLOB_NOMATCH`. I'd be appreciate if anyone can provide information on suspicious

Hello. This might be a silly problem, but I'm a bit a newbie at this, and the internet didn't give me a solution to this yet. I installed a mail server with postfix, dovecot, postfixadmin and a mysql DB for authentification, using this tutorial : <http://www.exratione.com/2012/05/a-mailserver-on-ubuntu-1204-postfix-doveco t-mysql/>

using rc3 and with the latest pigeonhole, I had problems with dovecot (deliver) keeping up with high volumes of E-mail. I tried sdbox, mdbox, and cyrdir all with similar (failed) result. using the default Maildir I had no problems. I did not try mbox. The problems seemed to happen when there were multiple deliver's running to the same folder I had defined in my sieve rules, either it would

Hi Timo & Dovecot users, We have a 2-node director setup which front-ends for 4 nodes which share a clustered filesystem (GFS). All nodes run Dovecot 2.0.18. Approximately 40k users, but typically only a few thousand active at any time. The director nodes run sendmail, which deliver mail "locally" using LMTP to the director, which then feeds to SMTP on the real servers (also