similar to: Authentication Problem with dovecot-2.3.0.1

> On 08 March 2018 at 10:00 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > On 8 March 2018 at 10:09, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > > > > On 07.03.2018 22:07, Odhiambo Washington wrote: > > > > I am a little confused here. > > > > I have been running 2.2.34 which I installed in /opt/dovecot2.2

At least doveconf -n output would help. I guess related to authentication settings. Are there any errors in logs? > On 1 Jun 2017, at 12.14, Odhiambo Washington <odhiambo at gmail.com> wrote: > >> On 30 May 2017 at 21:16, Timo Sirainen <tss at iki.fi> wrote: >> >> https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz >>

On 24 Nov 2018, at 8.33, Odhiambo Washington <odhiambo at gmail.com> wrote: > > > I installed 2.3.4 and just used it with the config files for 2.3.3 without changing anything in the configuration. > I then realized that the LDA was throwing errors. > > 2018-11-24 00:02:51 1gQIaw-000AZS-Bc </var/spool/virtual/crownkenya.com/john.doe/Maildir

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm using Dovecot v2.2 with unix_listener auth-client { } to verify passwords for a different service. However, it looks like that auth_failure_delay effects all connects going through that socket. I mean: connect /var/run/dovecot2.2/auth-client attempt bad auth 2s penalty NO disconnect ==> Note, it's another connection almost

Hi, again. 1. Can somebody explain me about dovecot's shared mailboxes? 2. What does it do while searching shared mailboxes (debug_log cannot explain it)? What files is it looking for? 3. Need i set dovecot-shared file into directory which are shared (if i want to have separate flags for separate users)? 4. Some errors are hard to understand. For example, # pwd

Hello, given a Debian 9 system with Dovecot 2.2.34 installed from self-built packages made from the official tarball combined with Stephan Bosch's debian files (upgraded multiple times from packages made in a similar way). Today, I updated this system to 2.3.0.1 from the official repository at repo.dovecot.org. After the update, dovecot wouldn't start because of: > dovecot: master:

pull the patches from the port..... On Tue, Feb 5, 2019 at 2:28 PM Odhiambo Washington via dovecot < dovecot at dovecot.org> wrote: > Oh, so manual compile should NOT work and it's okay or am I missing > something? > > On Tue, 5 Feb 2019 at 23:26, The Doctor <doctor at doctor.nl2k.ab.ca> wrote: > >> On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo

Hello. I have problems to compile Dovecot2.2.13 with rpmbuild using options: ./configure \ --prefix=/usr \ --with-ssl=openssl \ --with-ssldir=/etc/ssl \ --sysconfdir=/etc \ --without-vpopmail \ --with-pam \ --without-bsdauth \ --without-sql \ --without-nss \ --without-ldap \ --without-pgsql \

the patches are already in git master. I've pulled them into the mail/dovecot port. The dovecot guys/gals will release it eventually, but the port works TODAY. On Tue, Feb 5, 2019 at 2:33 PM Odhiambo Washington <odhiambo at gmail.com> wrote: > I have always been able to compile manually, even from RCs so I believe I > should be able to compile from the tarball as well. >

2.3.4 had the same compile issues.... On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> wrote: > Noted. > > I will wait for dovecot-2.3.4.2 tarball then. > > In all the servers I listed (+2 more), I never use the mail/dovecot port. > > I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have > built in preparation for the

On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote: > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > Due to DMARC issues some people have failed to receive the latest security > > information, so here it is repeated for both releases: > > > > 2.3.4.1 > > > >

On Tue, Feb 05, 2019 at 11:18:45PM +0300, Odhiambo Washington via dovecot wrote: > On Tue, 5 Feb 2019 at 20:32, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > Due to DMARC issues some people have failed to receive the latest security > > information, so here it is repeated for both releases: > > > > 2.3.4.1 > > > >

Testing a compile on FreeBSD. gmake[2]: Entering directory '/usr/home/wash/Tools/Dovecot/fts-xapian/src' /bin/sh ../libtool --tag=CXX --mode=compile c++ -DHAVE_CONFIG_H -I. -I.. -I/opt/dovecot2.3/include/dovecot -I/opt/dovecot2.3/include/dovecot -g -O2 -MT fts-backend-xapian.lo -MD -MP -MF .deps/fts-backend-xapian.Tpo -c -o fts-backend-xapian.lo fts-backend-xapian.cpp libtool:

Hi there, I've already asked this question on FreeBSD forums without getting any response. So, I thought it's a good idea to ask it again here. I've setup Dovecote2 (2.2.13) + Postfix + SpamAssassin on my FreeBSD 10 VPS and it works flawlessly. Though, I couldn't setup the Dovecot Antispam plugin to train SpamAssassin when I move mails to the Junk folder. I installed the

On Fri, Nov 23, 2018 at 04:06:53PM +0300, Odhiambo Washington wrote: > On Fri, 23 Nov 2018 at 15:29, Timo Sirainen <tss at iki.fi> wrote: > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig > > Binary packages in https://repo.dovecot.org/ > > > > * The default postmaster_address is now

Op 14-1-2019 om 13:40 schreef Aki Tuomi: > > Just to remind that now that there is a github repo for fts-xapian, > you could maybe open these issues there instead? > Although README.md currently says: "Please feel free to send your questions, together with the dovecot log file, to jom at grosjo.net <mailto:jom at grosjo.net> or to the dovecot ML dovecot at dovecot.org

Okay, I was hoping it has something to do with where I am stuck compiling. Could you kindly share your configure options? Mine which has always worked with Dovecot versions prior to 2.3 is refusing to work on FreeBSD i386. <cut> mv -f .deps/test_auth_cache-test-auth-cache.Tpo .deps/test_auth_cache-test-auth-cache.Po clang -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth

On Fri, Nov 23, 2018 at 04:02:27PM +0300, Odhiambo Washington wrote: > On Fri, 23 Nov 2018 at 15:29, Timo Sirainen <tss at iki.fi> wrote: > > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz > > https://dovecot.org/releases/2.3/dovecot-2.3.4.tar.gz.sig > > Binary packages in https://repo.dovecot.org/ > > > > * The default postmaster_address is now

FreeBSD-12 Dovecot-2.3.5 I am having problems with one use Mar 25 21:30:12 imap(gau.mon at crownkenya.com)<91364><U7qCZO+ECfCaRh6E>: Fatal: master: service(imap): child 91364 killed with signal 6 (core dumped) Mar 25 21:30:14 imap(gau.mon at crownkenya.com)<2381><moHYZO+EDvCaRh6E>: Fatal: master: service(imap): child 2381 killed with signal 6 (core dumped) Mar 26 06:29:26

Aki Tuomi, Fri, 02 Mar 2018 20:06:35 +0200: > the problem is default > ?protocols = imap pop3? Ah, OK. I wasn't aware that the default had changed. It seems to be protocols = imap pop3 lmtp now. > packaging should use > protocols = > protocols = $protocols imap Yep, explicitly setting protocols = before !include_try /usr/share/dovecot/protocols.d/*.protocol helps. IMO