Re: [Dovecot] mail archiving
On Friday 09 October 2009 17:18:53 dhottin...@harrisonburg.k12.va.us wrote: > Im curious if anyone is archiving emails and what they are using. I > currently utilize sendmail/procmail/dovecot. What exactly do you mean by archiving? We use Postfix and Dovecot to backup any sent and received mail for our users. Postfix, using sender_bcc_maps, resends any mail to the sending user via an address extension (i.e. mail sent by f...@example.org gets resent to foo+s...@example.org) and Dovecot with Sieve, using the sieve_before directive, filters such sent mail into a private namespace that is hidden from the user (Backup/sent). Backing up received mail works very similar (ending up in Backup/received) but Postfix is not involved; this is a job for Sieve alone, again using the sieve_before directive and an appropriate script. So Postfix/Dovecot/Sieve. If ACLs worked a bit better in 1.2.x [1] I could even make the Backup namespace visible to its user and just ensure, via ACLs, that the user cannot delete any messages in this namespace. But this'll have to wait for 2.0 I believe. Does that answer your question? Andreas [1] http://dovecot.org/list/dovecot/2009-September/042783.html -- Andreas Ntaflos GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4 signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] status & use-case of fts_solr?
On Fri, Oct 9, 2009 at 7:21 PM, Patrick Nagel wrote: > Cross-referencing > http://www.dovecot.org/list/dovecot/2009-September/042904.html > > So when you have a huge amount of folders (like we do... there are users > with >1 folders), Solr could have a big advantage through the single > index. thanks for the reference. i clearly need to try both & see. looking, atm, for a comprehensivce list of MUAs that can search squat vs solr indexes. if, in fact, solr's the better performance solution, i hope that the IMAP compliance might, somehow, get addressed -- either from the Dovecot side, the MUAs, or both.
Re: [Dovecot] @2.0, --sysconfdir incorrectly populated with dovecot/*.conf
On Oct 9, 2009, at 11:31 PM, PGNet Dev wrote: On Fri, Oct 9, 2009 at 7:40 PM, Timo Sirainen wrote: This is intended, because there are now lots of config files by default. Or should this be done somehow differently? lots of config file is fine ... according to: http://www.gnu.org/prep/standards/html_node/Directory-Variables.html " ... The directory for installing read-only data files ..." should, iiuc, specify the DIR that CONF FILES are installed in. not a DIR that another DIR is installed in. admittedly, i have NO clue as to how "rigid" that's supposed to be. I think many other programs also use a directory. Anyway the point is that just doing "./configure" should still access /usr/local/etc/dovecot/ dovecot.conf. the default, as spec'd @ ./configure --help says, --sysconfdir=DIRread-only single-machine data [PREFIX/etc] which seems to imply that the .conf files are installed in PREFIX/etc ... not PREFIX/etc/dovecot And that's definitely something that's never wanted with v2.0. It would just pollute the etc/ directory with lots of files. the fact remains that, atm, ./configure "as usual" (1) doesn't seem to create the /dovecot/ directory _under_ sysconfdir, Hmm. That could be a good idea. and (2) causes an error (e.g., dovecot -n) when it doesn't find the files that a user would even manually place in the directory they'd expect the files to be in. Well, it does say: doveconf: Fatal: open(/usr/local/etc/dovecot/dovecot.conf) failed: No such file or directory (example config in /usr/local/share/doc/dovecot/ example-config/) Do you have some idea how that could be made clearer? of course it's trivial to "figure out" once you get the error msg, but the goal would be to avoid the problem in the 1st place ... Avoid what problem? That v2.0's config is in different directory than v1.x's? The wouldn't be compatible anyway. Or for a new installation it should put the example files to prefix/etc/dovecot/ directly? 2.0's behavior should be made consistent with the correct implementation in 1.2.x, or clarified as different in --help/docs. I don't think it's possible to change --help's text. As for other docs.. I'm not really sure how I should even start describing all the v2.0 changes and where.. The v2.0's changed configuration is going to break so many wiki pages.. personally, i'd suggest cloning the 1.0/1.2 wiki to a parallel site, and making it just a 2.0 wiki -- to which changes can be made. imo, trying to maintain a single site for all versions is just going to get horribly confusing, tough to maintain, and almost impossible to deprecate when the time comes. Apache HTTPD does a very nice job of parallel sites for each version. That's what I was also thinking, but I still need to pick one "primary" site where all the old wiki.dovecot.org/ links go. And it'll probably take at least 1-2 years until Dovecot v2.x usage is higher than v1.x and then lots of people try to use v2.0 configuration examples with v1.x and complain that they don't work.. Unless I could somehow clearly enough show in the wiki pages what version they're for and actually get people to notice without making the font size half the page size.
Re: [Dovecot] @2.0, --sysconfdir incorrectly populated with dovecot/*.conf
On Fri, Oct 9, 2009 at 7:40 PM, Timo Sirainen wrote: > This is intended, because there are now lots of config files by default. Or > should this be done somehow differently? lots of config file is fine ... according to: http://www.gnu.org/prep/standards/html_node/Directory-Variables.html " ... The directory for installing read-only data files ..." should, iiuc, specify the DIR that CONF FILES are installed in. not a DIR that another DIR is installed in. admittedly, i have NO clue as to how "rigid" that's supposed to be. > Anyway the point is that just doing > "./configure" should still access /usr/local/etc/dovecot/dovecot.conf. the default, as spec'd @ ./configure --help says, --sysconfdir=DIRread-only single-machine data [PREFIX/etc] which seems to imply that the .conf files are installed in PREFIX/etc ... not PREFIX/etc/dovecot the fact remains that, atm, ./configure "as usual" (1) doesn't seem to create the /dovecot/ directory _under_ sysconfdir, and (2) causes an error (e.g., dovecot -n) when it doesn't find the files that a user would even manually place in the directory they'd expect the files to be in. of course it's trivial to "figure out" once you get the error msg, but the goal would be to avoid the problem in the 1st place ... >> 2.0's behavior should be made consistent with the correct >> implementation in 1.2.x, or clarified as different in --help/docs. > > I don't think it's possible to change --help's text. As for other docs.. I'm > not really sure how I should even start describing all the v2.0 changes and > where.. The v2.0's changed configuration is going to break so many wiki > pages.. personally, i'd suggest cloning the 1.0/1.2 wiki to a parallel site, and making it just a 2.0 wiki -- to which changes can be made. imo, trying to maintain a single site for all versions is just going to get horribly confusing, tough to maintain, and almost impossible to deprecate when the time comes. Apache HTTPD does a very nice job of parallel sites for each version.
Re: [Dovecot] @2.0, --sysconfdir incorrectly populated with dovecot/*.conf
On Oct 9, 2009, at 10:28 PM, PGNet Dev wrote: to document from #irc, in 1.2.x, specifying ./configure ... --sysconfdir=/path/to/dir ... correctly results in dovecot.conf looked for as "/path/to/dir/ dovecot.conf". in 2.0, dovecot incorrectly creates a dovecot dir in the sysconfdir, and looks for, /path/to/dir/dovecot/dovecot.conf This is intended, because there are now lots of config files by default. Or should this be done somehow differently? Anyway the point is that just doing "./configure" should still access /usr/local/etc/ dovecot/dovecot.conf. 2.0's behavior should be made consistent with the correct implementation in 1.2.x, or clarified as different in --help/docs. I don't think it's possible to change --help's text. As for other docs.. I'm not really sure how I should even start describing all the v2.0 changes and where.. The v2.0's changed configuration is going to break so many wiki pages..
[Dovecot] @2.0, --sysconfdir incorrectly populated with dovecot/*.conf
to document from #irc, in 1.2.x, specifying ./configure ... --sysconfdir=/path/to/dir ... correctly results in dovecot.conf looked for as "/path/to/dir/dovecot.conf". in 2.0, dovecot incorrectly creates a dovecot dir in the sysconfdir, and looks for, /path/to/dir/dovecot/dovecot.conf 2.0's behavior should be made consistent with the correct implementation in 1.2.x, or clarified as different in --help/docs. thanks.
Re: [Dovecot] status & use-case of fts_solr?
Hi, On Thu, 8 Oct 2009 21:41:36 -0700, PGNet Dev wrote: > hi, > > On Thu, Oct 8, 2009 at 7:56 PM, Timo Sirainen wrote: >> It's just not possible, because it doesn't support substring searches. >> But >> then again, perhaps no one cares. It's not like gmail's search is IMAP >> compliant either. >> >>> if the goal is fast, indexed FTS of dovecot IMAP stores from within a >>> MUA, is fts_solr even helpful? or is it targeted for web interfaces to >>> search ... ? >> >> You can add the break-imap-search option and it'll be helpful with those >> MUAs that use IMAP SEARCH command (Thunderbird I think, but not Apple >> Mail >> or Outlook). > > Ok, clear. So, from a MUA perspective ... *IS* fts_solr > faster/better/cheaper/whatever than fts_squat? > > It _seems_ that squat is fast, _does_ substring searches, and _is_ > under your control in dovecot. Life seems simpler, but just as > functional, with "just squat". > > I'm clearly missing or misunderstanding the "solr advantage" ... Cross-referencing http://www.dovecot.org/list/dovecot/2009-September/042904.html So when you have a huge amount of folders (like we do... there are users with >1 folders), Solr could have a big advantage through the single index. Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone:+86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key: E883A005 https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005
Re: [Dovecot] Panic when using QRESYNC
On Fri, 2009-10-09 at 12:56 -0600, Michael M. Slusarz wrote: > Oct 9 12:49:30 bigworm EXT(slusarz): : > /home/slusarz/Maildir/dovecot.index.log: Transaction log changed > unexpectedly, can't get modseq I'll still need to get this fixed. > Oct 9 12:49:30 bigworm EXT(slusarz): : Panic: file imap-fetch.c: line > 227 (get_expunges_fallback): assertion failed: (mail->uid > next_uid) But the crash is anyway now fixed: http://hg.dovecot.org/dovecot-1.2/rev/73c4a7d325fe signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Berkely DB authentication?
On Fri, 2009-10-09 at 15:30 -0700, Marc Perkel wrote: > Does Dovecot support berkeley DB authentication? I'm looking for > something simple that is perhaps a single file for multiple domains and > something the Exim can also read. No, and I'm actually hoping to get rid of all traces of BDB code in Dovecot. I just don't seem to have the skills to make it work reliably. Couldn't you make Exim do SMTP AUTH via dovecot-auth? signature.asc Description: This is a digitally signed message part
[Dovecot] Berkely DB authentication?
Does Dovecot support berkeley DB authentication? I'm looking for something simple that is perhaps a single file for multiple domains and something the Exim can also read.
Re: [Dovecot] Panic when using QRESYNC
Quoting Timo Sirainen : On Fri, 2009-10-09 at 22:33 +0200, Pascal Volk wrote: > 2 EXAMINE "INBOX" (QRESYNC (1254166848 789 > 1,2,6,7,109,113,193,230,231,279,284)) Hi Michael, maybe Timo has sent his reply only to you. If not: there is patch: imap: Don't crash on SELECT .. QRESYNC if it didn't give seq-uid map. http://hg.dovecot.org/dovecot-1.2/rev/352eab3d6ade Actually that's for a different crash. I couldn't immediately reproduce Michael's problem so I decided to leave it for later.. Timo, I saved the various dovecot cache/index files - let me know if that would be useful for tracking down this issue. michael
Re: [Dovecot] very frequent disconnections
On Fri, 2009-10-09 at 16:09 -0400, Dan Christensen wrote: > The very frequent dropped connections don't happen if I don't use TLS. > To summarize: > > - they happen with TLS to port 143 > - they don't happen with a plain connection to port 143 > - they don't happen with a TLS connection to port 11143 This clearly indicates some firewall/antivirus/IDS in the middle believing that port 143 only has plaintext traffic and then get entirely confused when they see TLS traffic and at some point decide to kill the connection. I guess using imaps on port 993 would also fix it? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Panic when using QRESYNC
On Fri, 2009-10-09 at 22:33 +0200, Pascal Volk wrote: > > 2 EXAMINE "INBOX" (QRESYNC (1254166848 789 > > 1,2,6,7,109,113,193,230,231,279,284)) > > Hi Michael, > > maybe Timo has sent his reply only to you. If not: there is patch: > > imap: Don't crash on SELECT .. QRESYNC if it didn't give seq-uid map. > http://hg.dovecot.org/dovecot-1.2/rev/352eab3d6ade Actually that's for a different crash. I couldn't immediately reproduce Michael's problem so I decided to leave it for later.. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Panic when using QRESYNC
On 10/09/2009 08:56 PM Michael M. Slusarz wrote: > Been seeing these occasionally for the last few weeks. Only way to > fix is to remove cache files in the affected mailbox. Reproduced with > both 1.2.5 and 1.2.6. > > IMAP transaction: > - > > * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID > ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE > CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC > ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in as slusarz > 1 enable qresync > * ENABLED QRESYNC > 1 OK Enabled. > 2 EXAMINE "INBOX" (QRESYNC (1254166848 789 > 1,2,6,7,109,113,193,230,231,279,284)) Hi Michael, maybe Timo has sent his reply only to you. If not: there is patch: imap: Don't crash on SELECT .. QRESYNC if it didn't give seq-uid map. http://hg.dovecot.org/dovecot-1.2/rev/352eab3d6ade Hope that helps Regards, Pascal -- The trapper recommends today: f007ba11.0928...@localdomain.org
Re: [Dovecot] very frequent disconnections
Timo Sirainen writes: > On Wed, 2009-10-07 at 20:55 -0400, Dan Christensen wrote: >> Oct 7 20:19:40 jdc dovecot: IMAP(jdc): Connection closed bytes=303/1423 >> Oct 7 20:44:00 jdc dovecot: IMAP(jdc): Disconnected in APPEND >> bytes=1081/1965 > > The connection just got closed from Dovecot's point of view. > > Have you tried without SSL? The very frequent dropped connections don't happen if I don't use TLS. To summarize: - they happen with TLS to port 143 - they don't happen with a plain connection to port 143 - they don't happen with a TLS connection to port 11143 - they don't happen if I connect using ssh jdc.math.uwo.ca dovecot --exec-mail imap Very strange. I can trigger the drop 100% of the time by copying 20 or 30 messages from a local folder to a remote imap folder. > Anyway I can't think of anything besides some weird network issue or > maybe some firewall/antivirus in the middle. Could be. But now it's clear that it's not affecting all traffic to port 143, only tls traffic. Weird. > Some clients also support "imap over ssh", you could try that. Basically > use "ssh server dovecot --exec-mail imap" as the command. That works well and is also quite fast to connect, so I'll probably stick with it. Thanks for the help, Dan
[Dovecot] Panic when using QRESYNC
Been seeing these occasionally for the last few weeks. Only way to fix is to remove cache files in the affected mailbox. Reproduced with both 1.2.5 and 1.2.6. IMAP transaction: - * PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in as slusarz 1 enable qresync * ENABLED QRESYNC 1 OK Enabled. 2 EXAMINE "INBOX" (QRESYNC (1254166848 789 1,2,6,7,109,113,193,230,231,279,284)) Log output: --- Oct 9 12:49:30 bigworm EXT(slusarz): : /home/slusarz/Maildir/dovecot.index.log: Transaction log changed unexpectedly, can't get modseq Oct 9 12:49:30 bigworm EXT(slusarz): : Panic: file imap-fetch.c: line 227 (get_expunges_fallback): assertion failed: (mail->uid > next_uid) Oct 9 12:49:30 bigworm EXT(slusarz): : Raw backtrace: /usr/lib/dovecot/imap [0x4a199b] -> /usr/lib/dovecot/imap(i_syslog_fatal_handler+0x2b) [0x4a1a5b] -> /usr/lib/dovecot/imap [0x4a10f6] -> /usr/lib/dovecot/imap(imap_fetch_begin+0x6bb) [0x42415b] -> /usr/lib/dovecot/imap(cmd_select_full+0x54a) [0x41e5ba] -> /usr/lib/dovecot/imap [0x420b4d] -> /usr/lib/dovecot/imap [0x420c2d] -> /usr/lib/dovecot/imap(client_handle_input+0x135) [0x420e55] -> /usr/lib/dovecot/imap(client_input+0x5c) [0x42192c] -> /usr/lib/dovecot/imap(io_loop_handler_run+0xbd) [0x4a988d] -> /usr/lib/dovecot/imap(io_loop_run+0x18) [0x4a8d08] -> /usr/lib/dovecot/imap(main+0x531) [0x429441] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x776a09ed] -> /usr/lib/dovecot/imap [0x4199f9] Oct 9 12:49:30 bigworm dovecot: dovecot: child 9556 (imap) killed with signal 6 (core dumps disabled) GDB output: --- Program received signal SIGABRT, Aborted. 0x776b3f15 in raise () from /lib/libc.so.6 (gdb) bt full #0 0x776b3f15 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x776b5340 in abort () from /lib/libc.so.6 No symbol table info available. #2 0x004a19ad in ?? () No symbol table info available. #3 0x004a1a5b in i_syslog_fatal_handler () No symbol table info available. #4 0x004a10f6 in i_panic () No symbol table info available. #5 0x0042415b in imap_fetch_begin () No symbol table info available. #6 0x0041e5ba in cmd_select_full () No symbol table info available. #7 0x00420b4d in ?? () No symbol table info available. #8 0x00420c2d in ?? () No symbol table info available. #9 0x00420e55 in client_handle_input () No symbol table info available. #10 0x0042192c in client_input () No symbol table info available. #11 0x004a988d in io_loop_handler_run () No symbol table info available. #12 0x004a8d08 in io_loop_run () No symbol table info available. #13 0x00429441 in main () No symbol table info available.
Re: [Dovecot] Binary locations
Ed W wrote: > Timo Sirainen wrote: >> Where do you think the following binaries should be installed to? The >> possible locations are: >> >> - bin/ >> - sbin/ >> > > Should these not be /usr/bin and /usr/sbin ? > > I believe that /bin and /sbin are for system essentials and /usr/bin for > package installed binaries? > Timo did not put a leading / in there - I assume that means add your $PREFIX to those paths. ~Seth
Re: [Dovecot] Binary locations
Timo Sirainen wrote: Where do you think the following binaries should be installed to? The possible locations are: - bin/ - sbin/ Should these not be /usr/bin and /usr/sbin ? I believe that /bin and /sbin are for system essentials and /usr/bin for package installed binaries? - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) I haven't read the FHS on these, but empirically this seems to be used only for internal system binaries, ie not executed by the user. On my systems /lib/whatever isn't pathed and so you couldn't run them from a command line I agree that it could be helpful to have a multi-talented admin utility. Additionally don't overlook being able to symlink the binary to some other name and have it execute as this function by name, ie "multicall" a la busybox, etc Cheers Ed W
Re: [Dovecot] Fatal: chdir( ) failed: Permission denied
On Fri, Oct 09, 2009 at 12:14:25PM -0400, Timo Sirainen wrote: > >Oct 9 16:43:49 jura dovecot: dovecot: Fatal: chdir(/a/home/mina) > >failed: Permission denied (euid=1118 > >0(mina) egid=11332(devel) missing +x perm: /a/home) > > Oh, right, this happens before execing imap. Hmm. Well, > mail_drop_priv_before_exec=yes probably helps you. I'll have to > figure out if I should change something here.. > Just FYI, the problem remains after turning the mail_drop_priv_before_exec=yes flag on. -- Vallo
Re: [Dovecot] Fatal: chdir( ) failed: Permission denied
On Oct 9, 2009, at 11:14 AM, Vallo Kallaste wrote: Oct 9 16:43:49 jura dovecot: dovecot: Fatal: chdir(/a/home/mina) failed: Permission denied (euid=1118 0(mina) egid=11332(devel) missing +x perm: /a/home) Oh, right, this happens before execing imap. Hmm. Well, mail_drop_priv_before_exec=yes probably helps you. I'll have to figure out if I should change something here..
Re: [Dovecot] Fatal: chdir( ) failed: Permission denied
On Fri, Oct 09, 2009 at 11:26:19AM -0400, Timo Sirainen wrote: > On Oct 9, 2009, at 11:14 AM, Vallo Kallaste wrote: > > >The reason seems to be that user primary group is "devel" and > >directory /a/home has ACL which gives execute permission only to the > >users in "domain users" group. Now the catch is that the user _is_ > >member of "domain users" group and is happily accessing his home > >directory over CIFS(Samba) for long time. > > What does Dovecot log with auth_debug=yes? > Oct 9 18:53:49 jura dovecot: auth(default): client in: AUTH 1 PLAIN service=imapsecured lip=192.168 .10.3rip=192.168.25.1lport=143 rport=3659 Oct 9 18:53:49 jura dovecot: auth(default): client out: CONT 1 Oct 9 18:53:49 jura dovecot: auth(default): client in: CONT Oct 9 18:53:49 jura dovecot: auth-worker(default): pam(ftest,192.168.25.1): lookup service=dovecot Oct 9 18:53:49 jura dovecot: auth-worker(default): pam(ftest,192.168.25.1): #1/1 style=1 msg=Password: Oct 9 18:53:49 jura dovecot: auth(default): client out: OK1 user=ftest Oct 9 18:53:49 jura dovecot: auth(default): master in: REQUEST36 26941 1 Oct 9 18:53:49 jura dovecot: auth(default): passwd(ftest,192.168.25.1): lookup Oct 9 18:53:49 jura dovecot: auth(default): master out: USER 36 ftest system_groups_user=ftestuid =11745 gid=11332 home=/a/home/ftest Oct 9 18:53:49 jura dovecot: imap-login: Login: user=, method=PLAIN, rip=192.168.25.1, lip=192.168.10.3, T LS Oct 9 18:53:49 jura dovecot: dovecot: Fatal: chdir(/a/home/ftest) failed: Permission denied (euid=117 45(ftest) egid=11332(devel) missing +x perm: /a/home) Oct 9 18:53:49 jura dovecot: dovecot: child 26943 (imap) returned error 89 (Fatal failure) Uid/gid are right, gid=11332 is group "devel". The user has several supplementary groups which are something like this (mangled): jura:~ # id ftest uid=11745(ftest) gid=11332(devel) groups=11332(devel),11812(xxx),11813(xxx_test),10513(domain users),11472(xxxmonitor),11409(monitor),11354(offline_xxx_mon),11323(it),11456(YYY),11237() -- Vallo
Re: [Dovecot] status & use-case of fts_solr?
On Oct 9, 2009, at 12:41 AM, PGNet Dev wrote: if the goal is fast, indexed FTS of dovecot IMAP stores from within a MUA, is fts_solr even helpful? or is it targeted for web interfaces to search ... ? You can add the break-imap-search option and it'll be helpful with those MUAs that use IMAP SEARCH command (Thunderbird I think, but not Apple Mail or Outlook). Ok, clear. So, from a MUA perspective ... *IS* fts_solr faster/better/cheaper/whatever than fts_squat? Depends on what type of search query the user used. It _seems_ that squat is fast, Is it? With my mails it seems to be pretty slow when updating the index. I've been thinking of some way to redesign it because of that. _does_ substring searches, and _is_ under your control in dovecot. Life seems simpler, but just as functional, with "just squat". I'm clearly missing or misunderstanding the "solr advantage" ... Squat also uses more disk space than Solr, I think.
Re: [Dovecot] Using sieve with virtual delivery & maildir
On Oct 8, 2009, at 7:41 AM, Jerry wrote:
I am using Postfix virtual users/domains with Dovecot virtual delivery
to maildir style mailboxes. Now I want to get sieve working to sort
out
a few minor delivery problems.
I want all mail with a message header "Delivered-To: foo
+...@domain.com
placed in the /var/mail/vhost/example.com/foo/new directory.
So basically you just want the +bar part to be ignored? http://wiki.dovecot.org/LDA/Postfix
explains how to configure Postfix to do it ("This example ignores
address extensions" part).
Re: [Dovecot] how to config dovecot for multiple domains, multiple SSL certs, and conditional IP access -- with passwd-file passdb?
On Oct 6, 2009, at 10:05 PM, PGNet Dev wrote:
i'd like to configure dovecot to,
host multiple domains, each on a separate IP
setup a separate SSL cert for each domain
respond with a different login_greeting for each domain
restrict access to, and access type (e.g., TLS req'd vs noTLS,
secure auth OK) of, imap login based with conditional rules based on
the guest's IP address.
Unfortunately Dovecot v1.x can't do any of this, except for "tls
required/not required" part. Upcoming Dovecot v2.0 could do all of
this though. For now you'd have to run a separate Dovecot instance
with a separate config file for each such IP. Or, of course, Dovecot
v2.0 alpha1 should be out pretty soon and testers are always
appreciated. :)
In v2.0 you can do things like:
local_ip 1.2.3.4 {
ssl_cert_file =
Re: [Dovecot] Binary locations
On Oct 6, 2009, at 11:57 AM, Timo Sirainen wrote: On Tue, 2009-10-06 at 11:32 -0400, Timo Sirainen wrote: 1) These probably belong to bin/ or sbin/ or both: - doveadm doveadm is supposed to be this featureful thing that can do all kinds of admin-related stuff. Perhaps one possibility would be to make all of these its subcommands: This is what I ended up doing yesterday. - authtest doveadm auth .. doveadm auth doveadm user - dovecotpw doveadm pw .. Yep. 3) Index file dumping programs, mostly meant for debugging problems: - idxview - listview - logview - mailboxlogview - threadview doveadm dump (automatically detects what type the file is). Yep. 4) Some extra tools that might be useful sometimes: - imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8) doveadm mutf7 .. I'm not sure about this. Doesn't seem like it's much of an "admin" feature. For now it's in libexec/imap-utf7. - maildirlock : Lock a Maildir, primarily intended for compressing files in maildir This could stay separate. Stayed separate.
Re: [Dovecot] Fatal: chdir( ) failed: Permission denied
On Oct 9, 2009, at 11:14 AM, Vallo Kallaste wrote: The reason seems to be that user primary group is "devel" and directory /a/home has ACL which gives execute permission only to the users in "domain users" group. Now the catch is that the user _is_ member of "domain users" group and is happily accessing his home directory over CIFS(Samba) for long time. What does Dovecot log with auth_debug=yes?
Re: [Dovecot] Fatal: chdir( ) failed: Permission denied
On Fri, Oct 09, 2009 at 11:15:29AM -0400, Charles Marcus wrote: > On 10/9/2009, Vallo Kallaste (ka...@estpak.ee) wrote: > > Dovecot fails to chdir() into users home directory giving the following > > error: > > DC version / dovecot -n? Uhm, I'm truly sorry: M$ DC is NT4 with all the patches one can dig up. # 1.2.5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.16 i686 Linux (i586) login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_location: maildir:~/.maildir lda: postmaster_address: postmas...@some.where mail_plugins: sieve mail_plugin_dir: /usr/lib/dovecot/modules/lda auth default: verbose: yes passdb: driver: pam userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve_global_path: /etc/dovecot/sieve/default.sieve sieve_dir: ~/.sieve sieve_global_dir: /etc/dovecot/sieve/global/ -- Vallo
[Dovecot] mail archiving
Im curious if anyone is archiving emails and what they are using. I currently utilize sendmail/procmail/dovecot. thanks, ddh -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante
Re: [Dovecot] Fatal: chdir( ) failed: Permission denied
On 10/9/2009, Vallo Kallaste (ka...@estpak.ee) wrote: > Dovecot fails to chdir() into users home directory giving the following error: DC version / dovecot -n? -- Best regards, Charles
[Dovecot] Fatal: chdir( ) failed: Permission denied
Hi Dovecot fails to chdir() into users home directory giving the following error: Oct 9 16:43:49 jura dovecot: dovecot: Fatal: chdir(/a/home/mina) failed: Permission denied (euid=1118 0(mina) egid=11332(devel) missing +x perm: /a/home) Oct 9 16:43:49 jura dovecot: dovecot: child 14441 (imap) returned error 89 (Fatal failure) The reason seems to be that user primary group is "devel" and directory /a/home has ACL which gives execute permission only to the users in "domain users" group. Now the catch is that the user _is_ member of "domain users" group and is happily accessing his home directory over CIFS(Samba) for long time. Also, the user has no problem entering his home directory when using shell access. It just seems like the user lost membership of a bunch of supplementary groups. The group membership info is coming from M$ PDC via winbind and NSS. We have few users and can change the users primary group and/or relax the /a/home directory ACL, but overall this is not right. Shall I shut up or can we hope for a fix or at least explanation? Thanks jura:/a # ls -la drwxrws--T+ 3 root domain admins 18 Oct 8 15:10 home jura:/a # getfacl home/ # file: home # owner: root # group: domain\040admins user::rwx group::rwx group:domain\040users:--x mask::rwx other::--- -- Vallo
Re: [Dovecot] Bad_MIME on vacation messages
On 10/7/2009, Stephen Vaughan (stephenvaug...@gmail.com) wrote: > We are using Dovecot Sieve 0.1.12, the auto reply message contains ^M > characters at the end of a few lines, they are only visable through vi, > example: So, the solution is to find out what is breaking the headers (adding the ^M characters). You keep assuming it is a dovecot problem, but I don't think it is. You've never posted your vacation or sieve scripts or dovecot -n output (that I can see), so that would be a good place to start. My best guess is its either a bad sieve script or something weird qmail is doing. -- Best regards, Charles
Re: [Dovecot] backup using rsync
Yes. Be sure to check your rsync version. As I recall the 2.x series has bugs related to this. I had a similar problem on MacOS until I upgraded to 3.0.6 and all is well with ':' on MacOS & Ubuntu at this level. Robert Schetterer wrote: Ed W schrieb: Scott Murman wrote: i'm trying to backup the dovecot Maildir files over a cifs share. source is a debian build, share is a readynas. i've been getting rsync: mkstemp 'filename goes here' failed: Not a directory (20) errors. rsync is v3.0. i believe this is related to the dovecot file naming convention that includes characters such as ':' in the filename. anyone else seeing similar behavior? a workaround? i can go to different backup strategies, but rsync is cheap and effective for my needs. thanks, Is backup over ssh an option? Alternatively could you run an rsync server at one end or the other (which then also avoids using cifs in the middle)? Ed W i ll do backups with rsync on maildirs with courier ( which has also : in filenames ) without any problems, as well i backup whole machines including sockets etc without any problems so the problem cant be dovecot here check your rsync version and script i would guess, maybe cifs has problems ..., use ssh ,ftp, nfs etc instead, or backup rsync in a local dir first then tar it followed by copy over cifs just one tar file -- Love feeling your best ever, all day, every day? Click http://RadicalHealth.com for the easy way!
Re: [Dovecot] backup using rsync
Ed W schrieb: > Scott Murman wrote: >> i'm trying to backup the dovecot Maildir files over a cifs share. >> source is a debian build, share is a readynas. i've been getting >> rsync: mkstemp 'filename goes here' failed: Not a directory (20) >> errors. rsync is v3.0. i believe this is related to the dovecot >> file naming convention that includes characters such as ':' in the >> filename. anyone else seeing similar behavior? a workaround? i >> can go to different backup strategies, but rsync is cheap and >> effective for my needs. thanks, >> > > Is backup over ssh an option? > > Alternatively could you run an rsync server at one end or the other > (which then also avoids using cifs in the middle)? > > Ed W i ll do backups with rsync on maildirs with courier ( which has also : in filenames ) without any problems, as well i backup whole machines including sockets etc without any problems so the problem cant be dovecot here check your rsync version and script i would guess, maybe cifs has problems ..., use ssh ,ftp, nfs etc instead, or backup rsync in a local dir first then tar it followed by copy over cifs just one tar file -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria
Re: [Dovecot] Binary locations
On Tuesday 06 of October 2009, Pascal Volk wrote: > On 10/06/2009 05:32 PM Timo Sirainen wrote: > > Where do you think the following binaries should be installed to? The > > possible locations are: > > > > - bin/ > > - sbin/ > > - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) > > > > So the binaries are: > > > > 1) These probably belong to bin/ or sbin/ or both: > > - authtest > > - dovecotpw > > - doveadm > > > > 2) Binaries that you might want to call from mail_executable setting: > > - rawlog > > - gdbhelper > > > > 3) Index file dumping programs, mostly meant for debugging problems: > > - idxview > > - listview > > - logview > > - mailboxlogview > > - threadview > > > > 4) Some extra tools that might be useful sometimes: > > - imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8) > > - maildirlock : Lock a Maildir, primarily intended for compressing > > files in maildir > > > > And perhaps some of the binaries should be renamed? The authtest > > actually now looks like a bad name. Maybe it should have been > > "doveauthtest" or "dovecot-authtest" or ..? > > under $PREFIX/bin: > authtest (or doveauthtest) > dovecotpw > imap-utf7 > maildirlock Nooo, these are too generic names to be in bin (also not $PREFIX/bin but @bindir@ as in autoconf convention). Everything that's not meant to be run by hand should be in @libdir@/dovecot (or @libexecdir@/dovecot). Proposition of "doveadm subcommand" was much nicer than splitting into tons of bin/sbin utils. doveadm subcommand can actually simply call @libdir@/dovecot/subcommand if someone want's separate binaries instead of single one. > Regards, > Pascal > -- Arkadiusz MiśkiewiczPLD/Linux Team arekm / maven.plhttp://ftp.pld-linux.org/
Re: [Dovecot] Bad_MIME on vacation messages
On 10/08/2009 01:57 AM Stephen Vaughan wrote: > Hi, > > I know I've brought this up before (see > http://www.mail-archive.com/dovecot@dovecot.org/msg20974.html), and I've > since upgraded to 1.2.6, but our vacation messages are still being rejected > because of Bad_MIME. > > We are using Dovecot Sieve 0.1.12, the auto reply message contains ^M > characters at the end of a few lines, they are only visable through vi, > example: > > Received: from mail.domain.com (HELO alejandro.domain.com) (123.123.123.123) > by mail.domain.com.au with SMTP; 7 Oct 2009 17:48:13 -0600 > Received: (qmail 3531 invoked from network); 8 Oct 2009 10:48:18 +1100 > Received: from unknown (HELO mail.domain.com.au) (192.168.200.10) > by alejandro.domain.com with SMTP; 8 Oct 2009 10:48:18 +1100 > Received: (qmail 16185 invoked by uid 1007); 8 Oct 2009 10:48:17 +1100 > X-Sieve: Dovecot Sieve 0.1.12^M > Message-ID: ^M > Date: Thu, 08 Oct 2009 10:48:17 +1100^M > From: > To: > Subject: Out of office reply^M > Auto-Submitted: auto-replied (vacation)^M > Precedence: bulk^M > MIME-Version: 1.0^M > Content-Type: text/plain; charset=utf-8^M > Content-Transfer-Encoding: 8bit^M > > Is there someway to fix this? Pretty much every mail server is rejecting the > vacation email's. Hi, sounds interesting, but I can't reproduce it. When you send an email to: dovecot_test + vacation-test @ localdomain . org you will get an auto reply, without CRLFs in the mail header. Maybe qmail is converting the LFs to CRLFs in the mail header. Regards, Pascal -- The trapper recommends today: c01dcofe.0928...@localdomain.org
Re: [Dovecot] backup using rsync
Scott Murman wrote: i'm trying to backup the dovecot Maildir files over a cifs share. source is a debian build, share is a readynas. i've been getting rsync: mkstemp 'filename goes here' failed: Not a directory (20) errors. rsync is v3.0. i believe this is related to the dovecot file naming convention that includes characters such as ':' in the filename. anyone else seeing similar behavior? a workaround? i can go to different backup strategies, but rsync is cheap and effective for my needs. thanks, Is backup over ssh an option? Alternatively could you run an rsync server at one end or the other (which then also avoids using cifs in the middle)? Ed W
Re: [Dovecot] how to config dovecot for multiple domains, multiple SSL certs, and conditional IP access -- with passwd-file passdb?
PGNet Dev wrote: i'd like to configure dovecot to, host multiple domains, each on a separate IP setup a separate SSL cert for each domain respond with a different login_greeting for each domain restrict access to, and access type (e.g., TLS req'd vs noTLS, secure auth OK) of, imap login based with conditional rules based on the guest's IP address. Sensible goals, but somewhere down the path it's going to get awkward for various reasons. One of the things I have toyed with is simply naming the servers something more generic and then using a single set of servers for all domains. The point of the slightly obscure generic domain name is that it doesn't then annoy anyone in particular that the server is named under their competitor's name or whatever Depends how technical the users are, but I would have thought it was fairly rare for people to be investigating and moaning about reverse dns or banners? This potentially saves you a lot of IPs and makes managing multiple hosts a lot easier? Not what you asked, but hopefully an interesting option Good luck Ed W
Re: [Dovecot] Better APPEND performance
Timo Sirainen wrote: On Wed, 2009-10-07 at 17:53 -0500, Mike Abbott wrote: 1. For every other APPENDed message, dovecot appends the new UID to the list quickly. No problem here, this is fast. 2. For every other other APPENDed message, dovecot scans the entire UID list. This is an O(n) algorithm. Since it happens every n/2 times it causes O(n^2) behavior across n consecutive APPENDs. I'll look at this more closely later, but did you already try maildir_very_dirty_syncs=yes? Does this behavior happen also with it? Hello Timo, Also i have observed this behaviour. Although i think it's not the most urgent matter, it would really be nice if you could speed up massive message imports. In our case, we don't use it that much for migration, but sometimes some POP users like to be able to backup their messages in the IMAP server. Thanks in advance, Hugo Monteiro. -- ci.fct.unl.pt:~# cat .signature Hugo Monteiro Email: hugo.monte...@fct.unl.pt Telefone : +351 212948300 Ext.15307 Web : http://hmonteiro.net Centro de Informática Faculdade de Ciências e Tecnologia da Universidade Nova de Lisboa Quinta da Torre 2829-516 Caparica Portugal Telefone: +351 212948596 Fax: +351 212948548 www.ci.fct.unl.pt ap...@fct.unl.pt ci.fct.unl.pt:~# _
Re: [Dovecot] Using sieve with virtual delivery & maildir
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 8 Oct 2009, Jerry wrote:
I am using Postfix virtual users/domains with Dovecot virtual delivery
to maildir style mailboxes. Now I want to get sieve working to sort out
a few minor delivery problems.
I want all mail with a message header "Delivered-To: foo+...@domain.com
placed in the /var/mail/vhost/example.com/foo/new directory.
Hmm, it's my impression that this is no duty for Sieve ... .
Would this work:
require "fileinto";
if anyof (header :contains "Delivered-To" "foo+...@domain.com") {
fileinto "f...@example.com";
stop;
}
Running 'sieve-test' works OK; however, I do not want to implement it
and suddenly start losing mail.
Well, install this script as the personal script of a test account and,
please, tell us the result :)
Bye,
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSs7iPnWSIuGy1ktrAQLInQgArETi3bNzXk6MFOAmtMZ1QIkJ9bPH4rxj
31q3CfNQivmfRENPG3f32mzPybt0b9OreI/jV/Wdc6xr6ZjzeaxxqacCCfE9T7tN
lxXN8vI9bkqYBBd/PUcFERVishYFxLMQH0Nkx7BoW+KcclKfvl1+3T31zBJVFhII
nhdGSW/CywAXBJ2nwJKlsJpKF6HhO7axiic7Fj6pUgkHn7yhaYO473EIDko5rgiF
Jhitn/Mxh28zQ3tAZ+mig1gNItu3k3FqLvHx+QUD3ZrtAGKoojClFGXOD1HtAiNj
0T2k/wncwFsCvJH4KF/QqiLAA8DzHVXS/1cJwWJUQQFDDlkyUHDvIQ==
=qVMT
-END PGP SIGNATURE-
