Typo in systemd commit HG 8dc79a437858
The apostrophes need to be removed from the LimitCORE example, otherwise the parameter will not be recognized: $ cat /etc/systemd/system/dovecot.service.d/service.conf [Service] #Environment='OPTIONS=-p' #LimitCORE=8192 LimitCORE=infinity signature.asc Description: Digital signature
Re: Typo in systemd commit HG 8dc79a437858
On 05/25/2015 06:14 AM, Thomas Leuxner wrote: The apostrophes need to be removed from the LimitCORE example, otherwise the parameter will not be recognized: $ cat /etc/systemd/system/dovecot.service.d/service.conf [Service] #Environment='OPTIONS=-p' #LimitCORE=8192 LimitCORE=infinity Oops, my bad. On my system i have (w/o drop-in files): ,--[ systemctl show --property=LimitCORE dovecot ]-- | LimitCORE=18446744073709551615 `-- But your message showed me just another typo. The setting name, for configuring the file descriptor limit, is LimitNOFILE - instead of LimitCORE. Stephan's next auto-build should contain the corrected version. Regards, Pascal -- The trapper recommends today: defaced.1514...@localdomain.org
Shared inbox?
I'm running dovecot 2.2.16 on my FreeBSD mail server. I've read information on the wiki about setting up shared mailboxes, but I want to do something that isn't really coved by the instructions I was reading there. My son (now 7 years old) has an account on the system, but doesn't use it directly. But, for things he's interested in like Minecraft, and/or the local zoo, we have given out his email address in a small number of places. What I would like to set up, both for now while he's not actually ever reading his email himself, and perhaps even for the future when we teach and/or allow for that, is for my wife and I to be able to view his inbox from our accounts. The instructions for setting up shared folders all are written so that they're secondary folders to all accounts. Is there a way to either (a) configure sharing someone elses Inbox by other accounts, or (b) setting up a separately configured shared folder to _act_ as the inbox for a single account? Thanks. Any suggestions to achieve the above described end goal would be appreciated. - Chris
Re: Typo in systemd commit HG 8dc79a437858
On Mon, 25 May 2015 15:50:08 + Pascal Volk user+dove...@localhost.localdomain.org wrote: On 05/25/2015 03:44 PM, Steve Litt wrote: Hey guys, please tell me that Dovecot does not depend on systemd! Nope, Dovecot doesn't depend on systemd. Why should it depend on systemd? I could ask the question why should it depend on systemd about a whole raft of programs that do depend on it. It's a mystery to me. Anyway, I'm glad that it doesn't. But: Dovecot supports systemd. If you want to enable systemd, use: ./configure --with-systemdsystemunitdir It sounds like the preceding is some sort of dohickey to enable Dovecot to more easily be started/managed by systemd. I hope that's all it is, and I hope it always remains voluntary, because installing systemd on my machine, the way I have it set up, would have all sorts of side effects. Anyway, in the near future I'll probably be managing Dovecot through Daemontools. Thanks for the explanation, SteveT Steve Litt May 2015 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz
Re: Typo in systemd commit HG 8dc79a437858
On Mon, 25 May 2015 08:14:41 +0200 Thomas Leuxner t...@leuxner.net wrote: The apostrophes need to be removed from the LimitCORE example, otherwise the parameter will not be recognized: $ cat /etc/systemd/system/dovecot.service.d/service.conf [Service] #Environment='OPTIONS=-p' #LimitCORE=8192 LimitCORE=infinity Hey guys, please tell me that Dovecot does not depend on systemd! SteveT Steve Litt May 2015 featured book: Quit Joblessness: Start Your Own Business http://www.troubleshooters.com/startbiz
Re: Typo in systemd commit HG 8dc79a437858
On 05/25/2015 03:44 PM, Steve Litt wrote: Hey guys, please tell me that Dovecot does not depend on systemd! Nope, Dovecot doesn't depend on systemd. Why should it depend on systemd? But: Dovecot supports systemd. If you want to enable systemd, use: ./configure --with-systemdsystemunitdir Regards, Pascal -- The trapper recommends today: beeffeed.1514...@localdomain.org
Re: timeout for POP3 query.
On 24 May 2015, at 10:34, Christian Eichert dove...@zp1.net wrote: Is there a way to timeout POP3 query if they come to often? More precise I want to know if there is a setting in dovecot that makes it ignore pop3 requests from a certain user if they come more often then a certain amount of time. I am looking for a setting in dovecot, not a firewall solution. I would like dovecot to answer something like requests come to often, please come back later. http://dovecot.org/patches/2.0/pop3-throttle-plugin.c may be useful for you. Although that was written for Dovecot v2.0 and it probably requires some changes to compile.
Re: Couldn't set transaction log view (seq 9..13)
Hi Timo, Thanks for your quick response, apologies for my slow one. Timo Sirainen t...@iki.fi writes: I'm using 2.2.13 on Debian stable, and I perform regular dsync backups. Typically if there is an error, dsync can recover from it the next time it is run, but I've been encountering a new error that doesn't seem to self-heal: # /usr/bin/dsync -u micah backup ssh -i /root/.ssh/id_rsa backmaildir@internal.example /usr/bin/dsync -u micah dsync-remote(micah): Error: /srv/maildirbackups/m/micah/daily.1/mailboxes/INBOX/dbox-Mails/dovecot.index: Couldn't set transaction log view (seq 9..13) dsync-remote(micah): Error: Failed to read transaction log for mailbox INBOX Re-running the dsync never fixes the issue. I'm happy to provide any additional information if so required to help track down this problem! Can you create a tarball of such mailbox directories that reproduces the problem? Probably this would work: - copy source and destination dboxes to /tmp/test/1 and /tmp/test/2 - delete all the mailboxes except INBOX I noticed an interesting bit of information doing this: the users that are having a problem have no dbox-Mails directory in their source mailboxes/INBOX directory - but on the destination where I am sending the backups, there is one. If I remove the backup's INBOX/ and then re-do the dsync, things work again. - delete all the u.* files from the INBOXes. This probably doesn't affect the dsync run - if it does run the mails instead through http://dovecot.org/tools/dbox-anonymize.pl I have no u.* files on either side. There are m.* files though? - delete dovecot.index.cache files - make sure you can still reproduce this error by running: doveadm -o mail=sdbox:/tmp/test/1 sync sdbox:/tmp/test/2 did you mean s/sdbox/mdbox/ here? also, I was using 'backup' and not sync, I dont know if that matters? I tried this with some that had issues, but I couldn't reproduce the error this way :p - tar czf test.tar.gz /tmp/test Then send the tarball to me and I can fix the bug. Oh, also it would be a good idea to test with a newer Dovecot version since there are some indexing fixes since v2.2.13.. I'm working on getting a newer version of dovecot installed to test this. Also I added some code that should give a better-debuggable error message if this happens: http://hg.dovecot.org/dovecot-2.2/rev/8146fdc0de34 great, this will certainly be helpful! micah
Segfault on doveadm sync -u an-specific-user tcp:other-node-ip:port
Hi! When I run doveadm sync -u an-specific-user tcp:192.168.0.2:12345, I get this error: http://pastebin.com/NxyyNGJk Only to one specific user... I've tried to repair with doveadm force-resync, unsuccessfully. Is this known? Ubuntu14.04 + Dovecot-2.2.15. My doveconf -n: http://pastebin.com/25sURwJL Thanks! -- Thiago Henrique
Re: Shared inbox?
May 25 2015 1:01 PM, Chris Ross cross+dove...@distal.com wrote: I'm running dovecot 2.2.16 on my FreeBSD mail server. I've read information on the wiki about setting up shared mailboxes, but I want to do something that isn't really coved by the instructions I was reading there. My son (now 7 years old) has an account on the system, but doesn't use it directly. But, for things he's interested in like Minecraft, and/or the local zoo, we have given out his email address in a small number of places. What I would like to set up, both for now while he's not actually ever reading his email himself, and perhaps even for the future when we teach and/or allow for that, is for my wife and I to be able to view his inbox from our accounts. The instructions for setting up shared folders all are written so that they're secondary folders to all accounts. Is there a way to either (a) configure sharing someone elses Inbox by other accounts, or (b) setting up a separately configured shared folder to _act_ as the inbox for a single account? Thanks. Any suggestions to achieve the above described end goal would be appreciated. - Chris I'll assume you've seen these: http://wiki2.dovecot.org/SharedMailboxes/Shared and http://wiki2.dovecot.org/ACL When I set them up that way, I shared the target inbox (we'll call it f...@example.com) to be accessible by user b...@example.com. When I go into my email client, I'll see something like: shared/f...@example.com/INBOX as a folder. To give bar@ access to foo@'s INBOX, I ran something like this: doveadm acl add \ -u f...@example.com \ INBOX user=b...@example.com \ lookup read write write-seen write-deleted insert\ post expunge create delete admin http://wiki2.dovecot.org/Tools/Doveadm/ACL covers the details of what all of the lookup read... bits and more do. The boxes don't have to be shared publicly if you use the private namespace. Hopefully that helps! Cheers, Drew Csillag
Creating IMAP folders/subfolders with Thunderbird
Hi, I have dovecot-2.2.15 on fedora21 with Thunderbird and having some difficulty creating subfolders and deleting folders. Creating subfolders results in a folder at the root with a caret instead of a slash called folder^subfolder with an entry in .subscriptions with that name, instead of a new folder under the directory. I'm also unable to delete any folders. The command from within Thunderbird is just completely ignored. Any idea what's happening here? Thanks, Alex