Mail Server Upgrade
Bookmark this URL; if you have problems getting your gigo.com mail (or any other mail hosted at gigo.com), this page should have information you may need.
Status: Done. Everything is back online now.
IMAP/POP3 specifically have been switched from Cyrus to Dovecot. Next weekend I'll likely upgrade the SMTP server, which will remove the last vestigages of any Cyrus gear around.
Webmail was upgraded mildly. The filter stuff, lots of new code if you're accessing it from SquirrelMail (webmail). Things appear to be working.
Hopefully nobody noticed any folder changes - I've set the new software up to expose mailboxes in a compatible way.
Unix users will find their mail in $HOME/Maildir . IF you use procmail, your procmail rules have been updated. I hope to get more documentation up in the next week on what you can do with it (including storing and pop3/imap accessing mailbox format, if you so choose).
http://gigo.com/archives/announcements/mail_server_upgrade.html
My contact info is listed via whois; or you can use:

This is a preemptive change of software to something more easy for me to manage, and consequently, easier to upgrade during emergencies.)
POP3 users: I expect you guys to have no change.
IMAP users: You MAY need to tell your mail client to rescan the folders on the server. You MAY need to actually remove the account, and re-add it. My hope is you don't notice at all.
IMAP users with big folders (100+ megs): You'll probably see greater impact. When I do cut you over, I'll have your most recent mail copied, and your INBOX synced. The catch-up sync may happen after the cutover. IF this is the case ,you may notice that if you deleted a message that it gets resynced from the old server.
SquirrelMail users: I expect no change.
Unix users only: When things are done, pop/imap storage will be moved from the cyrus private directory into your personal $HOME/Maildir/. Contact me if you want mbox format.
Frequently Asked Questions
Why are you doing this?
To simplify the mail server configuration, in the event of a security need to upgrade things in an emergency. My time is limited with my busy work schedule. With the changes I am making, security upgrades should cost me only a few minutes if/when needed. The previous setup was too hard to build and had too many dependencies.
Is the mail server insecure right now?
No. I'm doing this as a preventive measure. The newer software is trivial to upgrade the various components.

Inboxes via IMAP seem to be dong pretty good. Data of subdirs have not copied over the the Mirdir yet. I will be patient. There's going to be either a lag time or loss of email for any IMAP subdirs that use the filters in SquirrelMail as your second mail message did not make it to my main account. It is the only one that moves your mail to another folder.
Please send me details privately. I don't need your password but I do need to know what account, what folder, which rule, etc.
Mail is not lost. It looks like sieve is not honoring views and namespaces correctly, and created $HOME/Maildir/INBOX.INBOX.blah .
working on it.
BTW, the reason for this.. is.. because I made the folders match exactly up for imap. sieve doesn't know better.
Okay, changed the way squirrelmail writes sieve filters to strip the INBOX. prefix, and edited everyone's squirrelmail filters.
All INBOX.*.* mail has been moved up a level.