This is the backup/replication that we use. Assuming that dovecote uses the same mysql data base and folder structure, I don't think any modifications need to be done to accommodate dovecote. I will hopefully give this a try this week.
http://wiki.qmailtoaster.com/index.php/QMT_Failover_replication_Setup Thanks again. Craig. -----Original Message----- From: Eric Shubert [mailto:[EMAIL PROTECTED] Sent: 05 September 2008 18:13 To: Craig Smith Subject: Re: [qmailtoaster] Some IMAP related queries Craig Smith wrote: > Hi Eric, > > I've been looking into Dovecote, and from a performance point of view it > seems the best bet over courier. I've not been able to install this yet, > but was wondering from your experiences, would I have to adjust my > backup/replication process much? That depends on your backup/replication process, but I doubt that it would change much if any. > How well does Dovecote integrate? In > other words does it use the existing auth model and read qmails mysql data > etc? It integrates very easily. It is capable of authenticating using vpopmail, so it's just a matter of setting up the configuration properly. The documentation is very good, and IIRC has an example of vpopmail configuration. > Basically can you think of any major hurdles I may run into, or does > it run largely the same on the surface as courier but more efficiently. It's about as close to a drop-in replacement as you can get. It will automatically build all of the indexes and such that it needs, on the fly. It fixes itself if/when it sees something wrong. Pretty slick. > A few of our mailboxes are rather large and I like the idea of the faster > server with caching. I'm hoping to have a server next week to install and > test this on, but thought I would ask so I can eliminate a few things. The only thing I can think of that you'll need to decide is whether or not you want to set up your namespaces to be like courier (every subfolder under/within Inbox), or allow users to create subfolders along side of the inbox. I opted for the later, as the courier namespaces really bugged me. If you choose the later, there's nothing really to convert or anything. Might need to change subscriptions on the client side is all. The only difference setting it up is a configuration setting that is well documented. > Thanks again. Sure. Let me know if you need any help, but please keep this sort of thing on the list so others can benefit from the answers too. I like to reserve private consultations for clients. ;) > Craig. > > > -----Original Message----- > From: Eric Shubert [mailto:[EMAIL PROTECTED] > Sent: 02 September 2008 16:25 > To: [email protected] > Subject: Re: [qmailtoaster] Some IMAP related queries > > Craig Smith wrote: >> Hi Eric, >> >> The redundancy is the failover script that is on the wiki. The mysql >> database is exported out and the export file is replicated to the backup >> server. This process works great on our current pop3 server, as far as I >> can see it will work exactly the same on the imap side of things. >> Basically, mysql data exported and migrated to backup server. Qmail > control >> files and /vpopmail/domain folder is also replicated to the backup server. >> In the event of a failure, the backup server's ip is switched to match the >> live server. The mysql data is imported in and qmail services are > started. >> The mysql export/import is the same process as the backp and restore >> scripts. The users folders are generally only ever 15 minutes apart >> (depending on cron timing). >> >> I don't expect anything different but was wondering as we've only recently >> moved to imap if there was anything else I should be aware of. > > I can't think of anything. > >> As for the gui, I'm not holding out much hope for that although it would > be >> nice, what about at least a server based util to setup rules to move mail? >> What is the process that moves spam mails to the spam folder? Could that > be >> adapted? > > Possibly. That would be maildrop-toaster. > > I'm using dovecot in place of courier. I didn't like the way that Courier > requires all user-created folders be subfolders of the Inbox (for starters). > Dovecot also appears to perform better with large folders, handle shared > folders better, is more robust (recovers automatically from any errors), and > is under active development. See http://dovecot.org for more. > > As a result of using Dovecot, I'm also looking to use the accompanying > "deliver" program (Local Delivery Agent), which includes a plugin for the > standard "sieve" programming language. See http://wiki.dovecot.org/LDA/Sieve > for more. This will replace the use of maildrop. > > If you'd like to work on this with me, shoot me an mail off list. > >> Thanks >> >> Craig. >> >> -----Original Message----- >> From: Eric Shubert [mailto:[EMAIL PROTECTED] >> Sent: 01 September 2008 16:57 >> To: [email protected] >> Subject: Re: [qmailtoaster] Some IMAP related queries >> >> Craig Smith wrote: >>> Anyone? :) >>> >>> >>> -----Original Message----- >>> From: Craig Smith [mailto:[EMAIL PROTECTED] >>> Sent: 27 August 2008 16:24 >>> To: [email protected] >>> Subject: [qmailtoaster] Some IMAP related queries >>> >>> Hello all, >>> >>> 2 quick ones. I'm going to be implementing a redundant server for one of >>> our IMAP servers and I was wondering if there is anything I need to be >> aware >>> of that is possibly different in behaviour vs pop3. Jake the replication >>> script I setup, as far as I can see will work fine as it will replicate >> the >>> contents of the users mailfolders is there anything you (or anyone) can >>> think of that I might need to tweak? >> Authentication? >> What sort of redundancy are you implementing? Strictly backup/failover? >> >>> The other query I've had is regarding rules. Is it possible to allow >> users >>> to setup rules directly on the server. So basically, the server will >>> process users rules as mail comes in and put them in various folders >>> accordingly. Our directors have their Iphones setup to the imap server, >> and >>> as long as their clients are running to process email based on rules it's >>> great. However when their client isn't running, they end up with a load >> of >>> rubbish in the inbox. Is there anyway to control that on the server > (this >>> one I'm sure is possible), but allow them to configure it as they need >> with >>> some sort of UI? (this one I'm not so sure of) >> That'd be a great feature for imap users (imho). I don't know of anything > in >> this area off hand, but I haven't looked hard at all. Please keep us > posted >> on this one. >> >>> Hopefully that makes sense. >>> >>> Thanks >>> >> > > -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
