- dovecot - dovecot.org

MySQL issue
by Amaechi Janneh 30 May '17

30 May '17

Hello. It appears that I have an issue with my dovecot setup. When trying to authenticate, i get this error: May 28 20:18:26 AmaechiJ dovecot[10516]: imap-login: Login: user=< aj(a)example.com>, method=PLAIN, rip=, lip=, mpid=10879, TLS, ses...QOQBg9rlR> May 28 20:18:42 AmaechiJ dovecot[10516]: imap(aj(a)example.com): Connection closed in=116 out=1311 May 28 20:20:32 AmaechiJ dovecot[10516]: auth-worker(10892): Warning: mysql: Query failed, retrying: Table 'mailserver.users' doesn't … [View More]

3 4

Can only enable Sieve scripts not edit them (Roundcube)
by Paul Littlefield 29 May '17

29 May '17

Hello, (my first post so be gentle) I will be posting this to the Roundcube mailing list too, but thought it worth asking here as well. I have a Roundcube installation running Apache with Dovecot and Sieve. When logged in to Roundcube, a user can see the Sieve scripts and enable or disable them but NOT edit them or create new scripts. In other words, Dovecot will happily EDIT the script to mark it as 'false' but will not edit the actual rules or create a new rule... e.g. require ["… [View More]

3 3

user-defined special-use folders
by Fabian Schmidt 29 May '17

29 May '17

I plan to define SPECIAL-USE mailboxes and think about defining per user special-use folders for those who don't use the default folder names. Is this possible in dovecot? What I try: $ doveadm exec imap * PREAUTH [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 … [View More]

2 1

When will passdb callback to mechanism yield PASSDB_RESULT_NEXT?
by Peter Mogensen 29 May '17

29 May '17

Hi, code question... I've been trying to figure out the implications of the new "noauthenticate" passdb field. Internally it causes a passdb to result in PASSDB_RESULT_NEXT. When a SASL mechanism calls auth_request_lookup_credentials(...,callback) the passdb result is passed to the callback. But I can't really figure out when that result will ever be PASSDB_RESULT_NEXT. It seems the passdb fallthrough resolver will always replace it with PASSDB_RESULT_INTERNAL_FAILURE if it ends up … [View More]

2 1

No doveadm-save in wiki2?
by KT Walrus 29 May '17

29 May '17

Is “doveadm save” an undocumented feature? Or, just well-hidden? https://wiki2.dovecot.org/Tools/Doveadm <https://wiki2.dovecot.org/Tools/Doveadm> Kevin

3 5

Another mail_crypt question: figure out to password secure using mysql
by dovecot＠avv.solutions 26 May '17

26 May '17

Hello Community, (sorry to be more busy, hence more running questions in parallel :) ) As mentioned in another post, I am testing mail_crypt plugin. I was wondering how to really secure the process sothat even the admin cannot have any access to the other users mail content. My current config is simple: - using per-folder keys (hence the per-user spaces are preserved) - put the public/private global keys in base64 format into the sql DB (elliptic algo) This obviously allows anyone … [View More]

2 2

dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
by dovecot＠jeffandjessi.com 26 May '17

26 May '17

Still Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a connection is made the auth worker loads and emails are downloaded and everything "is fine". However, about … [View More]

2 1

Moving dovecot/maildir to new host, dovecot.* files
by John Gateley 26 May '17

26 May '17

Hello, I've done a fair amount of searching, and couldn't find a definitive answer. I am moving my dovecot/postfix servers and mail in Maildir formats to a new host. When I move the Maildir directories, what should I do with the dovecot.index/cache/log/etc. files? I know I can filter them out, and dovecot will recreate them, but is that the best approach? I am thinking of the following: Shut down postfix and dovecot on both the new and old server rsync the maildirs from the old server to the … [View More]

2 2

Issue with virtual folder: partially see them and cannot subscribe
by dovecot＠avv.solutions 26 May '17

26 May '17

Hello Community, I am trying to figure out hwo to use the virtual mailboxes, but remain a bit confused: - I see the Virtual speudo-folder - Eventuelly the name of the boxes underneath - But cannot see more, nor subscrie to the virtual mailboxes Dovecot: # 2.2.29.1 (e0b76e3): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.18 (29cc74d) # OS: Linux 4.4.50-v7+ armv7l Debian 8.0 ext4 auth_mechanisms = plain login log_path = /dev/stderr mail_attribute_dict = file:/sd/MAIL_IMAP_POP/… [View More]%d/%n/Maildir/dovecot-attributes mail_debug = yes mail_gid = vmail mail_location = maildir:/sd/MAIL_IMAP_POP/%d/%n/Maildir:LAYOUT=fs mail_plugins = " virtual mail_crypt" mail_uid = vmail 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 { inbox = yes location = mailbox { special_use = \Drafts name = Drafts } mailbox { special_use = \Junk name = Junk } mailbox { special_use = \Sent name = Sent } mailbox { special_use = \Sent name = Sent Messages } mailbox { special_use = \Trash name = Trash } prefix = name = inbox } namespace { hidden = no list = yes location = virtual:/sd/MAIL_IMAP_POP/%%d/%%n/Virtual prefix = Virtual/ separator = / subscriptions = yes type = private name = virtual } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_crypt_curve = secp521r1 mail_crypt_save_version = 2 sieve = file:/sd/MAIL_IMAP_POP/%d/%n/Sieve;active=/sd/MAIL_IMAP_POP/%d/%n/Sieve.active } service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { user = vmail name = auth-worker } service { unix_listener { group = postfix mode = 0666 user = postfix path = /var/spool/postfix/private/auth } unix_listener { mode = 0600 user = vmail path = auth-userdb } user = dovecot name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service { inet_listener { port = 143 name = imap } inet_listener { port = 993 ssl = yes name = imaps } name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service { unix_listener { group = postfix mode = 0600 user = postfix path = /var/spool/postfix/private/dovecot-lmtp } name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service { inet_listener { port = 110 name = pop3 } inet_listener { port = 995 ssl = yes name = pop3s } name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } ssl = required ssl_cert = </sd/MAIL_IMAP_POP/_ssl/pi3tv.local.avv_server.crt ssl_key = # hidden, use -P to show it userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " virtual mail_crypt sieve" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol lda { mail_plugins = " virtual mail_crypt virtual" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol imap { mail_plugins = " virtual mail_crypt virtual" service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } protocol pop3 { service replication-notify-fifo { name = aggregator } service anvil-auth-penalty { name = anvil } service auth-worker { name = auth-worker } service auth-client { name = auth } service config { name = config } service dict-async { name = dict-async } service dict { name = dict } service login/proxy-notify { name = director } service dns-client { name = dns_client } service doveadm-server { name = doveadm } service imap-hibernate { name = imap-hibernate } service imap { name = imap-login } service imap-urlauth { name = imap-urlauth-login } service imap-urlauth-worker { name = imap-urlauth-worker } service token-login/imap-urlauth { name = imap-urlauth } service imap-master { name = imap } service indexer-worker { name = indexer-worker } service indexer { name = indexer } service ipc { name = ipc } service lmtp { name = lmtp } service log-errors { name = log } service sieve { name = managesieve-login } service login/sieve { name = managesieve } service pop3 { name = pop3-login } service login/pop3 { name = pop3 } service replicator-doveadm { name = replicator } service login/ssl-params { name = ssl-params } service stats-mail { name = stats } } Any tip/suggestion? I tried several configs from https://wiki2.dovecot.org/Plugins/Virtual Example 1: Virtual/Deleted/dovecot-virtual: * deleted Example 2 Virtual/All/dovecot-virtual * -Trash -Trash/* all Thanks! [View Less]

2 6

Plugin "mail_crypt" - using folder keys
by Evgeniy Korneechev 26 May '17

26 May '17

Hi, i have two questions about using "folder keys" for encryption: 1. If i use this method how can i decrypt files manually? 2. If move a letter to another folder (or remove it), it will be unreadable. Log: imap(cloud): Error: read() failed: read(/home/cloud/Maildir/.Sent.test/cur/1485528498.M838579P2267....) failed: Decryption error: no private key available (uid=5, box=Sent.test, read reason=) imap(cloud): Info: Internal error occurred. Refer to server log for more information. or: imap(… [View More]

3 10

Public mailboxes and IPA (LDAP)
by Ranbir 26 May '17

26 May '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Everyone, I have a working Dovecot server that is using my IPA domain to lookup users and passwords. I also have a "public" namespace that has the inboxes for public email accounts. Everything is working for "regular" private email boxes. But, I can't see new messages delivered to any of the public inboxes. Incoming emails get delivered to the correct locations for the public inboxes: I just don't see them in my email clients. I'm not … [View More]sure what the problem is since I don't see an error in the dovecot logs. I also don't want to use the home directory location as provided by the IPA domain. I've worked around it by using file system symlinks, but I'd much rather just ignore the IPA provided home directory. I'm wondering if my workaround is the culprit behind new messages to the public folders not being seen by the client. Here's my config: # 2.2.10: /etc/dovecot/dovecot.conf auth_cache_negative_ttl = 0 auth_cache_size = 1 k auth_debug = yes auth_gssapi_hostname = $ALL auth_krb5_keytab = /etc/imap.keytab auth_mechanisms = plain gssapi auth_realms = SOME.REALM auth_username_format = %Ln auth_verbose = yes first_valid_uid = 1000 hostname = server listen = 1.1.1.1 mail_gid = virtual mail_location = maildir:~/Maildir mail_plugins = quota acl mail_uid = virtual 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 ihave mbox_write_locks = fcntl namespace { location = maildir:/var/spool/mail/domain.tld/public prefix = Public. separator = . subscriptions = no type = public } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } plugin { acl = vfile quota = maildir:User quota quota_rule = *:storage=500M sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster@%d protocols = imap lmtp service auth-worker { user = $default_internal_user } service auth { inet_listener { address = 1.1.1.1 port = 17900 } unix_listener auth-userdb { group = virtual mode = 0600 user = virtual } } service imap-login { process_min_avail = 2 service_count = 1 } service lmtp { inet_listener lmtp { address = 1.1.1.1 port = 24 } } ssl = required ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/conf.d/dovecot-ldap-userdb.conf.ext default_fields = uid=virtual gid=virtual driver = ldap } verbose_proctitle = yes protocol lmtp { mail_plugins = quota acl sieve } protocol lda { mail_plugins = quota acl sieve } protocol imap { mail_plugins = quota acl imap_quota imap_acl } - -- Ranbir -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCgAGBQJZJz5lAAoJEN7T/ly5z1dituQQAIvq/DyDq5JbyREpopj5XcgN RjuvFAf2VuR9ieBnJ66GZPS9kcLZusqTzFyBczJmvq5sHRR8+UvRhsDVGGRNGFS+ 5b6oJNbP5BYP+93Ik8Ai7XgkaSfzIVg6cpru0uzMN0FvzQWXGONKQhMI0dFF+rFf 377gxho3AiAUxffX/vRhOvmE5/loJL9g8WDd6qAdZ6Ow3X3ISIWTo8ICWcndxWJK WU+/vsXfg1Up96M9X38FIhCBVcJG+igUXqZ3/0+N4at/L6BI5BWmG21XpaReGORo QjVaDIeFw4supnaKJszYiiYU1vQRHyvW5p2V0l1Q7mIh/sqANYhqJpziCP9yx1gN g0iv32V2EPxI44ympuhFtAslqyyGhfMtHOsufQ/QbrwjJAML/TRJYuyqh0hiZ+0h anhkDmkb0mlJlroPYJatiqJZqOYNRmtT8QpRMqapELDBo/Rc2LzqnkrgEso2XjI3 yLYXSgV1cY7HNJzhIvmPWZDncF4LW5o3JpidCdcDRnXvDUc3tyb/qRQkvI1+Zycw P5n2r+9BcSWA194TU+QPzvdB9MKQ+Cn3dM0HwYkEqQXH7BVgKKvXobaM+mOgBjLL Ais+yc0aeoKV5r3ln74HPRyXfw0Zp9g128BwzQG597kPhXaXb9Hd5o58LMkdMfxs 5ycn42U8p2ZiKHFDx9vO =swZL -----END PGP SIGNATURE----- [View Less]

1 1

"@LIBICU_CFLAGS@: No such file or directory" during libtool command for lib-fts (cross compile)
by awl1 26 May '17

26 May '17

Hello, I am a complete newbie to dovecot, but do have reasonable experience in compiling Unix/Linux software. I am currently trying to do a cross-compile of dovecot-2.29.1 to be used on my home office Thecus NAS (host: Thecus kernel 2.6.33 on 32-bit Intel Atom: "i686-nptl-linux-gnu"; my build machine has Ubuntu 16.04.2 LTS) "from ground up", i.e. I need to build and provide all dovecot dependencies from within my module. My compiler toolchain (using gcc-5.2.0) has been set up properly … [View More]using ct-ng and works completely fine. I also have already successfully cross-compiled/built almost all dovecot dependencies (zlib, bzip2, xz, lz4, openssl-1.0.2, clucene-git, snowball-git, libexttextcat, icu) - i.e. including icu - and installed them properly into my cross-compile build root (/raid/data/module/Dovecot/sys as defined by Thecus module spec). My dovecot configure/make command is as follows: === export PKG_CONFIG=/usr/bin/pkg-config export PKG_CONFIG_PATH=/raid/data/module/Dovecot/sys/lib/pkgconfig export CC=$HOME/Thecus/n4200pro-5.2.0-toolchain/i686-nptl-linux-gnu/bin/i686-nptl-linux-gnu-gcc export CFLAGS="" export LDFLAGS="-L/raid/data/module/Dovecot/sys/lib -Wl,-rpath,/raid/data/module/Dovecot/sys/lib" export LIBS="" # -llib export CPPFLAGS=-I/raid/data/module/Dovecot/sys/include export CPP=$HOME/Thecus/n4200pro-5.2.0-toolchain/i686-nptl-linux-gnu/bin/i686-nptl-linux-gnu-cpp export CXX=$HOME/Thecus/n4200pro-5.2.0-toolchain/i686-nptl-linux-gnu/bin/i686-nptl-linux-gnu-g++ export CXXFLAGS="" export LT_SYS_LIBRARY_PATH=/raid/data/module/Dovecot/sys/lib export CXXCPP=$HOME/Thecus/n4200pro-5.2.0-toolchain/i686-nptl-linux-gnu/bin/i686-nptl-linux-gnu-cpp ./configure --host i686-nptl-linux-gnu \ --prefix=/raid/data/module/Dovecot/sys \ --libdir=/raid/data/module/Dovecot/sys/lib \ --localstatedir=/raid/data/module/Dovecot/com \ --sharedstatedir=/raid/data/module/Dovecot/var \ --disable-silent-rules \ --with-notify=inotify \ --with-lucene \ --with-stemmer \ --with-textcat \ --with-icu \ --with-solr \ --with-zlib \ --with-bzlib \ --with-lzma \ --with-ssl=openssl \ --with-ssldir=/raid/data/module/Dovecot/sys/etc/ssl \ --with-storages=mdbox,sdbox,maildir,mbox,cydir,imapc,pop3c \ --with-moduledir=/raid/data/module/Dovecot/sys \ --with-gnu-ld \ --with-sysroot=/raid/data/module/Dovecot/sys \ --with-libiconv-prefix=/raid/data/module/Dovecot/sys \ --with-libintl-prefix=/raid/data/module/Dovecot/sys make === and completes configuration just fine, but the make step runs into the following issue which I am unable to resolve even after several hours of investigation, so I am completely stuck at this point... :-( === (...) make[3]: Leaving directory '/home/andreas/Thecus/Dovecot/dovecot-2.2.29.1/src/lib-dovecot' Making all in lib-fts make[3]: Entering directory '/home/andreas/Thecus/Dovecot/dovecot-2.2.29.1/src/lib-fts' make all-am make[4]: Entering directory '/home/andreas/Thecus/Dovecot/dovecot-2.2.29.1/src/lib-fts' /bin/bash ../../libtool --tag=CC --mode=compile /home/andreas/Thecus/n4200pro-5.2.0-toolchain/i686-nptl-linux-gnu/bin/i686-nptl-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -I../../src/lib-mail -I../../src/lib-fts -I/raid/data/module/Dovecot/sys/include/libexttextcat/ @LIBICU_CFLAGS@ -DUDHRDIR=\""../../src/lib-fts"\" -DDATADIR=\"/raid/data/module/Dovecot/sys/share/dovecot\" -DTEST_STOPWORDS_DIR=\""../../src/lib-fts/stopwords"\" -I/raid/data/module/Dovecot/sys/include -std=gnu99 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/raid/data/module/Dovecot/sys/include -MT fts-filter.lo -MD -MP -MF .deps/fts-filter.Tpo -c -o fts-filter.lo fts-filter.c libtool: compile: /home/andreas/Thecus/n4200pro-5.2.0-toolchain/i686-nptl-linux-gnu/bin/i686-nptl-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -I../../src/lib-mail -I../../src/lib-fts -I/raid/data/module/Dovecot/sys/include/libexttextcat/ @LIBICU_CFLAGS@ -DUDHRDIR=\"../../src/lib-fts\" -DDATADIR=\"/raid/data/module/Dovecot/sys/share/dovecot\" -DTEST_STOPWORDS_DIR=\"../../src/lib-fts/stopwords\" -I/raid/data/module/Dovecot/sys/include -std=gnu99 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -Wstrict-aliasing=2 -I/raid/data/module/Dovecot/sys/include -MT fts-filter.lo -MD -MP -MF .deps/fts-filter.Tpo -c fts-filter.c -fPIC -DPIC -o .libs/fts-filter.o i686-nptl-linux-gnu-gcc: error: @LIBICU_CFLAGS@: No such file or directory Makefile:714: recipe for target 'fts-filter.lo' failed make[4]: *** [fts-filter.lo] Error 1 make[4]: Leaving directory '/home/andreas/Thecus/Dovecot/dovecot-2.2.29.1/src/lib-fts' Makefile:562: recipe for target 'all' failed === As far as I can tell, my pkgconfig file (/raid/data/module/Dovecot/sys/lib/pkgconfig/icu-i18n.pc) also seems to be fine: === # Copyright (C) 2016 and later: Unicode, Inc. and others. # License & terms of use: http://www.unicode.org/copyright.html # Copyright (C) 2010-2013, International Business Machines Corporation. All Rights Reserved. # CFLAGS contains only anything end users should set CFLAGS = # CXXFLAGS contains only anything end users should set CXXFLAGS = -std=c++11 # DEFS only contains those UCONFIG_CPPFLAGS which are not auto-set by platform.h DEFS = prefix = /raid/data/module/Dovecot/sys exec_prefix = ${prefix} #bindir = ${exec_prefix}/bin libdir = ${exec_prefix}/lib includedir = ${prefix}/include baselibs = -lpthread -ldl -lm #datarootdir = ${prefix}/share #datadir = ${datarootdir} #sbindir = ${exec_prefix}/sbin #mandir = ${datarootdir}/man #sysconfdir = ${prefix}/etc UNICODE_VERSION=9.0 ICUPREFIX=icu ICULIBSUFFIX= LIBICU=lib${ICUPREFIX} #SHAREDLIBCFLAGS=-fPIC pkglibdir=${libdir}/icu${ICULIBSUFFIX}/59.1 #pkgdatadir=${datadir}/icu${ICULIBSUFFIX}/59.1 ICUDATA_NAME = icudt59l #ICUPKGDATA_DIR=${exec_prefix}/lib #ICUDATA_DIR=${pkgdatadir} ICUDESC=International Components for Unicode Version: 59.1 Cflags: -I${includedir} # end of icu.pc.in Description: International Components for Unicode: Internationalization library Name: icu-i18n Requires: icu-uc Libs: -licui18n === Note that even adding a line stating LIBICU_CFLAGS=-I/raid/data/module/Dovecot/sys/include (just in order to set it to any non-null value) to the icu-i18n.pc file and/or setting an environment variable export LIBICU_CFLAGS=-I/raid/data/module/Dovecot/sys/include before running configure does NOT help to get rid of the above error... So do you have any idea why variable substitution for LIBICU_CFLAGS does not work, and what could be done to work around this? Many thanks in advance for your kind help with this! Best regards, Andreas awl1(a)gmx.net [View Less]

1 1

Dovecot/Sieve shortcuts?
by Adam Shostack 24 May '17

24 May '17

Hi, Is there a clean way to match on an email address the way procmail ^TO_ did? that was a macro which expanded to (^((Original-)?(Resent-)?(To|Cc|Bcc)|(X-Envelope |Apparently(-Resent)?)-To):(.*[^-a-zA-Z0-9_.])?) so you could write * ^TO_dovecot dovecot and grab messages to the list. In sieve, I find myseld writing ["To","cc"] and wonder if there's a better way. Adam

4 8

dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
by dovecot＠jeffandjessi.com 24 May '17

24 May '17

Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a connection is made the auth worker loads and emails are downloaded and everything "is fine". However, about 30 … [View More]

1 0

v2.2.30 release candidate released
by Timo Sirainen 24 May '17

24 May '17

https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.30.rc1.tar.gz.sig There are a couple of changes still coming, but now would be a good time to make sure anything unexpected hasn't broken. The final release should be out early next week. * auth: Use timing safe comparisons for everything related to passwords. It's unlikely that these could have been used for practical attacks, especially because Dovecot delays and flushes all … [View More]

1 0

Postfix and Dovecot SASL: log NTLM username
by Bradley Giesbrecht 24 May '17

24 May '17

dovecot 2.2.22 postfix 3.1.1 I’m seeing "SASL NTLM authentication failed: {long_hash}” in mail.log. Is there a way to log the SASL username? I think postfix is logging what Dovecot SASL is returning so I hope I am asking on the right list. Regards, Bradley Giesbrecht (pixilla)

2 5

dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11
by dovecot＠jeffandjessi.com 24 May '17

24 May '17

Trying to track down a dovecot issue .... The error message is: dovecot: auth-worker: Fatal: master: service(auth-worker): child XXXXX killed with signal 11 (core not dumped - set service auth-worker { drop_priv_before_exec=yes }) The setup is dovecot 2.2.29.1 with passwd and mysql auth db's and a very basic config. both authentications work ... the symptom is that after a connection is made the auth worker loads and emails are downloaded and everything "is fine". However, about 30 … [View More]

2 1

[imaptest] Explaining errors
by aduprat 24 May '17

24 May '17

Hi, I'm an Apache James committer and we are curious to use imaptest in order to validate our IMAP protocol implementation. I'm using the nightlybuild : imaptest-20170506 I follow the examples given in the /T/ /est IMAP server compliancy/ examples https://imapwiki.org/ImapTest/Examples. And I wanted to analyse the errors reported, here are some: Error: user1(a)james.org[11]: seq too high (16 > 15, state=APPEND): * 16 FETCH (BODY[HEADER.FIELDS (In-Reply-To From) ] "From: marcelo(a)… [View More]carpa.ciagri.usp.br") Error: user1(a)james.org[14]: seq too high (26 > 25, state=APPEND): * 26 FETCH (MODSEQ (6068) FLAGS (\Answered \Draft \Flagged)) Error: user1(a)james.org[14]: seq too high (20 > 16, state=APPEND): * 20 EXPUNGE Error: user10(a)james.org[18]: Keyword used without being in FLAGS: $Label1: * 1 FETCH (MODSEQ (8) FLAGS (\Answered \Deleted \Draft $Label1 $Label3)) Error: Checkpoint: Total RECENT count 6 larger than current message count 3 Warning: Disabling \Recent flag tracking Error: user1(a)james.org[5]: Owned flag changed: \Deleted: * 7 FETCH (FLAGS (\Answered \Deleted \Recent $Label2)) Error: user1(a)james.org[5]: STORE didn't return FETCH FLAGS for seq 18 (expunged=yes): 5.75 OK STORE completed. Error: user1(a)james.org[1]: SEARCH result missing seq 2 (uid 0): 1.13 OK SEARCH completed. Error: Keyword '$Label1' dropped, but it still had 1 references Do you have a link explaining what are those failures ? Is there a report by IMAP command giving us an idea about our compliancy ? Do you allow us to communicate about such tests, for example: - in news http://james.apache.org/#posts ? - in medium article ? We also would like to have James mentioned in the servers status page https://imapwiki.org/ImapTest/ServerStatus How may we help you for that ? Thanks in advance, -- Antoine Duprat Développeur LGS/OBM/R&D Committer/PMC Apache James ------------------ GROUPE LINAGORA 74-80 rue Roque de Fillol 92800 Puteaux +33 (0)8 10 25 12 51 +33 (0)6 45 63 27 17 aduprat(a)linagora.com ------------------ La présente transmission contient des informations confidentielles appartenant à Linagora, exclusivement destinées au(x) destinataire(s) identifié(s) ci-dessus. Si vous n'en faites pas partie, toute reproduction, distribution ou divulgation de tout ou partie des informations de cette transmission, ou toute action effectuée sur la base de celles-ci vous sont formellement interdites. Si vous avez reçu cette transmission par erreur, nous vous remercions de nous en avertir et de la détruire de votre système d'information. The present transmission contains privileged and confidential information belonging to Linagora, exclusively intended for the recipient(s) thereabove identified. If you are not one of these aforementioned recipients, any reproduction, distribution, disclosure of said information in whole or in part, as well as any action undertaken on the basis of said information are strictly prohbited. If you received the present transmission by mistake, please inform us and destroy it from your messenging and information systems. [View Less]

2 2

Sender address when notifying original recipient
by Christoph Pleger 23 May '17

23 May '17

Hello, I am using sieve with notification of the original recipient in the case that an email has been identified to contain a virus. After upgrading dovecot from 2.2.21 to 2.2.29.1, I now detected that in these notifications, their sender address is now <postmaster@>, instead of <postmaster(a)mailserver.domain>, like it was before. Is it possible to revert to the old format? Regards Christoph

3 5

Dovecot pop3 feature
by Markus Eckerl 22 May '17

22 May '17

Hi all, we are using dovecot since several years without any problems or trouble. Now we are having trouble with a few of our customers - they are trying to fetch their emails every few seconds (3-5!). These customers are using Microsoft Exchange Server and also all of these customers are cared by the same IT Professional... Is it possible to send a pop3 "LOGIN-DELAY" if the customers last login is only a few seconds away? A simple firewall rule for rate limiting is not possible because … [View More]

2 1

Configuration is not working with Thunderbird
by Quark 22 May '17

22 May '17

Hi, I'm new to the list (and postfix / dovecot), so if I mistakenly omit something, then please forgive me. I cannot log into Thunderbird via IMAP with my configuration. However, I can check the mail of each user by logging into their user account & then using the "mail" command. Is there something that is wrong with my config to not allow me to log into Thunderbird (Version 52.1.1)? I'm using Postfix 3.1.0 if that helps. Any help would be greatly appreciated. Thanks! Here is … [View More]

2 5

Backing up and restoring maildir folders
by Timothy D Legg 22 May '17

22 May '17

Hello, I am migrating to a different distribution of Linux that involves changing to an earlier version of dovecot (2.2.22 to 2.2.13). As part of this process, I will be copying several maildirs to the new machine. One of these has a number of files and directories that resemble this one example: cur/ dovecot.index dovecot.index.cache dovecot.index.log dovecot.mailbox.log dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.59206030 .Drafts/ new/ .Sent/ subscriptions tmp/ .Trash/ Is it … [View More]

2 1

core from 2.2.29.1
by Luciano Mannucci 22 May '17

22 May '17

I've got this in my logfile, should I worry? May 19 14:45:04 imap(liscia_mcs): Panic: file mail-index-transaction-update.c: line 19 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) May 19 14:45:04 imap(liscia_mcs): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9cd16) [0xb7568d16] -> /usr/lib/dovecot/libdovecot.so.0(+0x9cd9f) [0xb7568d9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb74f204e] -> /… [View More]usr/lib/dovecot/libdovecot-storage.so.0(+0xe3ebf) [0xb76b7ebf] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xe730c) [0xb76bb30c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_uid+0x1d) [0xb76bf47d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_decision_state_update+0xac) [0xb769ff8c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_lookup_headers+0x7f) [0xb76a23bf] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb2898) [0xb7686898] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xbf) [0xb768723f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x45) [0xb7601e95] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb4fc1) [0xb7688fc1] -> /usr/lib/dovecot/libdovecot-storage.so.0(+ 0xb518f) [0xb768918f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_close+0x136) [0xb76896e6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x6c) [0xb761085c] -> dovecot/imap() [0x8052e1d] -> dovecot/imap() [0x805303c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x67) [0xb7580997] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xeb) [0xb75823ab] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x45) [0xb7580a55] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb7580c18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2d) [0xb74fd1ad] -> dovecot/imap(main+0x344) [0x806dbc4] -> /lib/libc.so.6(__libc_start_main+0xfe) [0xb7357c2e] May 19 14:45:04 imap(liscia_mcs): Fatal: master: service(imap): child 24082 killed with signal 6 (core dumped) Here is mi doveconf -n: # 2.2.29.1 (e0b76e3): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: Linux 3.0.101-105-pae i686 openSUSE 11.4 (i586) ext3 auth_cache_size = 3 k auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes default_client_limit = 1249 default_vsz_limit = 712 M disable_plaintext_auth = no first_valid_gid = 0 first_valid_uid = 100 info_log_path = /var/log/dovecot/logfile.info listen = * log_path = /var/log/dovecot/logfile login_greeting = Dovecot at Baobab ready. login_trusted_networks = 127.0.0.0/8 212.45.144.0/24 192.168.134.0/24 mail_location = mbox:/var/spool/mailboxes/%u:INBOX=/var/spool/mail/%u:DIRNAME=mbox:INDEX=/var/dovecot_indexes/%u maildir_copy_with_hardlinks = no 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 mbox_lock_timeout = 443 secs namespace { inbox = yes location = prefix = separator = . type = private } passdb { driver = pam } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } protocols = pop3 imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imaps { address = * } process_limit = 512 } service pop3-login { chroot = executable = pop3-login -D inet_listener pop3s { address = * } process_limit = 512 } ssl_ca = </etc/ssl/ca.crt ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = mail_log notify } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes } protocol lda { info_log_path = /var/log/dovecot/lda.log log_path = /var/log/dovecot/lda-errors.log postmaster_address = postmaster(a)mcs.it } Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/ [View Less]

1 0

Re: Pacaging/build issues with AIX and vac (dovecot-2.2.25)
by seema pandhre 22 May '17

22 May '17

Hi Micheal, I am currently working on AIX + VAC + NTPv4 build. and I have also faced same issues as mentioned by you in link https://www.dovecot.org/list/dovecot/2016-October/105597.html Wondering if you have got any resolution for above issue. If yes, please help me with your guidance. thanks in advance, seema

1 0

Using Dovecot for a Geo-replicated World-wide Email Service
by Lennart Oldenburg 22 May '17

22 May '17

Hello everyone, my colleagues and I from Technische Universität Berlin are currently looking into the best way to setup a Dovecot-powered email service that is simultaneously accessible world-wide and still provides short response times by redirecting users to the geographically-closest cluster. We imagine the setup to make use of multiple data center regions in public clouds around the world, e.g. in Amazon Web Services (AWS) or Google Compute Platform (GCP). At the same time, state is … [View More]considered to be shared, i.e. changes made on file system in any local cluster will have to be synchronized with all other clusters around the globe (mailbox replication) and mailboxes might be manipulated from any data center in the world, potentially at the same time. Naturally, problems arise. We have multiple questions and would be very interested in the best way to approach them based on your experiences and recommendations: 1) Which path should we take replication-wise? Please keep in mind that we are targeting replication between more than 2 clusters. Traditionally, in a rather small local setup with mostly reliable network, a distributed file system such as NFS or GlusterFS might be the best option. Unfortunately, though, when scaling to more than 2 data centers geographically-distributed around the globe, latency becomes severe and distributed file systems might not be the way to go anymore. What is your recommendation for replicating state? 2) We are mostly interested in providing short response times to client requests while maintaining global state consistency (that is, avoiding conflicts in state and not losing any user data). What are your recommendations in that direction? Any particular performance optimizations we could apply to Dovecot? 3) Is there a recommended way to measure and monitor Dovecot's service quality? For example, is there a way to export "live" metrics of a running Dovecot deployment to something such as Prometheus (https://prometheus.io)? 4) Maildir as the way to represent mailboxes and deliver emails on file system is kind of a given. I wonder, though, how well is dbox replicatable? What happens when dbox files are synchronized (e.g. via dsync) and a conflict arises? Does dbox offer a performance improvement over Maildir? 5) We perceive Dovecot to come with many optimizations to speed up "read" IMAP commands, i.e. non-state-changing ones. Is this perception correct? Or is Dovecot able to use its various index and log files for fast "write" IMAP commands (e.g. CREATE, DELETE, RENAME, APPEND, STORE, ...) as well? 6) Would DovecotPRO by Dovecot Oy offer any advantage to state replication? For example, could the Object Storage Plugin be used to replicate mailboxes through some object store service offered world-wide? 7) Is the setup we have in mind based on Dovecot a feasible solution for world-wide email comparable to services like Gmail? If not, what would you change or not do at all? Please excuse if some questions might be of rather basic nature, we are not at all Dovecot experts. I tried to gather as much information on that topic as possible from the wiki and sources found online but I might have missed an important page. In that case, please point me towards existing resources on the questions raised above. Thanks in advance and kind regards, Lennart Oldenburg [View Less]

1 0