- dovecot - dovecot.org

Re: Pathetic Upgrade Question: 2.0.9 to 2.3.0
by Peter 09 Jan '18

09 Jan '18

On 09/01/18 11:46, John Tulp wrote: > Should I send a response to your message via an email to > dovecot(a)dovecot.org ? > Or just reply to you directly like this ? You should always reply to the mailing list unless told otherwise. > For CentOS version, I need to support 32-bit x86 a while longer. Ok. > Could you possibly save me some time and provide a > link on the dovecot.org site ? https://repo.dovecot.org/ > I really did not want to install from > source, I was very surprised that I did not find a link to download a > completely built backage on dovecot.org. The official dovecot repo is fairly new, but also GhettoForge has been providing dovecot packages for CentOS 6 and 7 for quite some time now. > Regarding yum update, yes, I would assume that I would not run yum > update after that build/install. That's a bad idea. You need to run updates on a regular basis to fix new vulnerabilities that are discovered such as the very recent meltdown and spectre vulnerabilities (look these up, they're serious). > I'm really perplexed as to why yum update would not just take me to > 2.3.0 ??? I guess the RedHat folks just include "certain" releases of > packages in the repositories ? See: https://access.redhat.com/security/updates/backporting Peter

1 0

openssl question
by Selcuk Yazar 08 Jan '18

08 Jan '18

Hi we are using dovecot on secure port when i try to command openssl s_client -connect mail.mydomain:pop3s it works perfect. it says ***OK Dovecot ready*** Also i check from https://www.sslshopper.com/ssl-checker.html web page i can see all correct ceritificate paths but i try to this command openssl s_client -connect mail.mydomain:pop3s -starttls imap it says CONNECTED and hang. second command is correct? also my thunderbird client doesnt work with 143 port and STARTTLS. is this general issue or have we config error? thanks in advance Selçuk YAZAR

1 0

mail delivery interrupts force-resync
by Felipe Gasper 08 Jan '18

08 Jan '18

Hi all, We have recently had some power failures have led to corrupt mdbox instances. Dovecot’s fsck appears to get caught in a loop when the recipient has a large amount of mail. In the example log output below, each “rebuilding indexes” seems to be interrupted by a new IMAP connection. Later, when our folks realized the issue and blocked access to the mailbox, the index rebuild finished in about 90 seconds. Is it possible for the fsck to “lock” the mailbox or otherwise protect against this? Thank you! -Felipe Gasper ==================== - Jan 2 13:15:13 mx1.cpanel.net dovecot: imap(kenp(a)cpanel.net): Logged out in=1657, out=9420, bytes=1657/9420 Jan 2 13:15:13 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:13 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:13 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:13 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: mdbox /home/cpmailuser/mail/cpanel.net/aaron.stone/storage: rebuilding indexes -- Jan 2 13:15:18 mx1.cpanel.net dovecot: imap(a.lateef(a)cpanel.net): Connection closed (LIST finished 0.121 secs ago) in=56, out=1805, bytes=56/1805 Jan 2 13:15:18 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:18 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: mdbox /home/cpmailuser/mail/cpanel.net/aaron.stone/storage: rebuilding indexes -- Jan 2 13:15:23 mx1.cpanel.net dovecot: imap(w.little(a)cpanel.net): Connection closed (UID FETCH finished 0.098 secs ago) in=151, out=1903, bytes=151/1903 Jan 2 13:15:24 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:24 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): msgid=<20180102142708.383C9C2042D(a)hou-1.auth.dns.prod.cpanel.net>: saved mail to INBOX Jan 2 13:15:24 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:24 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: mdbox /home/cpmailuser/mail/cpanel.net/aaron.stone/storage: rebuilding indexes -- Jan 2 13:15:26 mx1.cpanel.net dovecot: imap(rochelemagne(a)cpanel.net): Logged out in=38, out=535, bytes=38/535 Jan 2 13:15:28 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:28 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: mdbox /home/cpmailuser/mail/cpanel.net/aaron.stone/storage: rebuilding indexes -- Jan 2 13:15:32 mx1.cpanel.net dovecot: imap-login: Login: user=<l.patterson(a)cpanel.net>, method=PLAIN, rip=208.74.121.106, lip=208.74.121.68, mpid=30642, TLS, session=<g+Ex7M9hSSnQSnlq> Jan 2 13:15:33 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:33 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:33 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:33 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:33 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: mdbox /home/cpmailuser/mail/cpanel.net/aaron.stone/storage: rebuilding indexes -- Jan 2 13:15:40 mx1.cpanel.net dovecot: imap(michael.karr(a)cpanel.net): Logged out in=38, out=535, bytes=38/535 Jan 2 13:15:40 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:40 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: mdbox /home/cpmailuser/mail/cpanel.net/aaron.stone/storage: rebuilding indexes -- Jan 2 13:15:44 mx1.cpanel.net dovecot: imap-login: Disconnected (auth failed, 2 attempts in 44 secs): user=<test(a)cpanel.net>, method=PLAIN, rip=189.4.115.5, lip=208.74.121.68, TLS, session=<OkJJ6s9hM+C9BHMF> Jan 2 13:15:44 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:44 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:44 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: fscking index file /home/cpmailuser/mail/cpanel.net/aaron.stone/storage/dovecot.map.index Jan 2 13:15:44 mx1.cpanel.net dovecot: lmtp(aaron.stone(a)cpanel.net): Warning: mdbox /home/cpmailuser/mail/cpanel.net/aaron.stone/storage: rebuilding indexes ========================

1 0

Duplicate mailbox id, mailbox does not exist when attempting to give a new guid
by Daniel Botting 08 Jan '18

08 Jan '18

Hi, We have one user whose mailbox cannot replicate as below, dovecot version is: 2.2.13 mail.log shows the below for the user: Jan 3 16:20:57 hostname dovecot: dsync-server(user): Error: Duplicate mailbox GUID <guid number> for mailboxes <mailbox name.sub folder> and <mailbox name.sub folder> - giving a new GUID <guid number> to <mailbox name.subfolder> Jan 3 16:20:57 hostname dovecot: dsync-server(user): Error: Couldn't update mailbox <sub folder name> GUID: Mailbox doesn't exist: <sub folder name> Looking at their mailbox the folder does exist. If you are able to assist that would be appreciated. Kind regards Daniel Botting Codethink Ltd

1 0

Re: TLS problem after upgrading from v2.2 to v2.3
by Joseph Tam 08 Jan '18

08 Jan '18

Jan Vejvalka <jan.vejvalka(a)lfmotol.cuni.cz> writes: >> Mine are below and they work just fine: >> >> ssl_cipher_list = >> ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!3DES:!MD5:!PSK:!SSLv2:!SSLv3 I notice all the ciphers use DH, so did you a generate a permanent DH key? (https://wiki2.dovecot.org/Upgrading/2.3) ssl-parameters.dat file is now obsolete. You should use ssl_dh setting instead: ssl_dh=</etc/dovecot/dh.pem You can convert an existing ssl-parameters.dat to dh.pem: dd if=/var/lib/dovecot/ssl-parameters.dat bs=1 skip=88 | openssl dh -inform der > /etc/dovecot/dh.pem Joseph Tam <jtam.home(a)gmail.com>

2 1

Locks directory change
by Federico Bartolucci 08 Jan '18

08 Jan '18

Hello, it's the first time for me writing to the list, I'm trying to change the location into which the Dovecot's locks are done reserving a special temporary directory on an other partition, then adding to the dovecont.conf the line: mail_location = maildir:~/Maildir:VOLATILEDIR=/tmp_lock/%2.256Nu/%u so that through the VOLATILEDIR directive the locks should be written in this path. We observe though that the locks for many users are still done in the real maildir (NFS mounted filesystem) as if in some situations this instruction is not effective. Anybody knows if are there other things to change or to do or what could be the reason? (for instance to login in a specific way or doing a particular operation). Regards, Federico

3 3

Removing IMAP ID command
by Alex Hautequest 08 Jan '18

08 Jan '18

Hello all. Happy 2018! How can I disable the dovecot IMAP ID command, or hide the product name, so one does not eyeball what server software I am running (which happens to be v2.2.33.2)? Please see below for an example: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Ready. * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN A001 OK Pre-login capabilities listed, post-login capabilities have more. * ID ("name" "Dovecot") A002 OK ID completed. A003 BAD Error in IMAP command received by server. * BYE Logging out A004 OK Logout completed. It does not seems POP3 advertises itself: +OK Ready. +OK CAPA TOP UIDL RESP-CODES PIPELINING AUTH-RESP-CODE STLS SASL . Thanks and regards, Alex.

2 1

Mailing list content filtering changes
by Timo Sirainen 07 Jan '18

07 Jan '18

I've now disabled all content filtering in Mailman, because of the failing DKIM/DMARC issues. Hopefully that solves them for now.. Although this will mean that we'll probably start getting HTML mails to this list, which isn't ideal. I guess an alternative could be to reject any mails with text/html MIME part, but that could prevent some people from sending any mails to this list unless they switch to a different client/webmail.. Also that feature doesn't seem to be possible at least with the Mailman version we're currently using. BTW. All/most of the Gmail and Yahoo users just got disabled by mailman due to DMARC bounces. I've (hopefully) re-enabled mail for all of them.

2 1

Re: Updated Dovecot 2.3.0 now getting 2 strange log errors
by tony 07 Jan '18

07 Jan '18

I did some more digging around and found this is reproducible on multiple hosts running the same version of Dovecot/Pigeonhole/Postfix. The problem resurfaces on any host to an account with enabled Vacation/OOO response. The Vacation/OOO reply filter was created in Roundcubemail, but has been fine for years. One thing to note is in Dovecot 2.3.0 I did enable UTF8, but even if I disable UTF8 the issue remains. What I have discovered after digging around is.. * After a fresh postfix restart all expected processes are running without any postdrop process. postgrey 13080 0.0 0.2 73036 21108 ? Ss 17:23 0:00 postgrey --inet=127.0.0.1:10030 --pidfile=/run/postgrey/postgrey.pid --group=postgrey --user=postgrey --daemonize --greylist-text=Greylisted for %s seconds --auto-whitelist-clients root 13107 0.0 0.0 385700 108 ? Ssl 17:23 0:00 /usr/local/bin/pwhois_milter -i /run/pwhois_milter/pwhois_milter.pid -l /var/log/mail/mail.log -u postfix -g postfix -w global.pwhois.org root 13192 0.0 0.0 122536 5856 ? Ss 17:23 0:00 /usr/lib/postfix/bin/master -w postfix 13193 0.0 0.1 138524 8996 ? S 17:23 0:00 pickup -l -t unix -u postfix 13194 0.0 0.1 138572 9088 ? S 17:23 0:00 qmgr -l -t unix -u postfix 13320 0.0 0.1 163908 9832 ? S 17:24 0:00 proxymap -t unix -u postfix 13321 0.0 0.1 142756 9632 ? S 17:24 0:00 tlsmgr -l -t unix -u postfix 13322 0.0 0.1 138524 9280 ? S 17:24 0:00 anvil -l -t unix -u postfix 13352 0.0 0.1 168896 13520 ? S 17:24 0:00 smtpd -n smtp -t inet -u -o stress= -s 2 -o content_filter=spamassassin postfix 13539 0.0 0.1 163920 10156 ? S 17:24 0:00 trivial-rewrite -n rewrite -t unix -u postfix 14369 0.0 0.1 164300 10340 ? S 17:26 0:00 cleanup -z -t unix -u postfix 14370 0.0 0.1 124180 8844 ? S 17:26 0:00 pipe -n spamassassin -t unix user=spamd argv=/usr/bin/vendor_perl/spamc -f -e /usr/sbin/sendmail -oi -f ${sender} ${recipient} postfix 14375 0.0 0.1 142856 9344 ? S 17:26 0:00 lmtp -t unix -u vmail 14446 0.0 0.0 44008 7496 ? S 17:26 0:00 dovecot/quota-status -p postfix * During the problem where the logs are complaining about permission denied and sendmail exiting with signal 15 (caused by inbound email to an address with enabled Vacation notice filter) there is a running postdrop process and several expected processes are not running. postgrey 13080 0.0 0.2 73036 21132 ? Ss 17:23 0:00 postgrey --inet=127.0.0.1:10030 --pidfile=/run/postgrey/postgrey.pid --group=postgrey --user=postgrey --daemonize --greylist-text=Greylisted for %s seconds --auto-whitelist-clients root 13107 0.0 0.0 461572 408 ? Ssl 17:23 0:00 /usr/local/bin/pwhois_milter -i /run/pwhois_milter/pwhois_milter.pid -l /var/log/mail/mail.log -u postfix -g postfix -w global.pwhois.org root 13192 0.0 0.0 122536 5856 ? Ss 17:23 0:00 /usr/lib/postfix/bin/master -w postfix 13193 0.0 0.1 138524 8996 ? S 17:23 0:00 pickup -l -t unix -u postfix 13194 0.0 0.1 138644 9128 ? S 17:23 0:00 qmgr -l -t unix -u postfix 13321 0.0 0.1 142756 9632 ? S 17:24 0:00 tlsmgr -l -t unix -u postfix 20793 0.0 0.1 138524 9092 ? S 17:39 0:00 anvil -l -t unix -u vmail 25340 0.0 0.0 44108 7664 ? S 17:46 0:00 dovecot/quota-status -p postfix vmail 26298 0.0 0.1 122088 8536 ? S 17:49 0:00 /usr/bin/postdrop -r —— * When the issue is not present, an email TO any address with a disabled Vacation/OOO response filter is processed with no issues and stored in the respective folder moved by an existing filter not related to Vacation/OOO. Expected processes are still running (no postdrop process which when running seems to be causing the problem) * When the issue is not present, an email TO an address with a enabled Vacation/OOO response filter is processed and stored in the Inbox, but an auto-response fails to send. The result are these errors with the permission denied being repeated every ~minute. Dec 29 17:49:58 lmtp(jsomeone(a)domain.email)<26296><qbe8H6jwRlq4ZgAAUXb6+w>: Error: sieve: msgid=<CAE2c3QaGTiFDt5rdHEy2YeoSe+XBcB9Q5SGeOtknWKf2wgXZhQ(a)mail.gmail.com>: failed to send vacation response to someone(a)gmail.com: <Failed to execute sendmail> (temporary error) Dec 29 17:50:08 lmtp: Error: postdrop: warning: mail_queue_enter: create file maildrop/569031.26298: Permission denied * After the problem starts again with the errors shown in the logs a postdrop process stays running in the background. After a short while the number of postfix processes decreases. * If I kill the postdrop process then the logged errors stop and the expected processes all show up again. I am running out of ideas on why this has suddenly surfaced. - TC

5 12

quota issue - fs backend troubles with mount
by Arturo Bianchi 07 Jan '18

07 Jan '18

Hi, with the last update to version 2.2.33.2 I had problems with quota management; the plugin no longer reads the configuration correctly or something undocumented has changed! Until the version 2.2.30.2 the mount parameter work well, now no longer; so with... plugin { quota = fs:HOME:mount=/home quota2 = fs:INBOX:mount=/var/spool } ...the server no longer works and I read this in the log: Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so Debug: Quota root: name=HOME=fs args=mount=/home Debug: Quota grace: root=HOME bytes=0 (10%) Debug: Quota root: name=INBOX backend=fs args=mount=/var/spool Debug: Quota grace: root=INBOX bytes=0 (10%) Error: User initialization failed: Failed to initialize quota: Quota root HOME: fs quota init failed: Unknown parameter for backend fs: =/home I saw that the method for acquiring the parameters was revised in the src/plugins/quota/quota-fs.c but I still could not understand why it fails! Some advice? Do I have a formatting problem or am I missing some news about it? Thanks, Arturo. -- 73s

1 1