- dovecot - dovecot.org

doveadm backup fails (compromised single attachment storage)
by Webert de Souza Lima 03 Oct '16

03 Oct '16

Hi, A couple of months ago I had a problem with Single Attachment Storage after infrastructure migration; All mailboxes were rsynced to another filesystem, and that may have broken Single Attachment Storage. Many, many (if not all) mailboxes show the below logs on dovecot: imap(foo(a)bar.com): Error: read(attachments-connector(zlib(/dovecotdir/mail/ bar.com/foo/mailboxes/INBOX/dbox-Mails/u.26426))) failed: read(/dovecotdir/attach/ bar.com/de/86/de8673894d6fb3f4460e3c26436eefa9a73517fa0f000452f553822367220… b/l]) failed: open(/dovecotdir/attach/ bar.com/de/86/de8673894d6fb3f4460e3c26436eefa9a73517fa0f000452f553822367220…) failed: No such file or directory When that happens, the MUA keeps syncing forever. Now, I need to migrate all mailboxes (again) to another dovecot instance (with no SAS), which works perfectly for new users but when I try to migrate users from my current dovecot server for this new server, I get such errors again, and I can't migrate: 2016-09-29T12:20:50.995934059Z Sep 29 12:20:50 dsync-server(foo(a)bar.com): Error: dsync(cf7d091311eb): read(attachments-connector(zlib(/dovecotdir/mdbox/bar.com/foo/storage/m.1))) failed: read(/dovecotdir/attach/ bar.com/0c/df/0cdf86b1920938fe3a043f87e2ee9e63dda276bd5b9fba687e4a0c63d181c… b/l]) failed: open(/dovecotdir/attach/ bar.com/0c/df/0cdf86b1920938fe3a043f87e2ee9e63dda276bd5b9fba687e4a0c63d181c…) failed: No such file or directory (last sent=mail, last recv=mail_request (EOL)) Is there a way to fix the attachments problem? (I know I can't recover such files, that's Ok) Is there a way to migrate (dsync backup) ignoring such problems? Thanks in advance.

1 2

shared folders
by Scherff 03 Oct '16

03 Oct '16

Hi, i am stuck. Try to install shared folders - dovecot is running fine. ACL is working. But i can't get running the shared folders. Maybe someone can help. This are the relevant conf. I think i have some mistake there - perhaps in location - changed try and error - stuck: mail_home = /var/vmail/mailboxes/%d/%n mail_location = maildir:~/mail:LAYOUT=fs namespace { hidden = no ignore_on_failure = no list = children location = maildir:%%h/mail:INDEX=%h/mail/shared/%%u:CONTROL=%h/mail/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = mailbox Archives { auto = subscribe special_use = \Archive } mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Notes { auto = subscribe } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = } plugin { # global acl - prevent expunche for some folder acl = vfile:/var/vmail/dovecot-acl acl_shared_dict = file:/var/vmail/db/shared-mailboxes.db } protocol imap { imap_idle_notify_interval = 15 mins mail_max_userip_connections = 30 mail_plugins = " acl imap_acl" } protocol lmtp { mail_plugins = " acl" } Need some hint. Thanks Alfred

2 1

Shared folder in a sharded cluster setup
by Peer Heinlein 03 Oct '16

03 Oct '16

Hi! With Dovecot Director and Proxy or the new (great!) TAG-feature from Dovecot it's easy to set up a shared IMAP-Cluster with individual local filesystems. But I'm unsure if it's possible to build a setup where shared mailboxes still can work. If user A is on Cluster (1) and user B is on (2), and Cluster (1) does not have access to the mail-home from B on (2), then user A can not reach the shared folders provided from User B on (2). I hope that there is a kind of backend-proxy-mechanism, so that the imap process of A on (1) can imap-proxy the requests for the shared folder to a node from cluster shard (2). And: To be exact, the imap process on (1) should forward the request to cluster (2) by the director system to make sure, that the connection will terminate on the right active backend of User B. This sounds like a special problem if local filesystems with mdbox are used and I now the great features of using Dovecot on Object Store, where every node can check out all mail-locations from all users. But especially on obox-systems it is very important that requests for a user are always terminated on the same backend. So how can shared folders work there?! Node (1) can not checkout the shared folders from User B if his obox storage is already active on another host (2)! 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

Requiring client certificate on only one interface
by Braden Thomas 02 Oct '16

02 Oct '16

Hi, I'm trying to require client certificates on only one interface. I'm running dovecot 2.1.7. There have been a couple of recent threads about this kind of configuration: http://dovecot.org/list/dovecot/2016-August/105244.html (Aug 2016) http://www.dovecot.org/list/dovecot/2016-February/103067.html (Feb 2016) However, these threads recommend an approach that no longer works. Specifically, the "-l" or "-P" arguments to imap-login no longer work. Is there currently a recommended way to configure dovecot like this? Braden

1 0

Re: Bug: Shared Mailbox - Case Sensitivity
by Aki Tuomi 01 Oct '16

01 Oct '16

Can you provide doveconf -n? ---Aki TuomiDovecot oy -------- Original message --------From: Leander Schäfer <info(a)netocean.de> Date: 01/10/2016 03:41 (GMT+02:00) To: Aki Tuomi <aki.tuomi(a)dovecot.fi>, Dovecot Mailing List <dovecot(a)dovecot.org>, Timo Sirainen <tss(a)iki.fi> Subject: Re: Bug: Shared Mailbox - Case Sensitivity Am I missing something, or might this be a bug as it seems to me? Am 16.09.16 um 14:21 schrieb Leander Schäfer: > Hi Aki, > > > Thanks for your advice. Yes, I'm aware of this. Yet lowercasing should > be the default since Dovecot 2.1.x., isn't it? Yet I wouldn't know > where exactly to implement this %L, since the ACLs are set through > IMAP commands through the users mailclient like Thunderbird. So in > other words, the email address to whom the user want to grant ACLs > provided by the user's mailclient, has nothing to do with my auth > backend where e.g. %u => %Lu would apply. PLease correct me if I'm > wrong here. > > > It clearly looks like a bug of the internal processing of the > "dovecot-acl-list" files. It simply lacks on a lowercase enforcement > in the code, like it already seems to do for the "dovecot-acl" file. > > > Best regards > > Leander Schäfer > > > > Am 16.09.16 um 12:53 schrieb Aki Tuomi: >> >> On 16.09.2016 12:54, Leander Schäfer wrote: >>> Hi, >>> >>> unfortunately I found a bug in Dovecot's ACL handling for shared >>> mailboxes. It turns out Dovecot doesn't enforce lower casing the >>> privileged username to whom the mailbox should be shared to. This >>> results in a invalid configuration. Users get confused, since they >>> passed on a valid email address in their ACL setup. >>> >>> /usr/local/www/default/mail/test(a)mydomain.localdomain/maildir/.Spam/dovecot-acl >>> >>> >>> user=leander(a)mydomain.localdomain eilrwts >>> ^^ works >>> >>> /usr/local/www/default/mail/leander(a)mydomain.localdomain/maildir/dovecot-acl >>> >>> >>> user=test(a)mydomain.localdomain eilrwts >>> ^^ works >>> >>> /usr/local/www/default/mail/test(a)mydomain.localdomain/maildir/.Drafts/dovecot-acl >>> >>> >>> user=Leander(a)MyDomain.LocalDomain eilrwts >>> ^^ Doesn't work >>> >>> Best regards >>> Leander Schäfer >> Hi! Did you know you can use %Lu instead of %u to force lowercasing? >> >> Aki

1 0

Re: NFSv4 and Maildir
by Joseph Tam 01 Oct '16

01 Oct '16

> we have a setup with (CentOS 6) Director+Dovecot, Maildir as storage on > NetApp NFS v3. Every time I try to switch to NFS v4 I found issue with > lock (and others). So for me NFSv4 with Maildir is "unstable" or need a > fine tuning that I don't know. I found the same thing, and turning off write delegation seemed to have solved the problem. I still don't know why, though. Joseph Tam <jtam.home(a)gmail.com>

2 1

Bug: Shared Mailbox - Case Sensitivity
by Leander Schäfer 01 Oct '16

01 Oct '16

Hi, unfortunately I found a bug in Dovecot's ACL handling for shared mailboxes. It turns out Dovecot doesn't enforce lower casing the privileged username to whom the mailbox should be shared to. This results in a invalid configuration. Users get confused, since they passed on a valid email address in their ACL setup. /usr/local/www/default/mail/test(a)mydomain.localdomain/maildir/.Spam/dovecot-acl user=leander(a)mydomain.localdomain eilrwts ^^ works /usr/local/www/default/mail/leander(a)mydomain.localdomain/maildir/dovecot-acl user=test(a)mydomain.localdomain eilrwts ^^ works /usr/local/www/default/mail/test(a)mydomain.localdomain/maildir/.Drafts/dovecot-acl user=Leander(a)MyDomain.LocalDomain eilrwts ^^ Doesn't work Best regards Leander Schäfer

3 4

acl_group not working not working correctly
by Leander Schäfer 01 Oct '16

01 Oct '16

Hi, I'm trying to setup group based ACLs coming from OpenLDAP. My setup doesn't require a POSIX Group match. In the Dovecot configuration file I have this: "user_attrs = [...], mailAclGroups=acl_groups" as well as "acl = vfile:/usr/local/etc/dovecot/global-acls:cache_secs=300". The user has "public" in the LDAP attribute "mailAclGroups". It seems to get everything right. I checked with doveadm - and I see public ist listed as expected: cat /var/log/debug.log [...] Sep 16 23:39:04 WM-01 dovecot: auth: Debug: client passdb out: OK 1 user=leander(a)mydomain.localdomain acl_groups=public [...] cat /usr/local/etc/dovecot/global-acls INBOX owner lrwstipekxa Drafts owner lrwstipeka Sent owner lrwstipeka Spam owner lrwstipeka Trash owner lrwstipeka Public authenticated l Public group-override=public lrwstipekx Public/* group-override=public lrwstipekx doveadm mailbox list -u leander(a)mydomain.localdomain Drafts Sent Trash Spam Shared Public Public/Service Center Shared/test(a)mydomain.localdomain Shared/test(a)mydomain.localdomain/Drafts Shared/test(a)mydomain.localdomain/Sent Shared/test(a)mydomain.localdomain/Trash Shared/test(a)mydomain.localdomain/Spam INBOX But here comes the strange thing: telnet equal to Thunderbird: . LIST "" "*" * LIST (\HasNoChildren \Drafts) "/" Drafts * LIST (\HasNoChildren \Sent) "/" Sent * LIST (\HasNoChildren \Trash) "/" Trash * LIST (\HasNoChildren \Junk) "/" Spam * LIST (\Noselect \HasChildren) "/" Shared * LIST (\HasChildren) "/" Shared/test(a)mydomain.localdomain * LIST (\HasNoChildren) "/" Shared/test(a)mydomain.localdomain/Drafts * LIST (\HasNoChildren) "/" Shared/test(a)mydomain.localdomain/Sent * LIST (\HasNoChildren) "/" Shared/test(a)mydomain.localdomain/Trash * LIST (\HasNoChildren) "/" Shared/test(a)mydomain.localdomain/Spam * LIST (\HasNoChildren) "/" INBOX . OK List completed (0.000 + 0.000 + 0.092 secs). Public and Public/* shoul be listed as well, but it isn't. Any idea why it is behaving like this? Thanks Best regards Leander Schäfer

1 1

[patch] Improved error checking for the dovecot-antispam-plugin
by Robert Munteanu 30 Sep '16

30 Sep '16

Hi, Hopefully this is the right channel for such a patch. I have a minor enhancement to submit for the antispam plugin http://hg.dovecot.org/dovecot-antispam-plugin It adds minimal error checking for the sendmail_binary, otherwise the reported error in case of a missing binary or one with missing permissions is generic and not useful. Thanks, Robert -- http://robert.muntea.nu/

3 6

NFSv4 and Maildir
by Robert Blayzor 30 Sep '16

30 Sep '16

Recently moving to newer storage platforms for mailbox storage so looking at moving mounts from NFSv3 with lots of issues with locking and caching to NFSv4. There seems to be a lot of benefits to v4 along with some other new features, namely “delegation”. So the question boils down to, to delegate or not delegate on Maildir storage. There may be many reasons based on actual platform why to do (or not to do this), but I want to get the general opinion from others that may have more experience with this. Our setup is several FreeBSD 10.x clients running Dovecot/Exim, NetApp NFS mail storage (probably moving to TrueNAS) and using F5 load balancers for client side connections/SSL offload. From what I’ve found (and what i’ve read in the RFC) is that delegation seems to work best when there is NOT a lot of file contention from clients accessing the same files. I realize that in some situations many people are using director to try and keep users on the same client; in our case we’re doing it with F5 iRules. The F5 iRules work great for POP3 and IMAP session persistence, but unfortunately that doesn’t work for SMTP and Dovecot LDA, so we still have possible race conditions from the MTA’s delivering into “INBOX”. (mostly dovecot indexes updating at the same time). So the big question is, who is using Dovecot with maildirs with NFSv4 mounts. What has your experience been? Are you using delegation? By choice and why did you come to that decision. I’m drawing up the conclusion that if you can *mostly* control client control to specific files (ie: directing access to a mailbox to come from one client), then delegation might be ok. However, if you’re not using director and have several NFS mail clients racing to access mailboxes, then delegation might turn into chaos. Your comments welcome and appreciated. -- Robert inoc.net!rblayzor XMPP: rblayzor.AT.inoc.net PGP Key: 78BEDCE1 @ pgp.mit.edu

2 1

Re: Dovecot 2.2.25 fails on SSL
by Andreas M. Kirchwitz 30 Sep '16

30 Sep '16

Joseph Tam <jtam.home(a)gmail.com> wrote: >>> OK, the origin of your problem becomes clearer. You can hardcode these >>> paths into the executables by doing something like >>> >>> env CFLAGS='-I/my'ssl/include' \ >>> LDFLAGS='-L/your/ssl/lib -Wl,-rpath,/my/ssl/lib' \ >>> configure ... >> >> Based on your mail I've tried CFLAGS/LDFLAGS again, and >> now Dovecot didn't even compile any longer. > > I don't use the same OS as you, but what errors dis you get? To be exact here, it's not the compiler but the linker failing (of course, the whole problem is about the linking process). With "--as-needed", the crypto/ssl libraries are not linked at all with the object files. I don't quite understand why it doesn't fall back to the system crypto/ssl libraries because they are in the default pathes with all other libraries. (That's basically what most other software packages do if my custom pathes for "-L" "-Wl,-R" somehow get ignored in the building process.) IMHO, the unusual option "--as-needed" should be removed. There seems to be no benefit but it basically keeps Dovecot to be linked against any custom-specified library. Maybe it's just a problem with RHEL/CentOS 6 and the GCC that ships with it. I'm compiling a lot of software myself and link it against my custom OpenSSL. Never had this problem before, otherwise I would have known to specify "-Wl,--no-as-needed" to reverse ld's behavior to the default. Well, at least I've learned something new. :-) Regards, Andreas

2 1

Softlinks
by Chris 29 Sep '16

29 Sep '16

All, I'm using Maildir. Is it possible to move all (or only some) maildirs with softlinks to another partition? - Chris

2 2

Login just at special timeslots / working hours
by Götz Reinicke - IT Koordinator 29 Sep '16

29 Sep '16

Hi, is there a dovecot feature I did not found yet, which can limit the access to the server to special timeslots like working hours? Or is that a serverside / sssd / auth / pam / account feature? Thanks for hints to some helpfull documentation and sugesstions. Regards . Götz

4 4

dovecot is moving messages to spam
by Webert de Souza Lima 28 Sep '16

28 Sep '16

Hi, is there any dovecot rule settings besides X-Spam-Flag header? Can it move messages via IMAP? I have a message that is being moved to spam folder after delivered in the INBOX but it has no X-Spam-Flag and it's not beeing done by the user (I changed his password, suspended his account and made his login impossible). This happens only when certain "FROM" address is present in the body, like the following message (sent via telnet): From:<some.guy(a)some.domain> Subject: Test teste . Dovecot logs: Sep 28 13:08:00 lmtp(my.user(a)my.domain): Info: OOKlA3rA61dNbwAAkzG9Ng: sieve: msgid=unspecified: stored mail into mailbox 'INBOX' Sep 28 13:08:01 imap(my.user(a)my.domain): Info: copy from INBOX: box=INBOX.Spam, uid=154, msgid=, size=340, subject=Test Sep 28 13:08:01 imap(my.user(a)my.domain): Info: expunge: box=INBOX, uid=18147, msgid=, size=340, subject=Test Thanks in advance

3 4

FreeBSD port
by The Doctor 28 Sep '16

28 Sep '16

Is the person responsible for the FreeBSD port on this list? There might be a minor bug in a small piece of correction code issues in the last 4 days. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Time for the USA to hold a referendum on its republic and vote to dissolve!!

4 4

Dovecot Pro Community Edition
by Markus Petzsch 28 Sep '16

28 Sep '16

Hi, I'm trying to setup push notifications for Open-Xchange (OX) and struggle with finding the push_notification plugin. According to https://oxpedia.org/wiki/index.php?title=AppSuite:OX_Mail#Requirements it should be found in the Dovecot Pro Community Edition. I'm currently running dovecot that came with CentOS 7.2 but am intrested in OX's push feature. Can someone point me in the right direction where to find the community edition repos? https://oxpedia.org/wiki/index.php?title=Dovecot:Main_Page_Dovecot#dovecotq… only lists password protected repos. Thx for your help in advance. Best Regards Markus Petzsch

2 1

Trying to regain access to my email archive after an upgrade.
by Rick Jones 27 Sep '16

27 Sep '16

Hi - I had been running an Ubuntu 12.04 system on which I receive email, with an inbox in /var/mail/ and a bunch of folders under ~/Maildir. When I upgraded from 14.04 there were a bunch of questions about keeping old/new config files and my muddling through it has me seeing only the inbox, and then a Drafts, Sent and Trash Folder. I would like to regain access to the messages stored under ~/Maildir, but have been thoroughly unsuccessful. I seem to run into duplicate prefix issues and I suspect I have other issues, when I try to add: namespace rest { separator = / prefix = location = maildir:~/Maildir } to what is already present. I've seen a few of the wiki pages, but not fully understanding what is going-on I'm afraid I've not groked them terribly well. any help/pointers for this cluser would be much appreciated. rick jones raj@tardy:~$ dovecot --version 2.2.9 raj@tardy:~$ dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:25: 'imaps' protocol is no longer necessary, remove it doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:732: protocol managesieve {} has been replaced by protocol sieve { } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:904: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:942: passdb pam {} has been replaced by passdb { driver=pam } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1055: userdb passwd {} has been replaced by userdb { driver=passwd } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1117: auth_user has been replaced by service auth { user } # OS: Linux 3.13.0-95-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail 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 } passdb { driver = pam } protocols = imap service auth { user = root } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } raj@tardy:~$ vi /etc/dovecot/conf.d/15-mailboxes.conf raj@tardy:~$ dovecot --version 2.2.9

1 0

imapc fetch optimization
by Nagy, Attila 27 Sep '16

27 Sep '16

Hi, imapc does a lot of UID FETCH $UID (BODY.PEEK[]), which is nice, because it works even with the dumbest IMAP server, altough it really kills performance, especially on high latency lines. I wonder: if IMAP servers can effectively handle boundless fetches (like a list with all wanted UIDs, or simply 1:* if all are needed), do you see this as a good addition to develop? This could be a new imapc_features setting afterall... Thanks,

2 8

Drac Plugin
by Darryl Baker 27 Sep '16

27 Sep '16

I now have the drac plugin compiled and working. The plugin binary might even work with the Debian/Ubuntu binary. It was a one line change. I need to talk to the sendmail folks about their macro for the DRAC feature. My custom sendmail.cf code works in a way that makes using drac and SpamHaus for anyone on a blacklisted IP such as non-comercial Comcast users. I am hoping that the drac plugin will get fixed in the core distribution and possible the new binary make it into the Debian/Ubuntu binary build. *** dovecot-2.2.22/src/plugins/drac/drac-plugin.c 2016-09-23 22:49:56.345568783 -0500 --- dovecot-2.2.22/src/plugins/drac/drac-plugin.c-orig 2016-09-26 14:33:46.828670909 -0500 *************** *** 25,31 **** /* libdrac function */ int dracauth(char *, unsigned long, char **); ! const char *drac_plugin_version = DOVECOT_ABI_VERSION; static struct timeout *to_drac = NULL; static const char *drachost = NULL; /* dracd host */ --- 25,31 ---- /* libdrac function */ int dracauth(char *, unsigned long, char **); ! const char *drac_plugin_version = DOVECOT_VERSION; static struct timeout *to_drac = NULL; static const char *drachost = NULL; /* dracd host */ *Darryl Baker*

2 1

Re: Shared mailboxes nightmare (for me :-( )
by Felix Rubio 27 Sep '16

27 Sep '16

Hi KR, Just checked the folders, and they do not contain any of these subfolders. This is the structure I see: . ├── dovecot-acl-list ├── dovecot.list.index ├── dovecot.list.index.log ├── dovecot.list.index.log.2 ├── dovecot.mailbox.log ├── dovecot-uidvalidity ├── dovecot-uidvalidity.570e9b2d ├── mailboxes │ ├── folderB │ │ └── dbox-Mails │ │ ├── dovecot.index │ │ ├── dovecot.index.backup │ │ ├── dovecot.index.cache │ │ ├── dovecot.index.log │ │ └── dovecot.index.thread │ ├── dovecot-acl │ ├── folderA │ │ └── dbox-Mails │ │ ├── dovecot.index.cache │ │ └── dovecot.index.log │ ├── folderC │ │ └── dbox-Mails │ │ ├── dovecot.index │ │ ├── dovecot.index.backup │ │ ├── dovecot.index.cache │ │ └── dovecot.index.log │ ├── INBOX │ │ └── dbox-Mails │ │ ├── dovecot.index │ │ ├── dovecot.index.backup │ │ ├── dovecot.index.cache │ │ └── dovecot.index.log │ ├── Junk │ │ └── dbox-Mails │ │ └── dovecot.index.log │ ├── Sent │ │ └── dbox-Mails │ │ ├── dovecot.index.cache │ │ └── dovecot.index.log │ └── Trash │ └── dbox-Mails │ └── dovecot.index.log ├── sieve │ ├── dovecot.sieve │ ├── dovecot.svbin │ └── tmp ├── spamassassin │ ├── bayes.mutex │ ├── bayes_seen │ └── bayes_toks ├── storage │ ├── dovecot.map.index │ ├── dovecot.map.index.log │ ├── m.1 │ ├── m.10 │ ├── m.11 │ ├── m.12 │ ├── m.13 │ ├── m.14 │ ├── m.2 │ ├── m.3 │ ├── m.4 │ ├── m.5 │ ├── m.6 │ ├── m.7 │ ├── m.8 │ └── m.9 └── subscriptions Update: I have finally managed to see these folders in roundcube, after setting subscriptions=no (instead of yes) in the shared namespace. Also, I have been able to keep it working with the single dovecot-acl file I have inside mailboxes. Is this structure correct? I am asking becaus I have another user, for which I migrated the format to mdbox, for which I have these folders (curr, tmp, new) but also the structure I have for the shared :s. Are both formats mixed for that user? Thank you, Felix On 27 September 2016 00:25:40 CEST, "dovecot(a)avv.solutions" <dovecot(a)avv.solutions> wrote: >Quick thought: are the sub-folder structure complete? > >I mean, do they have their cur+new+tmp directories? > >With their rights ownership+permissions? > >KR > >On 09/26/2016 11:31 PM, Felix Rubio Dalmau wrote: >> Hi everybody, >> >> I am honestly desperate: I have spent/invested the whole day in >trying to set a shared mailbox, with quite partial success. The INBOX >is merged with the top level mailbox, and there are many more folders. >To give an idea, for the shared account sharedacc(a)domain.org, this is >how looks the folder structure: >> >> sharedacc >> |-folderA >> |-folderB >> \-folderC >> >> in the account for usera(a)domain.org, I see the following: >> >> usera >> |-folderD >> |-folderE >> |-folderF >> \-shared >> \-sharedacc >> >> So, I do not get to see folderA, folderB, folderC, etc. >> >> My configuration is: >> >> # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf >> # Pigeonhole version 0.4.14 (099a97c) >> # OS: Linux 4.5.4-0 x86_64 Debian stretch/sid zfs >> >> mail_plugins = zlib expire acl >> >> plugin { >> acl = vfile >> acl_shared_dict = proxy::acl >> } >> >> dict { >> acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext >> } >> >> namespace { >> list = children >> location = >mdbox:/mnt/vmail/%%d/%%n:INDEXPVT=/mnt/vmail/indexes/shared/%%d/%%n >> prefix = shared/%%n/ >> separator = / >> subscriptions = yes >> type = shared >> } >> >> protocol lmtp { >> mail_plugins = zlib expire acl sieve >> } >> >> protocol imap { >> mail_plugins = zlib expire acl antispam imap_acl >> } >> >> the files I have one the account for sharedacc are: >> sharedacc >> |-dovecot-acl >> |-dovecot-acl-list >> \-mailboxes >> |-dovecot-acl >> |-folderA >> | \-dbox-Mails >> | \-dovecot-acl >> |-folderB >> | \-dbox-Mails >> | \-dovecot-acl >> \-folderC >> \-dbox-Mails >> \-dovecot-acl >> >> In dovecot-acl-list I have the following contents: >> 1474920778 folderA >> 1474920778 folderB >> 1474920778 folderC >> >> and in every dovecot-acl, I have: >> user=usera(a)domain.org akxeilprwts >> >> All the files on the filesystem are owned by the same vmail user. >> What is strange is that I can see all these folderA, folderB, folderC >in roundcube, and I can click to subscribe to them. However, when I go >back to the general view, the subscriptions have been reset and I see >only sharedacc, without a thing inside. Finally, in kmail I can see the >subscribed folders without a problem (??!) >> >> Can please somebody help me? -- Sent from my phone. Please excuse my brevity. -- Sent from my phone. Please excuse my brevity.

1 0

Shared mailboxes nightmare (for me :-( )
by Felix Rubio Dalmau 27 Sep '16

27 Sep '16

Hi everybody, I am honestly desperate: I have spent/invested the whole day in trying to set a shared mailbox, with quite partial success. The INBOX is merged with the top level mailbox, and there are many more folders. To give an idea, for the shared account sharedacc(a)domain.org, this is how looks the folder structure: sharedacc |-folderA |-folderB \-folderC in the account for usera(a)domain.org, I see the following: usera |-folderD |-folderE |-folderF \-shared \-sharedacc So, I do not get to see folderA, folderB, folderC, etc. My configuration is: # 2.2.25 (7be1766): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.14 (099a97c) # OS: Linux 4.5.4-0 x86_64 Debian stretch/sid zfs mail_plugins = zlib expire acl plugin { acl = vfile acl_shared_dict = proxy::acl } dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } namespace { list = children location = mdbox:/mnt/vmail/%%d/%%n:INDEXPVT=/mnt/vmail/indexes/shared/%%d/%%n prefix = shared/%%n/ separator = / subscriptions = yes type = shared } protocol lmtp { mail_plugins = zlib expire acl sieve } protocol imap { mail_plugins = zlib expire acl antispam imap_acl } the files I have one the account for sharedacc are: sharedacc |-dovecot-acl |-dovecot-acl-list \-mailboxes |-dovecot-acl |-folderA | \-dbox-Mails | \-dovecot-acl |-folderB | \-dbox-Mails | \-dovecot-acl \-folderC \-dbox-Mails \-dovecot-acl In dovecot-acl-list I have the following contents: 1474920778 folderA 1474920778 folderB 1474920778 folderC and in every dovecot-acl, I have: user=usera(a)domain.org akxeilprwts All the files on the filesystem are owned by the same vmail user. What is strange is that I can see all these folderA, folderB, folderC in roundcube, and I can click to subscribe to them. However, when I go back to the general view, the subscriptions have been reset and I see only sharedacc, without a thing inside. Finally, in kmail I can see the subscribed folders without a problem (??!) Can please somebody help me?

1 0

Re: Self-Signed Certificate issue
by Joseph Tam 26 Sep '16

26 Sep '16

Darryl Baker writes: > I am running a small email site which I am moving from uw-imapd and Solaris > to Ubuntu and Dovecot imaps and pop3s. I am trying to use a self-signed > certificate for this site. I am using Thunderbird as the test client. I've > tried both the pre-built snakeoil certificate and building a special one > for dovecot. In /var/log/mail.err I keep getting what I am interpreting as > a missing CA cert. The message is: > > dovecot: imap-login: Error: SSL: Stacked error: error:14094418:SSL > routines:ssl3_read_bytes:tlsv1 alert unknown ca: SSL alert number 48 > > The certificate was created by: > > openssl req -new -x509 -days 365 -nodes -out /etc/ssl/certs/dovecot.pem > -keyout /etc/ssl/private/dovecot.pem Are you using this as a server certificate or as a client certificate? Please output your dovecot's configuration, esp. your SSL setup. doveconf -n | grep ssl Joseph Tam <jtam.home(a)gmail.com>

1 0

Setting hostdomain
by Arie Peterson 25 Sep '16

25 Sep '16

Hi all, Preparing for a replication setup, I read (at the bottom of <http://wiki2.dovecot.org/Replication>) that `dovecot --hostdomain` should give a different output on the two servers. This is not the case for me: both give "localhost". I'm trying to change my configuration to set the hostdomain to another value, but I can't find how to do this. I tried: • setting the environment variable DOVECOT_HOSTDOMAIN=mydomain in /etc/default/dovecot (which is read by the init script); • adding the line import_environment = TZ DOVECOT_HOSTDOMAIN=mydomain to dovecot.conf; • the combination of both of the above. However, after restarting dovecot none of these changes seem to have any effect: `dovecot --hostdomain` still returns "localhost". This is with dovecot version 2.2.13. How should one change this setting? Thanks, Arie

2 2

fail to compile with openssl-1.1.x
by A. Schulze 25 Sep '16

25 Sep '16

Hi again, now I get compile errors. Is openssl-1.1.xy supported? iostream-openssl.c: In function 'openssl_iostream_verify_client_cert': iostream-openssl.c:118:37: error: dereferencing pointer to incomplete type subject = X509_get_subject_name(ctx->current_cert); ^ iostream-openssl.c:127:37: error: dereferencing pointer to incomplete type X509_verify_cert_error_string(ctx->error), certname)); Andreas ^

2 1

configure fail if libssl is named libssl-opt
by A. Schulze 25 Sep '16

25 Sep '16

Hello, I try to build dovecot with my own version of openssl. It's compiled in a way the libraries can coexist without symbol conflict with the real OpenSSL in /usr: They are named libssl-opt and libcrypto-opt. Now configure fail to find my libssl-opt: CFLAGS="..." CXXFLAGS="..." CPPFLAGS="..." LDFLAGS="..." SSL_LIBS='-lssl-opt -lcrypto-opt' ./configure ... --with-ssl=openssl ... checking for SSL_read in -lssl... no configure: error: Can't build with OpenSSL: libssl not found Is there an other way to tell configure the ssl libraries have other names? Andreas

1 1