- dovecot - dovecot.org

Re: Minor patches for builds against ancient platforms
by Joseph Tam 15 Jun '17

15 Jun '17

> I do know that this little box of horrors has 200-300MB mbox INBOXes on an > ext3 filesystem formatted in 2005. I am very nervous about converting them to > Maildir at this point. Fortunately, it just involves reformatting the data and a little reconmfiguration of dovcot. If you can find the tool and disk space, it's well worth doing. Of course, when running a proverbial dinosaur, you're often more preoccupied with preventing the next proverbial meteorite strike. > What I meant was, are certain types of filenames "blocked" by policy from > being created via IMAP commands? I'm sure I could run a few tests to answer > this for myself, or better still, go through Timo's code. I never saw anything that could do that -- maybe you can torture the virtual mailbox facility to get that done. If all your concerned is dovecot dot-files, you can place the indices somewhere else other than the user's filesapace. > One last problem area is that many users have soft-links to mailboxes > located on a second drive, but these never appear in folder enumeration > lists or they appear grayed out in SeaMonkey/Thunderbird. I've tried > just symbolically linking to directories containing other mboxes, but > sometimes it works, and sometimes it doesn't. I wonder if there's > paranoia checking in the code that follows symbolic links to ensure > that uids/gids of the "owning" directory and the linked-to directory > (or files within it) are the same. It works for me. From what I see, the ownership of the symlink is ignored; it's the underlying file that counts. Maybe a subscription issue? Joseph Tam <jtam.home(a)gmail.com>

2 1

Re: Minor patches for builds against ancient platforms
by Joseph Tam 14 Jun '17

14 Jun '17

"M. Balridge" <dovecot(a)r.paypc.com> writes: > I assume it's a rarely seen issue because few Dovecot users compile the > software in caves on computers powered by horse-pulled generator > wheels. I resemble that remark. >> Warning: Transaction log file /home/luser/mail/.imap/INBOX/dovecot.index.log >> was locked for 95 seconds (rotating while syncing) Timo recently explained to me it's probably caused by slow I/O or processing. This explanation is consistent with my observation that the users who get these messages have jumbo mailboxes. > imap(luser): Error: fchown(/home/luser/mail/.subscriptions.lock, > group=501(coregroup)) failed: Operation not permitted (egid=200(users), group > based on /home/luser/mail - see http://wiki2.dovecot.org/Errors/ChgrpNoPerm) > > imap(luser): Error: file_dotlock_open() failed with subscription file > /home/luser/mail/.subscriptions: Operation not permitted > > .subscriptions doesn't exist either as a file or a directory in the named > directories. > > Is there a "filter" against dot-files being opened within the bowels of dovecot? You can disable dotclock altogether, but I don't think this is what you meant. You can use locking method "dotlock_try" rather than "dotlock" -- the former will ignore quota/permissions problems and plow on. (It still logs it.) You could also align luser's mail folder group with with luser's GID, which is usually what I do. Maybe locks are created even when files don't exist as there may be a race condition where another process is creating/deleting it at the same time. Joseph Tam <jtam.home(a)gmail.com>

4 5

v2.2.30 released
by Timo Sirainen 13 Jun '17

13 Jun '17

https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.30.tar.gz.sig * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all failed authentications in 2 second intervals. Also it could have worked only when passwords were stored in plaintext in the passdb. * master process sends SIGQUIT to all running children at shutdown, which instructs them to close all the socket listeners immediately. This way restarting Dovecot should no longer fail due to some processes keeping the listeners open for a long time. + auth: Add passdb { mechanisms=none } to match separate passdb lookup + auth: Add passdb { username_filter } to use passdb only if user matches the filter. See https://wiki2.dovecot.org/PasswordDatabase + dsync: Add dsync_commit_msgs_interval setting. It attempts to commit the transaction after saving this many new messages. Because of the way dsync works, it may not always be possible if mails are copied or UIDs need to change. + imapc: Support imapc_features=search without ESEARCH extension. + imapc: Add imapc_features=fetch-bodystructure to pass through remote server's FETCH BODY and BODYSTRUCTURE. + imapc: Add quota=imapc backend to use GETQUOTA/GETQUOTAROOT on the remote server. + passdb imap: Add allow_invalid_cert and ssl_ca_file parameters. + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. + doveadm mailbox status: Add "firstsaved" field. + director_flush_socket: Add old host's up/down and vhost count as parameters - More fixes to automatically fix corruption in dovecot.list.index - dsync-server: Fix support for dsync_features=empty-header-workaround - imapc: Various bugfixes, including infinite loops on some errors - IMAP NOTIFY wasn't working for non-INBOX if IMAP client hadn't enabled modseq tracking via CONDSTORE/QRESYNC. - fts-lucene: Fix it to work again with mbox format - Some internal error messages may have contained garbage in v2.2.29 - mail-crypt: Re-encrypt when copying/moving mails and per-mailbox keys are used. Otherwise the copied mails can't be opened. - vpopmail: Fix compiling

7 12

rescann / reindex / rebuild a subfolder structure
by Götz Reinicke - IT Koordinator 13 Jun '17

13 Jun '17

Hi, an user is missing all mail from a folder and all subfolders which are still saved in the users maildir directory on the dovecot server. From an imap client she sees the main folder but empty. No subfolders. She told me with an other imap client and a new created account she has the same problem. Question: Can I resync / regenerate some folder... index.... something....-files from the dovecot side? Thanks for hints and regards . Götz

1 0

Re: Minor patches for builds against ancient platforms
by Joseph Tam 13 Jun '17

13 Jun '17

> On that note, has anyone written a tool that "harmonises" users mail > directories' permissions - ideally reading the dovecot configuration to assess > where *THE* mail directories are actually used by dovecot? doveadm user $user which will supply the second half: it will spit out the UID, GID, home and mail directories of a user as specified by dovecot's configuration. > I was surprised by the pickiness of the group ownership/permissions > issues, though reflecting on things, I can see why you'd at least want > some logging by default for those conditions. This is a consequence of writing secure software: it employs least privilege so that a fault will not result in someone being able to mess around with someone else's mail (or indices). GID can also govern access to shared mailboxes. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: namespace and folders
by Joseph Tam 13 Jun '17

13 Jun '17

Gregory Sloop <gregs(a)sloop.net> writes: > Using mbox format and this namespace > > namespace { > inbox = yes > hidden = yes > prefix = INBOX/ > } > ... > This is not a terrible problem, but it's cosmetically ugly and confusing for users. > I'd prefer to only see these folders as subscribed as sub-folders [or sub-items] under inbox. Pardon my naievty, but couldn't you just remove this namespace altogether and get rid of at least one set of duplicates (although it probably keep the non-preferred one). Joseph Tam <jtam.home(a)gmail.com>

1 0

service(auth): command startup failed?
by HL1234 12 Jun '17

12 Jun '17

Hello, I need help because since some days I can not figure out what error this is and where it come from. I have used dovecot since years. Know after an update it is broken. First I like to give you some data: It's a FreeBSD 11.0 Server with sendmail (SMTP) and dovecot for IMAP with SSL. #dovecot --build-options Build options: ioloop=kqueue notify=kqueue ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL drivers: mysql Passdb: checkpassword ldap pam passwd passwd-file sql Userdb: checkpassword ldap nss passwd prefetch passwd-file sql #dovecot --version 2.2.30.2 (c0c463e) I install the update with the FreeBSD ports. Before the update all was running fine. The state know is: form my client Outlook I can send eMail above SMTP. When I try to get my eMails by the IMAP-Server it is blocked. I have look around in the config files but I see nothing what has could be changed. I have tried to make new *.pem files with using the script in /usr/local/share/examples/dovecot/ but this havn't bring a solution. I need help for this error i see in the logs: dovecot.log master: Error: service(auth): command startup failed, throttling for 2 secs auth: Error: auth: environment corrupt; missing value for DOVECOT_ auth: Fatal: unsetenv(RESTRICT_SETUID) failed: Bad address auth: Error: auth: environment corrupt; missing value for DOVECOT_ auth: Fatal: unsetenv(RESTRICT_SETUID) failed: Bad address ..... dovecot-info.log imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 1 secs): user=<>, rip=77.178.105.78, lip=88.74.25.120, TLS Jun 12 23:01:15 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 8 secs): user=<>, rip=58.218.194.81, lip=88.74.25.120, TLS handshaking .... dovecot-debug.log imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [77.178.105.78] imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [77.178.105.78] imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [77.178.105.78] imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [77.178.105.78] auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth auth: Debug: Module loaded: /usr/local/lib/dovecot/auth/lib20_auth_var_expand_crypt.so auth: Debug: Read auth token secret from /var/run/dovecot//auth-token-secret.dat Have anyone an idea what is going wrong and how to fix it? Harald -- View this message in context: http://dovecot.2317879.n4.nabble.com/service-auth-command-startup-failed-tp… Sent from the Dovecot mailing list archive at Nabble.com.

1 0

Redis auth?
by Mark Moseley 12 Jun '17

12 Jun '17

I was curious what the status of this redis auth patch is: https://dovecot.org/list/dovecot/2016-June/104763.html

1 0

Re: Log authentication attempts
by j.emerlik 12 Jun '17

12 Jun '17

We alse have same problem, now we are running Dovecot 2.2.30.2 and also use Dovecot SASL for SMTP authentication (postfix 2.11). We need to save all failed login attempts to database as source IP address, username and date and time but post-login script can do this but only after successful login. Failed login attempts information may be useful in the fight with bruteforce attacks. It's possible to execude some script after failed login ("Password mismatch") ? Regards, Jacek

4 5

pigeonhole: imapsieve: AntiSpam example
by Larry Rosenman 12 Jun '17

12 Jun '17

Is there a reason why vnd.dovecot.execute is called out for sieve_global_extensions but no configuration or require is there for it on: https://wiki.dovecot.org/HowTo/AntispamWithSieve thanks! -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

2 3