Re: [Dovecot] lazy_expunge vs mulberry
On April 16, 2007 3:20:10 PM +0300 Timo Sirainen [EMAIL PROTECTED] wrote: On Sun, 2007-04-15 at 23:40 -0700, Frank Cusack wrote: I've configured the lazy_expunge plugin exactly like it says on the wiki. I can't seem to configure Mulberry to find the new namespaces. Any hints? I notice that the wiki says to use / as the separator. Mulberry has a setting for this, and the default is '.'. Leaving this as '.' in Mulberry and / in dovecot seems to work fine. (But I still can't access the .EXPUNGED or other namespaces.) Another page on the wiki says that the default separator for maildir is '.'. Why does the lazy_expunge page suggest using '/'? Well, the feature was developed for one specific user and that example configuration reflects how they wanted to use it. Or possibly the configuration I just happened to use while testing it. Or maybe it was an exact copy of how Cyrus's lazy expunges were explained. I don't remember. Your problem anyway is that hidden=yes makes the namespaces invisible to clients. I'll go remove them. Sure, I realize that. But in the Display Hierarchy dialog, Mulberry has a part to enter additional hierarchies (I guess this is namespaces), that aren't in the top part which is where Mulberry shows the advertised namespaces. When I enter EXPUNGED or .EXPUNGED or .EXPUNGED/ I get a folder in my mailboxes list but no subfolders and no messages in that folder (even though there are messages there). If I remove hidden=yes, Mulberry crashes on login. -frank
Re: [Dovecot] lazy_expunge vs mulberry
On 17.4.2007, at 9.06, Frank Cusack wrote: Your problem anyway is that hidden=yes makes the namespaces invisible to clients. I'll go remove them. Sure, I realize that. But in the Display Hierarchy dialog, Mulberry has a part to enter additional hierarchies (I guess this is namespaces), that aren't in the top part which is where Mulberry shows the advertised namespaces. When I enter EXPUNGED or .EXPUNGED or .EXPUNGED/ I get a folder in my mailboxes list but no subfolders and no messages in that folder (even though there are messages there). If I remove hidden=yes, Mulberry crashes on login. Try using some other names for the namespaces and hidden=no. At least if you're normally using '.' as separator then it's a bad idea to use different separators in different namespaces. And if you're using '.' as separator in those expunge namespaces, it's a bad idea to begin the namespace with a separator. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] timeout error in dovecot.log
On 17.4.2007, at 7.01, 黃家俊 wrote: By the way, can I specify a timeout value for it? #define LOG_DOTLOCK_TIMEOUT 60 in src/lib-index/mail-transaction- log.c. So not without modifying the sources. But lowering that will simply make it fail earlier. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Duplicate E-mail Problem
On 17.4.2007, at 0.11, Phillip T. George wrote: Oh..hmm. I may have left an important part of the log file out...it was previously grepped, but here it is, with the delete line in the middle: Apr 16 12:51:45 east dovecot: IMAP(user.domain.com), IP (70.177.64.93): copy - Spam: uid=718, msgid=[EMAIL PROTECTED] Apr 16 12:51:45 east dovecot: IMAP(user.domain.com), IP (70.177.64.93): deleted: uid=718, msgid=[EMAIL PROTECTED] Apr 16 12:51:45 east dovecot: IMAP(user.domain.com), IP (70.168.68.56): copy - Spam: uid=718, msgid=[EMAIL PROTECTED] deleted means it was marked with \Deleted flag. The message still exists in the mailbox so it can be copied. Only after it's expunged, it's really gone. PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] Public folders using NAMESPACE
On Tue, 2007-04-17 at 02:14 -0700, Joakim Ryden wrote: I've been trying to research how to (or if possible at all) implement public folders using the namespace feature on a server with multiple virtual domains. After about an hour of looking around I'm a little confused. :) Did you read this? http://wiki.dovecot.org/SharedMailboxes I now added a link there from ACL page. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Public folders using NAMESPACE
On Tue, April 17, 2007 2:29 am, Timo Sirainen wrote:
On Tue, 2007-04-17 at 02:14 -0700, Joakim Ryden wrote:
I've been trying to research how to (or if possible at all) implement public
folders using the namespace feature on a server with multiple virtual
domains.
After about an hour of looking around I'm a little confused. :)
Did you read this? http://wiki.dovecot.org/SharedMailboxes
I now added a link there from ACL page.
Thanks Timo! That's pretty helpful. I think I'm still missing something though.
I have the following configuration:
namespace public {
separator = .
prefix = Public Folders.
location = maildir:/var/mailstore/shared-folders/%d/Maildir
}
namespace private {
separator = .
prefix =
inbox = yes
}
With this, Public Folders shows up (testing with Thunderbird) but not as an
italic special folder (does that make sense?) as it does on all other accounts I
have on other servers which support public folders. I created a folder here:
/var/mailstore/shared-folders/domain.com/Maildir/.Announcements
which also shows up nicely, I can copy email in there and subscribe and
unsubsribe to this subfolder, but clicking on Public Folders gives: Mailbox
doesn't exist: Public Folders. which I'm sure is because I've missed or
misunderstood something :) Any ideas?
Cheers!
--Jo
Re: [Dovecot] Public folders using NAMESPACE
On Tue, April 17, 2007 3:48 am, Joakim Ryden wrote:
On Tue, April 17, 2007 2:29 am, Timo Sirainen wrote:
On Tue, 2007-04-17 at 02:14 -0700, Joakim Ryden wrote:
I've been trying to research how to (or if possible at all) implement public
folders using the namespace feature on a server with multiple virtual
domains.
After about an hour of looking around I'm a little confused. :)
Did you read this? http://wiki.dovecot.org/SharedMailboxes
I now added a link there from ACL page.
Thanks Timo! That's pretty helpful. I think I'm still missing something
though.
I have the following configuration:
namespace public {
separator = .
prefix = Public Folders.
location = maildir:/var/mailstore/shared-folders/%d/Maildir
}
namespace private {
separator = .
prefix =
inbox = yes
}
With this, Public Folders shows up (testing with Thunderbird) but not as an
italic special folder (does that make sense?) as it does on all other
accounts I
have on other servers which support public folders. I created a folder here:
/var/mailstore/shared-folders/domain.com/Maildir/.Announcements
which also shows up nicely, I can copy email in there and subscribe and
unsubsribe to this subfolder, but clicking on Public Folders gives: Mailbox
doesn't exist: Public Folders. which I'm sure is because I've missed or
misunderstood something :) Any ideas?
Cheers!
--Jo
Ok, I'm a dumb ass. If I would actually use my eyes I would see:
Another problem is that although the namespace prefix shows up as a normal
looking mailbox, Dovecot doesn't allow subscribing to it because it's not a real
mailbox. This will be fixed in later versions.
on the wiki page. Nevermind me :) I assume this hasn't been fixed yet?
Re: [Dovecot] Public folders using NAMESPACE
On Tue, 2007-04-17 at 03:48 -0700, Joakim Ryden wrote: With this, Public Folders shows up (testing with Thunderbird) but not as an italic special folder (does that make sense?) as it does on all other accounts I have on other servers which support public folders. I think I heard that Thunderbird uses IMAP ACL extension to check if some mailbox is shared or not. Dovecot doesn't support IMAP ACL extension yet. Or it might be something else too I suppose. which also shows up nicely, I can copy email in there and subscribe and unsubsribe to this subfolder, but clicking on Public Folders gives: Mailbox doesn't exist: Public Folders. which I'm sure is because I've missed or misunderstood something :) Any ideas? Well, unfortunately that doesn't work. Dovecot doesn't currently support subscribing to namespace prefixes, only to mailboxes inside the namespace. You might be able to kludge around that by making the subscription go to the private namespace. Either manually updating the subscriptions file, or removing this code from src/imap/cmd-subscriptions.c: if (!client_verify_mailbox_name(cmd, verify_name, subscribe, FALSE)) return TRUE; Actually another problem you're going to have is those shared namespace subscriptions, unless you want to force every user to have same ones. If you don't, you'll need to set CONTROL path to user-specific directory. For Dovecot v1.1 I'll try to figure out how to make all this work better. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] keeping indexes in tmpfs
Daniel L. Miller wrote: Justin McAleer wrote: I have the source mail spools on NFS as well. Just asking - not looking for a flame war. I had a miserable time trying to get NFS working with just my simple LAN - I've had much better results via Samba with either SMBFS or CIFS. Off-topic - but can I ask why you're using NFS? Going back to my first mail, the long and short of it is: However, we plan to run a cluster of these servers anyway, where we will keep domains/accounts going to a particular server but fail over to one of the others in case of an outage. We have a new Netapp, and have been running our email off NFS for years without problems. To be fair, we haven't needed shared storage before, but we spent a lot of money on reliable storage, so there the data stayed. What sort of problems have you run into? So far in my dovecot testing I haven't had any issues either. We did try a few clustered filesystems on a SAN mount instead, but the results were, at best, poor.
Re: [Dovecot] Public folders using NAMESPACE
Timo Sirainen wrote: On Tue, 2007-04-17 at 03:48 -0700, Joakim Ryden wrote: With this, Public Folders shows up (testing with Thunderbird) but not as an italic special folder (does that make sense?) as it does on all other accounts I have on other servers which support public folders. I think I heard that Thunderbird uses IMAP ACL extension to check if some mailbox is shared or not. Dovecot doesn't support IMAP ACL extension yet. Or it might be something else too I suppose. I think you're absolutely right. which also shows up nicely, I can copy email in there and subscribe and unsubsribe to this subfolder, but clicking on Public Folders gives: Mailbox doesn't exist: Public Folders. which I'm sure is because I've missed or misunderstood something :) Any ideas? Well, unfortunately that doesn't work. Dovecot doesn't currently support subscribing to namespace prefixes, only to mailboxes inside the namespace. You might be able to kludge around that by making the subscription go to the private namespace. Either manually updating the subscriptions file, or removing this code from src/imap/cmd-subscriptions.c: if (!client_verify_mailbox_name(cmd, verify_name, subscribe, FALSE)) return TRUE; Hmm, maybe I'm showing my lack of understanding of the inner workings of namespaces here (it is more than slightly possible!) but are you really supposed to be able to subscribe to a namespace? On other servers with this functionality that I have access to I think it's selectable but not subscribable per say. Actually another problem you're going to have is those shared namespace subscriptions, unless you want to force every user to have same ones. If you don't, you'll need to set CONTROL path to user-specific directory. Ah yes, I figured out the user-specific CONTROL and INDEX settings, pretty cool. One question or minor detail about the user-specific INDEX settings: it looks like Dovecot creates index folders for all namespace folders including a folder called .INBOX which seems redundant since the top level namespace (I assume INBOX refers to the top level name space in this case) shouldn't contain any messages, only folders, right? For Dovecot v1.1 I'll try to figure out how to make all this work better. Awesome. Thanks for your patience Timo! Cheers! --Jo
Re: [Dovecot] Time just moved backwards
Chaos Engine wrote: Of course my onboard clock is constantly off by more than 5 secs. I don't want to abandon time synchronization and I want to use dovecot. Maybe a -HUP signal would do? What do you propose? Not too long ago there was a similar question. You can simply recompile dovecot with one of the defines changed to whatever is going to suit you (putting aside that constantly off by 5 sec is just ... strange).
[Dovecot] PAM on AIX - resolved
I previously asked about this problem with pam on IBM's AIX Unix I get the errmsg: auth|security:err|error dovecot-auth PAM: load_modules: can not open module /usr/lib/security/pam_prohibit FWIW, it turned out that the default PAM libraries are 32 bit, while I had compiled DC at 64bit. The /etc/pam.conf lines come standard like this: telnet auth required /usr/lib/security/pam_aix To get 64 bit, you can either change the line like this: dovecot auth required /usr/lib/security/64/pam_aix OR, you can let PAM figure which bit-width library to use dovecot auth required pam_aix Needless to say, it would have been better if the IBM default was the second -- Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 [EMAIL PROTECTED] voice: 845-758-7475, fax: 845-758-7035
Re: [Dovecot] keeping indexes in tmpfs
Justin McAleer wrote: Daniel L. Miller wrote: Justin McAleer wrote: I have the source mail spools on NFS as well. Just asking - not looking for a flame war. I had a miserable time trying to get NFS working with just my simple LAN - I've had much better results via Samba with either SMBFS or CIFS. Off-topic - but can I ask why you're using NFS? Going back to my first mail, the long and short of it is: However, we plan to run a cluster of these servers anyway, where we will keep domains/accounts going to a particular server but fail over to one of the others in case of an outage. We have a new Netapp, and have been running our email off NFS for years without problems. To be fair, we haven't needed shared storage before, but we spent a lot of money on reliable storage, so there the data stayed. What sort of problems have you run into? So far in my dovecot testing I haven't had any issues either. I had issues just trying to get it to work at all. Either portmap wouldn't start, wouldn't share, wouldn't talk - something. Or I'd get it to work, and then my joke of a wiring closet would get bumped and the clients would freeze when their connection was interrupted. That last was actually one of my biggest problems (admittedly not an NFS fault - but an NFS overreaction). When the wires were repaired NFS settled down - but I had far more success with Samba, including automatically restoring broken connections without having the clients re-mount and/or re-boot. -- Daniel
Re: [Dovecot] Time just moved backwards
On 09/04/2007 03:24, Sean Kamath wrote: On Apr 8, 2007, at 2:20 PM, Bill Cole wrote: It is important for people to understand how much simpler it is now to run basically functional and non-abusive NTP than it was even 5 years ago. The work put into making pool.ntp.org usable has essentially eliminated the need to think much about NTP for most sites. Absolutely! It's been standard on Macs for some time (it's how it syncs with time.apple.com, etc). Ditto Windows XP, from time.windows.com. If MS can manage it, we surely can. Cheers, John.
[Dovecot] v1.1 plans
I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to update index file handling to use less locks and update dovecot.index file less often. The file formats would still stay backwards compatible with v1.0. After this I'm hoping to get index files working well with NFS even with attribute cache enabled. Dovecot v2.0 then brings incompatible index files and more or less rewritten configuration file handling. It could still support old config file format and settings, but the default will be somewhat different. I'm hoping to release the first alphas/betas in 2-3 months, with v1.1.0 maybe even as early as next summer. The good thing here is that index file code hasn't changed much since v1.0, so it should be stable. The bad thing is that I've added a couple of completely new indexes. I'm also quite busy for the next month, but I'm not sure how much it affects my coding. :) The largest already implemented new features are: + Added support for IMAP UIDPLUS extension + IMAP SORT: Sort keys are indexed, which makes SORT commands faster. + IMAP THREAD: Threads are indexed into a dovecot.index.thread file. It can usually be updated incrementally, so this makes THREAD fast. + Added Dovecot-specific X-REFERENCES2 threading algorithm. It's similar to REFERENCES, but it doesn't do base subject merging and it sorts the threads by their newest message. + When saving messages, update cache file immediately with the data that we expect client to fetch later. Maildir-only currently. + Mailbox list indexes. Mailbox metadata is stored there, so STATUS commands can return synchronized mailboxes' metadata simply by reading a single mailbox list index file. - FIXME: Currently works only with Maildir++ layout. + Expire plugin can be used to keep track of oldest messages in specific mailboxes. A nightly run can then quickly expunge old messages from the mailboxes that have them. The tracking is done using lib-dict, so you can use either Berkeley DB or SQL database. + Namespaces are supported everywhere now. - FIXME: except by convert plugin + Full text search indexing support with Lucene and Squat backends. + OTP and S/KEY authentication mechanisms (by Andrey Panin). + mbox and Maildir works with both Maildir++ and FS layouts. You can change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to mail_location. Features that I'm planning on implementing: - Fully supported shared mailboxes and IMAP ACL extension - Replace Squat FTS indexes with my new design - Case-insensitive searches with non-ASCII text as well - Maybe add support for all kinds of IMAP extensions that can be easily supported. LEMONADE extensions especially: CONDSTORE, CATENATE and maybe even URLAUTH if I can figure out how it should work. If a feature can be implemented completely as a plugin, it could still come in v1.1.beta stage, because it won't destabilize the rest of the Dovecot anyway. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1 plans
Timo Sirainen wrote: Features that I'm planning on implementing: - Fully supported shared mailboxes and IMAP ACL extension - Replace Squat FTS indexes with my new design - Case-insensitive searches with non-ASCII text as well - Maybe add support for all kinds of IMAP extensions that can be easily supported. LEMONADE extensions especially: CONDSTORE, CATENATE and maybe even URLAUTH if I can figure out how it should work. If a feature can be implemented completely as a plugin, it could still come in v1.1.beta stage, because it won't destabilize the rest of the Dovecot anyway. In my testing of using sql dictionary for quota, it appears pretty buggy. Are you aware of such problems? Either way, would you consider reliable dictionary quota support a target for 1.1? I did find that it seemed to blow maildir++ away in terms of performance. We have a few really large maildirs that basically choke when quota is enabled using maildir++ (200,000+ messages). On top of the performance gains, gathering disk usage for billing changes from parsing hundreds of thousands of maildirsize files (and du -s or equivalent for those really large maildirs, ugh) to a single sql query, Even more, we could explore enforcing quota on our mail gateways if they just need a sql connection for realtime usage info. So, as you can imagine, I would love to be able to use dictionary in a production environment :) And just to be clear, I am not trying to demand that any of this gets priority or anything, just trying to gauge your intentions and maybe throw out some ideas to show the potential value :) Congrats on hitting 1.0.0.
Re: [Dovecot] v1.1 plans
On Tue, 2007-04-17 at 15:41 -0400, Justin McAleer wrote: In my testing of using sql dictionary for quota, it appears pretty buggy. Are you aware of such problems? Either way, would you consider reliable dictionary quota support a target for 1.1? Actually I think I did it today. The biggest problem with v1.0 implementation was that expunges could be counted multiple times if multiple processes were running. I ran imaptest for a while with 10 connections and in 3 different tests the dict quota always contained correct values, so I thought it was probably working. I did find that it seemed to blow maildir++ away in terms of performance. We have a few really large maildirs that basically choke when quota is enabled using maildir++ (200,000+ messages). Even if filenames had the ,S=size? Another problem is that the quota is read, and possibly recalculated, much more often than is really necessary.. I haven't fixed that yet in v1.1. signature.asc Description: This is a digitally signed message part
[Dovecot] v1.1 plans - sieve?
In the 1.1 plans (http://dovecot.org/list/dovecot/2007-April/021974.html) I don't see any mention of sieve... is this intentional? Sieve support is a priority for me... I'm going to have to see if I can get it via exim's support if dovecot's not going to add it in 1.1. Cheers, David
Re: [Dovecot] v1.1 plans
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Sirainen schrieb: I think I won't do any actual releases until it's mostly feature complete. Then maybe v1.1.alpha1 or v1.1.beta1. So if you want to test it before then, use CVS or the nightly snapshots. I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. I want to update index file handling to use less locks and update dovecot.index file less often. The file formats would still stay backwards compatible with v1.0. After this I'm hoping to get index files working well with NFS even with attribute cache enabled. Dovecot v2.0 then brings incompatible index files and more or less rewritten configuration file handling. It could still support old config file format and settings, but the default will be somewhat different. I'm hoping to release the first alphas/betas in 2-3 months, with v1.1.0 maybe even as early as next summer. The good thing here is that index file code hasn't changed much since v1.0, so it should be stable. The bad thing is that I've added a couple of completely new indexes. I'm also quite busy for the next month, but I'm not sure how much it affects my coding. :) The largest already implemented new features are: + Added support for IMAP UIDPLUS extension + IMAP SORT: Sort keys are indexed, which makes SORT commands faster. + IMAP THREAD: Threads are indexed into a dovecot.index.thread file. It can usually be updated incrementally, so this makes THREAD fast. + Added Dovecot-specific X-REFERENCES2 threading algorithm. It's similar to REFERENCES, but it doesn't do base subject merging and it sorts the threads by their newest message. + When saving messages, update cache file immediately with the data that we expect client to fetch later. Maildir-only currently. + Mailbox list indexes. Mailbox metadata is stored there, so STATUS commands can return synchronized mailboxes' metadata simply by reading a single mailbox list index file. - FIXME: Currently works only with Maildir++ layout. + Expire plugin can be used to keep track of oldest messages in specific mailboxes. A nightly run can then quickly expunge old messages from the mailboxes that have them. The tracking is done using lib-dict, so you can use either Berkeley DB or SQL database. + Namespaces are supported everywhere now. - FIXME: except by convert plugin + Full text search indexing support with Lucene and Squat backends. + OTP and S/KEY authentication mechanisms (by Andrey Panin). + mbox and Maildir works with both Maildir++ and FS layouts. You can change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to mail_location. Features that I'm planning on implementing: - Fully supported shared mailboxes and IMAP ACL extension - Replace Squat FTS indexes with my new design - Case-insensitive searches with non-ASCII text as well - Maybe add support for all kinds of IMAP extensions that can be easily supported. LEMONADE extensions especially: CONDSTORE, CATENATE and maybe even URLAUTH if I can figure out how it should work. If a feature can be implemented completely as a plugin, it could still come in v1.1.beta stage, because it won't destabilize the rest of the Dovecot anyway. Hi Timo, - - Fully supported shared mailboxes and IMAP ACL extension will be very nice will you include some quota warn code to lda like maildrop does ? - -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGJTznfGH2AvR16oERAl+qAJ48qfm6XpfupgDCoWujZf3v3TNwJgCeJfeU EIbbGAv5F+GdzzBiD+bel5I= =KQKu -END PGP SIGNATURE-
Re: [Dovecot] v1.1 plans - sieve?
On Tue, 17 Apr 2007 22:30:38 +0100 David Anderson [EMAIL PROTECTED] wrote: In the 1.1 plans (http://dovecot.org/list/dovecot/2007-April/021974.html) I don't see any mention of sieve... is this intentional? Sieve support is a priority for me... I'm going to have to see if I can get it via exim's support if dovecot's not going to add it in 1.1. Cheers, David Dovecot has had Sieve support for quite some time. It is mentioned on the download page. Download Sieve plugin v1.0.1 for Dovecot's local delivery agent. http://wiki.dovecot.org/LDA/Sieve !DSPAM:20,46254065212871570999577!
Re: [Dovecot] v1.1 plans
On Tue, 2007-04-17 at 23:32 +0200, Robert Schetterer wrote: will you include some quota warn code to lda like maildrop does ? There's already a patch for that in v1.0. So yes, I'll most likely include that to v1.1 once it gets ported. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] lazy_expunge vs mulberry
On April 17, 2007 11:21:14 AM +0300 Timo Sirainen [EMAIL PROTECTED] wrote: On 17.4.2007, at 9.06, Frank Cusack wrote: Your problem anyway is that hidden=yes makes the namespaces invisible to clients. I'll go remove them. Sure, I realize that. But in the Display Hierarchy dialog, Mulberry has a part to enter additional hierarchies (I guess this is namespaces), that aren't in the top part which is where Mulberry shows the advertised namespaces. When I enter EXPUNGED or .EXPUNGED or .EXPUNGED/ I get a folder in my mailboxes list but no subfolders and no messages in that folder (even though there are messages there). If I remove hidden=yes, Mulberry crashes on login. Try using some other names for the namespaces and hidden=no. At least if you're normally using '.' as separator then it's a bad idea to use different separators in different namespaces. And if you're using '.' as separator in those expunge namespaces, it's a bad idea to begin the namespace with a separator. Yeah, actually I adjusted all the names and separators as well and still no luck (should have mentioned that earlier). However, after trying to revert to my previous config, I found that diddling the separator made my entire Mailder inaccessible until I removed dovecot-uidlist. So I probably need to revisit this. -frank
Re: [Dovecot] v1.1 plans
I'd like dovecot to have option '-e' to edit configs like postfix has. I understand dovecot configs are much more complex and have nested blocks. But may be double-colon notation to qualify identifiers by block names will work, like: --- dovecot -e 'socket listen::client::path=/tmp/dovecot-auth-client' -- Sergey Ivanov
Re: [Dovecot] v1.1 plans - sieve?
On Tuesday 17 Apr 2007, Brad wrote: Dovecot has had Sieve support for quite some time. It is mentioned on the download page. Download Sieve plugin v1.0.1 for Dovecot's local delivery agent. http://wiki.dovecot.org/LDA/Sieve Sorry... I know about and am using the sieve plugin... I should have said MANAGESIEVE. I realise there's a patch for that, but I was wondering if something's going to make it into 1.1. David
Re: [Dovecot] v1.1 plans - sieve?
On Tue, 2007-04-17 at 22:59 +0100, David Anderson wrote: Sorry... I know about and am using the sieve plugin... I should have said MANAGESIEVE. I realise there's a patch for that, but I was wondering if something's going to make it into 1.1. I don't think so. I want to distribute it with Sieve plugin, and that pretty much requires changes that come only in v2.0. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1 plans
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Timo Sirainen schrieb: On Tue, 2007-04-17 at 23:32 +0200, Robert Schetterer wrote: will you include some quota warn code to lda like maildrop does ? There's already a patch for that in v1.0. So yes, I'll most likely include that to v1.1 once it gets ported. Thx Timo , thats nice - -- Mit freundlichen Gruessen Best Regards Robert Schetterer https://www.schetterer.org Munich/Bavaria/Germany -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGJUpxfGH2AvR16oERAn8UAJ4nsha7CxYo+PcbR64wU76LgImYbACfXWwc O3VUhOjhfIGQbFtzHExiFzA= =SL68 -END PGP SIGNATURE-
Re: [Dovecot] v1.1 plans
On Tue, 2007-04-17 at 21:46 +0300, Timo Sirainen wrote: I'm planning on keeping v1.1 almost completely compatible with v1.0. There could be some minor configuration file changes, but for most people v1.0's dovecot.conf should work with v1.1. Please, this needs to be Everyone's v1.0 dovecot.conf will work in v1.1. If you're going to change the configuration file format even in some subtle way, please bump the major version. Likewise with plugin support... if you're going to break API or ABI, please bump the major version. It's easy enough to avoid breaking compatibility gratuitously. People do not expect configuration files to need changing between minor releases and they'll be quite upset if things break. Richard signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.1 plans
I want to update index file handling to use less locks and update dovecot.index file less often. The file formats would still stay backwards compatible with v1.0. After this I'm hoping to get index files working well with NFS even with attribute cache enabled. Music to my ears - as im sure with many other NFS sites. Regards __ Dean Manners
[Dovecot] help with static userdb
Hey,
This may be a dumb question... I'm trying to set up 1.0 with a static
userdb, and I'm getting stuck. I have:
userdb static {
args = uid=500 gid=500 home=/domains/%d/%n
}
When I attempt to log in as, say, [EMAIL PROTECTED] (via telnet, so
I *know* I'm logging in as that user), the debug log says that it
thinks my home directory is /domains//kyle.
I even tried, just to check what might be going on:
args = uid=500 gid=500 home=/domains/%u/%d/%n
It then thought my home directory was /domains/kyle//kyle.
Can anyone help me? Where might that be getting cleared?
~Kyle
--
The more men you make free, the more freedom is strengthened and the
... greater is the security of the State.
-- Frederick Douglas, Nov 17, 1864
pgp4bFGKR5Irj.pgp
Description: PGP signature
Re: [Dovecot] v1.1 plans
On Tuesday, April 17 at 05:58 PM, quoth Sergey: I'd like dovecot to have option '-e' to edit configs like postfix has. I understand dovecot configs are much more complex and have nested blocks. But may be double-colon notation to qualify identifiers by block names will work, like: --- dovecot -e 'socket listen::client::path=/tmp/dovecot-auth-client' I would like that too---it would make supporting multiple virtual domains with different SSL keys (on different IP addresses, obviously) MUCH easier. Currently I need to maintain separate config files for each. ~Kyle -- Power always thinks it has a great soul and vast views beyond the comprehension of the weak; and that it is doing God's service when it is violating all his laws. -- John Adams pgpHefOQ33HE2.pgp Description: PGP signature
Re: [Dovecot] v1.1 plans - sieve?
On Tuesday 17 April 2007 16:13, Timo Sirainen wrote: On Tue, 2007-04-17 at 22:59 +0100, David Anderson wrote: MANAGESIEVE I don't think so. In the meantime you can use pysieved. The 1.0 release should be out any day now. http://woozle.org/~neale/src/pysieved Neale
