- dovecot - dovecot.org

chroot: Error: Temp file creation to /tmp
by bvr 29 Jun '16

29 Jun '16

Hello, We are using dovecot (2.2.10) and it's working great! When I enable chrooting by appending /./ to the homedirs I'm getting errors like this: mail1 dovecot[47074]: imap(user): Error: Temp file creation to /tmp/dovecot.imap.mail1.70079. failed: No such file or directory On the surface everything seems to be working fine and I have not been able to produce the error myself. Any ideas? Thanks in advance, bvr.

2 2

exempt local auth-client UNIX socket from failed login penalty // add to login_trusted_networks ?
by Steffen Kaiser 29 Jun '16

29 Jun '16

-----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 immediately following each connect /var/run/dovecot2.2/auth-client attempt good auth 2s penalty OK disconnect Can I disable auth_failure_delay for local UNIX sockets? How do I add it to login_trusted_networks? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBV20MbHz1H7kL/d9rAQKm1AgAiVjjSimUTapEbhqHwZzfQWLzcJlkfm2W z5smziGbVELYb0/COPd84GK6wyUF7+3iRZOuVPhLRdljhB72PWRe+hHX3KgMWHr2 1o5WLkX+0cGEwSXMvJ2w3ee/zmxYxva2WI+PjSzkgvvhxGMtnIxO7mMglEV5zbbq ZxJcC1Ba4T9qpUhRIw3EQ5VPRs4cnLBz3Im4IDGLduWAGJYf/Rrxh+x+k3IqMtzb v92ErjgQtz5bN+bgEtQ8C33UehoZeZ93eA3V8o/OiwZPtWyneWL6Yqwxni4LjtLI R4wuu0N6Ea/BbA/fsElquRer0bXH2Zkt5mckJpDG6Rbe/IO5WYXq0A== =axyE -----END PGP SIGNATURE-----

2 2

dsync unstable? (other strange detail)
by Heiko Schlittermann 29 Jun '16

29 Jun '16

Hi, I'm trying to migrate from Cyrus (remote side) to Dovecot 2.2.24 (local). On the local side the destinations folders, and indexes are empty. The command I'm using is doveadm \ -o mail_plugins= \ -o imapc_master_user=<cyrus-user> \ -o imapc_password=<cyrus-password> \ -o imapc_host=<cyrus-ip> \ \ -o imapc_ssl_verify=no \ -o imapc_ssl=imaps \ -o imapc_port=993 \ backup -f -u "heiko" -R imapc: \ || { rc=$? echo "EXIT: $rc" >&2 exit $rc } On successive runs of the above command I get: dsync(heiko): Warning: Deleting mailbox 'Serververwaltung.Mailinglisten Anforderung': UID=16 GUID= is missing locally EXIT: 75 dsync(heiko): Warning: Deleting mailbox 'Serververwaltung.Mailman': UID=2 GUID= is missing locally EXIT: 75 dsync(heiko): Warning: Deleting mailbox 'Serververwaltung.Servermeldungen': UID=514 GUID= is missing locally EXIT: 75 dsync(heiko): Warning: Deleting mailbox 'Serververwaltung.Servermeldungen.AIDE': UID=188292 GUID= is missing locally EXIT: 75 dsync(heiko): Warning: Deleting mailbox 'Serververwaltung.Servermeldungen.AIDE.AIDE - 2012': UID=9343 GUID= is missing locally EXIT: 75 Any idea where to look next? Is 'doveadm backup' the wrong tool for such migration? (I'd say with about 2.2.9 I had similar problems, but at least it didn't stop at every subfolder.) Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

2 6

FTS search used / useful on an IMAP proxy?
by Luca Lesinigo 29 Jun '16

29 Jun '16

We are preparing an IMAP proxy based on dovecot-2.2.22, basic proxy functionality is already working and I’m trying to understand if having the FTS service configured on the dovecot *proxy* would be of any use. I do suspect it would be useless, I guess dovecot in imap proxy mode just forwards any command to the backend and does not bother to do anything about it, but I’m failing to find a definitive answer in the documentation. If I am guessing correctly, an fts service would only be useful if configured and working on the actual backend. Can anyone clarify my doubts? thank you, -- Luca Lesinigo

3 2

Disabling passdb pam in local.conf
by Patrick Ben Koetter 29 Jun '16

29 Jun '16

Greetings, I'm trying to create a configuration that leaves every config file deployed by an install process or paket management software untouched. The goal is to put every configuration required into /etc/dovecot/local.conf. I've come quite far, but I fail to disable pam as passdb service in local.conf. What I get if I run doveconf -n is this section: passdb { driver = pam } It is in there, because 10-auth.conf includes it: !include auth-system.conf.ext These actions are not an option at the moment: - modify /etc/dovecot/conf.d/10-auth.conf and comment/remove the !include-statement - create an /etc/dovecot/dovecot.conf which would contain all options required and would not include any other *.conf files Reading http://wiki2.dovecot.org/ConfigFile I see ways to include external files, but nothing to exclude a file in local.conf. Knowing Timo I would expect there is a way to acchieve what I want. I just don't seem to find it. What am I missing? Regards, p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

8 20

Suggestion: Split login_trusted_networks
by Peter Mogensen 29 Jun '16

29 Jun '16

Hi, For the upcoming 2.3 development, I'd like to re-suggest this: It seems the use of login_trusted_networks is overloaded. Example: * It's used for indicating which hosts you trust to provide XCLIENT remote IP's. (like a proxy) * It's used for indicating from which hosts you trust logins enough to disable auth penalty. (like in a webmail) Often these two uses cases have a different set of hosts. So you can't have one set of hosts which you trust for XCLIENT and another set of hosts you trust for not being the origin of brute force attacks. /Peter

2 2

Where Dovecot stores subscribtions for shared folder
by Miloslav Hůla 28 Jun '16

28 Jun '16

Hi, could please someone hint me, where Dovecot stores subscribtions for shared folder? Our configuration: namespace { disabled = no hidden = no ignore_on_failure = no inbox = no list = children location = maildir:/vmail/user/%%n/Maildir:INDEXPVT=/vmail/user/%n/Maildir/Shared/%%n prefix = user.%%n. separator = . subscriptions = yes type = shared } When I subscribe to 'user.test', I'll get ~Maildir/Shared/test/.INBOX/dovecot.index.pvt.log in it. When I unsubscribe from 'user.test', file stays there and its hash is the same. Kind regards, Milo

2 1

doveadm purge -A includes users with gid outside of limits and then reports error
by Michal Hlavinka 27 Jun '16

27 Jun '16

Hi, one our user reported that when he runs "doveadm purge -A" it goes through users that don't have gid in the first_valid_gid-last_valid_git range and it reports error. For example: doveadm(dovenull): Error: user dovenull: Mail access for users with GID 996 not permitted (see first_valid_gid in config file, gid from userdb lookup). doveadm(dovenull): Error: User init failed auth/userdb-passwd.c : passwd_iterate_want_pw(...) has checks for UID range, but does not have checks for GID range. Is there any reason for this? We've added those checks (see attached patch) and all seems fine. Cheers, Michal Hlavinka

1 0

Mailboxes on NFS or iSCSI
by Miloslav Hůla 27 Jun '16

27 Jun '16

Hello, we are running Dovecot (2.2.13-12~deb8u1) on Debian stable. Configured with Mailbox++, IMAP, POP3, LMTPD, Managesieved, ACL. Mailboxes are on local 1.2TB RAID, it's about 5310 accounts. We are slowly getting out of space and we are considering to move Mailboxes onto Netapp disk array with two independent network connections. Are there some pitfalls? Not sure we should use NTP or iSCSI mounts (both open implementations are not so shiny). Thanks for sharing any experiences. Kind regards, Milo

3 3

fts_solr crashs
by M. Koehler 27 Jun '16

27 Jun '16

Hi, I´ve set up in dovecot 2.2.24-1~auto+49 (from dovecot repo) fts_solr and fts_tika - jetti8 (from Debian Jessie) and latest tika-server running on a seperate machine. But if I want to rescan all messages for reindexing for instance all attachments with "doveadm -v index -u user(a)domain.tld INBOX" with 3137 mail in the INBOX it counts and then by 2900 mails the doveadm crashes with the following error message: doveadm(user(a)domain.tld): Info: INBOX: Caching mails seq=1..3137 2900/3137doveadm(user(a)domain.tld): Error: fts_solr: Indexing failed: 500 Java heap space java.lang.OutOfMemoryError: Java heap space doveadm(user(a)domain.tld): Panic: file http-client-request.c: line 769 (http_client_request_send_payload): assertion failed: (ret == 0) doveadm(user(a)domain.tld): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x8dc1e) [0x7f269375ec1e] -> /usr/lib/dovecot/libdovecot.so.0(+0x8dc98) [0x7f269375ec98] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f26936fd02e] -> /usr/lib/dovecot/libdovecot.so.0(http_client_request_send_payload+0xc8) [0x7f2693716b88] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(solr_connection_post_more+0x49) [0x7f2691c538b9] -> /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so(+0x361e) [0x7f2691c4f61e] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x9a17) [0x7f2692ad5a17] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x9e20) [0x7f2692ad5e20] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(fts_build_mail+0x999) [0x7f2692ad6809] -> /usr/lib/dovecot/modules/lib20_fts_plugin.so(+0x1056e) [0x7f2692adc56e] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_precache+0x29) [0x7f2693a1f7b9] -> doveadm(+0x2e947) [0x7f26943be947] -> doveadm(+0x28daf) [0x7f26943b8daf] -> doveadm(+0x2989d) [0x7f26943b989d] -> doveadm(doveadm_cmd_ver2_to_mail_cmd_wrapper+0x278) [0x7f26943ba788] -> doveadm(doveadm_cmd_run_ver2+0x560) [0x7f26943c8c70] -> doveadm(doveadm_cmd_try_run_ver2+0x37) [0x7f26943c8cc7] -> doveadm(main+0x1df) [0x7f26943aa33f] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f2693347b45] -> doveadm(+0x1a716) [0x7f26943aa716] I don´t see any shortages on the seperate solr machine. What could I do? How do I get more details to locate the problem?! Thanks a lot and regards, Michael

2 2

fts_solr not working
by Jeff Gamsby 27 Jun '16

27 Jun '16

I am running ISPConfig 3 on Debian and have managed to install the dovecot-solr and dovecot-fts plugins. I have solr running undet tomcat at http://localhost:8880 but the indexing is not working. I am using Dovecot 2.17 I do not understand namespaces and why fts_solr needs them, I just want to index the entire users Maildir. I am trying to index a users mailbox but am getting the following error: (changed user name) doveadm fts rescan -u user(a)user.com inbox doveadm(user(a)user.com): Error: Namespace prefix not found: inbox running that in debig mode gives: doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib20_fts_plugin.so doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib21_fts_solr_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so: undefined symbol: quota_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so doveadm(user(a)user.com): Debug: Added userdb setting: mail=maildir:/var/vmail/user.com/user/Maildir doveadm(user(a)user.com): Debug: Added userdb setting: plugin/quota_rule=*:storage=0B doveadm(user(a)user.com): Debug: Added userdb setting: plugin/sieve=/var/vmail/user.com/user/.sieve doveadm(user(a)user.com): Debug: Effective uid=5000, gid=5000, home=/var/vmail/user.com/user doveadm(user(a)user.com): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/vmail/user.com/user/Maildir doveadm(user(a)user.com): Debug: maildir++: root=/var/vmail/user.com/user/Maildir, index=, control=, inbox=/var/vmail/user.com/user/Maildir, alt= doveadm(user(a)user.com): Debug: fts: No fts setting - plugin disabled doveadm(user(a)user.com): Error: Namespace prefix not found: inbox in conf.d/10-mail.conf I have this namespace defined: namespace inbox { # Namespace type: private, shared or public #type = private # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. # The default however depends on the underlying mail storage format. #separator = # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # mail_location, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension. You'll most likely also want to set list=no. This is mostly # useful when converting from another server with different namespaces which # you want to deprecate but still keep working. For example you can create # hidden namespaces with prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = no protocol imap { plugin { fts = solr fts_solr = break-imap-search url=http://localhost:8880/solr/ } } protocol pop3 { plugin { fts = solr fts_solr = break-imap-search url=http://localhost:8880/solr/ } # Show the mailboxes under this namespace with LIST command. This makes the # namespace visible for clients that don't support NAMESPACE extension. # "children" value lists child mailboxes, but hides the namespace prefix. #list = yes # Namespace handles its own subscriptions. If set to "no", the parent # namespace handles them (empty prefix should always have this as "yes") #subscriptions = yes } I had to put this in dovecot.conf in order for the plugin to be enabled: mail_plugins = fts fts_solr solr is reachable at localhost:8880/solr and appears to be working. Please help, any suggestions are welcome Thanks

4 5

dsync is unstable?
by Heiko Schlittermann 27 Jun '16

27 Jun '16

Hi, I'm doing a backup from a Cyrus to a Dovecot (2.2.24) instance. On the dovecot side (localhost) I'm running doveadm \ -o mail_plugins= \ -o imapc_master_user=cyrus \ -o imapc_password=<cyrus-passwd> \ -o imapc_host=<cyrus-ip> \ \ -o imapc_ssl_verify=no \ -o imapc_ssl=imaps \ -o imapc_port=993 \ backup -f -u "heiko" -R imapc: dsync(heiko): Warning: Deleting mailbox 'Trash': UID=18290 already exists locally for a different mail: highest than remote's UIDs (remote UIDNEXT=19588) The destination (local system) does not change while running backup, the remote system (cyrus) can't be stopped while running this backup. Repeating the above command sometimes helps, sometimes not. Sometimes the names of the mailboxes dsync deletes change… Any idea how to stabilize it? I'm talking about cca 4500 mailboxes. Best regards from Dresden/Germany Viele Grüße aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

1 0

Postfix and Dovecot LDA vs. LMTP
by Michael Fox 26 Jun '16

26 Jun '16

I'm new to Dovecot and will be using it with Postfix. I'm looking for recommendations regarding the use of Dovecot's LDA or LMTP for virtual mailbox delivery. Many of the simple examples on the wiki use LDA. So I've set that up initially. But apparently an advantage of LMTP is recipient verification. So, as I understand it, LMTP would let Postfix know whether or not the message was deliverable to a local virtual recipient without needing to have a separate virtual recipients map in Postfix. That sounds like a nice simplification. But I see in Ubuntu that the dovecot-lmtp package is not marked with the Canonical support icon, like the pop, imap, and other packages are. I don't have a contract with Canonical. But I'm wondering why they would not support the lmtp package when they do support most of the others. Is it possible that the dovecot LMTP package is not as stable or reliable? I'd appreciate comments from experienced users of postfix with dovecot. Are you using Dovecot LDA or LMTP and why? Thanks much, Michael

8 14

Authentication Penalty with ID x-originating-ip, HAproxy
by Tobias 24 Jun '16

24 Jun '16

The wiki states that anvil's authentication penalties are skipped when IP is in login_trusted_networks. http://wiki.dovecot.org/Authentication/Penalty Is there a way to enable the authentication penalties for specific advertised remote IPs, when the connecting IP is in "login_trusted_networks", and it advertises the originating remote IP via 'ID ("x-originating-ip", "<remote-ip>")'? And with regards to HAproxy, is anvil's authentication penalties by default transparent with regards to the remote IP advertised in the proxy protocol header? /Tobias

1 1

FW: error using default_fields in passwd-file
by Michael Fox 24 Jun '16

24 Jun '16

I didn't see a response. Sending again and adding doveconf -n output. ---- I'm trying to put virtual user mail in: /var/vmail/<domain>/<user-local-part> I tried setting the home field in the userdb to /var/vmail/%d/%n But apparently variable expansion doesn't happen in the userdb because the Dovecot LDA created the literal directory /var/vmail/%d/%n/Maildir So then I tried to use default_fields as shown here: http://wiki2.dovecot.org/AuthDatabase/PasswdFile So I tried: userdb { driver = passwd-file args = username_format=%n /etc/dovecot/auth.d/%d/passwd default_fields = home=/var/vmail/%d/%n } But when I reload doveadm I get: doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 87: Unknown setting: default_fields I tried override_fields: userdb { driver = passwd-file args = username_format=%n /etc/dovecot/auth.d/%d/passwd override_fields = home=/var/vmail/%d/%n } And I get the same type of error: doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 87: Unknown setting: override_fields What gives? Michael doveconf -n: # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-86-generic i686 Ubuntu 12.04.5 LTS auth_verbose = yes disable_plaintext_auth = no mail_gid = vmail mail_location = maildir:~/Maildir mail_uid = vmail passdb { driver = pam } passdb { args = /etc/dovecot/deny-users deny = yes driver = passwd-file } passdb { args = username_format=%n /etc/dovecot/auth.d/%d/passwd driver = passwd-file } pop3_uidl_format = %08Xv%08Xu protocols = pop3 service auth { unix_listener auth-userdb { mode = 0600 user = vmail } } ssl = no ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } userdb { args = username_format=%n /etc/dovecot/auth.d/%d/passwd driver = passwd-file } protocol lda { postmaster_address = postmaster@xxxxx }

1 0

error using default_fields in passwd-file
by Michael Fox 23 Jun '16

23 Jun '16

I'm trying to put virtual user mail in: /var/vmail/<domain>/<user-local-part> I tried setting the home field in the userdb to /var/vmail/%d/%n But apparently variable expansion doesn't happen in the userdb because the Dovecot LDA created the literal directory /var/vmail/%d/%n/Maildir So then I tried to use default_fields as shown here: http://wiki2.dovecot.org/AuthDatabase/PasswdFile So my config is: userdb { driver = passwd-file args = username_format=%n /etc/dovecot/auth.d/%d/passwd default_fields = home=/var/vmail/%d/%u } But when I reload doveadm I get: doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 87: Unknown setting: default_fields I tried override_fields: userdb { driver = passwd-file args = username_format=%n /etc/dovecot/auth.d/%d/passwd override_fields = home=/var/vmail/%d/%u } And I get the same type of error: doveconf: Fatal: Error in configuration file /etc/dovecot/local.conf line 87: Unknown setting: override_fields What gives? Michael

1 0

fts lucene crashes in 2.2.24
by Wolfgang Rosenauer 23 Jun '16

23 Jun '16

Hi, I've just enabled FTS via Lucene on my Dovecot 2.2.24 installation but I see the indexer crashing ?always?. This simple testcase with a very tiny testing mailbox exposes the issue immediately: doveadm -v index -u anmesse INBOX Program received signal SIGSEGV, Segmentation fault. rescan_clear_unseen_mailbox (rescan_ctx=rescan_ctx@entry=0x0, vname=0x555555839820 "INBOX.Testfolder 2", hdr=hdr@entry=0x7fffffffdaf0) at lucene-wrapper.cc:831 831 (enum mailbox_flags)0); (gdb) bt full #0 rescan_clear_unseen_mailbox (rescan_ctx=rescan_ctx@entry=0x0, vname=0x555555839820 "INBOX.Testfolder 2", hdr=hdr@entry=0x7fffffffdaf0) at lucene-wrapper.cc:831 box = 0x7ffff76fd0ad <mailbox_list_iter_next+285> metadata = {guid = "\230\332\377\377\377\177\000\000\200߈UUU\000", virtual_size = 140737340823160, physical_size = 140737488345756, first_save_date = 140737488345840, cache_fields = 0x555500000000, precache_fields = (MAIL_FETCH_SAVE_DATE | MAIL_FETCH_PHYSICAL_SIZE | MAIL_FETCH_NUL_STATE | MAIL_FETCH_STREAM_BINARY | MAIL_FETCH_IMAP_BODY | MAIL_FETCH_IMAP_BODYSTRUCTURE | MAIL_FETCH_IMAP_ENVELOPE | MAIL_FETCH_FROM_ENVELOPE | MAIL_FETCH_REFCOUNT | MAIL_FETCH_BODY_SNIPPET | unknown: 1409286144), backend_ns_prefix = 0x0, backend_ns_type = (unknown: 4294957808)} #1 0x00007ffff489aade in rescan_clear_unseen_mailboxes (index=index@entry=0x555555822e20, rescan_ctx=rescan_ctx@entry=0x0) at lucene-wrapper.cc:863 iter = 0x55555588d530 info = <optimized out> vname = <optimized out> hdr = {last_indexed_uid = 0, settings_checksum = 3784394109, unused = 0} ns = 0x55555580f6c0 #2 0x00007ffff489b700 in lucene_settings_check (index=0x555555822e20) at lucene-wrapper.cc:429 set_checksum = <optimized out> ret = <optimized out> #3 lucene_index_build_init (index=0x555555822e20) at lucene-wrapper.cc:448 lock_path = 0x5555557dd320 "/srv/dovecot/anmesse/maildir/lucene-indexes/write.lock" st = {st_dev = 93823560581121, st_ino = 0, st_nlink = 140737344007992, st_mode = 4150696184, st_uid = 32767, st_gid = 5, __pad0 = 0, st_rdev = 93824995156880, st_size = 93824995175648, st_blksize = 140737351975397, st_blocks = 93824995096256, st_atim = {tv_sec = 140737488346056, tv_nsec = 5}, st_mtim = {tv_sec = 5, tv_nsec = 93824995156880}, st_ctim = { tv_sec = 93824995175648, tv_nsec = 140737488346352}, __glibc_reserved = {140737488346352, 93824995267672, 140737344364485}} exists = <optimized out> #4 0x00007ffff4899dbe in fts_backend_lucene_update_set_build_key (_ctx=0x55555583a550, key=0x7fffffffdcf0) at fts-backend-lucene.c:366 ctx = 0x55555583a550 backend = 0x555555822ce0 __FUNCTION__ = "fts_backend_lucene_update_set_build_key" #5 0x00007ffff674c984 in fts_backend_update_set_build_key (ctx=0x55555583a550, key=key@entry=0x7fffffffdcf0) at fts-api.c:175 __FUNCTION__ = "fts_backend_update_set_build_key" #6 0x00007ffff674dbb8 in fts_build_mail_header (block=0x7fffffffdcd0, block=0x7fffffffdcd0, ctx=0x7fffffffdd20) at fts-build-mail.c:174 hdr = <optimized out> key = {uid = 96, type = FTS_BACKEND_BUILD_KEY_HDR, part = 0x5555557dd2c0, hdr_name = 0x5555558396b0 "Return-Path", body_content_type = 0x0, body_content_disposition = 0x0} ret = <optimized out> #7 fts_build_mail_real (mail=0x555555838190, update_ctx=0x55555583a550) at fts-build-mail.c:548 block = {part = 0x5555557dd2c0, hdr = 0x555555839458, data = 0x55550000007c <error: Cannot access memory at address 0x55550000007c>, size = 0} ret = <optimized out> input = 0x555555838eb0 raw_block = {part = 0x5555557dd2c0, hdr = 0x5555558395e0, data = 0x0, size = 0} skip_body = false ctx = {mail = 0x555555838190, update_ctx = 0x55555583a550, content_type = 0x0, content_disposition = 0x0, body_parser = 0x0, word_buf = 0x0, pending_input = 0x0, cur_user_lang = 0x0} prev_part = 0x5555557dd2c0 parser = 0x555555839070 decoder = 0x555555839440 parts = 0x31 body_part = false body_added = false binary_body = <optimized out> error = 0x60 <error: Cannot access memory at address 0x60> #8 fts_build_mail (update_ctx=0x55555583a550, mail=mail@entry=0x555555838190) at fts-build-mail.c:594 _data_stack_cur_id = 5 #9 0x00007ffff675393e in fts_mail_index (_mail=0x555555838190) at fts-storage.c:501 ft = 0x5555558366a0 flist = 0x55555581ea68 #10 fts_mail_precache (_mail=0x555555838190) at fts-storage.c:520 _data_stack_cur_id = 4 mail = 0x555555838190 fmail = <optimized out> ft = <optimized out> #11 0x00007ffff76987b9 in mail_precache (mail=0x555555838190) at mail.c:401 _data_stack_cur_id = 3 p = 0x555555838190 #12 0x0000555555582fa7 in cmd_index_box_precache (box=0x55555582fd80) at doveadm-mail-index.c:75 ctx = 0x555555839be0 metadata = {guid = '\000' <repeats 15 times>, virtual_size = 0, physical_size = 0, first_save_date = 0, cache_fields = 0x0, precache_fields = (MAIL_FETCH_STREAM_HEADER | MAIL_FETCH_STREAM_BODY | MAIL_FETCH_RECEIVED_DATE | MAIL_FETCH_SAVE_DATE | MAIL_FETCH_PHYSICAL_SIZE | MAIL_FETCH_VIRTUAL_SIZE | MAIL_FETCH_UIDL_BACKEND | MAIL_FETCH_GUID | MAIL_FETCH_POP3_ORDER), backend_ns_prefix = 0x0, backend_ns_type = (unknown: 0)} counter = 0 max = 15 status = {messages = 15, recent = 0, unseen = 0, uidvalidity = 1048765368, uidnext = 151, first_unseen_seq = 0, first_recent_uid = 151, last_cached_seq = 0, highest_modseq = 0, highest_pvt_modseq = 0, keywords = 0x0, permanent_flags = 0, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 0, no_modseq_tracking = 0, have_guids = 1, have_save_guids = 1, have_only_guid128 = 0} mail = 0x555555838190 ret = 0 trans = 0x555555834310 search_args = 0x0 seq = <optimized out> #13 cmd_index_box (info=<optimized out>, info=<optimized out>, ctx=0x555555807410) at doveadm-mail-index.c:130 box = 0x55555582fd80 status = {messages = 130, recent = 0, unseen = 0, uidvalidity = 0, uidnext = 1434552496, first_unseen_seq = 21845, first_recent_uid = 4294958896, last_cached_seq = 32767, highest_modseq = 93824995069728, highest_pvt_modseq = 93824995074385, keywords = 0x555555819868, permanent_flags = 4150947016, permanent_keywords = 1, allow_new_keywords = 1, nonpermanent_modseqs = 1, no_modseq_tracking = 1, have_guids = 1, have_save_guids = 1, have_only_guid128 = 1} ret = 0 #14 cmd_index_run (_ctx=0x555555807410, user=0x5555558188b0) at doveadm-mail-index.c:201 _data_stack_cur_id = 2 iter = 0x55555582b9f0 info = <optimized out> ret = 0 user = 0x5555558188b0 _ctx = 0x555555807410 ctx = 0x555555807410 i = <optimized out> #15 0x000055555557dedf in doveadm_mail_next_user (ctx=ctx@entry=0x555555807410, cctx=cctx@entry=0x7fffffffe2a0, error_r=error_r@entry=0x7fffffffe0b8) at doveadm-mail.c:400 input = {module = 0x0, service = 0x5555555b15a9 "doveadm", username = 0x5555557da298 "anmesse", session_id = 0x0, session_id_prefix = 0x0, local_ip = {family = 0, u = {ip6 = {__in6_u = { ---Type <return> to continue, or q <return> to quit--- __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = { __in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, userdb_fields = 0x0, flags_override_add = (unknown: 0), flags_override_remove = (unknown: 0), no_userdb_lookup = 0, debug = 0} error = 0x20 <error: Cannot access memory at address 0x20> ip = <optimized out> ret = <optimized out> __FUNCTION__ = "doveadm_mail_next_user" #16 0x000055555557e843 in doveadm_mail_single_user (ctx=ctx@entry=0x555555807410, cctx=cctx@entry=0x7fffffffe2a0, error_r=error_r@entry=0x7fffffffe0b8) at doveadm-mail.c:431 __FUNCTION__ = "doveadm_mail_single_user" #17 0x000055555557e8fd in doveadm_mail_cmd_exec (ctx=ctx@entry=0x555555807410, cctx=cctx@entry=0x7fffffffe2a0, wildcard_user=wildcard_user@entry=0x0) at doveadm-mail.c:589 ret = <optimized out> error = 0x7ffff7fe89e8 "" #18 0x000055555557f6ef in doveadm_cmd_ver2_to_mail_cmd_wrapper (cctx=0x7fffffffe2a0) at doveadm-mail.c:1030 mctx = 0x555555807410 wildcard_user = <optimized out> username_args = {0x5555555b1479 "-u", 0x5555557da298 "anmesse", 0x0} fieldstr = 0x7ffff73d7423 <t_malloc0+35> "H\203\304\bH\211\330[]\303\017\037" username_args_count = <optimized out> i = <optimized out> mail_cmd = {alloc = 0x555555582ad0 <cmd_index_alloc>, name = 0x5555555b3e7b "index", usage_args = 0x5555555b2ee8 "[-u <user>|-A] [-S <socket_path>] [-q] [-n <max recent>] <mailbox mask>"} #19 0x000055555558c93c in doveadm_cmd_run_ver2 (argc=4, argv=0x5555557e13a0, cctx=cctx@entry=0x7fffffffe2a0) at doveadm-cmd.c:524 param = <optimized out> pargv = {arr = {buffer = 0x5555557d9a40, element_size = 104}, v = 0x5555557d9a40, v_modifiable = 0x5555557d9a40} opts = {arr = {buffer = <optimized out>, element_size = 32}, v = <optimized out>, v_modifiable = <optimized out>} pargc = 7 c = -1 li = 21845 pool = 0x5555557d9778 optbuf = 0x5555557d9790 __FUNCTION__ = "doveadm_cmd_run_ver2" #20 0x000055555558c9d7 in doveadm_cmd_try_run_ver2 (cmd_name=<optimized out>, argc=4, argv=0x5555557e13a0, cctx=0x7fffffffe2a0) at doveadm-cmd.c:447 cmd = <optimized out> #21 0x000055555556fb1f in main (argc=4, argv=0x5555557e13a0) at doveadm.c:376 cctx = {cmd = 0x5555557e8208, argc = 7, argv = 0x5555557d9a78, username = 0x5555557da298 "anmesse", cli = true, local_ip = {family = 0, u = {ip6 = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = { __in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0} cmd_name = 0x5555557e13dc "index" quick_init = false c = <optimized out> doveconf -n: # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 4.1.21-14-default x86_64 openSUSE 42.1 (x86_64) auth_mechanisms = plain login imap_id_log = * mail_gid = vmail mail_home = /srv/dovecot/%u mail_location = maildir:~/maildir mail_plugins = acl fts fts_lucene virtual zlib quota mail_uid = vmail mailbox_list_index = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace { list = children location = maildir:/srv/dovecot/%%u/maildir:INDEX=~/maildir/shared/%%u:CONTROL=~/maildir/shared/%%u prefix = shared.%%n. separator = . subscriptions = yes type = shared } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Entwürfe { special_use = \Drafts } mailbox "Gesendete Objekte" { special_use = \Sent } mailbox Sent { special_use = \Sent } mailbox "Sent Items" { special_use = \Sent } mailbox Spam { auto = create special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile acl_shared_dict = file:/srv/dovecot/shared-mailboxes.db fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars="@" quota = dict:User quota::file:%h/dovecot-quota quota_grace = 10%% quota_rule = *:storage=100M quota_rule2 = INBOX.Trash:storage=+10M quota_status_nosuser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full / Mailbox ist voll quota_status_success = DUNNO sieve = file:~/sieve;active=~/.dovecot.sieve zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0777 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { address = 127.0.0.1,::1 port = 12340 } } ssl_cert = < ssl_dh_parameters_length = 2048 ssl_key = < ssl_options = no_compression ssl_prefer_server_ciphers = yes userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { args = username_format=%n /etc/dovecot/shared-mailboxes default_fields = uid=600 gid=600 home=/srv/dovecot/%n driver = passwd-file } protocol lmtp { mail_plugins = acl fts fts_lucene virtual zlib quota sieve } protocol imap { mail_max_userip_connections = 30 mail_plugins = acl fts fts_lucene virtual zlib quota imap_acl imap_zlib imap_quota namespace inbox { location = mailbox Spam { autoexpunge = 90 days } mailbox Trash { autoexpunge = 370 days } prefix = } }

3 4

newbie userdb lookup problem
by Michael Fox 23 Jun '16

23 Jun '16

I'm new to Dovecot and I'm having trouble getting basic, flat file userdb lookups to work. This must have been asked before, but if so, I can't find it. I'm following the basic setup here: http://wiki2.dovecot.org/HowTo/SimpleVirtualInstall with a few minor differences. Output of doveconf -n is below, as well as relevant entries from postfix main.cf and master.cf. When I send a message to a virtual user that will be handled by Dovecot, Postfix hands it off to Dovecot LDA. But I get the following error in the log: Jun 22 20:53:33 xxxxx dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=5000(vmail) egid=5000(vmail) missing +r perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755) /var/run/dovecot/ is indeed owned by root:root with 0755 permissions. The actual passwd file used for userdb/passdb is currently owned by root:vmail with 0640 permissions. I read http://wiki2.dovecot.org/UserIds but I just don't understand the section on "Authentication process user". It's very vague. It doesn't explain which service is used for which circumstances or how to correlate the userdb/passdb file permissions with the service user/group settings for best security. The http://wiki2.dovecot.org/HowTo/SimpleVirtualInstall link mentions nothing about having to modify the auth or auth-worker services. And the http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix page mentions a new "doveauth" user which isn't described elsewhere and sets service auth to user postfix and group postfix, something not mentioned anywhere else. /etc/doveconf/10-master.conf says that the service auth socket is typically readable only by root. Uhm. OK. Well, my passwd file is owned by root. I don't know how that relates to the socket. So I don't understand the problem. Bottom line, each information source seems to say something completely different. I can't correlate the information in the above sources into any actionable result. Questions: Basically, can someone please explain how the permissions for userdb and passdb lookup work (i.e. file permissions vs. service permissions)? What's the best solution to solve the above problem permission problem in the most secure way? Adjust the config of service auth? If so, how and why? Or adjust my passwd file ownership? If so, how and why? I'm really trying to understand the why, not just the what. Thanks much. Michael Output of doveconf -n follows: # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-86-generic i686 Ubuntu 12.04.5 LTS auth_verbose = yes disable_plaintext_auth = no mail_gid = vmail mail_location = maildir:~/Maildir mail_uid = vmail passdb { driver = pam } passdb { args = username_format=%n /var/vmail/auth.d/%d/passwd driver = passwd-file } pop3_uidl_format = %08Xv%08Xu protocols = pop3 ssl = no ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } userdb { args = username_format=%n /var/vmail/auth.d/%d/passwd driver = passwd-file } protocol lda { postmaster_address = postmaster@xxxxx } Postfix main.cf: virtual_alias_maps = hash:/etc/postfix/virtual virtual_mailbox_domains = xxxx virtual_mailbox_maps = hash:/etc/postfix/vmailbox virtual_transport = dovecot Postfix master.cf: # Dovecot LDA # Ref: http://wiki2.dovecot.org/LDA/Postfix # Allows user+extension(a)domain.com (recipient_deliminter = + in main.cf) dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/lib/dovecot/dovecot-lda -f ${sender} -d ${user}@${nexthop} -m ${extension}

2 3

Pluggable SNI?
by Felipe Gasper 23 Jun '16

23 Jun '16

Hello, How feasible would it be to have a “pluggable” Dovecot setup that would permit arbitrary logic for fetching TLS/SNI certificates and key, rather than having to hard-code each domain’s resources in a configuration file? A couple scenarios that I envision such a framework being able to accommodate: 1) An internal TLS service that accepts queries via a UNIX socket by domain name and returns certificate/key. 2) A directory where these resources are stored, indexed by domain name. Thank you! -FG

2 2

post-login script and original remote ip in proxy mode
by j.emerlik 22 Jun '16

22 Jun '16

Hi, i have similar problem like this: "On Mon, 2013-05-27 at 23:40 +0300, Ibrahim Harrani wrote: > Hi, > > I am running dovecot on 3 qmail-ldap server backend. > dovecot configured to use auth_pop3 wrapper for authentication. > Users logins to the qmail-ldap pop3&imap pools randomly. If a user is > mailhost is not the connected server, dovecot proxies the connection to the > user mailhost. In this case, I can not get the original client IP address > via post-logins script on user host. I see only the first connected server > IP as $IP environment. Set login_trusted_networks setting pointing to the proxies' IPs/network and you'll get the original IP. Requires v2.1.2+ to work with pop3 proxying." What can I do in case if dovecot proxy is installed ona same server ? Setting of login_trusted_networks causes issue like: dovecot: imap-login: proxy(xxx): Login failed to xxx:9993: [UNAVAILABLE] Account is temporarily unavailable. dovecot: imap-login: Disconnected (internal failure, 1 successful auths) on port 9993 works service dovecot imap on port 8993 works service courier imap proxy works on 993

1 0

Storage upgrade maildir suggestions?
by Götz Reinicke - IT Koordinator 22 Jun '16

22 Jun '16

Hi, we start to run out of diskspace soon as our users start to keep mails for longer time periods. That's fine, but space consuming. The maildirs are about 1 TB in total, and not long ago we enabled zlib which is very nice. Now I have some thoughts about the next steps: a) Migrating the whole system to a new server with more storage? b) Install a virtual server for the mailsystem and an extra storage system may be NFS? c) Stay with the current server and move all mails to a bigger NFS storage. The last option c) would be the most easy one for me as I currently have NFS space. Any thoughts? Hints regarding the NFS storage? Pros Cons? I have seen the dovecot wiki on NFS already and for now we will stay with one single dovecot server. Thanks and regards . Götz

3 4

autocreate: We need "auto=init"!
by Peer Heinlein 22 Jun '16

22 Jun '16

There had been several discussions about the common problem, that there's need for a autocreate-function that creates mailboxes ONLY for new users that had never been logged in before. The reason: Existing users already HAVE "special folders" with localized names. Creating "standard names" at every login will produce confusion, because then they have multiple Sent-Folders and aren't be able to delete them, because they'll always be recreated. I would love to have: 1) auto = init Create the folders ONLY if the whole Storage-Folder (e.g.: ~/Maildir or e.g. `/mdbox) is create (=creation of the INBOX itself). Don't create any folder if the main INBOX already exists. Since there has to be a hook to autoreate a non-existing INBOX it should be able to use this action to also create the folders with auto=init at the same time. 2) auto by type Create that "special folder" only if no other special folder exists. If we have "Sent" and "Sent Items" we could set "mailbox Sent { auto=create-by-type }" so this folder will only be created if no other "\Sent" folder (like "Sent Items") already exists. Dovecot could make sure, that there is AT LEAST ONE or JUST ONE of the special folder \Draft, \Trahs, \Sent. Personally: I would prefere (1) -- and that's what several users already requestet here at the list in the last two years. Function (1) is the only way to change the behavior on a complex, already running system with existing users. That's the way how to introduce new folders for new users without breaking everything for existing users. Any chance for us the get this? 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

2 1

Dovecot 2.2.24 coredump client_check_command_hangs()
by Peter Eriksson 22 Jun '16

22 Jun '16

I’m seeing core dumps from Dovecot’s imap process (around 1/day currently) from client_check_command_hangs(). Dovecot 2.2.24 OS: Solaris 10 CPU: x86 Filesystem: Local ZFS Most crashes are associated with one user (with 25GB of mail in his mailboxes) but some (two) are also associated with other user with “just” 10GB mail. Please find enclosed various log files/traces. Let me know if there is something else I might be able to provide that might give more insight into this. The output is from one of the “25GB”-user crashes. He is able to access mail normally most of the time though so the client recovers and he hasn’t reported this issue to us. — [Lı.U] SysAdmin KITVS-IFM & ITI-NET IT.LiU.SE +46-13-28 2786

2 1

Fedora + Dovecot - only one client can connect per user?
by Thomas Cameron 20 Jun '16

20 Jun '16

Howdy - I am running dovecot-2.2.24-1.fc23.x86_64 on Fedora 23. It's up to date as of last night. When I log in from a desktop using Thunderbird on Linux, my Android phone (Nexus 6P) stops receiving mail. It happens if I'm on my laptop or my desktop. My wife has the same problem using Thunderbird on Windows. If she leaves the house and forgets to shut down her MUA, her phone can't retrieve messages. Is this expected behavior? Can I change it? I feel like it's pretty common for folks to have multiple devices which access the same mail account. Between phones, tablets, PCs, etc., this seems like a pretty common scenario. It's a pretty vanilla setup: [root@wintermute ~]# dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # OS: Linux 4.4.4-301.fc23.x86_64 x86_64 Fedora release 23 (Twenty Three) mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_cipher_list = PROFILE=SYSTEM ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } Thanks! Thomas

2 1

Recipient delimiter and lmtp proxying
by Dave 20 Jun '16

20 Jun '16

Hi, I'm attempting to proxy lmtp using director to hash to the same backend as pop3/imap. My pop3/imap users are of the form: username and my lmtp users are of the form: <username@domain> Where domain is fairly redundant but does carry some useful information. Now, I can proxy lmtp using user=%{username} and destuser=%{orig_user}, and this all appears to work correctly. However, if I also try to pass a detail part through to the backend the lmtp users now take the form: <username+detail@domain> I can still use user=%{username} with recipient_delimiter = +, and the detail is correctly stripped, hashing works as expected. However, I can no longer use destuser=%{orig_user} Because recipient_delimiter = +, destuser becomes: <username@domain> And the detail part never reaches the backend. There doesn't appear to be any variables suitable for the destuser expansion - %{auth_user} is unsupported (UNSUPPORTED_VARIABLE_auth_user) on override_fields and in the sql passdb driver. Is there any "correct" way to do this? I can think of a couple of approaches that may work, but both seem like hacks to me: 1. Unset recipient_delimiter and manually strip the detail from the username in the passdb lookup. 2. Give up on passing detail via the login and instead pass the detail via a message header to sieve. Any thoughts/suggestions? -- Dave

1 2

Migrate Dovecot email archive
by Marco Usai 20 Jun '16

20 Jun '16

Yesterday I'vemigrated Dovecot mail archive between two servers using the procedure below: 1) Createon the new server the same email accounts existing on the old server. 2) Transferthe "tarred" mail folder from the old to the new server. For testingpurposes, on Outlook 2007 I've deleted a .pst cache file, forcing the client todownload all emails again. The switchwas absolutely transparent without any problem. All the emails were availableand Outlook 2007 noticed no changes. Can Iconsider this a correct procedure or should I use some tools like Dsync ?

3 3

Increased errors "Broken MIME parts" in log file
by Alessio Cecchi 20 Jun '16

20 Jun '16

Hi, after the last upgrade to Dovecot 2.2.24.2 (d066a24) I see an increased number of errors "Broken MIME parts" for users in dovecot log file, here an example: Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): Corrupted index cache file /home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 34 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=410000005b070000000000007b07000000000000fc0a000000000000400b0000000000000300000048000000800700000000000060000000000000006400000000000000200000000000000021000000000000000100000040000000260800000000000027000000000000002900000000000000ea00000000000000f000000000000000440000005d090000000000001e000000000000002000000000000000b308000000000000e0080000000000002d00000001000000410000007b09000000000000b208000000000000de080000000000000000000000000000000000000000000000000000) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): Corrupted index cache file /home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 35 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=410000005b070000000000007b07000000000000fd0a000000000000410b0000000000000300000048000000800700000000000060000000000000006400000000000000200000000000000021000000000000000100000040000000260800000000000027000000000000002900000000000000eb00000000000000f100000000000000440000005e090000000000001e000000000000002000000000000000b308000000000000e0080000000000002d00000001000000410000007c09000000000000b208000000000000de080000000000000000000000000000000000000000000000000000) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): unlink(/home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): Corrupted index cache file /home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 49 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): unlink(/home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): Corrupted index cache file /home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 50 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): unlink(/home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): Corrupted index cache file /home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 54 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): unlink(/home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache) failed: No such file or directory (in mail-cache.c:28) Jun 01 15:25:29 Error: imap(alessio.cecchi(a)skye.it): Corrupted index cache file /home/domains/skye.it/alessio.cecchi/Maildir/dovecot.index.cache: Broken MIME parts for mail UID 55 in mailbox INBOX: Cached MIME parts don't match message during parsing: Cached header size mismatch (parts=) I try to run: - doveadm index -u alessio.cecchi(a)skye.it INBOX - doveadm force-resync -u alessio.cecchi(a)skye.it INBOX - delete all dovecot.* files for user but the error reappears always (for the same UID) when I do "search" from webmail. All works fine for the users but I don't think is good to have these errors in log file. My configuration: # dovecot -n # 2.2.24.2 (d066a24): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (5986a78) # OS: Linux 2.6.32-642.el6.x86_64 x86_64 CentOS release 6.8 (Final) auth_cache_negative_ttl = 2 mins auth_cache_size = 20 M auth_cache_ttl = 20 mins auth_master_user_separator = * auth_mechanisms = plain login auth_worker_max_count = 50 deliver_log_format = msgid=%m, from=%f, subject="%s": %$ dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext expire = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 89 first_valid_uid = 89 imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_idle_notify_interval = 29 mins imap_logout_format = in=%i out=%o session=<%{session}> imap_max_line_length = 2 M last_valid_gid = 89 last_valid_uid = 89 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 10.0.0.157 login_trusted_networks = 10.0.0.0/24 mail_fsync = always mail_location = maildir:~/Maildir mail_plugins = quota acl expire zlib maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext vnd.dovecot.duplicate mmap_disable = yes namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%n/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = username_format=%Ld /etc/dovecot/extra/alias-domains-denylogin.txt deny = yes driver = passwd-file } passdb { args = /etc/dovecot/dovecot-deny-sql.conf.ext deny = yes driver = sql } passdb { args = /etc/dovecot/extra/master-users driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl antispam_backend = mailtrain antispam_mail_notspam = --ham antispam_mail_sendmail = /usr/bin/sa-learn antispam_mail_spam = --spam antispam_spam = Spam antispam_trash = Trash expire = Trash expire2 = Spam expire_dict = proxy::expire fts = solr fts_solr = url=http://10.0.0.5:8983/solr/ quota = maildir:UserQuota quota2 = dict:Quota Usage::noenforcing:proxy::sqlquota quota_grace = 10M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.sieve sieve_dir = ~/sieve sieve_extensions = +vnd.dovecot.duplicate -vacation zlib_save = gz zlib_save_level = 6 } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, bytes=%i/%o, session=<%{session}> protocols = imap pop3 sieve sendmail_path = /var/qmail/bin/sendmail service anvil { unix_listener anvil-auth-penalty { mode = 00 } } service auth { client_limit = 6524 unix_listener auth-userdb { group = vchkpw mode = 0660 user = vpopmail } } service dict { process_limit = 500 unix_listener dict { group = vchkpw mode = 0660 user = vpopmail } } service imap-login { process_min_avail = 4 service_count = 0 } service imap-postlogin { executable = script-login /etc/dovecot/scripts/imap-postlogin.sh unix_listener imap-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service imap { executable = imap imap-postlogin process_limit = 5000 vsz_limit = 384 M } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { process_min_avail = 4 service_count = 0 } service pop3-postlogin { executable = script-login /etc/dovecot/scripts/pop3-postlogin.sh unix_listener pop3-postlogin { group = vchkpw mode = 0660 user = vpopmail } user = vpopmail } service pop3 { executable = pop3 pop3-postlogin process_limit = 1024 } service quota-warning { executable = script /etc/dovecot/scripts/quota-warning.sh unix_listener quota-warning { user = vpopmail } user = vpopmail } service stats { fifo_listener stats-mail { group = vchkpw mode = 0660 user = vpopmail } } ssl = no ssl_protocols = !SSLv2 !SSLv3 submission_host = 127.0.0.1 userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol lda { mail_fsync = optimized mail_location = maildir:~/Maildir:INDEX=MEMORY mail_plugins = quota acl expire zlib sieve } protocol imap { mail_max_userip_connections = 50 mail_plugins = quota acl expire zlib imap_quota imap_acl imap_zlib } protocol sieve { mail_max_userip_connections = 2 } protocol pop3 { mail_max_userip_connections = 15 } -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice

5 9

tlsv1 alert unknown ca: SSL alert number 48
by Maurizio Dall'Acqua 19 Jun '16

19 Jun '16

The version of Roundcube I am using is 0.9.5+dfsg1-4.1

3 6

Custom storage backend
by Cornelius Charlie 18 Jun '16

18 Jun '16

Hello, We use a storage backend that is using non-standard apis. We would like to know if there is some way to write a storage backend as a plugin instead of hardcoding our changes directly into the dovecot source ? Thanks.

2 1

archive all saved IMAP messages
by KT Walrus 18 Jun '16

18 Jun '16

I need to archive (i.e., send to another mail server) all messages saved on my mail servers. I’ve implemented for SMTP submission, but haven’t figured out how to archive messages saved by IMAP (like to Drafts, Sent, etc.). How would I best implement this? Can I enable Sieve plugin for IMAP? Or, some other method? Like one way backup to archive server? I really only need to archive the messages sent/saved by a user and not the messages received from other users. Kevin

2 4

tlsv1 alert unknown ca: SSL alert number 48
by Maurizio Dall'Acqua 18 Jun '16

18 Jun '16

Hi, I have set up a mail server with postfix+dovecot 2.2.13 on my raspberry pi running Raspbian Jassie OS. Now I would like to add an on-line e-mail client like Squirrelmail or Roundcube. I was able to start up these two clients but when I try to login I get this error message in the dovecot log: tlsv1 alert unknown ca: SSL alert number 48 But I have inserted the self-signed certificate and key in /etc/dovecot/conf.d/10-master.conf Moreover, I can send and receive e-mails from/to my server, and I can login successfully to dovecot IMAP with Thunderbird. Can somebody give me a clue on how to solve this problem? Any help would me much appreciated. Regards, Maurizio

4 9

Mail dates
by ＠lbutlr 18 Jun '16

18 Jun '16

Where exactly does dovecot get the date that it reports via IMAP? I have a lot of messages that were restored from an archive and so all have the same date, despite being over the span over several years. I tried setting the timestamps of the files to the date in the Received header, but that didn’t seem to make any difference to what my IMAP clients see. Do I have to rename the files to the right epoch seconds in order for dovecot to show the right dates to the IMAP clients? … It seems I’ve been here before, but I don’t remember the solution … -- 'What is this thing, anyway?' said the Dean, inspecting the implement in his hands. 'It's called a shovel', said the Senior Wrangler. 'I've seen the gardeners use them. You stick the sharp end in the ground. Then it gets a bit technical.' --Reaper Man

2 7

Advice needed: SMTP/LMTP or IMAP for internal message delivery
by KT Walrus 17 Jun '16

17 Jun '16

I’ve implemented “next day” delivery this week by taking messages submitted through Postfix, queuing the messages in a MySQL database, and sending them out for delivery through another Postfix instance/Dovecot LMTP proxy with final delivery using the destination mail servers LMTP service. Delivery is sent to a “next day” mail server which is sync’d to the recipient’s mail server using “doveadm sync -A tcp:next-day-mail:12345” on each mail server in the early morning. This all appears to be working well. I do have a need to deliver these messages into specific mail folders in the recipient’s mailbox and I was planning on using global Sieve scripts running on the “next day” mail server to place the messages in the proper folder (not all messages are delivered to the INBOX folder). I am using a PHP script to move the messages from Postfix to the MySQL database and then later sending them via SMTP to the internal Postfix instance for delivery to the “next day” mail server. I started investing how to code the Sieve scripts today and it occurred to me that I could greatly simplify message delivery by using IMAP to deliver the messages to the “next day” mail server. The PHP script would be able to deliver the exact message that should be stored to the proper folders setting the \Seen flags appropriately. My backend “next day” mail server already supports Master password login so I figure the PHP script should be able to login via IMAP to access the folders in the recipient mailboxes. Also, the PHP script could do other mailbox maintenance tasks when it connects to the user’s mailbox such as purge folders by age, message count, etc. The PHP script could also retrieve info about the current state of the user’s mailbox folders (like the date of the oldest unread message, how many messages have been read in the last week or so, etc) and store this data in the MySQL DB. I’m looking for any advice on whether to scrap the current plan of deploying internal Postfix SMTP/Dovecot LMTP proxy/Dovecot LMTP/Sieve script for “next day” mail delivery and just write PHP script to access Dovecot IMAP (direct to the “next day” mail server or to the user’s mail server for “immediate” delivery). This would allow me to drop using Dovecot LMTP at all. Postfix SMTP would only be configured to invoke a PHP script to deliver messages to the database (which is already implemented). Postfix would still use Dovecot IMAP authentication, but only Dovecot IMAP service would need to be “highly available”. Any opinions? Should I dump LMTP? Kevin

1 0

Migrate email account from Dovecot to Dovecot servers
by Marco Usai 17 Jun '16

17 Jun '16

Hello, 1) I needto migrate some mbox imap email accounts from a shared webhosting provider toanother one. 2) Bothservers seem to use Devecot, as a telnet command on port 143 shows an identicalresponse:* OK[CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE NAMESPACESTARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. 3) I don'tknow Dovecot version because I don't have access to "dovecot --version"command. 4) I can'tuse "doveadm-sync" because the command is not available on my sharedhosting account. 5) I preferto leave imapsync perl script as the last option because I want to preserve theUID. So, I needto know what migration procedure can be adopted: if I copythe /home/user/mail/ directory containing all email account from the sourceserver to the destination server, can I expect to see all accounts working withall the emails transferred ? Should I firstcreate from cPanel all the email account with identical names and password onthe destination server ? Anysuggestion will be much appreciated. Thanks in advance!

1 0

Double variable expansion / multiple password mechanisms
by Leon Kyneur 17 Jun '16

17 Jun '16

Hi, Trying to solve the problem of supporting multiple auth mechanisms + proxy and really don't want to store user passwords in plain test and fine to do master user to backend. I had the crazy thought I could do something like the following: For each user Store supported password schemes as LDAP attributes: userPasswordCRAM-MD5: {CRAM-MD5}xxx userPasswordDIGEST-MD5: {DIGEST-MD5}xxxx userPasswordSCRAM: {SCRAM-SHA-1}xxxx userPasswordNTLM: {NTLM}xxxx then: =password=%{ldap:userPassword%m} <- Though this doesn't work.. just wondering if it could possibly work or if I should give up on this crazy idea :) Thanks Leon

3 5

Multiple ACTIVE Sieve scripts
by Aaron Müller 17 Jun '16

17 Jun '16

Hi! Is there a reason the email filter sieve can only activate one single script? > list "mailinglists.sieve" "spam.sieve" ACTIVE > activate mailinglists.sieve > list "mailinglists.sieve" ACTIVE "spam.sieve" > I can't see the logic here ... I am doing something wrong? Aaron

2 1

Mailbox location
by Doug Hardie 17 Jun '16

17 Jun '16

I am running a small server with a fixed number of users. Postfix is using dovecot lda so that I can run pigeonhole. I have setup a user file with the ids and passwords and everything authenticates properly. Postfix uses that also. However, mail is consistently delivered to user@domain. How do I tell it to deliver to just user? I have tried setting a variety of different things like: 10-mail.conf:mail_location = maildir:/var/mail/home_mail/%u userdb { driver = static args = uid=2222 gid=2222 home=/var/mail/home_mail/%u } and a few other things. None of them affected the mailbox location. Fortunately, this is a test system as I probably have mucked up the config files by now. — Doug

2 2

sieve-extprogram: How to hand over a variable or pipe a mail so a shell script?
by M. Koehler 17 Jun '16

17 Jun '16

Hi, I´m just playing around with sieve-extprogram but it didn´t works like I think. I want a. execute a shell script that get the subject as parameter my try: require ["fileinto","variables","envelope","vnd.dovecot.execute"]; if header :contains "Subject" "123test" { execute :input "${1}" "exec-test"; keep; } and require ["fileinto","variables","envelope","vnd.dovecot.execute"]; if header :contains "Subject" "123test" { execute "exec-test" "${1}"; keep; } The shell script will create a file with $1 as text. But I didn´t get any output - the created file is empty b. later the complete mail should piped to the shell script require ["fileinto","variables","envelope","vnd.dovecot.execute"]; if header :contains "Subject" "123test" { execute :pipe "exec-test"; keep; } This should (as http://hg.rename-it.nl/dovecot-2.2-pigeonhole/raw-file/tip/doc/rfc/spec-bos… described) hand over the complete mail to the script But I don´t know how I handle the complete mail with a shell script? I think the mail will not hand over as a parameter to the shell script, right? But how should I store the mail into a file or should I pipe it through a sed command line (and so one) into a shell script? Hope someone could bring some lights into my darkness :) Best regards, Michael

2 2

quota rules for mail users
by mkawada＠redhat.com 16 Jun '16

16 Jun '16

Dear All, Is it possible to make quota rules under $HOME/Maildir/* mailboxes with a specific command such as 'edquota' when the first email arrives at the $HOME/Maildir/{new,cur,tmp} of a user. In the below example, the <UserB> is the one who gets an email for the first time. edquota -p <UserA> <UserB> ---man edquot--- -p, --prototype=protoname Duplicate the quotas of the prototypical user specified for each user specified. This is the normal mechanism used to initialize quotas for groups of users. --- To configure quotas in postfix/dovecot environment, it seems that you need to use dovecot-lda plugin, and then my exact question is as follows: Is it possible to automatically run any commands or scripts in order to set a quota rule to $HOME/Maildir/* mailboxes when users receive an email for the first time? I just found the post-login service allows you to execute scripts after authentication in the following URL, but I have not found the exact way to make it. http://www.dovecot.org/list/dovecot/2009-November/044279.html Any comments/suggestions would be greatly appreciated. -- Masaharu Kawada

2 3

Re: Multiple ACTIVE Sieve scripts
by Larry Rosenman 15 Jun '16

15 Jun '16

I have a "master" script that includes all my other snippets. And each file can have MULTIPLE scripts. Let me know if you need more info. Also, mail to you (Aaron) BOUNCES: Delivery to the following recipient failed permanently: mail(a)aaron-mueller.de Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the server for the recipient domainaaron-mueller.de by mail.aaron-mueller.de. [37.120.190.162]. The error that the other server returned was: 554 5.7.1 <mail(a)aaron-mueller.de>: Relay access denied On Wed, Jun 15, 2016 at 12:43 PM, Larry Rosenman <larryrtx(a)gmail.com> wrote: > I have a "master" script that includes all my other snippets. And > each file can have MULTIPLE scripts. Let me know if you need more > info. > > > On 6/13/16, Aaron Müller <mail(a)aaron-mueller.de> wrote: > > Hi! > > > > Is there a reason the email filter sieve can only activate one single > > script? > > > >> list > > "mailinglists.sieve" > > "spam.sieve" ACTIVE > >> activate mailinglists.sieve > >> list > > "mailinglists.sieve" ACTIVE > > "spam.sieve" > >> > > > > I can't see the logic here ... I am doing something wrong? > > Aaron > > > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com > US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281 > -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

1 0

sieve_extprograms: how to filter original message twice?
by N0T3P4D 15 Jun '16

15 Jun '16

Hi, I use dovecot and sieve_extprograms to encrypt all incoming messages with the help of a Python script. Now, I want to process the _original_ message a second time. However, as expected, the second filter is applied to the already filtered message. For reference, here's a copy of the sieve script in question: if address :matches "To" "X(a)Y.Z" { fileinto "INBOX"; filter "gpgit.py" ["X(a)Y.Z", "--encrypt"]; fileinto "encrypted"; filter "gpgit.py" ["X(a)Y.Z", "--wrap"]; # Should be applied to the original message but uses the result of the first filter command fileinto "wrapped"; stop; } Does anyone have an idea how to modify the script to get the intended result? Please cc me, as I'm not subscribed. Thanks for your help Jeremias

2 2

Building Dovecot 2.2.24 GIT HEAD version
by Juan C. Blanco 15 Jun '16

15 Jun '16

Hello, I'm testing the last GIT (master-2.2) versión of dovecot 2.2 but I'm not able to build new rpm packages with our SPEC file on Centos 5.11. The problem seems to be with a new lib-dcrypt library, the file "src/lib-dcrypt/dcrypt-openssl.c" includes the file "openssl/ec.h" but the OpenSSL devel package included in Centos 5.11 is openssl-devel-0.9.8e-40.el5_11 that not contains the "openssl/ec.h" file I don't know if the next dovecot 2.2 release (derived from 2.2.24 GIT) will not be compatible with Centos 5.11 or if it will be necesary to install some optional openssl packages. Regards. -- +-------------------------------------------------------------------+ | Juan C. Blanco | | | | Centro de Calculo | | | E.T.S. Ingenieros Informáticos | E-mail: jcblanco(a)fi.upm.es | | Universidad Politécnica de Madrid | | | Campus de Montegancedo | | | Boadilla del Monte | Tel.: (+34) 91 336 7466 | | 28660 MADRID (Spain) | Fax : (+34) 91 336 6913 | +-------------------------------------------------------------------+

1 0

Upgrade to 2.2.9 breaks sasl auth
by Paul 15 Jun '16

15 Jun '16

Hi This is my 1st time here so please be gentle. I have encountered one problem since upgrading from 2.0.19 to 2.2.9 which has me beat. The system provides sasl auth services via inet to a postfix 2.11 system. Since the upgrade postfix complains of no sasl methods available. The same dovecot configuration is used on both versions. Now I get these results looking at the inet connection Version 2.0.19 root@larch:~# telnet 192.168.3.15 12345 Trying 192.168.3.15... Connected to 192.168.3.15. Escape character is '^]'. VERSION 1 1 MECH PLAIN plaintext MECH LOGIN plaintext MECH CRAM-MD5 dictionary active SPID 23223 CUID 1 COOKIE d0b71942d48585303f9ae4681baabf87 DONE Version 2.2.9 root@larch:~# telnet 192.168.3.112 12345 Trying 192.168.3.112... Connected to 192.168.3.112. Escape character is '^]'. VERSION 1 1 SPID 5300 Seems be something lacking in the response from 2.2.9 that fits the "no sasl methods" response from postfix I believe I should supply root@larchvm:/etc/dovecot-sasl# dovecot -n -c dovecot.conf # 2.2.9: dovecot.conf # OS: Linux 3.13.0-88-generic i686 Ubuntu 14.04.4 LTS auth_mechanisms = plain login cram-md5 auth_verbose_passwords = plain base_dir = /var/run/dovecot-sasl/ disable_plaintext_auth = no instance_name = sasl mail_chroot = /chroot/mail mail_location = maildir:~/Maildir mail_plugins = quota managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacati on subaddress comparator-i;ascii-numeric relational regex imap4flags copy includ e variables body enotify environment mailbox date ihave namespace { inbox = yes location = prefix = INBOX. type = private } passdb { args = /etc/dovecot-sasl/dovecot-sqlmd5.conf driver = sql } plugin { deleted_to_trash_folder = Trash quota = maildir:User quota quota:noenforcing quota_rule = Trash:ignore sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { inet_listener auth-userdb { address = 192.168.3.112 port = 12345 ssl = yes } unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { mode = 0600 } } service imap-login { inet_listener imap { address = 213.210.16.65 port = 143 } inet_listener imaps { address = 213.210.16.65 port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { address = 213.210.16.65 port = 4190 } } ssl_cert = </etc/ssl/certs/pe.pem ssl_key = </etc/ssl/private/pe.pem userdb { args = /etc/dovecot-sasl/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = quota imap_quota deleted_to_trash } Any help or suggestion warmly welcomed

2 3

shutdown_clients has no effect on doveadm stop
by Roland Rosenfeld 14 Jun '16

14 Jun '16

I try to restart dovecot 2.2.24 (for changing limits) without killing all IMAP and POP3 sessions. dovecot(1) tells me: When shutdown_clients is set to no, existing sessions will continue to use the old settings, after a dovecot reload. Also all sessions will keep alive after a dovecot stop. By default all active sessions will be shut down. According to my "dovecot -n" (see below), I have set "shutdown_clients=no", so "doveadm stop" should keep my open sessions. But if I try this out with a simple telnet to port 143 during "doveadm stop", I see the following: $ telnet imap 143 Connected to imap. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a login user(a)example.com XXXXX a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS BINARY MOVE QUOTA ACL RIGHTS=texk] Logged in * BYE Server shutting down. Connection closed by foreign host. The "BYE Server shutting down." happens exactly at the time, when I press return after "doveadm stop", "systemctl stop dovecot", or "systemctl restart dovecot" in the other shell. Only "systemctl reload dovecot" keeps the open sessions healthy. So it seems that either the man page is wrong, or shutdown_clients=no has no effect after dovecot stop... Greetings Roland dovecot -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.5 auth_cache_negative_ttl = 5 mins auth_cache_size = 100 M auth_cache_ttl = 15 mins auth_default_realm = netcologne.de auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf } disable_plaintext_auth = no listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " mail_fsync = always mail_gid = 999 mail_location = maildir:~/mail mail_plugins = acl quota zlib mail_uid = 999 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags mmap_disable = yes namespace { list = children location = maildir:%%h/mail:INDEX=~/mail/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/passwd.master driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl quota = maildir sieve = ~/.dovecot.sieve sieve_dir = ~/mail/sieve sieve_extensions = +imapflags zlib_save = gz } pop3_no_flag_updates = yes pop3_uidl_format = %v.%u protocols = imap pop3 sieve service auth { unix_listener auth-master { group = vmail mode = 0600 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap { process_limit = 4000 } service managesieve-login { inet_listener sieve { port = 4190 } } service managesieve { process_limit = 100 } service pop3 { process_limit = 1000 } shutdown_clients = no ssl = no syslog_facility = local2 userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { mail_max_userip_connections = 10 mail_plugins = acl quota zlib imap_quota imap_acl } protocol pop3 { mail_plugins = acl quota zlib }

2 3

Alternate Storage and quota limits
by mailing lists 14 Jun '16

14 Jun '16

Hi all, is there any way of exclude messages storaged in alternate storage (*dbox mailbox format) from being included in the quota usage? I think this is not possible but let me ask.

1 0

Alternate Storage and quota limits
by mailing lists 14 Jun '16

14 Jun '16

Hi all, is there any way of exclude messages storaged in alternate storage (*dbox mailbox format) from being included in the quota usage? I think this is not possible but let me ask.

1 0

Advice on once a day message delivery setup
by KT Walrus 14 Jun '16

14 Jun '16

I’m adding once a day mail delivery to my site. Messages are marked by the sender as “overnight” or “once a week” delivery. The way I’m planning on implementing this is to queue messages until midnight in a MySQL database. Each mailbox will be kept in two Dovecot mailstores. The first mailstore will give the users IMAP access to their mailbox. A second mailstore will hold the next day’s new messages. At midnight, a cron job runs to send messages in the MySQL database out to the second mailstore. Then, at 6am, a second cron job will run to sync the two mailstores using doveadm sync. What I am expecting to happen is that during the day, notification messages (from the site) may be delivered to the first mailstore (the one providing IMAP access to the user) but no messages from other users sent during the day will come until after 6am the next day. Each time the user submits a new message, a notification message is sent back to the sender with a link for editing the queued message in the MySQL database and an indication of when it is scheduled for delivery. I am kind of assuming that the morning sync process is fast enough so it can easily complete before noon (in 6 hours) even if I end up having lots of mailboxes on each fully loaded Dovecot server. Is the doveadm sync process reliable and efficient enough for this type of “once a day” morning new message mail delivery? Or, should I just start delivering messages after midnight and not bother with the second mailstore and subsequent sync? Just looking for any advice… I kind of like the idea of modeling my mail service after the US Post Office where the mailman delivers new mail once a day rather than like Twitter/Facebook where messages are posted in real time to encourage users to monitor their boxes throughout the day. Kevin

3 2

doveadm-server protocol change?
by Heiko Schlittermann 13 Jun '16

13 Jun '16

Hi, I'm doing quota checks from a remote machine (the real setup is a bit more complex, if necessary I can explain it in more detail, but I just extracted the bits that are easily reproduceable) # nc backend1 24245 VERSION doveadm-server 1 0 PLAIN agrVMDvHgz0ya2HHzax5svwB2ZHS¹ + heiko quota get But since the backend is upgraded to 2.2.22 it's not possible anymore. The exuse in the log of the backend is: dovecot: doveadm(149.1.1.1¹): Fatal: USER environment is missing and -u option not used Running the `doveadm quota get -u heiko` locally on the backend works as expected. But using the the doveadm-server it doesn't. # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) # OS: Linux 4.4.0-22-generic x86_64 Ubuntu 16.04 LTS … auth_cache_negative_ttl = 0 auth_cache_ttl = 0 auth_master_user_separator = * base_dir = /run/dovecot/ imap_metadata = yes lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_attribute_dict = file:%h/dovecot-attributes mail_location = maildir:~:INBOX=/volumes/dovecot/inbox/%2.256Nn/%n:INDEX=/volumes/dovecot/cache/%2.256Nn/%n mail_plugins = quota mbox_md5 = all mmap_disable = yes namespace inbox { … passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.passdb.conf.ext driver = ldap } plugin { quota = maildir:User quota quota_grace = 10%% sieve = /volumes/dovecot/sieve/%2.256Nn/%n/.dovecot.sieve sieve_dir = /volumes/dovecot/sieve/%2.256Nn/%n } pop3_uidl_format = %v.%u protocols = " imap lmtp pop3" service auth { extra_groups = ssl-cert } service doveadm { inet_listener { port = 24245 } } service lmtp { inet_listener lmtp { port = 2525 } } ssl = required ssl_cert = </etc/ssl/certs/snakeoil-crt.pem ssl_key = </etc/ssl/private/snakeoil-key.pem userdb { driver = prefetch override_fields = home=/volumes/dovecot/home/%2.256Nn/%n uid=vmail gid=vmail } userdb { args = /etc/dovecot/dovecot-ldap.userdb.conf.ext driver = ldap override_fields = home=/volumes/dovecot/home/%2.256Nn/%n uid=vmail gid=vmail } verbose_proctitle = yes protocol lmtp { mail_plugins = quota sieve quota } protocol lda { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota } local 149.1.1.0/24¹ { doveadm_password = # hidden, use -P to show it } ¹) It's changed :)

5 13

doveadm fts rescan <namespace> doesn't seem(!) to find <namespace>
by Larry Rosenman 13 Jun '16

13 Jun '16

thebighonker.lerctr.org ~ $ doveadm fts rescan \#ARCHIVE doveadm(ler): Error: Namespace prefix not found: #ARCHIVE thebighonker.lerctr.org ~ $ doveadm fts rescan #ARCHIVE thebighonker.lerctr.org ~ $ doveadm fts rescan inbox doveadm(ler): Error: Namespace prefix not found: inbox thebighonker.lerctr.org ~ $ Doveconf -n attached. -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larryrtx(a)gmail.com US Mail: 17716 Limpia Crk, Round Rock, TX 78664-7281

1 1

Potential bug report: Cannot use ":args" option via Pigeonhole Sieve pipe plugin
by Zeeshan Muhammad 13 Jun '16

13 Jun '16

Hi all, Following the instructions noted at http://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Pipe , I am trying to make use of the Pigeonhole sieve pipe plugin to execute an application with custom arguments via my test sieve script: require ["vnd.dovecot.pipe"]; if address :is "to" "test(a)example.com" { pipe :args [ "first-arg", "second-arg" ] "sieve-pipe-example"; } I am editing my test sieve script via Mozilla Thunderbird v45.1.1 using the Sieve email-client addon (v0.2.3h, see https://github.com/thsmi/sieve#releases and https://addons.mozilla.org/en-US/thunderbird/addon/sieve/ ) When I attempt to save the example sieve script above, I get the following error returned by ManageSieve via Mozilla Thunderbird's Sieve addon: "The script could not be saved: Sieve mail filter: line 3: error: unknown tagged argument ':args' for the pipe command (reported only once at first occurrence). Sieve mail filter: error: validation failed." I have setup sieve-pipe-example as follows in my 90-sieve.conf configuration: service sieve-pipe-script { executable = script /usr/bin/echo user = dovenull # socket name is program-name in Sieve unix_listener sieve-pipe-example { } } I cannot see where I am going wrong. I have combed through the specification at http://hg.rename-it.nl/dovecot-2.2-pigeonhole/raw-file/tip/doc/rfc/spec-bos… as well as the official Dovecot/Pigeonhole wiki-pages and cannot find a solution. If I omit the :args option (and the arguments array), the sieve script successfully gets accepted by ManageSieve. Am I encountering a potential bug or am I doing something silly in my test setup? # Dovecot version: v2.2.24 # Pigeonhole version: v0.4.14 # Operating system: CentOS Linux release 7.2.1511 (Core) # CPU architecture: x86_64 # Dovecot -n output (I have filtered my IP addresses and mail server's FQDN): # 2.2.24 (a82c823): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 3.10.0-327.18.2.el7.x86_64 x86_64 CentOS Linux release 7.2.1511 (Core) auth_default_realm = example.com base_dir = /var/run/dovecot/ default_login_user = vpopmail first_valid_uid = 500 info_log_path = /dev/stderr last_valid_uid = 500 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes log_path = /dev/stderr mail_debug = yes mail_location = maildir:~/Maildir mail_max_userip_connections = 20 mail_plugins = " fts fts_lucene" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext editheader vnd.dovecot.pipe namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = vpopmail } plugin { fts = lucene fts_autoindex = yes fts_lucene = whitespace_chars=@. sieve = file:~/sieve;active=~/.dovecot.sieve sieve_execute_socket_dir = sieve-execute sieve_extensions = +editheader +vnd.dovecot.pipe sieve_pipe_socket_dir = sieve-pipe sieve_plugins = sieve_extprograms } protocols = imap pop3 sieve service auth { unix_listener auth-userdb { group = vchkpw mode = 0666 user = vpopmail } } service imap-login { inet_listener imap { address = 127.0.0.1 port = 143 ssl = no } inet_listener imaps { address = 192.168.1.1 port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } } service pop3-login { inet_listener pop3 { address = 127.0.0.1 port = 110 ssl = no } inet_listener pop3s { address = 192.168.1.1 port = 995 ssl = yes } } service sieve-pipe-script { executable = script /usr/bin/echo group = dovenull user = dovenull } ssl_cert = </etc/ssl/certs/example.com.crt ssl_key = </etc/ssl/certs/example.com.key ssl_protocols = !SSLv2 !SSLv3 userdb { driver = vpopmail } verbose_proctitle = yes protocol lda { hostname = mail.example.com info_log_path = /var/log/dovecot/dovecot-lda.log log_path = /var/log/dovecot/dovecot-lda-errors.log mail_plugins = " fts fts_lucene sieve" postmaster_address = postmaster(a)example.com } protocol imap { mail_plugins = " fts fts_lucene imap_zlib" }

2 2