- dovecot - dovecot.org

questions concerning dovecot
by Rajesh M 04 Sep '17

04 Sep '17

hello all had some basic questions 1) what is the logic behind the numbering of files in the conf.d folder ... is this to define the sequence of execution of the config files ? 2) Concerning global scripts, is the default.sieve, before i understand that they get executed when the user does not have his private sieve script. are sieve_before, sieve_after and sieve_global_path all globalscripts ? thanks rajesh

2 1

Failed to repair mdbox index / wrong dbox version
by Peer Heinlein 04 Sep '17

04 Sep '17

After a filesystem crash dovecot isn't able to repair some of the m-Files. That's okay in general -- but I wonder why he's complaining about "wrong dsync version" if I execute "doveadm force-resync" locally: doveadm(user(a)mailbox.org): Warning: mdbox /mail-mailbox/mailbox.org/1846405//mdbox/storage: rebuilding indexes doveadm(user(a)mailbox.org): Error: Corrupted dbox file /xxxx//mdbox/storage/m.340 (around offset=154): Invalid dbox version I would accept every log that it's too broken to be repaired, but "Invalid dbox version"? Maybe it's somewhere else a bug that this m-file couldn't be repaired? # 2.2.32 (dfbe293): /etc/dovecot/dovecot.conf # Object storage plugin version 2.2.32 (afd3ef1) # Pigeonhole version 0.4.20 (11e3001) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.9 with mdbox/zlib. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

1 0

v2.2.32 released
by Timo Sirainen 04 Sep '17

04 Sep '17

https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz https://dovecot.org/releases/2.2/dovecot-2.2.32.tar.gz.sig Two more fixes since rc2. And repeating: There are various changes in this release that can be used to significantly reduce disk IO with: 1) NFS storage especially, but I guess also other remote filesystems and even some with local disks 2) When mail storage and INDEX storage are separated * imapc: Info-level line is logged every time when successfully connected to the remote server. This includes local/remote IP/port, which can be useful for matching against external logs. * config: Log a warning if plugin { key=no } is used explicitly. v2.3 will support "no" properly in plugin settings, but for now any value at all for a boolean plugin setting is treated as "yes", even if it's written as explicit "no". This change will now warn that it most likely won't work as intended. + Various optimizations to avoid accessing files/directories when it's not necessary. Especially avoid accessing mail root directories when INDEX directories point to a different filesystem. + mail_location can now include ITERINDEX parameter. This tells Dovecot to perform mailbox listing from the INDEX path instead of from the mail root path. It's mainly useful when the INDEX storage is on a faster storage. + mail_location can now include VOLATILEDIR=<path> parameter. This is used for creating lock files and in future potentially other files that don't need to exist permanently. The path could point to tmpfs for example. This is especially useful to avoid creating lock files to NFS or other remote filesystems. For example: mail_location=sdbox:~/sdbox:VOLATILEDIR=/tmp/volatile/%2.256Nu/%u + mail_location's LISTINDEX=<path> can now contain a full path. This allows storing mailbox list index to a different storage than the rest of the indexes, for example to tmpfs. + mail_location can now include NO-NOSELECT parameter. This automatically deletes any \NoSelect mailboxes that have no children. These mailboxes are sometimes confusing to users. + mail_location can now include BROKENCHAR=<char> parameter. This can be useful with imapc to access mailbox names that aren't valid mUTF-7 charset from remote servers. + If mailbox_list_index_very_dirty_syncs=yes, the list index is no longer refreshed against filesystem when listing mailboxes. This allows the mailbox listing to be done entirely by only reading the mailbox list index. + Added mailbox_list_index_include_inbox setting to control whether INBOX's STATUS information should be cached in the mailbox list index. The default is "no", but it may be useful to change it to "yes", especially if LISTINDEX points to tmpfs. + userdb can return chdir=<path>, which override mail_home for the chdir location. This can be useful to avoid accessing home directory on login. + userdb can return postlogin=<socket> to specify per-user imap/pop3 postlogin socket path. + cassandra: Add support for result paging by adding page_size=<n> parameter to the connect setting. + dsync/imapc, pop3-migration plugin: Strip also trailing tabs from headers when matching mails. This helps with migrations from Zimbra. + imap_logout_format supports now %{appended} and %{autoexpunged} + virtual plugin: Optimize IDLE to use mailbox list index for finding out when something has changed. + Added apparmor plugin. See https://wiki2.dovecot.org/Plugins/Apparmor - virtual plugin: A lot of fixes. In many cases it was also working very inefficiently or even incorrectly. - imap: NOTIFY parameter parsing was incorrectly "fixed" in v2.2.31. It was actually (mostly) working in previous versions, but broken in v2.2.31. - Modseq tracking didn't always work correctly. This could have caused imap unhibernation to fail or IMAP QRESYNC/CONDSTORE extensions to not work perfectly. - mdbox: "Inconsistency in map index" wasn't fixed automatically - dict-ldap: %variable values used in the LDAP filter weren't escaped. - quota=count: quota_warning = -storage=.. was never executed (try #2). v2.2.31 fixed it for -messages, but not for -storage. - imapc: >= 32 kB mail bodies were supposed to be cached for subsequent FETCHes, but weren't. - quota-status service didn't support recipient_delimiter - acl: Don't access dovecot-acl-list files with acl_globals_only=yes - mail_location: If INDEX dir is set, mailbox deletion deletes its childrens' indexes. For example if "box" is deleted, "box/child" index directory was deleted as well (but mails were preserved). - director: v2.2.31 caused rapid reconnection loops to directors that were down.

2 1

Commands loging to mail log
by Slobodan Zdravkovic 04 Sep '17

04 Sep '17

Hi, In case when user login with pop3 and only download only mail headers (partial download), but not email body, there is nothing in mail.log Is it possible to configure one of the existing dovecot plugins to log actions like TOP and LIST or is it possible to write new plugin for dovecot which can fetch this actions ? Thank you and regards,

1 0

Mixed Autehtnication and password schemes
by Raymond Sellars 04 Sep '17

04 Sep '17

Hi Looking for some confirmation/direction on how to achieve the following. We have a requirement to support both SASL PLAIN and DIGEST-MD5 authentication (certification reasons). In addition to this we have an application (webmail) that utilises a master password pattern for access, as the contain web portal provides the necessary authentication. I have access to users passwords in PLAIN text and looking to utilise the dict lookup mechanism for passwords. Problem #1 https://wiki2.dovecot.org/Authentication/MultipleDatabases - "Currently the fallback works only with the PLAIN authentication mechanism." The above not suggests I can't use DIGEST-MD5 with master password configuration, if using more than one passdb setup. I don't understand why there would be a restriction as the password validation should just fall through irrespective. Problem #2 How do I enforce some kind of account access policy Currently we're backing the authentication with an Identity and Authentication system. I would like to block IMAP access if a user's account is locked out, expired, or inactive. Similarly if there are too many IMAP attempts with the incorrect password I would like the account system wide to be locked out. With Dict lookup I don't seem a mechanism to keep the IDM system aware of login attempt/failures, since it pulls the plaintext password and validates internally. Is this possible? As a worse case does Dovecot implement any type of account access policies? Out IT security reviewers are hot on account policies, i.e. lockouts, expiries, and back off attempts. Thanks Raymond Solution Architect - Orion Health

2 4

Pigeonhole 0.4.20 source archive based on v. 0.4.20-rc1?
by Markus Schönhaber 02 Sep '17

02 Sep '17

Hi, looking at the source archive of pigeonhole 0.4.20 <https://pigeonhole.dovecot.org/releases/2.2/dovecot-2.2-pigeonhole-0.4.20.t…> I noticed that the contained ChangeLog mentions v0.4.20.rc1 as first entry and pigeonhole-version.h defines git revision 7cd71ba as version where I'd expect 4a55e6c. This is probably no big deal. But since Makefile.in and install-sh also differ (see attached diff) from the patch contained in <http://xi.rename-it.nl/debian.new/pool/jessie-rc-auto/dovecot-2.2/dovecot_2…> I thought I'd ask whether this is something without importance or something which should be changed. -- Regards mks

2 2

mail_log_events and dsync
by manu＠netbsd.org 02 Sep '17

02 Sep '17

Hello mail_log_events is handy to track what happened to a given message. Unfortunatly, it seems dsync activity is not captured. This causes messages to appear or vanish without a log trace. Did I miss a setting to get it? How should I track how something went wrong with dsync? -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu(a)netbsd.org

1 0

RE: General IMAP question
by Joseph Tam 02 Sep '17

02 Sep '17

"Scott Techlist" <techlist06(a)msws.org> writes: > How will the IMAP account behave with the current mail_location setting below? > > mail_location = mbox:~/mail:INBOX=/var/mail/%u > > That is, where will the IMAP account's mail "go"? Right now it goes to > /var/mail/[localusername]. Maybe incorrectly, I assumed IMAP required > Maildir format? How are folders handled with this setting?. The one > IMAP account would be used for spamassassin training, it would need 2 > shared/public folders ("spam", "ham"). IMAP is a protocol: it does not dictate the storage format. You're free to use whatever format dovecot supplies a backend for, including mbox or maildir. What your mail_location specifies is that the INBOX is a mbox (not maildir) formatted file located at /var/mail/[localusername]. Other mailboxes are located in ~[localusername]/mail/* (also mbox formatted). If the IMAP account requires 2 externally supplied mailboxes or folders (spam, ham) accessible via IMAP, you'll either have to copy them into the IMAP user's mail/ folder, or setup special name spaces that maps to the mailboxes' path. The mailboxes need appropriate file permissions so that the IMAP user can access it. Joseph Tam <jtam.home(a)gmail.com>

1 0

Sync mailservera!
by nlekkas＠gmail.com 02 Sep '17

02 Sep '17

Hello to all ! I have two servers using dovecot and want to sync them with doveasm ...... I am using usersb as user backend ....database Can anyone help me config them... Is there any use guide about it ? Thans in advance for the help ! Nick

4 4

RE: General IMAP question
by Scott Techlist 01 Sep '17

01 Sep '17

Software is Centos7, Dovecot 2.2.10 >Use that single mailbox with IMAP, others stay to POP Thanks, I considered that and looked up the ways to restrict IMAP access. But: How will the IMAP account behave with the current mail_location setting below? mail_location = mbox:~/mail:INBOX=/var/mail/%u That is, where will the IMAP account's mail "go"? Right now it goes to /var/mail/[localusername]. Maybe incorrectly, I assumed IMAP required Maildir format? How are folders handled with this setting?. The one IMAP account would be used for spamassassin training, it would need 2 shared/public folders ("spam", "ham").

3 2