Re: [Dovecot] Conditionally use a sieve script with deliver?
On Thursday 21 January 2010 11:13:22 Marcus Rueckert wrote: On 2010-01-20 21:11:59 +, Kārlis Repsons wrote: I found a post in this list [0], which says sieve scripts can be used to deliver mail as read. However, can it be done somehow conditionally, I mean, with a direct or indirect switch for deliver? For a nonexistent example, it would be simply | deliver -m path/to/maildir -r or maybe an environment variable could be exported to deliver sieve and checked there? (Still not sure if sieve can replace maildrop in my case, however, using it with dovecot creates various problems with interoperability; but perhaps I can just add those imap4flags like \\seen myself to the message with maildrop and avoid mess with sieve at all?) [0] http://www.dovecot.org/list/dovecot/2008-July/032294.html just curious: what stops you from migrating your maildrop rules to sieve? darix [not about dovecot here] My silly and honest answer is: the fact, that I found maildrop first some weeks ago and it seemed very flexible (a feeling of security in a sense, that I won't have any impossible thing), but then I came across the mentioned problem and still I haven't learned much about sieve. So, if I have some 50KB of mailfilter rules, which I want to divide across a tree of filter files, each of which can inherit variables from their includers, handle mailinglists, sometimes deliver copies to multiple maildirs, is there a reasonable chance I can do with sieve? signature.asc Description: This is a digitally signed message part.
[Dovecot] ldap and mail_location
hi.. im running dovecot 1.2.9 and checking against an openldap. i defined in dovecot.conf mail_location = maildir:/mail/%u and now all mails are stored under /mail/my.e...@mydomain.com how can i store them in /mail/ldapuid ? these userdb and passdb settings drive me crazy.. looks like ldap is a bigger thing then i thougt :) thx
Re: [Dovecot] ldap and mail_location
hi again.. user_filter = ((objectClass=gosaMailAccount)(|(mail=%u)(gosaMailAlternateAddress=%u))) this works to check if the account is valid but i cant figure out how to set the maillocation i think this is done in user_attrs but no idea how to use the uid. i tryed user_attrs = home=maildir:/mail/%uid but that did not work. i tryed also to add a (..(uid=%uid)) to the user_filter but no luck.. any hinds or tips 2010/1/21 spamv...@googlemail.com: hi.. im running dovecot 1.2.9 and checking against an openldap. i defined in dovecot.conf mail_location = maildir:/mail/%u and now all mails are stored under /mail/my.e...@mydomain.com how can i store them in /mail/ldapuid ? these userdb and passdb settings drive me crazy.. looks like ldap is a bigger thing then i thougt :) thx
Re: [Dovecot] Conditionally use a sieve script with deliver?
On 2010-01-21 12:06:33 +, Kārlis Repsons wrote: My silly and honest answer is: the fact, that I found maildrop first some weeks ago and it seemed very flexible (a feeling of security in a sense, that I won't have any impossible thing), but then I came across the mentioned problem and still I haven't learned much about sieve. So, if I have some 50KB of mailfilter rules, which I want to divide across a tree of filter files, each of which can inherit variables from their includers, handle mailinglists, sometimes deliver copies to multiple maildirs, is there a reasonable chance I can do with sieve? it mostlikely is. but without knowing the exact script it is hard to say yes. atleast all my maildrop rules work in sieve. darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org
Re: [Dovecot] ldap and mail_location
ok.. sry for spam.. figured it out.. user_attrs = homeDirectory=home,uid=mail=maildir:/mail/%$ 2010/1/21 spamv...@googlemail.com: hi again.. user_filter = ((objectClass=gosaMailAccount)(|(mail=%u)(gosaMailAlternateAddress=%u))) this works to check if the account is valid but i cant figure out how to set the maillocation i think this is done in user_attrs but no idea how to use the uid. i tryed user_attrs = home=maildir:/mail/%uid but that did not work. i tryed also to add a (..(uid=%uid)) to the user_filter but no luck.. any hinds or tips 2010/1/21 spamv...@googlemail.com: hi.. im running dovecot 1.2.9 and checking against an openldap. i defined in dovecot.conf mail_location = maildir:/mail/%u and now all mails are stored under /mail/my.e...@mydomain.com how can i store them in /mail/ldapuid ? these userdb and passdb settings drive me crazy.. looks like ldap is a bigger thing then i thougt :) thx
Re: [Dovecot] Maildir and IMAP keywords
On Thu, 2010-01-21 at 10:25 +0100, Per-Erik Persson wrote: When a user in thunderbird toggles some flags like junk, spam or something similar dovecot appends these flags form a-z to the end of the file in maildir. I have another application that also access the maildirs which gets really upset with these flags and ignore those emails. Are there any other way for dovecot to store these flags to make it compatible with other softwares? I thought that a..z way was the most compatible way, because Maildir spec says New flags may be defined later. I've never before heard that some software didn't like them. How about fixing that one software instead? signature.asc Description: This is a digitally signed message part
[Dovecot] feature question: local delivery from SMTP
Does Dovecot really need a separate MTA for inbound mail? Or can it receive SMTP directly if there is no forwarding to do? What about spam/virus filtering in that case? -- Phil Howard KA9WGN - ka9...@gmail.com
Re: [Dovecot] 1.2.9 imap crash with backtrace
* Timo Sirainen t...@iki.fi: This should fix it (and hopefully doesn't expose another bug): http://hg.dovecot.org/dovecot-1.2/rev/a1177c6cf8c7 I think that fixes all of the duplicate entry in uidlist errors that have been reported recently. So please test soon and report how it goes over a few days, and I'll release 1.2.10. I applied it today. Let's see how it goes. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
[Dovecot] Fastest restart of dovecot after upgrade: HOW?:
I'm running dovecot under runit: #!/bin/sh echo '/var/core/%p' /proc/sys/kernel/core_pattern ulimit -n 8096 ulimit -c unlimited exec /usr/local/sbin/dovecot -F (that way, together with incron, I can automatically generate the coredumps I'm posting all the time) If I apply a patch and recompile, what is the fastest way of restarting dovecot? Which part of the process structure can be killed and takes all it's children with it? ├─runsvdir─┬─runsv───ntpd │ ├─runsv─┬─dovecot─┬─2*[dovecot-auth] │ │ │ ├─1203*[imap] │ │ │ ├─64*[imap-login] │ │ │ ├─64*[managesieve-log] │ │ │ └─64*[pop3-login] │ │ └─svlogd killall dovecot? Is that guaranteed to wipe out ALL child processes as well? I had to use (at least in the past): sv d /var/service/dovecot killall dovecot killall -9 imap-login ps auxwww|grep dovecot to make sure everything would be dead... -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] Fastest restart of dovecot after upgrade: HOW?:
On 21.1.2010, at 16.35, Ralf Hildebrandt wrote: Which part of the process structure can be killed and takes all it's children with it? ├─runsvdir─┬─runsv───ntpd │ ├─runsv─┬─dovecot─┬─2*[dovecot-auth] │ │ │ ├─1203*[imap] │ │ │ ├─64*[imap-login] │ │ │ ├─64*[managesieve-log] │ │ │ └─64*[pop3-login] │ │ └─svlogd killall dovecot? Is that guaranteed to wipe out ALL child processes as well? If you set shutdown_clients=yes. Although even with =no it should stop listening. I had to use (at least in the past): sv d /var/service/dovecot killall dovecot killall -9 imap-login ps auxwww|grep dovecot to make sure everything would be dead... I guess there can be bugs.. But in general the processes should notice immediately that master died, and immediately close their listeners and optionally shut down.
Re: [Dovecot] Fastest restart of dovecot after upgrade: HOW?:
* Timo Sirainen t...@iki.fi: If you set shutdown_clients=yes. Although even with =no it should stop listening. shutdown_clients=yes is the default? I think it is :) I guess there can be bugs.. But in general the processes should notice immediately that master died, and immediately close their listeners and optionally shut down. In some cases that didn't happen with the imap processes. Anyway. I'll just try it now. -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] feature question: local delivery from SMTP
On Qua, 20 Jan 2010, Phil Howard wrote: Does Dovecot really need a separate MTA for inbound mail? Or can it receive SMTP directly if there is no forwarding to do? What about spam/virus filtering in that case? Dovecot does not receive mails. It only serves them to users via IMAP or POP3. So, yes, you need a program like exim or postfix. -- BOFH excuse #424: operation failed because: there is no message for this error (#1014) Eduardo M KALINOWSKI edua...@kalinowski.com.br
Re: [Dovecot] Conditionally use a sieve script with deliver?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 21 Jan 2010, Kārlis Repsons wrote: My silly and honest answer is: the fact, that I found maildrop first some weeks ago and it seemed very flexible (a feeling of security in a sense, that I won't have any impossible thing), but then I came across the mentioned problem and still I haven't learned much about sieve. So, if I have some 50KB of mailfilter rules, which I want to divide across a tree of filter files, each of which can inherit variables from their includers, handle mailinglists, sometimes deliver copies to multiple maildirs, is there a reasonable chance I can do with sieve? Well, if you have a running maildrip infrastructure, I would not change it. If you need your users have hack their own, I probably would go with Sieve, because the times I used maildrop most of the users - if touching the script - broke it. Sieve is more restricted, IMHO, and therefore more save if users hack their own. E.g. you cannot run external programs, which probably is a major security risk. One thing, that Sieve is not able to do, is to deliver to multiple users without re-sending the mail. Regards, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBS1hwRr+Vh58GPL/cAQIGNAgAoYla45q3Zc8P+e4a/dagDdVSBIH4KePd NuOxrsCsX/ra0FZSt2xILbzFqCsx+Kx0krnFNrJjgiSlJHWddNHRFoWY+tzP/u/S HjLmqv5Q5q4zj+n9IbroXNufFhfnhPQJRLnjRflbazyyPybDq1nK/nxtNmCfo3AP 9rZ1gC3m6XtLFBHlcWwVuGzeATxa657g+ESA+NzYPtMRBQPXkyFiZNN4SmViVpx1 FqQNOk5iG+EZPYsOcjBTiqgDwtS3vunu39B2OM3MybsvCFQNfHWgrl2GPv8bO8Cc WQQBFfBr5YQyVxKIoXOkMe7nYNOWMQgZfsGwfHO6QBF4mQuydEj5ng== =RWMc -END PGP SIGNATURE-
Re: [Dovecot] 1.2.9 imap crash with backtrace
Good news and bad news. The good news is that I've been core dump free for about 24 hours. The duplicate message issue is still there, so if you wanted that fix then I guess the patch is not complete yet, otherwise it looks good. The bad news is that I'm now convinced that another problem I've been experiencing is real and not related to any of this since it's still persists. Randomly for a few releases now myself and my coworkers have been seeing a weird bug where old mail marked as read suddenly becomes marked as new again when going into a folder. Sometimes it's as bad as the entire folder deciding it is all unread when in fact is was all read, other times it's randomly a few pieces of mail that constantly revert to unread status. I've watched this on my personal server as well as heard complaints from our user population. I don't believe this is an NFS issue because my personal account is a standalone server with both a local index and maildir running 1.2.9. Also, I'm only ever connected from one place at a time. Just this morning when I got to work I logged in with Thunderbird and my dovecot mailing list folder suddenly had 3,000 new messages in it, all of which had been previous read. I marked the folder as read, then a little while later I went into the older and they all reverted to new again. I've also seen it where if I try deleting one of these messages marked as new, it disappears for a second, then magically reappears in my folder as new. Unfortunately, I'm not seeing a single log message related to this. As you can tell, I watch the logs like a hawk, yet nothing ever appears to throw an error or any message whatsoever. All my test cases have been with Thunderbird 3.0, I'm not sure if other clients are seeing this. Any idea? On 01/20/2010 01:45 PM, Timo Sirainen wrote: On 20.1.2010, at 20.24, David Halik wrote: Jan 20 13:13:59 gehenna13.rutgers.edu dovecot: IMAP(user): /rci/nqu/rci/u2/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 3: 1259771459.M806388P24066V04240001I002E8FC6_0.gehenna7.rutgers.edu,S=3927:2,S (uid 8420 - 9532) .. Notice it's dump free at the end! ;) Well, that's good, although I had also hoped that the Duplicate file entry errors would have gone away. -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] 1.2.9 imap crash with backtrace
On 21/01/2010 17:53, David Halik wrote: Good news and bad news. The good news is that I've been core dump free for about 24 hours. The duplicate message issue is still there, so if you wanted that fix then I guess the patch is not complete yet, otherwise it looks good. The bad news is that I'm now convinced that another problem I've been experiencing is real and not related to any of this since it's still persists. Randomly for a few releases now myself and my coworkers have been seeing a weird bug where old mail marked as read suddenly becomes marked as new again when going into a folder. Sometimes it's as bad as the entire folder deciding it is all unread when in fact is was all read, other times it's randomly a few pieces of mail that constantly revert to unread status. I've watched this on my personal server as well as heard complaints from our user population. I don't believe this is an NFS issue because my personal account is a standalone server with both a local index and maildir running 1.2.9. Also, I'm only ever connected from one place at a time. Just this morning when I got to work I logged in with Thunderbird and my dovecot mailing list folder suddenly had 3,000 new messages in it, all of which had been previous read. I marked the folder as read, then a little while later I went into the older and they all reverted to new again. I've also seen it where if I try deleting one of these messages marked as new, it disappears for a second, then magically reappears in my folder as new. Unfortunately, I'm not seeing a single log message related to this. As you can tell, I watch the logs like a hawk, yet nothing ever appears to throw an error or any message whatsoever. All my test cases have been with Thunderbird 3.0, I'm not sure if other clients a re seeing this. Hello, same problem here. I use Thunderbird 3.0.1. The strange thing is that with the same version of TB on my PC at home I don't have this issue. The same TB on my work PC has this issue and only on one account (that has Dovecot as imap server) but I have other account (some with dovecot, other with courier-imap) where this does not happen, so I think is TB related. Also here no NFS, ext3.
Re: [Dovecot] 1.2.9 imap crash with backtrace
On 21.1.2010, at 19.10, David Halik wrote: This seems to have started since TB 3.0 came out. Especially, with the new indexing feature they added. I'm not seeing it with Pine or SQMail accessing the same servers. The problem is all my users are convinced it's my mail servers. ;) However, it does seem to only happen with my dovecot backends. I haven't seen this with my non-dovecot accounts. Is it possible the TB 3.0 has some issues with dovecot specifically that we're not aware of? QRESYNC maybe?
Re: [Dovecot] 1.2.9 imap crash with backtrace
On 21.1.2010, at 19.13, Timo Sirainen wrote: On 21.1.2010, at 19.10, David Halik wrote: This seems to have started since TB 3.0 came out. Especially, with the new indexing feature they added. I'm not seeing it with Pine or SQMail accessing the same servers. The problem is all my users are convinced it's my mail servers. ;) However, it does seem to only happen with my dovecot backends. I haven't seen this with my non-dovecot accounts. Is it possible the TB 3.0 has some issues with dovecot specifically that we're not aware of? QRESYNC maybe? CONDSTORE I mean. Looks like others have had the same problem: http://getsatisfaction.com/mozilla_messaging/topics/thunderbird_3_rc1_seems_to_be_having_problems_keeping_read_messages_marked_as_read
[Dovecot] Dovecot SNMP
Hi folks, Today I setup Cacti for my environment and I was wondering if there are some templates/scripts for Cacti or SNMP I could use to gather some statistics from Dovecot. Thanks in advance. BR Chris
Re: [Dovecot] 1.2.9 imap crash with backtrace
On 01/21/2010 12:14 PM, Timo Sirainen wrote: On 21.1.2010, at 19.13, Timo Sirainen wrote: On 21.1.2010, at 19.10, David Halik wrote: This seems to have started since TB 3.0 came out. Especially, with the new indexing feature they added. I'm not seeing it with Pine or SQMail accessing the same servers. The problem is all my users are convinced it's my mail servers. ;) However, it does seem to only happen with my dovecot backends. I haven't seen this with my non-dovecot accounts. Is it possible the TB 3.0 has some issues with dovecot specifically that we're not aware of? QRESYNC maybe? CONDSTORE I mean. Looks like others have had the same problem: http://getsatisfaction.com/mozilla_messaging/topics/thunderbird_3_rc1_seems_to_be_having_problems_keeping_read_messages_marked_as_read Yep, this is definitely the same problem. https://bugzilla.mozilla.org/show_bug.cgi?id=517461 Apparently, the fix was supposed to happen in 3.0.1. but people are still reporting the problem. At least they're aware of it and working on it. Thanks Timo. -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] 1.2.9 imap crash with backtrace
Am 21.01.2010 18:14, schrieb Timo Sirainen: On 21.1.2010, at 19.13, Timo Sirainen wrote: On 21.1.2010, at 19.10, David Halik wrote: This seems to have started since TB 3.0 came out. Especially, with the new indexing feature they added. I'm not seeing it with Pine or SQMail accessing the same servers. The problem is all my users are convinced it's my mail servers. ;) However, it does seem to only happen with my dovecot backends. I haven't seen this with my non-dovecot accounts. Is it possible the TB 3.0 has some issues with dovecot specifically that we're not aware of? QRESYNC maybe? CONDSTORE I mean. Looks like others have had the same problem: http://getsatisfaction.com/mozilla_messaging/topics/thunderbird_3_rc1_seems_to_be_having_problems_keeping_read_messages_marked_as_read There is a bug report for Thunderbird 3.0 and CONDSTORE: https://bugzilla.mozilla.org/show_bug.cgi?id=524902 Setting mail.server.default.use_condstore = false in Thunderbird disables CONDSTORE support and gets rid of this issue...
[Dovecot] nologin in auth proto version 1.1
I notice that the nologin parameter for the AUTH command is gone in version 1.1 of Dovecot Authentication Protocol. nologin was added in 1.1, so that authentication client could indicate that there will be no subsequent master requests to retrieve user info. Could we have nologin back please? Kirill
Re: [Dovecot] nologin in auth proto version 1.1
* Kirill Miazine [2010-01-21 21:09]: I notice that the nologin parameter for the AUTH command is gone in version 1.1 of Dovecot Authentication Protocol. nologin was added in 1.1, so that authentication client could indicate I meant 1.0, of course. that there will be no subsequent master requests to retrieve user info. Could we have nologin back please? Kirill
Re: [Dovecot] nologin in auth proto version 1.1
On 21.1.2010, at 22.09, Kirill Miazine wrote: I notice that the nologin parameter for the AUTH command is gone in version 1.1 of Dovecot Authentication Protocol. nologin was added in 1.1, so that authentication client could indicate that there will be no subsequent master requests to retrieve user info. Could we have nologin back please? Where do you see nologin ever mentioned in authentication protocol? I don't see it in v1.0's auth-protocol.txt. It's still working, it's just not really part of the protocol itself.
Re: [Dovecot] nologin in auth proto version 1.1
* Timo Sirainen [2010-01-21 22:17]: On 21.1.2010, at 22.09, Kirill Miazine wrote: I notice that the nologin parameter for the AUTH command is gone in version 1.1 of Dovecot Authentication Protocol. nologin was added in 1.1, so that authentication client could indicate that there will be no subsequent master requests to retrieve user info. Could we have nologin back please? Where do you see nologin ever mentioned in authentication protocol? I don't see it in v1.0's auth-protocol.txt. It's still working, it's just not really part of the protocol itself. Quoting yourself: But I think this should be fixed so that it's not necessary to do it. So I added a new nologin field to AUTH request. If it's used, the request will be freed immediately when authentication is finished. So v1.0.11 will have it (whenever it gets released..) as well as the next v1.1.beta.
Re: [Dovecot] nologin in auth proto version 1.1
On 21.1.2010, at 22.38, Kirill Miazine wrote: Could we have nologin back please? Where do you see nologin ever mentioned in authentication protocol? I don't see it in v1.0's auth-protocol.txt. It's still working, it's just not really part of the protocol itself. Quoting yourself: But I think this should be fixed so that it's not necessary to do it. So I added a new nologin field to AUTH request. If it's used, the request will be freed immediately when authentication is finished. So v1.0.11 will have it (whenever it gets released..) as well as the next v1.1.beta. Anyway, like I said, it's not gone. It just was never added to the document. Maybe it should be mentioned there.
Re: [Dovecot] nologin in auth proto version 1.1
Ok, I didn't understand it wasn't gone. I only read the doc today :) * Timo Sirainen [2010-01-21 22:58]: On 21.1.2010, at 22.38, Kirill Miazine wrote: Could we have nologin back please? Where do you see nologin ever mentioned in authentication protocol? I don't see it in v1.0's auth-protocol.txt. It's still working, it's just not really part of the protocol itself. Quoting yourself: But I think this should be fixed so that it's not necessary to do it. So I added a new nologin field to AUTH request. If it's used, the request will be freed immediately when authentication is finished. So v1.0.11 will have it (whenever it gets released..) as well as the next v1.1.beta. Anyway, like I said, it's not gone. It just was never added to the document. Maybe it should be mentioned there.
Re: [Dovecot] 1.2.9 imap crash with backtrace
Hi! I'm pretty unsure this is only a TB3 problem. Saw the same result with TB 2.0, but I'm unsure if this was after changing something on the server. After 2 days of mailproblems we downgraded back to Dovecot 1.1 yesterday and no one reported this bug since this downgrade. Greetings, Thorsten
Re: [Dovecot] IMAP only for some users or via webmail
It's always worth searching the mailing list to see if the question's already been asked You don't say how you run your authentication backend. I'll hazard a guess that you're using MySQL, in which case you should see http://old.nabble.com/Allow-POP3-per-Domain-td27143238.html for reference. In your case, you'll just have to adapt the SELECT statement somewhat. Ronald. Ronald MacDonald : +44-7772-351655 ron...@rmacd.com : http://www.rmacd.com 4/1 Gillespie Crescent, Edinburgh EH10 4HT 2010/1/21 Federico Tomasczik ftomasc...@gmail.com: Hello! First, sorry for my English... I'm a newbie with Dovecot and I have some questions, I'm testing Dovecot 1.1.11 in a virtual machine. I wish in the future, migrate this to a real server. Ok, but i need this: 1) A group of users can use IMAP or POP3. 2) The others, only can use POP3. But, this users can use IMAP only with a webmail (the webmail is in the same server that Dovecot) It is possible? How? Thanks! Federico Ch. Tomasczik
Re: [Dovecot] IMAP only for some users or via webmail
On 22.1.2010, at 0.51, Federico Tomasczik wrote:
1) A group of users can use IMAP or POP3.
2) The others, only can use POP3. But, this users can use IMAP only
with a webmail (the webmail is in the same server that Dovecot)
It is possible? How?
If you're using SQL, you can do something iike:
password_query = .. where ('%s' != 'imap' or imap_allowed=true or '%r' =
'127.0.0.1') and ..
The idea being that your webmail connections are coming from 127.0.0.1 and
they're always allowed.
Re: [Dovecot] IDLE timing issue - dovecot or fetchmail issue?
I haven't reported this to the fetchmail developers, but I will now that I've confirmed it's their bug. For those interested, I've raised this on the fetchmail list here: https://lists.berlios.de/pipermail/fetchmail-users/2010-January/002183.html With the help of Timo and the fetchmail devs, this issue has now been fixed and will be included in fetchmail 6.3.14. See the post to fetchmail list: https://lists.berlios.de/pipermail/fetchmail-users/2010-January/002238.html Thanks, Matt
Re: [Dovecot] virtual mailbox / INTHREAD use case, issues, questions
At Tue, 19 Jan 2010 16:51:04 +0200, Timo Sirainen wrote: On Wed, 2010-01-06 at 11:50 -0500, David Abrahams wrote: At Wed, 6 Jan 2010 14:17:40 +0200, Timo Sirainen wrote: On 4.1.2010, at 20.47, David Abrahams wrote: 1. I had to manually create the virtual folder for all my users or they couldn't access their mail at all. Is this fixed in 2.0? No. OK, is it considered a bug that should be addressed? IMO there should at least be a way to tell dovecot to ignore the non-existence of a particular folder. Actually it looks like v2.0 just creates the directory if it's missing. I'm not really sure if it's a good thing or not, but I guess I moved that part of the code to be common across all storages, so maybe it's good. :) Well, my inclination would be to ignore missing directories until you try to do something with them. If I set up a fancy virtual folder arrangement for advanced users I'd like ordinary users not to ever have to encounter it. lots of mailboxes should cause error to be logged. What does the error look like? I could search my logs for it. Easiest would be to make Dovecot log errors to a different file (log_path to different than info_log_path). Then you wouldn't have to search for errors, simply see if anything shows up in the error log. I'll try that, thanks. If you want to grep, I suppose anything with Error: or Fatal: or Panic: prefix would do. Nothing in the current logs, but they may have been rotated out. 7. I tried to create an IMAP search, rather than a virtual folder, that looked for x-mailbox INBOX header like the virtual folder does. It too came up empty. It doesn't exactly surprise me because I don't see an x-mailbox header in any of these messages. x-mailbox doesn't use a header, it uses the actual mailbox name where the message exists. Oh... what if the message exists in multiple mailboxes? Typically anything in INBOX can also be found in my all mail archive. .. I guess that means it's crucial that, whatever else I do, INBOX should be part of the all mail virtual folder in order for this to work. I didn't quite understand that before, and I think it's important to have a description somewhere of how x-mailbox works that would help me to get to that conclusion. Certainly the existing description at http://wiki.dovecot.org/Plugins/Virtual that it represents the original mailbox isn't adequate for that purpose. Hmm. If you're making a virtual mailbox out of another virtual mailbox, I'm not entirely sure what X-MAILBOX should do. Currently it returns the parent virtual mailbox's name. But should it instead return the mailbox name that physically contains the mails? I'm beginning to think that it probably should. Why? Because fetching from there will be faster? Having got the x-mailbox insight (I think---thanks), I have tried the following combinations: # ~/Maildir/virtual/INBOX/dovecot-virtual INBOX zz_archive* inthread refs x-mailbox inbox shows only messages in INBOX. THe archives are actually in folders like zz_archive.2010.01 Is this fast or slow then? Oh, perfectly fast, but also perfectly ineffective :-) # ~/Maildir/virtual/all/dovecot-virtual * all # ~/Maildir/virtual/INBOX/dovecot-virtual virtual.all inthread refs x-mailbox inbox Appears to hang It's probably going to take a while to build the thread index. After that it should be pretty fast. It would be easier to see how far it gets by talking imap: a login username password b select virtual.all c thread refs all d select virtual.INBOX a login username pw a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH] Logged in b select virtual.all closed (boom!) I guess that explains my problem... after a fashion. Ah, my error file contains lots of these: Jan 21 18:06:01 IMAP(dave): Error: mmap() failed with index cache file /home/dave/Maildir/.zz_archive.2009.06/dovecot.index.cache: Cannot allocate memory Jan 21 18:06:01 IMAP(dave): Fatal: pool_system_realloc(1048576): Out of memory Okay, I bumped up mail_process_size from 256 to 1024 and it seems not to be bailing out quite so soon. b select virtual.all * FLAGS (\Answered \Flagged \Deleted \Seen \Draft unknown-3 unknown-5 unknown-6 $Forwarded $NotJunk unknown-0 unknown-2 NonJunk NotJunk gnus-forward $Junk Junk gnus-download gnus-save unknown-1 $Label1 JunkRecorded $MDNSent unknown-4 gnus-expire unknown-8 receipt-handled) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft unknown-3 unknown-5 unknown-6 $Forwarded $NotJunk unknown-0 unknown-2 NonJunk NotJunk gnus-forward $Junk Junk gnus-download gnus-save unknown-1 $Label1
