- dovecot - dovecot.org

lmtp segfault after upgrade
by Tom Sommer 19 May '17

19 May '17

I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting flooded by these errors: lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] lmtp[46304]: segfault at 91 ip 00007f771ba64d11 sp 00007ffe830635a0 error 4 in libdovecot.so.0.0.0[7f771b9bf000+11c000] lmtp[45775]: segfault at 21 ip 00007f206ed81d11 sp 00007ffd0f0daad0 error 4 in libdovecot.so.0.0.0[7f206ecdc000+11c000] lmtp[46649]: segfault at 21 ip 00007ff4aa027d11 sp 00007ffc05841430 error 4 in libdovecot.so.0.0.0[7ff4a9f82000+11c000] lmtp[45774]: segfault at 21 ip 00007ff1f3e0bd11 sp 00007ffe0ba00340 error 4 in libdovecot.so.0.0.0[7ff1f3d66000+11c000] lmtp[45776]: segfault at 411 ip 00007f96ded95d11 sp 00007ffce6401870 error 4 in libdovecot.so.0.0.0[7f96decf0000+11c000] lmtp[46896]: segfault at 21 ip 00007fbf1aa70d11 sp 00007ffc79e22bf0 error 4 in libdovecot.so.0.0.0[7fbf1a9cb000+11c000] lmtp[46695]: segfault at 21 ip 00007fd5ccad6d11 sp 00007ffe19e759d0 error 4 in libdovecot.so.0.0.0[7fd5cca31000+11c000] lmtp[45773]: segfault at 21 ip 00007f0eb7b65d11 sp 00007fff9d02e570 error 4 in libdovecot.so.0.0.0[7f0eb7ac0000+11c000] lmtp[47101]: segfault at 21 ip 00007fa95b052d11 sp 00007fff2d5485a0 error 4 in libdovecot.so.0.0.0[7fa95afad000+11c000] lmtp[45772]: segfault at 21 ip 00007f2f52b49d11 sp 00007fff99a4a6e0 error 4 in libdovecot.so.0.0.0[7f2f52aa4000+11c000] lmtp[46595]: segfault at 21 ip 00007f0ccbdbad11 sp 00007ffd17bfe9e0 error 4 in libdovecot.so.0.0.0[7f0ccbd15000+11c000] lmtp[45770]: segfault at 21 ip 00007f94a576ed11 sp 00007ffc29c2ff00 error 4 in libdovecot.so.0.0.0[7f94a56c9000+11c000] lmtp[45769]: segfault at 21 ip 00007f34999b5d11 sp 00007ffe28818350 error 4 in libdovecot.so.0.0.0[7f3499910000+11c000] lmtp[47371]: segfault at 21 ip 00007f13c611fd11 sp 00007ffcdb000b10 error 4 in libdovecot.so.0.0.0[7f13c607a000+11c000] lmtp[47419]: segfault at 21 ip 00007f4010ff2d11 sp 00007ffd97519420 error 4 in libdovecot.so.0.0.0[7f4010f4d000+11c000] lmtp[47511]: segfault at 581 ip 00007fd5e3d21d11 sp 00007ffce61f29c0 error 4 in libdovecot.so.0.0.0[7fd5e3c7c000+11c000] lmtp[47277]: segfault at 21 ip 00007f04c3d6cd11 sp 00007ffc421da1b0 error 4 in libdovecot.so.0.0.0[7f04c3cc7000+11c000] lmtp[45771]: segfault at 21 ip 00007f55c690ed11 sp 00007fff35521fc0 error 4 in libdovecot.so.0.0.0[7f55c6869000+11c000] lmtp[47543]: segfault at 21 ip 00007f11ea946d11 sp 00007ffdd9a97690 error 4 in libdovecot.so.0.0.0[7f11ea8a1000+11c000] lmtp[47669]: segfault at 21 ip 00007f8f58abbd11 sp 00007ffdd5573220 error 4 in libdovecot.so.0.0.0[7f8f58a16000+11c000] lmtp[46959]: segfault at 41 ip 00007ff9d6f3ed11 sp 00007ffe28dc8ea0 error 4 in libdovecot.so.0.0.0[7ff9d6e99000+11c000] Any ideas? -- Tom

4 17

per user procmail filtering and dovecot-lda
by James Nord 18 May '17

18 May '17

Hi all, I recently migrated my system (postfix/Dovecot)from mbox to Maildir. Almost everything is working (phone and thunderbird show all my mail and folders with mail) However I am stuck on my .procmailrc rules # cat /etc/procmailrc SENDMAIL=/usr/sbin/sendmail SENDMAILFLAGS=-oi LOGFILE=/var/log/procmail.log ORGMAIL=${HOME}/Maildir/ DEFAULT=${ORGMAIL} MAILDIR=${HOME}/Maildir/ DELIVER="/usr/lib/dovecot/deliver -d $LOGNAME" # next line is to support user .procmailrc files INCLUDERC=$HOME/.procmailrc :0 w | $DELIVER # cat ~/.procmailrc :0 w * ^List-ID:.*jenkinsci-dev.googlegroups.com | $DELIVER -m mailing-lists/jenkinsci-dev :0 w * ^List-ID:.*jenkinsci-users.googlegroups.com | $DELIVER -m mailing-lists/jenkinsci-users However dovecot-lda complains that the mailboxes "mailing-lists/jenkinsci-users", "mailing-lists/jenkinsci-dev" etc do not exist so delivers to the INBOX. Everything I have read says that the mailbox specified by -m is the name as seen by the mail client, and this is what the client sees (see image). I have tried changing the mailbox to INBOX/mailing-lists/... inbox/mailing-lists/... but the same still happens. So I am missing something somewhere and my google foo is unfortunately letting me down this time. Is there someone that can help me? (I'm not subscribed to the list so a CC to me would be appreciated) Regards /James

5 7

Re: Sieve GLOBAL + Sieve LOCAL
by Joseph Tam 17 May '17

17 May '17

Luescher Claude <stargate(a)tango.lu> writes: > I am using dovecot: > ... > ii dovecot-sieve 1:2.2.10-1 amd64 > secure POP3/IMAP server - Sieve filters support > ... > doveconf -n | grep -i sieve > Since doveconf does not indicate I believe my version does not support: > > sieve_global_path I see mentions of this configuration variable in 7 year old dovecot posts, so it's been around a long time. You should do doveconf -a | grep sieve_global_path since "-n" won't list unchanged (defaulted) configuration values. Joseph Tam <jtam.home(a)gmail.com>

1 0

Conditionally Filter Mails During IMAP Fetch
by Ory Drilon 17 May '17

17 May '17

Hi, is there a way to arbitrarily filter out mails at the moment the IMAP request is made, based on properties of the IMAP session and the mail itself? All the filtering methods I find occur during delivery time.

2 1

Re: ACL and virtual user
by Davide Marchi 15 May '17

15 May '17

...I had under my eyes the solution I have not seen: * user=foo lrw Public user=bar lrwstipekxa Public/* user=bar lrwstipekxa I was enough (in my case) add the initial "*" wildcards, like this: * user=info(a)mydomain.com lrwsi where the "*" wildcards means all groups. I have verified and so the configuration is perfect, the user can not delete their own messages The fact remains that on the wiki dovecot ACL these steps, in the case of virtual users, are not clear, at least in my opinion. :-) I hope at least that my experience can be of assistance to other users. Many many thanks! Davide

1 0

ACL and virtual user
by Davide Marchi 15 May '17

15 May '17

Hi friends, I would like to remove write rights for a specific virtual user/email address. I've read the wiki "https://wiki2.dovecot.org/ACL" but there is nothing about it. So I started reading and rereading some old ML, like this: https://www.dovecot.org/list/dovecot/2006-June/013683.html where they talk about something like that but I would like to implement current guidelines for the "Global ACL file" and for virtual user. So I've try: * user=foo lrw Public user=bar lrwstipekxa Public/* user=bar lrwstipekxa But in my case for virtual user, so I tried (obviously I changed the email address with a generic one): -------------- #user=info(a)mydomain.com lrwsi -------------- Log: May 15 10:40:44 server dovecot: imap(info(a)mydomain.com): Error: Global ACL file /etc/dovecot/dovecot-acl line 1: Unknown ID 'lrwsi' -------------- #owner #user=info at mydomain.com lrwsi -------------- Log: May 15 10:47:58 server dovecot: imap(info(a)mydomain.com): Error: Global ACL file /etc/dovecot/dovecot-acl line 1: Missing ACL rights -------------- #user=info at mydomain.com lrwsi -------------- Log: May 15 10:51:57 server dovecot: imap(info(a)mydomain.com): Error: Global ACL file /etc/dovecot/dovecot-acl line 2: Unknown ID 'at' But none of these gave results, could you explain better or gime me an example? Many many thanks! Davide Italy

1 0

[BUG] doveadm kick doesn't play well with hibernate
by Christian Balzer 15 May '17

15 May '17

Hello, Dovecot 2.2.27 (Debian Jessie backports). When issuing a "doveadm kick" for a specific user I was greeted by: --- "warning: other connections would also be kicked from following users:" --- and a list of 22odd thousand users. As it turns out, kick wants to smack the hibernation proces(ses) that have hibernated sessions for this user, obviously the wrong approach here. If there's doveadm command to wake up and thus un-hibernate sessions for a specific user this could be used as a workaround but a quick glance suggest no such thing. This functionality is absolutely crucial for us as we need this for our custom mailbox migration functionality. If there's no workaround or fix within 2 months I'll be forced to disable hibernation again (with a heavy heart). Regards, Christian -- Christian Balzer Network/Systems Engineer chibi(a)gol.com Global OnLine Japan/Rakuten Communications http://www.gol.com/

2 2

Dovecot 2.2.29.1 + VPopMail 5.4.33
by Nicholas Chua 12 May '17

12 May '17

Hi all, I have a fresh installation of a Vpopmail 5.4.33 + Dovecot 2.2.29.1 + SQL As usual I followed the AuthDatabase/VPopMail wiki password_query = SELECT CONCAT(pw_name, '@', pw_domain) AS user, \ pw_clear_passwd AS password \ FROM vpopmail \ WHERE pw_name = '%n' AND pw_domain = '%d' user_query = SELECT pw_dir as home, \ 89 AS uid, 89 AS gid \ FROM vpopmail \ WHERE pw_name = '%n' AND pw_domain = '%d' For VPopMail, I prefer to have an individual table in the vpopmail database for each domain. So my structure will be something like this vpopmail.abc_com vpopmail.xyz_com To achieve this I add this configure when compiling VPopMail --disable-many-domains But dovecot will not read vpopmail.abc_com, instead it keep looking for vpopmail.vpopmail auth-worker(8643): Warning: mysql: Query failed, retrying: Table 'vpopmail.vpopmail' doesn't exist If I remove --disable-many-domains in the configuration, I have no issue. Is there a new password and user query to have this working? The last working version I had installed is Dovecot 2.2.15 Thank you nic

1 0

folders in public namespace only visable to 2nd folder level in 2.2.29.1
by Andreas Oster 11 May '17

11 May '17

Hi all, I am currently facing an issue with Dovevot version 2.2.29.1 where subfolders in a public namespace are only visible to the 2nd folder level: namespace Public -> folder "1st" -> folder -> "2nd" -> folder "3rd" .... When one user creates a subfolder below the 2nd level other users do not see that folder and are unable to subscribe to this folder. Folders created under the 1st level however are visible and subscribable by other users. namespace { disabled = no hidden = no ignore_on_failure = no inbox = no list = children type = public separator = / prefix = Public/ location = maildir:/var/vmail/public:INDEXPVT=~/Maildir/public subscriptions = no } I do not know at which point ( dovecot update ) this issue appeared. Does anyone face the same problem ? Thank you for your kind help best regards Andreas

5 5

Example for doveadm-save using Doveadm HTTP API
by KT Walrus 11 May '17

11 May '17

I could use an example of how to use curl to save a new message to a user’s INBOX using the Doveadm HTTP API. https://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP <https://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP> Do I really use the -d option and inline the entire new message in the command-line? Or, should I create a temporary .json file with the message wrapped in JSON and pass this filename to the -d option? Does anyone have a PHP class that abstracts the HTTP API commands? I’ve been using the Roundcube Framework to deliver new messages by IMAP, but I’m experimenting whether the Doveadm HTTP API might be a better solution. I eventually want my PHP code to do full administration of my users mailboxes. I was planning on using Sieve pipe PHP scripts in conjunction with IMAP to do full admin on mailboxes (as they receive new messages or change a flag, I would trigger maintenance on the mailbox such as deleting or moving to the trash old messages or filing a copy of a new message in a folder). Finally, is the Doveadm HTTP API stable enough to use in production? It seems like the documentation is rather minimal. Can this interface really be used for new message delivery instead of LMTP in production? Or, is this a bad idea to combine mailbox administration with new message delivery? Does anyone here use the Doveadm HTTP API in production? Kevin

3 5