RE: High availability email server...
Hi, you can also use DRBD for replication on the block level. Then you need no SAN and have a shared nothing architecture. You will need a high speed link between the sites (GBIT). An alternative is a SAN with replication. You can also use md for this purpose (host based SAN raid). Two cheap MSA 1000/1500 will do just fine. We have done a installation with 2 MSA 1500 san arrays mirrored with MD on the host level in production since 1 year. Runs without a problem. There are aprox. 3500 active users on the servers. Exim and other services (e.g. LDAP) are also protected in the cluster. We used SteelEye LifeKeeper as cluster software. Contact me if you need more information. Regards, Robert Heinzmann COMPUTER CONCEPT CC Computersysteme und Kommunikationstechnik GmbH Robert Heinzmann Wiener Str. 114 - 116 Email: [EMAIL PROTECTED] 01219 Dresden Telefon:+49 (0)351/8 76 92-0 Telefax:+49 (0)351/8 76 92-99 Internet: http://www.cc-dresden.de -Ursprüngliche Nachricht- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Chris St. Pierre Gesendet: Freitag, 28. Juli 2006 15:12 An: Chad A. Prey Cc: info-cyrus@lists.andrew.cmu.edu Betreff: Re: High availability email server... Chad-- We've put /var/lib/imap and /var/spool/imap on a SAN and have two machines -- one active, and one hot backup. If the active server fails, the other mounts the storage and takes over. This is not yet in production, but it's a pretty simple setup and can be done without running any bleeding edge software, and it appears that it will work fine. There's no need to use a SAN, either -- you could share your mail storage out via NFS with the same effect. We're going production with this in mid-August; if you'd like to know how everything goes, drop me a note in a month or so. Chris St. Pierre Unix Systems Administrator Nebraska Wesleyan University On Thu, 27 Jul 2006, Chad A. Prey wrote: Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
ipurge / cyr_expire with recursion
Hello, I have a problem with ipurge and cyr_expire (cyrus 2.2.3 from SuSE SLES 9). We have the requirement to delete all e-Mails in a users INBOX (non recursive) and the users SPAM and TRASH folders (recursive) after 90 day. Mails in folders created by the users should not be deleted. Lets say the user has the following folder structure: INBOX (*) |- Mailinglists |- Apache |- Tomcat |- Archive |- October |- November |- Spam (*) |- Jan (*) |- ... (*) |- Dec (*) |- Trash (*) All mail in folders marked with a (*) that are older than 90 days should be deleted. If the user creates a folder TEST it should look like this (no automatic deletion of mails in TEST): INBOX (*) |- Mailinglists |- Apache |- Tomcat |- Archive |- October |- November |- Spam (*) |- Jan (*) |- ... (*) |- Dec (*) |- Trash (*) |- TEST All mails in the SPAM and TRASH folders should be deleted recursivly -- This is working well with ipurge and the pattern user.%.Spam and user.%.Trash ipurge -d 10 -f 'user.%.Spam' Working on user..Spam... total messages 20 total bytes 5438 Deleted messages 9 Deleted bytes2446 Remaining messages 11 Remaining bytes 2992 Working on user..Spam.X... total messages 19 total bytes 5186 Deleted messages 8 Deleted bytes2183 Remaining messages 11 Remaining bytes 3003 The deletion of mails in the INBOX should NOT be recursive, because it would be fatal. -- This is not possible with ipurge, because it always works recursivly To solve this issue I thought about using the cyr_expire cron job. I can mark a mailbox with the expire flag (mailboxcfg user. expire 90), but the problem here is, that this is also recursive. To get the solution I have I would have to do the following: mailboxcfg user. expire 90 mailboxcfg user..* expire 0 mailboxcfg user..Trash* expire 90 mailboxcfg user..Spam* expire 90 This sets the right expiration dates I want as info user.* shows. Also cyr_expire deletes all the e-Mails accordingly. The problem with this solution is, that if a user creates a Mailbox, it automatically inherits the expiration settings of the parent. If the folder is created below the INBOX, all mails in this folder are also deleted after 90 days -- PROBLEM. So none of the two solutions is working a 100% ok (of course I could set up a cron job always running before the cyr_expire job setting the expiration date for all Mailboxes that do not already have a expiration date associated to 0. This is error prone: - The job setting expiration dates for all folders not having a expiration date associated yet runs - A user creates a mailbox and copies all of ist mails to this new folder (archiving) - The job cyr_expire runs and deletes all e-Mails older that 90 days (UUPS!) Is there any other way to get this working with cyrus 2.2.3 ? Does a later version of cyrus provide this feature ? Regards, Robert COMPUTER CONCEPT CC Computersysteme und Kommunikationstechnik GmbH Robert Heinzmann Wiener Str. 114 - 116 Email: [EMAIL PROTECTED] 01219 Dresden Telefon:+49 (0)351/8 76 92-0 Telefax:+49 (0)351/8 76 92-99 Internet: http://www.cc-dresden.de Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
