- dovecot - dovecot.org

[Dovecot] [PATCH, RFC] add APOP authentication mechanism
by Andrey Panin 14 Aug '17

14 Aug '17

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

3 2

(Solved) Re: Upgrade path from MySQL to MariaDB broken? (Akonadi)
by Volker Wysk 14 Aug '17

14 Aug '17

Hello! I've found it out, how you can solve/work around the problem: Nextcloud needs MariaDB. It won't work (so it seems) with MySQL. So mariadb- server needs to be installed. This replaces MySQL (mysql-server-core-5.7 and mysql-client-core-5.7) with MariaDB. The problem is that after that, Akonadi won't start any longer. "aconadictl start" outputs a lot of messages. The problem can be repaired by doing this, after the installation of MariaDB: akonadictl stop rm -r ~/.local/share/akonadi akonadictl start Bye, Volker

1 1

2.1 to 2.2.31 on new server?
by voytek＠sbt.net.au 13 Aug '17

13 Aug '17

I have a Centos 6 server with Dovecot 2.1.17/mysql/virtual domains I'm setting a new Centos 7 server, and, aim to install 2.2.31 from Ghetoforge dumb question, can I install 2.3 on new server, then, copy old /etc/dovecot tree to new /etc/dovecot ? appreciate any tips and advice, V

3 2

new install on Centos 7
by voytek＠sbt.net.au 12 Aug '17

12 Aug '17

I currently have Postfix Dovecot MySQL on Centos 6, looking at migrating to new server new server is CentOS 7.3, but, the Centos repo version is dovecot x86_64 1:2.2.10-7.el7 what is the best way to install current release Dovecot on a new server ? tia, V

2 3

Re: new install on Centos 7
by Joseph Tam 11 Aug '17

11 Aug '17

>> Or consider compiling it yourself from source. It may be more work, but >> you get complete control over your versioning, your package dependencies, >> etc. If a bug that affects you gets fixed on a bleeding edge version >> (or is only available as a patch), you can fix it right away rather than >> waiting for the package maintainer to catch up to it. > > Or just ping me in #ghettoforge on Freenode and I'll generally get it > fixed quickly, if I haven't already seen it on the list and fixed it. Not all package maintainers are as responsive as you are. I've lost count of the number of problems reported here, where people could not move from version 1.x, because their repo did not have anything newer, or for reason out of their control, they can't update because it would/could break something else. > There are downsides to compiling yourself. To be sure. (Incidentally, auto-updates are sometimes *not* what people want -- stability of a working system is paramount over anything that might jeopardize that.) Compiling from source is not everybody's cup of tea, but it does allow complete control over the build. Repo-packages usually are built with kitchen-sink options, which may not suit everyone. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: Certificate cache on iOS with sending mail
by Joseph Tam 11 Aug '17

11 Aug '17

On Thu, 10 Aug 2017, Larry Rosenman wrote: > Which mail client on iOS? Sorry, maybe not iOS, but definitely MacOSX Mail app. Joseph Tam <jtam.home(a)gmail.com>

2 3

Re: Certificate cache on iOS with sending mail
by Joseph Tam 11 Aug '17

11 Aug '17

Alef Veld writes: >> I'm wondering if there is any cache for a certificate or something, my >> maillog shows up something like 10 bytes read, -1. So it returns an >> error. I deleted the accounts and created them again, still no go. >> >> Anyone had anything similar before? On top of the usual mail set up problems (and it appears to be some SSL/STARTLS port number mismatch), setting up a iPhone/MacOSX mail client can be an exercise in frustration as cause and effect may not be synchronous. What can happen is that after setting up parameters, if they don't work (owing to misconfiguration or transient network problem), your mail client will start varying the mail parameters (port #, TLS/SSL parameters, with/without domain, etc.) in hopes of finding something that works. Sort of auto-discovery/auto-correction. All of a sudden, without apparent cause, it will bump into the right settings (which may co-incide with your original settings) and it will start working. Uber confusing. I believe if you disable the "Automatically manage connection" feature, it will make your settings fixed. This may not be the cause of your original problem, but at least you won't be trying to troubleshoot a moving target. Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: new install on Centos 7
by Joseph Tam 10 Aug '17

10 Aug '17

>> I currently have Postfix Dovecot MySQL on Centos 6, looking at migrating >> to new server >> >> new server is CentOS 7.3, but, the Centos repo version is >> >> dovecot x86_64 1:2.2.10-7.el7 >> >> what is the best way to install current release Dovecot on a new server ? > > GhettoForge has dovecot22 packages as well which provide the latest > stable version of Dovecot for CentOS 6 and 7. Or consider compiling it yourself from source. It may be more work, but you get complete control over your versioning, your package dependencies, etc. If a bug that affects you gets fixed on a bleeding edge version (or is only available as a patch), you can fix it right away rather than waiting for the package maintainer to catch up to it. Joseph Tam <jtam.home(a)gmail.com>

2 1

Certificate cache on iOS with sending mail
by Alef Veld 10 Aug '17

10 Aug '17

So I generated a new certificate for dovecot, and ever since I have this weird problem that my iPhone can still receive mail but cannot send using that mailserver. Same for my iMac. My laptop works fine still and can do both. Local issue you would say right. I'm wondering if there is any cache for a certificate or something, my maillog shows up something like 10 bytes read, -1. So it returns an error. I deleted the accounts and created them again, still no go. Anyone had anything similar before? Sent from my iPhone

2 2

dict client auth-worker service count not obeyed?
by Peter Mogensen 10 Aug '17

10 Aug '17

Hi, I've noticed that in recent dovecot versions at least since 2.2.29 and not in 2.2.12 a dovecot auth-worker will happily issue two Lshared/passdb... queries on the same dict socket. Not always, but sometimes. It used to be that the dict client always closed the socket (AFAIK) after 1 query. But now I see 2 queries issued on the same connection. How does this work wrt. the service_count limit of the auth worker process being default 1 ?? Is it not obeyed? /Peter

1 0