Disable SIS
Hi, I'm currently running a small home-server with Dovecot. A long time ago I configured it with SIS enabled. I would like to stop using SIS. If I remove sis from mail_attachment_fs will the old mails that are stored in SIS-storage still be accessible? How can I convert all mailboxes to stop using SIS and store attachments back in the mails? Rgds, N.
Re: Disable SIS
On 14 Mar 2018, 20:42 +0100, Aki Tuomi , wrote: > > > On 14 March 2018 at 21:17 Nick Rosier < nick+dove...@bunbun.be> wrote: > > > > > > Hi, > > > > I'm currently running a small home-server with Dovecot. A long time ago > > I configured it with SIS enabled. I would like to stop using SIS. > > > > If I remove sis from mail_attachment_fs will the old mails that are > > stored in SIS-storage still be accessible? > > How can I convert all mailboxes to stop using SIS and store attachments > > back in the mails? > > > > Rgds, > > N. > > doveadm backup -u username maildir:/tmp/Maildir > > and then you can convert it back to sdbox after disabling sis by clearing the > existing dbox files and running > > doveadm -omail_location=maildir:/tmp/Maildir backup -u username > sdbox:~/something > > remember to take backups Thanks for the quick response. I’ve tried a backup on 1 mailbox and indeed it stores the mails with attachments. I had tried it as an sdbox backup with the option to disable SIS but that didn’t seem to work. Does anybody know if disabling SIS in the current setup will stop saving attachments to SIS but keep reading those that are already stored there? N.
Re: Disable SIS
On 14 Mar 2018, 21:06 +0100, Tanstaafl , wrote: > On Wed Mar 14 2018 15:17:58 GMT-0400 (Eastern Standard Time), Nick > Rosier wrote: > > I'm currently running a small home-server with Dovecot. A long time ago > > I configured it with SIS enabled. I would like to stop using SIS. > > > > If I remove sis from mail_attachment_fs will the old mails that are > > stored in SIS-storage still be accessible? > > How can I convert all mailboxes to stop using SIS and store attachments > > back in the mails? > > As one who used Dovecot years ago without SIS (it still wasn't well > baked) but was very interested in it, I'm curious why you want to stop > using it? I like experimenting with new technology and I liked the idea of SIS. I still think it is but I really don’t need it for the small mail-server I’m running and it adds a lot of complexity to the setup. There’s also AFAIK no tools to verify integrity or clean-up the SIS. So I’d like to go back to a simple storage solution.
Re: Disable SIS
On 15 Mar 2018, 09:43 +0100, Aki Tuomi , wrote: > > > On 15.03.2018 10:40, Nick Rosier wrote: > > On 14 Mar 2018, 20:42 +0100, Aki Tuomi , wrote: > > > > > > > > > On 14 March 2018 at 21:17 Nick Rosier < nick+dove...@bunbun.be> wrote: > > > > > > > > > > > > Hi, > > > > > > > > I'm currently running a small home-server with Dovecot. A long time ago > > > > I configured it with SIS enabled. I would like to stop using SIS. > > > > > > > > If I remove sis from mail_attachment_fs will the old mails that are > > > > stored in SIS-storage still be accessible? > > > > How can I convert all mailboxes to stop using SIS and store attachments > > > > back in the mails? > > > > > > > > Rgds, > > > > N. > > > > > > doveadm backup -u username maildir:/tmp/Maildir > > > > > > and then you can convert it back to sdbox after disabling sis by clearing > > > the existing dbox files and running > > > > > > doveadm -omail_location=maildir:/tmp/Maildir backup -u username > > > sdbox:~/something > > > > > > remember to take backups > > > > > > Thanks for the quick response. I’ve tried a backup on 1 mailbox and indeed > > it stores the mails with attachments. I had tried it as an sdbox backup > > with the option to disable SIS but that didn’t seem to work. > > > > Does anybody know if disabling SIS in the current setup will stop saving > > attachments to SIS but keep reading those that are already stored there? > > > > N. > It will prevent you from reading the mails completely. That’s what I was afraid of. That means I need to convert all mailboxes all at once. I had hoped I could disable SIS and migrate 1 mailbox at a time. N.
Re: fts_lucene error
On 2015-05-17 17:45, Marcus Rueckert wrote: On Sun, 17 May 2015 17:29:54 +0200 Hanns Mattes wrote: lmtp(r...@bruecko.de): Error: Couldn't load required plugin /usr/lib64/dovecot/modules/lib21_fts_lucene_plugin.so: dlopen() failed: /usr/lib64/dovecot/modules/lib21_fts_lucene_plugin.so: undefined symbol: _ZN6lucene8analysis8snowball16SnowballAnalyzerC1EPFiPKvmP6bufferEPKc I asked Timo about it already on irc but no answer yet. could be related to enabling textcat support, which might have indirectly turn on some libstemmer code. I can confirm: got the same error when enabling textcat support on the latest FreeBSD-port of dovecot. After disabling it, FTS lucene worked again. Rgds, N.
doveadm index panic
Hi, running dovecot 2.2.18. when I try to re-index my INBOX I get following error: # doveadm index -u u...@domain.com INBOX doveadm(u...@domain.com): Warning: I/O leak: 0x80101ada0 (line 120, fd 15) doveadm(u...@domain.com): Warning: Timeout leak: 0x801019fe0 (line 325) doveadm(u...@domain.com): Panic: file ioloop.c: line 39 (io_add_file): assertion failed: (callback != NULL) zsh: abort doveadm index -u u...@domain.com INBOX Any ideas? Rgds, N.
Re: doveadm index panic
On 2015-05-19 11:44, Nick Rosier wrote:
Hi,
running dovecot 2.2.18. when I try to re-index my INBOX I get following
error:
# doveadm index -u u...@domain.com INBOX
doveadm(u...@domain.com): Warning: I/O leak: 0x80101ada0 (line 120, fd
15)
doveadm(u...@domain.com): Warning: Timeout leak: 0x801019fe0 (line 325)
doveadm(u...@domain.com): Panic: file ioloop.c: line 39 (io_add_file):
assertion failed: (callback != NULL)
zsh: abort doveadm index -u u...@domain.com INBOX
Doesn't seem to be limited to running the indexer manually:
2015-05-19T13:08:21.825235+02:00 mail dovecot:
indexer-worker(u...@domain.com): Warning: I/O leak: 0x10b80da0 (line
120, fd 20)
2015-05-19T13:08:21.825253+02:00 mail dovecot:
indexer-worker(u...@domain.com): Warning: Timeout leak: 0x10b7ffe0 (line
325)
2015-05-19T13:08:22.853198+02:00 mail dovecot:
indexer-worker(u...@domain.com): Panic: file ioloop.c: line 39
(io_add_file): assertion failed: (callback != NULL)
2015-05-19T13:08:22.853325+02:00 mail dovecot: indexer: Error: Indexer
worker disconnected, discarding 1 requests for u...@domain.com
2015-05-19T13:08:22.853367+02:00 mail dovecot: imap(u...@domain.com):
Error: indexer failed to index mailbox INBOX
2015-05-19T13:08:22.854205+02:00 mail dovecot:
indexer-worker(u...@domain.com): Fatal: master: service(indexer-worker):
child 42599 killed with signal 6 (core not dumped - set service
indexer-worker { drop_priv_before_exec=yes })
Never seen this before. Don't know if it's related but I just switched
from fts_lucene to fts_solr.
Rgds,
N.
fts_solr Bad Request / BUG: Unknown internal error
Hi, yesterday I created a new mailbox; ever since (and only for the new mailbox) I am getting these errors: 2015-06-12T00:00:29.808526+02:00 mail dovecot: indexer-worker(x...@example.com): Error: fts_solr: Lookup failed: Bad Request 2015-06-12T00:00:29.808560+02:00 mail dovecot: indexer-worker(x...@example.com): Error: Mailbox INBOX: Status lookup failed: BUG: Unknown internal error Is this a known issue? Rgds, N.
doveadm index assertion failed
Hi, one of my mailboxes returns following error when I run doveadm index on it: Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) OS: FreeBSD 10.2 Dovecot: 2.1.19 Tika: 1.10 SOLR: 5.3.1 Running doveadm -D index does not show any more information indicating what causes this error (mail/folder/...) How I can find what is causing this error? Rgds, N.
Re: doveadm index assertion failed
Timo Sirainen wrote: On 05 Oct 2015, at 22:05, Nick Rosier wrote: Hi, one of my mailboxes returns following error when I run doveadm index on it: Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft<= CHARSET_MAX_PENDING_BUF_SIZE) OS: FreeBSD 10.2 Dovecot: 2.1.19 Tika: 1.10 SOLR: 5.3.1 I thought this would have definitely been fixed by now.. Can you find some specific email which is triggering this? It's either something strange that I didn't expect, or it's a bug in FreeBSD's iconv(). Also can you debug this like: gdb --args doveadm index -u user@domain INBOX run f 5 p src p ic_srcbuf p *src_size p srcleft I recompiled Dovecot with Debug but I suspect I will have to do it for all the required libraries as well; I did manage to find the offending message is in Trash but have not been able to pin-point which message it is. Just in case, here is the debugging info. I will see if I can compile all dependencies in debug mode as well. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... (gdb) run Starting program: /usr/local/bin/doveadm index -u @ Trash doveadm(@): Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) Program received signal SIGABRT, Aborted. 0x00080149f64a in thr_kill () from /lib/libc.so.7 (gdb) f 5 #5 0x000801143cd3 in i_panic (format=0x801191c30 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 275 failures.c: No such file or directory. in failures.c Current language: auto; currently minimal (gdb) p src No symbol "src" in current context. (gdb) p ic_srcbuf No symbol "ic_srcbuf" in current context. (gdb) p *src_size No symbol "src_size" in current context. (gdb) p srcleft No symbol "srcleft" in current context.
Re: doveadm index assertion failed
Nick Rosier schreef: Timo Sirainen wrote: On 05 Oct 2015, at 22:05, Nick Rosier wrote: Hi, one of my mailboxes returns following error when I run doveadm index on it: Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft<= CHARSET_MAX_PENDING_BUF_SIZE) OS: FreeBSD 10.2 Dovecot: 2.1.19 Tika: 1.10 SOLR: 5.3.1 I thought this would have definitely been fixed by now.. Can you find some specific email which is triggering this? It's either something strange that I didn't expect, or it's a bug in FreeBSD's iconv(). Also can you debug this like: gdb --args doveadm index -u user@domain INBOX run f 5 p src p ic_srcbuf p *src_size p srcleft I recompiled Dovecot with Debug but I suspect I will have to do it for all the required libraries as well; I did manage to find the offending message is in Trash but have not been able to pin-point which message it is. Just in case, here is the debugging info. I will see if I can compile all dependencies in debug mode as well. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... (gdb) run Starting program: /usr/local/bin/doveadm index -u @ Trash doveadm(@): Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) Program received signal SIGABRT, Aborted. 0x00080149f64a in thr_kill () from /lib/libc.so.7 (gdb) f 5 #5 0x000801143cd3 in i_panic (format=0x801191c30 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:275 275 failures.c: No such file or directory. in failures.c Current language: auto; currently minimal (gdb) p src No symbol "src" in current context. (gdb) p ic_srcbuf No symbol "ic_srcbuf" in current context. (gdb) p *src_size No symbol "src_size" in current context. (gdb) p srcleft No symbol "srcleft" in current context. recompiled dovecot + all dependencies with debug but I get the same output. anything else I can try?
Re: doveadm index assertion failed
Timo Sirainen wrote: > On 16 Oct 2015, at 23:44, Nick Rosier wrote: >>> gdb --args doveadm index -u user@domain INBOX >>> run >>> >>> f 5 >>> p src >>> p ic_srcbuf >>> p *src_size >>> p srcleft >> I recompiled Dovecot with Debug but I suspect I will have to do it for all >> the required libraries as well; I did manage to find the offending message >> is in Trash but have not been able to pin-point which message it is. Just in >> case, here is the debugging info. I will see if I can compile all >> dependencies in debug mode as well. >> >> Program received signal SIGABRT, Aborted. >> 0x00080149f64a in thr_kill () from /lib/libc.so.7 >> (gdb) f 5 >> #5 0x000801143cd3 in i_panic (format=0x801191c30 "file %s: line %d >> (%s): assertion failed: (%s)") at failures.c:275 > > I guessed the frame wrong. It's usually 5, but I guess in FreeBSD it's 6 > then. So try the same commands, but "f 6" first before "f 5" (and if that > doesn't work either, try f 7). Indeed Timo, this provides more info. Hope this helps to track down the bug. GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "amd64-marcel-freebsd"... (gdb) run Starting program: /usr/local/bin/doveadm index -u x...@xxx.xxx Trash doveadm(rob...@rkfomh.net): Panic: file charset-iconv.c: line 85 (charset_to_utf8_try): assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE) Program received signal SIGABRT, Aborted. 0x00080149f64a in thr_kill () from /lib/libc.so.7 (gdb) f 6 #6 0x000801138c2c in charset_to_utf8_try (t=0x6d0360, src=0x7e7cd6 "Your message\n\n From:+AAkAIgQgBEMEOgQ+BDIEPgQ0BDgEQgQ1BDsETAA- +BDgEPQREBD4EQAQ8BDAERgQ4BD4EPQQ9BD4EMwQ+AA- +BEYENQQ9BEIEQAQwACIA- \n\n To:+aaka-...@clasinfo.com\n\n Subj:+AAkEGgQwBDQEM"..., src_size=0x7fffdf18, dest=0x788680, result=0x7fffdf2c) at charset-iconv.c:85 85 charset-iconv.c: No such file or directory. in charset-iconv.c Current language: auto; currently minimal (gdb) p src $1 = ( const unsigned char *) 0x7e7cd6 "Your message\n\n From:+AAkAIgQgBEMEOgQ+BDIEPgQ0BDgEQgQ1BDsETAA- +BDgEPQREBD4EQAQ8BDAERgQ4BD4EPQQ9BD4EMwQ+AA- +BEYENQQ9BEIEQAQwACIA- \n\n To:+aaka-...@clasinfo.com\n\n Subj:+AAkEGgQwBDQEM"... (gdb) p ic_srcbuf $2 = 0x7e7d11 "A- +BDgEPQREBD4EQAQ8BDAERgQ4BD4EPQQ9BD4EMwQ+AA- +BEYENQQ9BEIEQAQwACIA- \n\n To:+aaka-...@clasinfo.com\n\n Subj:+AAkEGgQwBDQEMARBBEIEQAQ+BDIESwQ5AA- +BEMERwQ1BEIA-\n Sent:+AAkA-2012-06-1"... (gdb) p *src_size $3 = 901 (gdb) p srcleft $4 = 842 (gdb)
Re: Compile error Dovecot2-pigeonhole
Maximus wrote: FreeBSD 9.3 Dovecot 2.25 (7be1766) I'm trying to install Dovecot2-pigeonhole-0.4.14_2 from ports. Get an error: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" With options MAKE_JOBS_UNSAFE=yes: cc1: error: unrecognized command line option "-Wno-duplicate-decl-specifier" I was trying to compile from sources. Same error. Any suggestions? Latest build from port works fine for me. Build everything with poudriere but doubt that has anything to do with it. build started at Wed Jul 6 22:30:30 CEST 2016 port directory: /usr/ports/mail/dovecot2-pigeonhole building for: FreeBSD FreeBSD-10-default-job-02 10.3-RELEASE-p5 FreeBSD 10.3-RELEASE-p5 amd64 maintained by: l...@lerctr.org Makefile ident: $FreeBSD: head/mail/dovecot2-pigeonhole/Makefile 418095 2016-07-05 17:06:52Z adamw $ Poudriere version: 3.1.14 Part from build-log: /bin/sh ../../../libtool --tag=CC--mode=compile cc -DHAVE_CONFIG_H -I. -I../../.. -I/usr/local/include/dovecot -DMODULEDIR=\""/usr/local/lib/dovecot"\"-std=gnu99 -O2 -pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast *-Wno-duplicate-decl-specifier* -Wstrict-aliasing=2 -I/usr/local/include -I../../.. -MT edit-mail.lo -MD -MP -MF .deps/edit-mail.Tpo -c -o edit-mail.lo edit-mail.c libtool: compile: cc -DHAVE_CONFIG_H -I. -I../../.. -I/usr/local/include/dovecot -DMODULEDIR=\"/usr/local/lib/dovecot\" -std=gnu99 -O2 -pipe -DLIBICONV_PLUG -fstack-protector -fno-strict-aliasing -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast *-Wno-duplicate-decl-specifier* -Wstrict-aliasing=2 -I/usr/local/include -I../../.. -MT edit-mail.lo -MD -MP -MF .deps/edit-mail.Tpo -c edit-mail.c -fPIC -DPIC -o .libs/edit-mail.o I'm building with standard CC (clang): FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 Target: x86_64-unknown-freebsd10.3 Thread model: posix Are you using GCC? If so, why??? Rgds, N.
[Dovecot] Dovecot-Antispam 2.0 with SpamAssassin (sa-learn)
Hi, has anyone figured out how to use the dovecot-antispam plugin with sa-learn? I need to pass the username (u...@domain.tld) to sa-learn and --ham or --spam depending on the move. I was thinking of using the CRM14 option and replace the command and arguments but cannot find anything about the ability to pass the username. Any pointers would be welcome. N.
Re: [Dovecot] Dovecot-Antispam 2.0 with SpamAssassin (sa-learn)
Tom Hendrikx wrote: On 17/08/11 08:26, Nikita Koshikov wrote: On Tue, 16 Aug 2011 22:38:34 +0200 Nick Rosier wrote: Hi, has anyone figured out how to use the dovecot-antispam plugin with sa-learn? I need to pass the username (u...@domain.tld) to sa-learn and --ham or --spam depending on the move. I was thinking of using the CRM14 option and replace the command and arguments but cannot find anything about the ability to pass the username. Any pointers would be welcome. N. Write a wrapper on sa-learn. The script should parse env first and that exec learning with appropriative args, like: antispam_mail_sendmail = /etc/dovecot/plugins/spam.sh Scrip, something like: #!/bin/bash ( env> /tmp/antispam.$$ /usr/bin/sa-learn $@ exit 0 ) search for PWD environment in /tmp/antispam.$$ . I use the dspam backend and pass the user into the commandline with %u, which seems to work, but is not documented in the man page. To be clear, this is with the plugin from: http://wiki2.dovecot.org/Plugins/Antispam I've currently got it working with the MailTrain backend. Might consider reconfiguring it to dspam backend as I need to do some ENV parsing to get the user. Using %u as argument to pass to the wrapper would be easier but I couldn't find anything in de documentation as you said. N.
Re: [Dovecot] Multiple domains to one inbox and temporary redirects...
Simon Brereton wrote:
Hi
Can anyone point me to a howto to arrange for multiple domains to deliver to
one inbox with Dovecot? For example, us...@example.com and us...@example.net
should both be delivered to /var/spool/mail/virtual/example.net/user1
Currently, I have the dovecot LDA set as:
dovecot unix - n n - - pipe
flags=DRhu user=mailsystem argv=/usr/lib/dovecot/deliver -f ${sender} -d
${user}@${nexthop}
and in dovecot.conf:
mail_location: maildir:/var/spool/mail/virtual/%d/%n
For some domains only, I need to override that mail_location.
Related to that, when user1 leave and user2 would like to receive user1's
email, how can I get it so that email to us...@example.com is delivered to
us...@example.com? Previously when I was using Postfix to deliver the mails, I
could change the maildirloc in the DB - but I’m not sure how to accomplish this
with dovecot LDA.
I'm using Postfixadmin to manage users and have server alias-domains.
All mail sent to an alias-domain is delivered to the other domain. Quite
easy if you've got postfixadmin already setup.
Otherwise I think you could configure virtual_alias_maps in postfix to
something like hash:virtual_domains
virtual_domains:
@example.net@example.com
N.
Re: [Dovecot] Thunderbird caching problem
Chris Cappuccio wrote: Dave McGuire [mcgu...@neurotica.com] wrote: On 08/31/2011 02:59 PM, Chris Cappuccio wrote: Using a fairly simple dovecot config (which obviously needs some max limit tweaking) we have problems with IMAP synchronization between thunderbird clients. Two TB clients in the same IMAP mailbox will, from time to time, show different views of the same INBOX folders, when TB caching is enabled. The only fix is to right-click on the folder, go to "Properties" and use the "Repair Folder" option which repairs the local TB .msf cache file. Is there any server-side fix/workaround that would keep TB from regularly going out-of-sync ? This happens with TB3 and newer versions, in concert with either dovecot 1 or 2. I ran into exactly this problem as well, it is infuriating. A workaround was discussed here awhile back. Sticking this in the "protocol imap" block of dovecot.conf solved the problem completely: imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDP LUS LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS Interesting..How do I know that I really should be announcing all of these capabilities given my current dovecot version and config? With the config I posted, here's what I send out now * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Blahfart This is before login, you need to verify after login. Dovecot changes the capabilities it advertises after login. Remove CONDSTORE and QRESYNC; the CONDSTORE is the one messing it up for you. QRESYNC also implies CONDSTORE so you need to disable this one as well. N.
Re: [Dovecot] mail spool filesystem
Kelsey Cummings wrote: On Fri, Aug 19, 2011 at 03:48:00AM -0500, Stan Hoeppner wrote: On 8/17/2011 9:42 AM, Adrian Ulrich wrote: I read that XFS is a good choice, but is not too reliable... Are you using Maildir or MBOX? In any case: XFS would be my last choice: XFS is nice if you are working with large files (> 2GB), but for E-Mail i'd stick with ext3 (or maybe even reiser3) as it works very well with small files. XFS was designed for parallelism, whether with large files or small, ... Anyone been using ZFS on FreeBSD for mail spool storage? I'm using ZFS on FreeBSD 8.2. But to be honest, this is a personal/private mail-system with limited mailboxes. I really like the snapshots in ZFS. Every night I make a snapshot which I send to another server for backup. Every hour I make a new snapshot from which I send the incremental to the backup-server. That way if the worst happens I will only loose 1 hour of mail. ZFS was built for data integrity, not speed so if it's speed you are looking for this might not be the fastest but maybe fast enough. N.
Re: [Dovecot] What best decision to make for flatfiles or SQL when I use Dovecot2 + Postfix together?
Tom Hendrikx wrote: On 27/09/11 17:51, terryjames9...@mm.st wrote: Hello, I'm moving my mail server from Exchange to an opensource one. After a bunch of reading, I decided on building a Dovecot2 + Postfix server in a VirtualUsers-only + Multiple-domains configuration. Since my messages will be stored by Dovecot, and the documentation is really good, I figured that it's smartest to configure Dovecot, then make Postfix 'fit' to it, sharing the data files that way. I read through lots of the Dovecot wiki for v2. There are many ways for storing the database data. My goal is to only have data in one instances, used by both Postfix& Dovecot. I'm a little confused about: to do that sharing-in-one-place, do I have to use SQL or can I use the flatfiles like passwd-db? I think for sure someone already decided the best approach for this, and maybe I'm not understanding the logic to it. The data I think I need to share are: users (u...@domain.com) passwords user aliases (mapping us...@domain.com -> us...@domain.com) domains domain aliases (domain.com also receives email for domain2.com) And I think all of this can be in passwd-db in Dovecot. But I also want to make sure that Postfix ONLY accepts email for users/domains that exist, so it has to read that data too. Can I do this that way with the flatfiles? Or do I have to use the SQL approach? The problem with passwd(like) files is that they are almost never in the correct format to fit both daemons. The easiest way to use a database. You could check out postfixadmin: it contains the database format you need, the documentation to hook postfix and dovecot into it, and a nice web gui for administrating the list of domains, aliases, mailboxes, passwords, etc etc. +1 one on PostfixAdmin. Wouldn't want to live without it. The main advantage of using a DB is that all information is stored in 1 location and available in the right format through SQL-queries. My 1st config used flat-files and the biggest issue was keeping the different files in sync (i.e. when creating/deleting users making sure to update all the necessary files). My main concern was losing mails if the DB is unavailable but this isn't a problem; if the DB is unavailable Postfix will return a temporarily unavailable and the MTA should retry. Rgds, N.
Re: [Dovecot] What best decision to make for flatfiles or SQL when I use Dovecot2 + Postfix together?
terryjames9...@mm.st wrote: Hello Nick, On Tuesday, September 27, 2011 9:47 PM, "Nick Rosier" wrote: +1 one on PostfixAdmin. Wouldn't want to live without it. The main advantage of using a DB is that all information is stored in 1 location and available in the right format through SQL-queries. My 1st config used flat-files and the biggest issue was keeping the different files in sync (i.e. when creating/deleting users making sure to update all the necessary files). Did you try that system with flatfiles in Dovecot v2 or v1? I think that this instructed possibility, http://wiki2.dovecot.org/HowTo/VirtualUserFlatFilesPostfix, is only for v2? This was back with v1. It was working with a little script I wrote. A problem was delegating management of all the domains. My servers hosts a number of domains which are owned by different people (family+friends). With PostfixAdmin you can define which user administers which domains (another perk). Its that sync of the different files that I hope to avoid. If I can with flatfiles, all the better. If not then maybe I will have to use SQL. And then the Postfix Admin looks interesting. An additional advantage I found with PostfixAdmin is the possibility to run post-creation/editing/deleting scripts on mailboxes and domains. I'm using Amavisd-new and have the post-creation script create users in the Amavis-DB with e.g. the default policies for a user and populating some tables used by other tools (quarReminder etc...). Rgds, N. PS: my mailserver only hosts a couple of domains and less than 100 mailboxes. I could have done this with flat-files but the possibility to delegate mailbox creation/deletion to the domain owners was worth the "trouble" using a DB which I was using anyway for other services.
Re: [Dovecot] Strange error: DIGEST-MD5 mechanism can't be supported with given passdbs
Yubao Liu wrote:
> Hi all,
>
> I have no idea about that message, here is my configuration, what's wrong?
You have 2 passdb entries; 1 with a file and 1 with pam. I'm pretty sure
PAM doesn't support DIGEST-MD5 authentication. Could be the cause of the
problem.
> Debian testing, Dovecot 2.0.15
>
> $ doveconf -n
> # 2.0.15: /etc/dovecot/dovecot.conf
> # OS: Linux 3.1.0-1-686-pae i686 Debian wheezy/sid
> auth_default_realm = corp.example.com
> auth_krb5_keytab = /etc/dovecot.keytab
> auth_master_user_separator = *
> auth_mechanisms = gssapi digest-md5
> auth_realms = corp.example.com
> auth_username_format = %n
> first_valid_gid = 1000
> first_valid_uid = 1000
> mail_location = mdbox:/srv/mail/%u/Mail
> 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
> passdb {
> args = /etc/dovecot/master-users
> driver = passwd-file
> master = yes
> pass = yes
> }
> passdb {
> driver = pam
> }
> plugin {
> sieve = /srv/mail/%u/.dovecot.sieve
> sieve_dir = /srv/mail/%u/sieve
> }
> protocols = " imap lmtp sieve"
> service auth {
> unix_listener auth-client {
> group = Debian-exim
> mode = 0660
> }
> }
> ssl_cert = ssl_key = userdb {
> args = home=/srv/mail/%u
> driver = passwd
> }
> protocol lmtp {
> mail_plugins = " sieve"
> }
> protocol lda {
> mail_plugins = " sieve"
> }
>
> # cat /etc/dovecot/master-users
> x...@corp.example.com:
>
> The z is obtained by "doveadm pw -s digest-md5 -u
> x...@corp.example.com",
> I tried to add prefix "{DIGEST-MD5}" before the generated hash and/or add
> "scheme=DIGEST-MD5" to the passwd-file passdb's "args" option, both
> don't help.
>
> The error message:
> dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled)
> dovecot: auth: Fatal: DIGEST-MD5 mechanism can't be supported with given
> passdbs
> gold dovecot: master: Error: service(auth): command startup failed,
> throttling
>
> I opened debug auth log, it showed dovecot read /etc/dovecot/master-users
> and parsed one line, then the error occurred. Doesn't passwd-file
> passdb support
> digest-md5 password scheme? If it doesn't support, how do I configure
> digest-md5 auth
> mechanism with digest-md5 password scheme for virtual users?
>
> Regards,
> Yubao Liu
>
Rgds,
N.
Re: [Dovecot] Deduplication active - but how good does it perform?
Ralf Hildebrandt wrote: > I have deduplication active in my first mdbox: type mailbox, but how > do I find out how well the deduplication works? Is there a way of > finding out how much disk space I saved (if I saved some :) )? You could check how much diskspace all the mail uses (or the mail of a user) and compare it to the quota dovecot reports. But I think you would need quota's activated for this. E.g. on my small server used diskquota is 2GB where doveadm quota reports all users use 3.1GB.
Re: [Dovecot] Failed build with lucene plugin
Veniamin Gvozdikov wrote:
Hi,
I've tryed build dovecot with the lucene plugin but I have this is output:
/bin/sh ../../../libtool --tag=CXX--mode=compile c++
-DHAVE_CONFIG_H -I. -I../../.. -I../../../src/lib
-I../../../src/lib-mail -I../../../src/lib-index
-I../../../src/lib-storage -I../../../src/plugins/fts
-I../../../src/doveadm -I/usr/local/include -I/usr/local/lib -O2
-pipe -fno-strict-aliasing -MT lucene-wrapper.lo -MD -MP -MF
.deps/lucene-wrapper.Tpo -c -o lucene-wrapper.lo lucene-wrapper.cc
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../../..
-I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-index
-I../../../src/lib-storage -I../../../src/plugins/fts
-I../../../src/doveadm -I/usr/local/include -I/usr/local/lib -O2 -pipe
-fno-strict-aliasing -MT lucene-wrapper.lo -MD -MP -MF
.deps/lucene-wrapper.Tpo -c lucene-wrapper.cc -fPIC -DPIC -o
.libs/lucene-wrapper.o
Assembler messages:
FATAL: can't create .libs/lucene-wrapper.o: Permission denied
lucene-wrapper.cc:24:36: error: CLucene/util/CLStreams.h: No such file
or directory
lucene-wrapper.cc:25:45: error: CLucene/search/MultiPhraseQuery.h: No
such file or directory
In file included from lucene-wrapper.cc:26:
SnowballAnalyzer.h:12: error: expected constructor, destructor, or
type conversion before '(' token
*** Error code 1
1 error
*** Error code 1
1 error
*** Error code 1
1 error
*** Error code 1
1 error
Which platform/OS are you trying to compile on? Which version of
CLucene? You need at version 2.3.3.4 (not 0.9) as stated on the Wiki
(http://wiki2.dovecot.org/Plugins/FTS/Lucene)
N.
Re: [Dovecot] Failed build with lucene plugin
Veniamin Gvozdikov wrote:
Thank you. I'm using the FreeBSD, and clucene is 0.9. Now I'm try
compile 2.3.3.4 which's fails now, and then I'll try build the dovecot
with lucene plugin.
You need to compile CLucene 2.3.3.4 with Clang. I've also tried with the
FreeBSD included compiler but it fails. The recent addition of
SOLR-support to the dovecot2 port was made by and at the request of me.
I would like to add lucene 2.3.3.4 to ports as well but don't know the
proper procedure and I also hesitate because it only compiles with
Clang. I've contacted the author of the original lucene port but haven't
received a reply.
Rgds,
N.
2012/5/22 Nick Rosier:
Veniamin Gvozdikov wrote:
Hi,
I've tryed build dovecot with the lucene plugin but I have this is
output:
/bin/sh ../../../libtool --tag=CXX--mode=compile c++
-DHAVE_CONFIG_H -I. -I../../.. -I../../../src/lib
-I../../../src/lib-mail -I../../../src/lib-index
-I../../../src/lib-storage -I../../../src/plugins/fts
-I../../../src/doveadm -I/usr/local/include -I/usr/local/lib -O2
-pipe -fno-strict-aliasing -MT lucene-wrapper.lo -MD -MP -MF
.deps/lucene-wrapper.Tpo -c -o lucene-wrapper.lo lucene-wrapper.cc
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../../..
-I../../../src/lib -I../../../src/lib-mail -I../../../src/lib-index
-I../../../src/lib-storage -I../../../src/plugins/fts
-I../../../src/doveadm -I/usr/local/include -I/usr/local/lib -O2 -pipe
-fno-strict-aliasing -MT lucene-wrapper.lo -MD -MP -MF
.deps/lucene-wrapper.Tpo -c lucene-wrapper.cc -fPIC -DPIC -o
.libs/lucene-wrapper.o
Assembler messages:
FATAL: can't create .libs/lucene-wrapper.o: Permission denied
lucene-wrapper.cc:24:36: error: CLucene/util/CLStreams.h: No such file
or directory
lucene-wrapper.cc:25:45: error: CLucene/search/MultiPhraseQuery.h: No
such file or directory
In file included from lucene-wrapper.cc:26:
SnowballAnalyzer.h:12: error: expected constructor, destructor, or
type conversion before '(' token
*** Error code 1
1 error
*** Error code 1
1 error
*** Error code 1
1 error
*** Error code 1
1 error
Which platform/OS are you trying to compile on? Which version of CLucene?
You need at version 2.3.3.4 (not 0.9) as stated on the Wiki
(http://wiki2.dovecot.org/Plugins/FTS/Lucene)
N.
Re: [Dovecot] dovecot-metadata-9 released
Hi Dennis,
This fixed the problem. Thanks!
Rgds,
N.
Dennis Schridde wrote:
Hello Nick!
I am sorry - I forgot to mention that you need attached patch for dovecot.
Kind regards,
Dennis
Am Dienstag, 5. Juni 2012, 11:28:27 schrieb Nick Rosier:
Hi Dennis,
I'm trying to compile the plugin on FreeBSD 9 with Dovecot 2.1.7 and get
the following error:
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I..
-I/usr/local/include/dovecot -g -O2 -MT mailbox-ext.lo -MD -MP -MF
.deps/mailbox-ext.Tpo -c mailbox-ext.c -fPIC -DPIC -o
.libs/mailbox-ext.o mailbox-ext.c:25:19: error: missing binary operator
before token "("
mailbox-ext.c: In function 'mailbox_get_guid_string': mailbox-ext.c:32:
error: 'MAIL_GUID_128_SIZE' undeclared (first use in this function)
mailbox-ext.c:32: error: (Each undeclared identifier is reported only
once mailbox-ext.c:32: error: for each function it appears in.)
mailbox-ext.c:33: warning: implicit declaration of function
'mailbox_get_guid'
*** Error code 1
Stop in /root/work/dovecot-metadata-plugin-6fe39779d758/src. *** Error
code 1
Removing DOVECOT_PREREQ and "forcing" to use the 2.1 definition fixes
that (I couldn't find anywhere where that macro was defined).
Next I get another error, again caused by the DOVECOT_PREREQ:
libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I..
-I/usr/local/include/dovecot -g -O2 -MT imap-metadata-plugin.lo -MD -MP
-MF .deps/imap-metadata-plugin.Tpo -c imap-metadata-plugin.c -fPIC
-DPIC -o .libs/imap-metadata-plugin.o
imap-metadata-plugin.c: In function 'is_valid_rfc5464_entry_name':
imap-metadata-plugin.c:162: warning: comparison is always false due to
limited range of data type
imap-metadata-plugin.c:513:19: error: missing binary operator before
token "("
imap-metadata-plugin.c: In function 'cmd_getmetadata':
imap-metadata-plugin.c:516: warning: passing argument 2 of
'mail_namespace_find' from incompatible pointer type
imap-metadata-plugin.c: In function 'setmetadata_helper':
imap-metadata-plugin.c:596: warning: 'return' with a value, in function
returning void
imap-metadata-plugin.c:672:19: error: missing binary operator before
token "("
imap-metadata-plugin.c: In function 'cmd_setmetadata':
imap-metadata-plugin.c:675: warning: passing argument 2 of
'mail_namespace_find' from incompatible pointer type
*** Error code 1
Am I missing something on my system?
Rgds,
N.
Dennis Schridde wrote:
Hello everyone!
I just released dovecot-metadata-8, which is an implementation of RFC 5464
(IMAP METADATA), allowing to add comments/annotations/metadata to folders
of an email account.
2012-06-04: Version 9
* Added Dovecot 2.1 compatibility
* Fixed compliance with RFC 5464 Section 3.2
* Separated backend code into library
* Synced code of imap-annotatemore with imap-metadata
* Improved error messages
* Several bugfixes (incl. segfaults)
* Minor cleanups
Please get the code from [1] and send me an email for any problem you
find.
For more information please refer to my email from Sun, 12 Jun 2011
15:55:57 +0200 titled "dovecot-metadata-8 released".
Kind regards,
Dennis
[1] http://hg.dovecot.org/dovecot-metadata-plugin
Re: [Dovecot] migrating v.1 to v.2
Voytek Eymont wrote: I have a working Dovecot/MySQL with version 1.x I'm looking at setting a new server using ver. 2 I'm currently pre-planning: can I use config files from ver 1 installation on version 2 setup 'as is'; or what's a proper way to do such migration/upgrade ? Hi, this question has been asked numerous times. It's also (in my case) the 1st couple of hits when searching in Google for "dovecot wiki upgrading". Try this http://wiki2.dovecot.org/Upgrading/ Rgds, N.
Re: [Dovecot] migrating v.1 to v.2
Hi Voytek, no apologies needed; Timo created an excellent wiki so that should be the 1st thing to search. But if there's anything unclear just ask. I'm not an expert but made the transitions from 1.2 -> 2.0 -> 2.1 thanks to this documentation. N. Voytek Eymont wrote: Nick, thanks, and, apologies: I did have a brief look at the docs, clearly, not searched enough, my fault. the docs are amazing, and, excellent, and, have precise anwser, mea culpa upgrading". Try this http://wiki2.dovecot.org/Upgrading/
[Dovecot] Upgrade from 1.2.16 with sieve/managesieve to 2.0.8 with pigeonhole
Hi, I would like to upgrade my server from 1.2.16 with sieve and managesieve to 2.0.8 with pigeonhole. Will I get all functionality I was having before? Should this migration be painless or will it require some additional work? I've read the Upgrading guide so I know I need to create an additional user. I've migrated the mails from Maildir to dbox in the past (using the convert plugin); does that mean I'm fully dbox or am I in a maildir-dbox hybrid situation? I've noticed that there are still some maildir-formatted mail (e.g. 1259960330.M39P62710.mail,W=2195:2,S) in some of the maps. r...@mail /usr/local/etc # dovecot -n # 1.2.16: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.2-PRERELEASE amd64 zfs protocols: imap imaps managesieve ssl_ca_file: /etc/ssl/cert.pem ssl_cert_file: /etc/ssl/mail.crt ssl_key_file: /etc/ssl/mail.key version_ignore: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login valid_chroot_dirs: /var/spool/vmail mail_max_userip_connections(default): 50 mail_max_userip_connections(imap): 50 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_uid: 5000 first_valid_gid: 5000 mail_privileged_group: mail mail_location: dbox:/var/spool/vmail/%d/%n mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): acl imap_acl fts fts_squat autocreate mail_plugins(imap): acl imap_acl fts fts_squat autocreate mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(managesieve): dict_db_config: /usr/local/etc/dovecot-db.conf namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmas...@xxx.xxx mail_plugins: sieve acl mail_plugin_dir: /usr/local/lib/dovecot/lda deliver_log_format: msgid=%m: %$ sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login cram-md5 username_format: %Lu passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: acl: vfile:/usr/local/etc/dovecot/acls:cache_secs=300 acl_shared_dict: file:/var/db/dovecot/shared-mailboxes.db convert_mail: maildir:/var/spool/vmail/%d/%n expire_dict: proxy::expire expire: Trash 365 sieve: /var/spool/vmail/%d/%n/dovecot.sieve sieve_dir: /var/spool/vmail/%d/%n/sieve sieve_global_dir: /usr/local/etc/dovecot/sieve fts: squat fts_squat: partial=4 full=10 autocreate: Trash autocreate2: Drafts autocreate3: Spam autocreate4: Sent autosubscribe: Trash autosubscribe2: Drafts autosubscribe3: Spam autosubscribe4: Sent dict: expire: db:/var/db/dovecot/expire.db
[Dovecot] Migrate dbox 1.2 virtual mail to 2.0
Hi, I'm trying to migrate from Dovecot 1.2.16 to 2.0.7. Initially the mails were stored in Maildir format but I changed them to dbox using "fast Maildir migration" and some mails are still in the old maildir format. I'm trying to migrate these mails using dsync but dsync panics: % dsync -D -o mail_location=dbox:/var/spool/vmail/bunbun.be/nick mirror dbox:/var/spool/vmail2/bunbun.be/nick .. dsync(vmail): Panic: file mail-storage.c: line 1351 (mailbox_save_set_guid): assertion failed: (guid == NULL || *guid != '\0') zsh: abort (core dumped) dsync -D -o mail_location=dbox:/var/spool/vmail/bunbun.be/nick mirror Any ideas? N.
Re: [Dovecot] Migrate dbox 1.2 virtual mail to 2.0
Timo Sirainen wrote: On 7.1.2011, at 23.03, Nick Rosier wrote: I'm trying to migrate from Dovecot 1.2.16 to 2.0.7. Initially the mails were stored in Maildir format but I changed them to dbox using "fast Maildir migration" and some mails are still in the old maildir format. I'm trying to migrate these mails using dsync but dsync panics: http://dovecot.org/list/dovecot/2010-November/055191.html for explanation and http://dovecot.org/list/dovecot/2010-November/055192.html for the latest version. Rename the attachment.bin to dbox-dehybrid.c and compile it. The wiki should be upgraded I guess.. Thanks for the quick reply. I compiled the code and ran it as described. I got some errors (file not found errors for non-existing maildir messages) but the tool completed successfully. Unfortunately dovecot 2.0.7 was unable to read the dbox mails. All mailboxes were empty. In the log I found following errors: Invalid dbox header size I've also tried running dsync again on the dehybridified mailboxes but it still crashes. I tried running 2.0 on untouched mailboxes but got empty mailboxes. I've rolled back to 1.2.16 and the mailboxes from before the migration (thank god for zfs snapshots :-) ) and am able to view all mailboxes again. Any ideas? N.
[Dovecot] dsync not copying all mail
Hi, I'm still trying to migrate from Dovecot 1.2.16 to 2.0.7 on FreeBSD. Previous attempts have failed with mails not being visible after the upgrade. Version 1.2.16 was migrated from maildir to dbox about a year ago via the convert-plugin. After previous attempts to "clean" the hybrid maildir-dbox situation I used imapsync to copy all mails from the old account to a new account. I would assume in this case I get a clean dbox-mailmap. I tried to run dsync on this new map but noticed a lot of mails are not syncing: [vm...@mail ~]$ find /vmail2/new/bunbun.be/nick | wc -l 5329 [vm...@mail ~]$ find /vmail2/old/bunbun.be/nick | wc -l 6134 Any ideas? N.
Re: [Dovecot] dsync not copying all mail
Tobias Daucher wrote: Am 10.01.2011 14:59, schrieb Nick Rosier: Hi, I'm still trying to migrate from Dovecot 1.2.16 to 2.0.7 on FreeBSD. Previous attempts have failed with mails not being visible after the upgrade. Version 1.2.16 was migrated from maildir to dbox about a year ago via the convert-plugin. After previous attempts to "clean" the hybrid maildir-dbox situation I used imapsync to copy all mails from the old account to a new account. I would assume in this case I get a clean dbox-mailmap. I tried to run dsync on this new map but noticed a lot of mails are not syncing: [vm...@mail ~]$ find /vmail2/new/bunbun.be/nick | wc -l 5329 [vm...@mail ~]$ find /vmail2/old/bunbun.be/nick | wc -l 6134 Any ideas? N. deleted mails on old server... do expunge or purge befor syncing. imapsync will not copy deleted messages i think... The problem is not imapsync but dsync. I created a new account nick2 and synced, with imapsync all mails from nick to nick2. I moved the old maildir (nick) to nick.old and renamed nick2 to nick. I checked the new mail and all mails were there (with the exception of 23 mails which according to imapsync were duplicates). So at this point I have a new "clean" mailmap; there are no mails missing. I copied this new mailmap (nick) to a new filesystem (/vmail2/new) to do some migration tests and ran dsync to sync these mails. [vm...@mail ~]$ ./dsync -D -o mail_location=dbox:/vmail2/old/bunbun.be/nick mirror dbox:/vmail2/new/bunbun.be/nick When I compare the 2 maildirs there are about 800 files missing: [vm...@mail ~]$ find /vmail2/new/bunbun.be/nick | wc -l 5329 [vm...@mail ~]$ find /vmail2/old/bunbun.be/nick | wc -l 6134 If I do a diff on the missing files there are maps that are empty and where the source contains valid, non-deleted mails. N.
Re: [Dovecot] dsync not copying all mail
Timo Sirainen wrote: On 10.1.2011, at 15.59, Nick Rosier wrote: I'm still trying to migrate from Dovecot 1.2.16 to 2.0.7 on FreeBSD. Previous attempts have failed with mails not being visible after the upgrade. Version 1.2.16 was migrated from maildir to dbox about a year ago via the convert-plugin. After previous attempts to "clean" the hybrid maildir-dbox situation I used imapsync to copy all mails from the old account to a new account. I would assume in this case I get a clean dbox-mailmap. I tried to run dsync on this new map but noticed a lot of mails are not syncing: Hmm. I thought I already answered this. Maybe I got distracted while answering it and aborted.. Anyway, you need a different way to migrate the hybrid maildir. http://dovecot.org/list/dovecot/2010-September/053012.html had some old ideas, but there is a newer program explained in http://dovecot.org/list/dovecot/2010-November/055191.html and the program itself is slightly updated in http://dovecot.org/list/dovecot/2010-November/055192.html. Save the attachment.bin into dbox-dehybrid.c and compile and run it. Get backups. :) Hi Timo, you had indeed answered this; I tried the utility but it did not help. That's why I tried the imapsync approach in hope that would clean the messages and create a new dbox-only account. I also ran the utility on the synced mailboxes and retried dsync but that did not fix it either. I'm really puzzled to why this is. How can I recognize a hybrid mailbox? All mailboxes only contain dovecot.index, dovecot.index.log, dbox.index and u.* files. N.
Re: [Dovecot] dsync not copying all mail
Timo Sirainen wrote: On 10.1.2011, at 21.25, Nick Rosier wrote: you had indeed answered this; I tried the utility but it did not help. That's why I tried the imapsync approach in hope that would clean the messages and create a new dbox-only account. I also ran the utility on the synced mailboxes and retried dsync but that did not fix it either. I'm really puzzled to why this is. How can I recognize a hybrid mailbox? All mailboxes only contain dovecot.index, dovecot.index.log, dbox.index and u.* files. If there are no filenames that begin with a number, then it's not a hybrid mailbox. If there are more u.* files than number of messages in a converted mailbox with dsync, then .. well .. I'd just use Dovecot v2.0 on the original non-converted mailbox: doveadm -u username force-resync INBOX This will make sure all of INBOX's u.* files are in the index files. Do the same for the rest of the mailboxes too. Thank you very much, that solved the problem! Ran force-resync on all mailboxes that were missing mails (made handy use of the subscriptions file) and they "automagicly" re-appeared. Just had to mark them read again. N.
Re: [Dovecot] migration dovecot 1 --> dovecot 2
Frank Bonnet wrote: Hello I plan to migrate my mailhub from 1 to 2 , is it a good idee to remove all indexes .imap directories from the new server before starting it in production state ? What mailbox format are you using? I had sdbox in 1.x and had some problems with the indexes when moving to 2.x. Even removing them did not solve the problem. The solution was to run doveadm force-resync for all mailboxes of all users (luckily it's a private server with only a few mailboxes and it can easily be scripted) to regenerate the indexes.
Re: [Dovecot] Force STARTTLS on port 143 for !internalnetwork
Ralf Hildebrandt wrote: Hi! How can I force users which are connecting from OUTSIDE our newtworks to user STARTTLS on Port 143? Right now we resort to IMAPS on port 993, but an additional STARTTLS enabled login on the default port would make things easier! You can probably add login_trusted_networks = localnet IIRC this allows for unsecure login from your localnet but forces all other networks to use a secure authentication method (e.g. SSL, STARTTLS, CRAM or DIGEST). N.
[Dovecot] SIS generating 2 different hashes for the same mail and attachment
Hi, I've been testing SIS over the weekend as it seems to be a nifty feature. I don't have that many users and mailboxes but still... I only added the following line to my configuration: mail_attachment_dir = /var/spool/vmail/attachments As a test I sent a mail from GMail to 2 mailboxes (1 To and 1 CC). The attachment got saved to the attachment directory (on ZFS): # find . ./04 ./04/78 ./04/78/0478b28c2a4c235370bb3cef4bc0482bb6000dae-b8819638a60e574d5b530100bde47b1f-2088e7301f9e3c4dc97ebde47b1f-244 ./04/78/0478b28c2a4c235370bb3cef4bc0482bb6000dae-007dcd01a70e574d5c530100bde47b1f-98d08416e4712b4d75310100bde47b1f-192 # ls -l total 519 -rw--- 1 vmail vmail 242866 Feb 12 23:50 0478b28c2a4c235370bb3cef4bc0482bb6000dae-007dcd01a70e574d5c530100bde47b1f-98d08416e4712b4d75310100bde47b1f-192 -rw--- 1 vmail vmail 242866 Feb 12 23:50 0478b28c2a4c235370bb3cef4bc0482bb6000dae-b8819638a60e574d5b530100bde47b1f-2088e7301f9e3c4dc97ebde47b1f-244 So these files are not hardlinks, they are 2 seperate files. Checksums are the same: # sum * 58522 238 0478b28c2a4c235370bb3cef4bc0482bb6000dae-007dcd01a70e574d5c530100bde47b1f-98d08416e4712b4d75310100bde47b1f-192 58522 238 0478b28c2a4c235370bb3cef4bc0482bb6000dae-b8819638a60e574d5b530100bde47b1f-2088e7301f9e3c4dc97ebde47b1f-244 # md5 * MD5 (0478b28c2a4c235370bb3cef4bc0482bb6000dae-007dcd01a70e574d5c530100bde47b1f-98d08416e4712b4d75310100bde47b1f-192) = 684863b31dad701857642caedcdbf20a MD5 (0478b28c2a4c235370bb3cef4bc0482bb6000dae-b8819638a60e574d5b530100bde47b1f-2088e7301f9e3c4dc97ebde47b1f-244) = 684863b31dad701857642caedcdbf20a Did I miss something? I would have expected the file once in the attachment_dir. Rgds, N.
[Dovecot] segmentation fault with doveadm search
Configuration: Dovecot 2.0.11 on FreeBSD 8.2 When I run a search to generate the FTS search indexes I get following error: # doveadm search -A body dead_beef [1]34789 segmentation fault doveadm search -A body dead_beef How can I (help) troubleshoot this? Rgds, N.
Re: [Dovecot] segmentation fault with doveadm search
Nick Rosier wrote: Configuration: Dovecot 2.0.11 on FreeBSD 8.2 When I run a search to generate the FTS search indexes I get following error: # doveadm search -A body dead_beef [1]34789 segmentation fault doveadm search -A body dead_beef How can I (help) troubleshoot this? With the use of DTrace I was able to track that the last Folder it searched was a Virtual-folder (all mails unseen). After temporarily moving this folder and running the command again it did not sigsegv. How can I prevent a search from trying to index Virtual-folders? Rgds, N.
Re: [Dovecot] segmentation fault with doveadm search
Timo Sirainen wrote: On Thu, 2011-03-17 at 14:38 +0100, Nick Rosier wrote: # doveadm search -A body dead_beef [1]34789 segmentation fault doveadm search -A body dead_beef How can I (help) troubleshoot this? With the use of DTrace I was able to track that the last Folder it searched was a Virtual-folder (all mails unseen). After temporarily moving this folder and running the command again it did not sigsegv. How can I prevent a search from trying to index Virtual-folders? Could you get gdb backtrace? gdb --args doveadm search -A body dead_beef run bt full I assume I will have to re-install from source; FreeBSD ports strips during install so I doubt that would be handy. Rgds, N.
Re: [Dovecot] segmentation fault with doveadm search
Timo Sirainen wrote: On Thu, 2011-03-17 at 17:54 +0100, Nick Rosier wrote: Hope this is better: #1 0x00080231ab21 in fts_build_deinit (_ctx=0x801ea2640) at fts-storage.c:551 Yes, much better. Easy fix: http://hg.dovecot.org/dovecot-2.0/rev/3d48418b0501 Thanks, fixed :-)
Re: [Dovecot] Sieve or not?
Jim Knuth wrote: Hello, I use V 2.11 and my question is: Is one present Sieve with this version or MUST this specially compiles? # 2.0.11 (31d8d43fa6b5): /etc/dovecot/dovecot.conf # OS: Linux 2.6.29.4 i686 Debian wheezy/sid For sieve you will have to install pigeonhole (http://wiki2.dovecot.org/Pigeonhole) N.
Re: [Dovecot] WiKi V2
Brian Hayden wrote: On Mar 30, 2011, at 3:35 PM, nick+dove...@bunbun.be wrote: Jim Knuth wrote: small question: Will the WiKi of the version 2 be updated shortly? Many things are not right at all. This would be really very nice. Many thanks in advance. It's a Wiki... feel free to correct :-) wiki: A collaborative website which can be directly edited using only a web browser, often by anyone with access to it. Just because someone *can* edit it doesn't mean they have the relevant subject matter knowledge necessary to do a proper job of it. Just because someone can competently follow instructions enough to tell that they are wrong doesn't mean that they know what is right. They may just be stuck. Unfortunatly this Wiki doesn't support discussion; that's how I've worked on other Wiki's. The OP said "Many things are not right at all". How do you expect a Wiki to get corrected. Just screaming at it: "You contain errors" will not automagicly fix them :-D Unfortunately putting documentation in a wiki usually just has the effect of making nobody feel like they really own it. Then helpful, respectful folks such as yourself say to anyone who wants documentation, "LEARN THE CODE AND DOCUMENT IT YOURSELF! It's a WIKI!" Who said anything about learning the code; I remember a recent post discussing errors in the general overview. Ignoring that of course the whole point of documentation is that it (hopefully) enables people to use software without having to read the source first... So how will incorrect documentation help people? Again, if there is a mistake in the documentation either fix it or point to it to have it fixed.
Re: [Dovecot] IPv6 & SSL
Luigi Rosa wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have a dual stack server with Dovecot 2.1.10 listening on v4 and v6 Dovecot has a Comodo SSL certificate issued via NameCheap that works as expected with IPv4 in 10-ssl.conf I have enabled these configuraction directives: ssl = yes ssl_cert =< /path/to/file.crt ssl_key =< /path/to/file.key ssl_parameters_regenerate = 202 hours If I connect to Dovecot using the IPv6 address of the server with Thunderbird 15.0.1 uising CRAM-MD5 averything is ok. If I enable SSL _and_ IPv6 on Thunderbird I get this error: How do you enable this in Thunderbird? If by "enabling IPv6" you mean you put in the IPv6 address in stead of the hostname, that's probably where you're wrong. The certificate contains your hostname, not the IP-address so the hostname verification check fails if you insert the IPv6 address (i.e. hostname.tld != 2001:470:1f09:203:fdbf:508e:4a29:56c5so your connection fails). I've verified this by changing the hostname to IPv6 in Thunderbird and got the same error as you do. You would get the same error if you configure the IPv4 address in TB. Oct 5 20:05:04 mail dovecot: imap-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=2001:470:1f09:203:fdbf:508e:4a29:56c5, lip=2001:470:1f09:203::badd:ecaf, TLS: SSL_read() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca: SSL alert number 48, session= This is a valid connection when I use the hostname: 2012-10-04T18:07:51.614187+02:00 mail dovecot: imap-login: Login: user=, method=CRAM-MD5, rip=::::, lip=::::, mpid=58179, TLS, TLSv1 with cipher RC4-MD5 (128/128 bits) Configure your DNS so your hostname points to both the IPv6 and IPv4 address. Your client will take take whichever protocol is preferred (IPv4 or IPv6). Rgds, N. Ciao, luigi - -- / +--[Luigi Rosa]-- \ I will tell you a great secret, Captain. Perhaps the greatest of all time. The molecules of your body are the same molecules that make up this station and the nebula outside, that burn inside the stars themselves. We are star stuff, we are the universe made manifest, trying to figure itself out. As we have both learned, sometimes the universe requires a change of perspective." --Delenn, "Distant Star", Babylon 5 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla -http://www.enigmail.net/ iEYEARECAAYFAlBvI50ACgkQ3kWu7Tfl6ZRBSACfRkp4FYpWaEZUQhIh0t6Vfs/I JbcAoKGZ769yogYS7faCXKvPTuhQiHA8 =jxCB -END PGP SIGNATURE-
Re: [Dovecot] how quotas works with postfix and dovecot
Wilberth Pérez wrote:
Hi everybody
any one knows, how i could edit dovecot to assign user quotas ?
I have now configured my dovecot.conf on this way:
protocol imap {
listen = *:143
mail_plugins = quota imap_quota
}
protocol pop3 {
listen = *:110
mail_plugins = quota
}
plugin {
quota = fs:INBOX:mount=/
quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95
}
however when a test my quota:
quota -v user1
Disk quotas for user1 (uid 107):
Filesystem *usage* *quota* limittimeleft files quota limit
timeleft
/var/mail 16911 10240 20480 NOT STARTED 49 1000 1500
dovecot or postfix (i don't know who really should sendme the
messsage) never sendme an quota warning
someone knows what happen ?
What version of Dovecot are you using? You have no quota_rule specified.
If using 1.1 or higher, check out this page:
http://wiki.dovecot.org/Quota/1.1
N.
Re: [Dovecot] how quotas works with postfix and dovecot
Wilberth Pérez wrote:
dovecot-1.2.10
knows how i can create quotas templates ?
cheers.
I have no experience using disk quota's but I think something like this
should work:
plugin {
quota = fs:Disk quota
quota_rule = INBOX:storage=
quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95
}
AFAIK, the backend is only used as a way to determine the used space,
not as a way to define the limits. So you need to specify the maximum
quota; the filesystem quota is not recognized. E.g. when specifying
maildir as backend Dovecot will check the maildir quota in stead of
using used diskspace as reported by the OS.
N.
LCC Wilberth de Jesús Pérez Segura CCSA- Administración de Servicios y
Seguridad de las TI
Correo: wilberth.pe...@uady.mx
Universidad Autónoma de Yucatán
Secretaría General
Coordinación Administrativa de Tecnologías de Información
RIUADY
C-59 x Av. Itzáes (999)923-74-28 Ext. 1117
Mérida, Yucatán, México 2010
El 12/03/2010 04:43 p.m., Nick Rosier escribió:
Wilberth Pérez wrote:
Hi everybody
any one knows, how i could edit dovecot to assign user quotas ?
I have now configured my dovecot.conf on this way:
protocol imap {
listen = *:143
mail_plugins = quota imap_quota
}
protocol pop3 {
listen = *:110
mail_plugins = quota
}
plugin {
quota = fs:INBOX:mount=/
quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95
}
however when a test my quota:
quota -v user1
Disk quotas for user1 (uid 107):
Filesystem *usage* *quota* limittimeleft files quota
limittimeleft
/var/mail 16911 10240 20480 NOT STARTED 49 1000 1500
dovecot or postfix (i don't know who really should sendme the
messsage) never sendme an quota warning
someone knows what happen ?
What version of Dovecot are you using? You have no quota_rule
specified. If using 1.1 or higher, check out this page:
http://wiki.dovecot.org/Quota/1.1
N.
[Dovecot] Shared mailboxes do not support subfolders
Hi, I'm currently running Dovecot 1.2.8 with dbox mailboxes. I've configured the use of shared mailboxes. I'm able to only see the top-level mailboxes: e.g. Inbox LogWatch Trash Sent but not LogWatch/Server1 LogWatch/Server2 Is this a know limitation of a bug? Rgds, N.
Re: [Dovecot] Shared mailboxes do not support subfolders
Frank Cusack wrote: On December 28, 2009 4:44:45 PM +0100 Nick Rosier wrote: Hi, I'm currently running Dovecot 1.2.8 with dbox mailboxes. I've configured the use of shared mailboxes. I'm able to only see the top-level mailboxes: e.g. Inbox LogWatch Trash Sent but not LogWatch/Server1 LogWatch/Server2 Is this a know limitation of a bug? If by shared you mean public, subfolders (with maildir) works for me. Shared as in user-shared mailboxes. I think it was a mailclient (TB) problem. After subscribing from webmail (roundcube) I'm able to see them. I will do some more testing to see if I can reproduce. N.
Re: [Dovecot] ManageSieve doe not work
Mike Werner wrote: Hi, I use MailScanner 4.74.16 (Ubuntu karmic). I convigured ManageSieve as discribed in http://wiki.dovecot.org/ManageSieve/Configuration. But sieve scripts are not applied to incoming mail. How can I determin what went wrong? ManageSieve is to manage sieve filters. Your MDA does the filtering. Have you configured Dovecot deliver as your MDA? See: http://wiki.dovecot.org/LDA N.
Re: [Dovecot] salted passwords
Leonardo Rodrigues wrote:
The idea of salted hash algorithms is to generate a different hash
even if the same text is entered. That can be easily seen with dovecotpw:
using NON-salted SHA256, same hash is generated for a given password
[r...@correio ~]# dovecotpw -s SHA256 -p 123
{SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM=
[r...@correio ~]# dovecotpw -s SHA256 -p 123
{SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM=
[r...@correio ~]# dovecotpw -s SHA256 -p 123
{SHA256}pmWkWSBCL51Bfkhn79xPuKBKHz//H6B+mY6G9/eieuM=
[r...@correio ~]#
using SALTED SHA256, a different hash is generated for the same given
password
[r...@correio ~]# dovecotpw -s SSHA256 -p 123
{SSHA256}FpJZqafpEVKp2heepp9Z7+OeHaX+DBVpLzd6GKg3BW1XqDS0
[r...@correio ~]# dovecotpw -s SSHA256 -p 123
{SSHA256}6lWmvtO3SKG5RMET5n89WMIp0xeCg3U14xH1xnAXbvkr8Yjk
[r...@correio ~]# dovecotpw -s SSHA256 -p 123
{SSHA256}7fXVjC7Iiu0Ko9SgyBpbDvbwMSkoxMILRjDUE0nNpCHBFaIa
[r...@correio ~]#
This ideia is OK to me ...
but i'm having a hard time trying to figure out how my
dovecot-sql.conf would be in the case i store salted SHA256 passwords
on the database. The idea is to use a RANDOM salt, not a fixed one,
just like dovecotpw does.
would it be as simple as changing the 'password', which today is
plaintext, by something like
concat('{SHA256}',password) ???
dont i have to give the salt, somehow ?? Or should i store the
salt used in the password, for example first or last N characters
is there anyone using dovecot with MySQL and SSHA256 passwords
that can share me the dovecot-sql.conf file ?
How about just putting
default_pass_scheme = SSHA256
in your dovecot-sql file? I do it that way for CRAM-MD5.
Rgds,
N.
