Re: Cyrus / Sieve
Jogi Hofmüller wrote: We are using postfix/cyrus here where postfix is delivering mail locally via lmtp and cyrus authenticates Users using saslauthd/pam. In a testing environment we are experimenting with LDAP at the moment and it works quite nicely. I got to setup a postfix/cyrus-system in a few weeks too. I already installed a testsystem and had no problems. Since both postfix and cyrus do have a sasl-mysql-plugin, I chose this solution over saslauthd/pam. But the more I read about cyrus, be it on a mailinglist or elsewhere, it seems to me that everybody uses cyrus in combination with saslauthd/pam. Is there some good reason not to use the mysql-plugins? (AFAIK it's the same with LDAP.) Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which SATA RAID controller?
Hi! What would be the disadvantage of a ICH5-R based RAID (ships with many mainboards) over a Promise pseudo-hardware-RAID? Does anybody know wether you can hot-swap with a ICH5-R/Promise-System or even Linux-Software-RAID, or not? Regards, Michael Kreilmeier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Which SATA RAID controller?
Hi! What would be the disadvantage of a ICH5-R based RAID (ships with many mainboards) over a Promise pseudo-hardware-RAID? Does anybody know wether you can hot-swap with a ICH5-R/Promise-System or even Linux-Software-RAID, or not? Regards, Michael Kreilmeier
Re: Moving Sites
Stupid Question: I have about 50 web sites and a few hundred e-mail accounts to move to a new server. New IP address, etc... Web sites are no problem, but I do not want my clients to notice any problems with e-mail. They have IMAP available, so many of the clients store their e-mail on the server. Any ideas on how to move the e-mail accounts seamlessly. I have all their MX records pointing to one address: mail.dailydata.net. I have rsync'd all the files over, and can do it again whenever, but that won't work as they will be checking their mail on one machine while, I assume, some might be delivered to the other, older server (I was planning on keeping the old server up a few days in case I screw up). Guess is boils down to this. When I update the address of mail.dailydata.net, it can take up to 72 hours for that change to perculate throughout the net, so I'm assuming some places will still try to send to the old IP and, if I leave that box on, be delivered to it. If I turn the other box off, I'm assuming they will bounce. You could set the refresh-, retry-, expire- and minimum-values in your dns-zone-file to low values (at least 72 hours before you change the mx-entry). When you choose an expire-value of 2h, your changes will take effect throughout the net within 2 hours. I never tried this out, but it works in theory:) Michael Kreilmeier. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Moving Sites
Stupid Question: I have about 50 web sites and a few hundred e-mail accounts to move to a new server. New IP address, etc... Web sites are no problem, but I do not want my clients to notice any problems with e-mail. They have IMAP available, so many of the clients store their e-mail on the server. Any ideas on how to move the e-mail accounts seamlessly. I have all their MX records pointing to one address: mail.dailydata.net. I have rsync'd all the files over, and can do it again whenever, but that won't work as they will be checking their mail on one machine while, I assume, some might be delivered to the other, older server (I was planning on keeping the old server up a few days in case I screw up). Guess is boils down to this. When I update the address of mail.dailydata.net, it can take up to 72 hours for that change to perculate throughout the net, so I'm assuming some places will still try to send to the old IP and, if I leave that box on, be delivered to it. If I turn the other box off, I'm assuming they will bounce. You could set the refresh-, retry-, expire- and minimum-values in your dns-zone-file to low values (at least 72 hours before you change the mx-entry). When you choose an expire-value of 2h, your changes will take effect throughout the net within 2 hours. I never tried this out, but it works in theory:) Michael Kreilmeier.
