Testing
Test
Testing
Test
Testing
Test
cvt_cyrusdb_all fails
I'm doing a test upgrade to FC4(installed on a new machine) which includes version 2.3.1 from FC2(on the existing server) which uses version 2.2.12 Oddly enough I managed to get the upgrade to work by manually converting mailboxlist.db and overwriting the new 2.3.1 install, but when I tried to convert deliver.db, everything went pearshaped. I have tried all sorts of ways to get the server back up, but I keep getting pretty fatal errors that are pretty obscure to me. This is the error I got when trying to copy the old lib/spool and just let cvt_cyrusdb_all do the work : cvt_cyrusdb_all version: 1.2.1 db_checkpoint: open: No such file or directory Finding last valid log LSN: file: 3 offset 614 db_recover: Skipping log file /var/lib/imap/db/log.02: historic log version 8 Recovery starting from [3][452] db_recover: /var/lib/imap/tls_sessions.db: unexpected file type or format db_recover: Recovery function for LSN 3 452 failed on backward pass db_recover: PANIC: Invalid argument db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery Finding last valid log LSN: file: 3 offset 614 db_recover: Skipping log file /var/lib/imap/db/log.02: historic log version 8 db_recover: /var/lib/imap/tls_sessions.db: unexpected file type or format db_recover: Recovery function for LSN 3 306 failed db_recover: PANIC: Invalid argument db_recover: DB_ENV->open: DB_RUNRECOVERY: Fatal error, run database recovery ERROR: catastrophic recovery of Berkeley databases failed you are using /var/lib/imap/sieve as your sieve directory. I consistently get the db_checkpoint: open error, but I don't know what it refers to to my knowledge the two machines are essentially identical in configuration and pretty standard. What to do? Henrik 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
Shared folders wild west
I'm trying to figure out how to manage mail folders by testing out a fresh install and replicating the existing accounts over. It may be the fault of the replication script, but it does seem like the server allows creating folders such as: user.info.shared.Promotion and user.info.shared.sales.Sent How do I make sure that such folders cannot be created. As it is it has completely broken folder namespaces. Henrik Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Space in folder names
Is there any way to handle folders with names containing spaces in cyradm, or do I need to create my own tools for that? Henrik Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Spaces in folder names
How do you specify a foldername containing spaces on the cyradm command prompt ? Henrik 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
Re: auth against active directory?
I googled the LDAP config and read through all the how-to's only took me a couple of days to get it working. Mind you that was the first mail server I ever configured. It's still running fine. I think I use the saslauth direct to LDAP auth on Fedora Core 2. I think I installed all rpm's using yum. I do recall it being a bit of a hairy experience until I started building the system up in a very methodical way. One trick is definately to us the testsaslauthd -u user -p pass command. "Bill Kearney" <[EMAIL PROTECTED]> skrev i en meddelelse news:[EMAIL PROTECTED]...>> But since cyrus 2.2 has the ability to speak LDAP directly where's the > need> to use saslauthd any longer?>> - Original Message - >> > Heh, 'easy enough' and LDAP rarely seem to be found together. Throw in> SASL>> > and it /really/ goes downhill.>> >>> > I figure it should be easy but given that I've never actually made a>> > 'generic' LDAP connection to an active directory I'm not entirely sure> where>> > to start. And given the potential for amount of time fiddling with >> > sasl> is>> > known to absorb I'm doubly cautious. I use cyrus-imapd -> saslauthd -> pam_ldap -> iplanet directory server. At our site, we create unix accounts by creating ldap entries in the>> iplanet directory server, then we create matching, synchronized accounts>> in AD for Windows. To the end users, it appears as one account. I don't authenticate against AD for cyrus, but I'm fairly familiar with>> using LDAP to talk to AD. Do you have any specific questions? I know of>> no reason it wouldn't work using pam_ldap as above.> > 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> 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
