Re: Cyrus-imapd2 installed through ports question
Anish Mistry wrote: On Monday 12 January 2004 06:59 pm, Jason Williams wrote: Hello everyone. I was having a problem after I installed cyrus-imapd2 through the ports tree. Everything on the installation went well. However, im seeing a error pop up in my log that I cannot figure out. Thus, I thought i'd ask here, see if anyone had any similiar problems. Note, this is on a FreeBSD 4.9 box: Cyrus-imapd-2.1.16 Cyrus-sasl-2.1.17 BerkeleyDB-4.1.25 This is from my /var/log/auth.log Jan 5 23:54:39 obsidianbox imapd[8015]: OTP unavailable because can't read/write key database /etc/opiekeys: Permission denied Jan 5 23:54:43 obsidianbox imapd[8015]: no user in db I get this too in my logs, but the user is still there, and found by the operation that tries to find the user, and everything still seems to work, so I ignore it and chalk it up to a cyrus bug. Hello, How did you configure sasl? If you by chance include sql support you will get log messages like this and more when you add users to the sasl DB. Auxprop is looking in the sql databases and other places first. If you are getting authenticated, that is all that matters. -- -Ryan Merrick [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Cyrus-imapd2 installed through ports question
Hello everyone. I was having a problem after I installed cyrus-imapd2 through the ports tree. Everything on the installation went well. However, im seeing a error pop up in my log that I cannot figure out. Thus, I thought i'd ask here, see if anyone had any similiar problems. Note, this is on a FreeBSD 4.9 box: Cyrus-imapd-2.1.16 Cyrus-sasl-2.1.17 BerkeleyDB-4.1.25 This is from my /var/log/auth.log Jan 5 23:54:39 obsidianbox imapd[8015]: OTP unavailable because can't read/write key database /etc/opiekeys: Permission denied Jan 5 23:54:43 obsidianbox imapd[8015]: no user in db The first one I figured out a workaround. Simple enough. The second one though, is really driving me up a wall. I'm completely baffled as to why this is showing up my logs. What is very odd, is that I can still connect and authenticate from a mail client. I also get it when I use 'imtest' for basic testing of the server. Lastly, I even get it when I connect to the 'cyradm' interface when I want to manage mailboxes. Yet, I can still login and things work. I've tried a variety of things and nothing seems to be working. Here is what I just did: Did a fresh install of FreeBSD 4.9. CVSup the ports and source tree. Navigated to /usr/ports/mail/cyrus-imapd2 port make -DWITH_BDB_VER=41 -DWITH_SKIPLIST_MBOX -DWITH_SKIPLIST_SEEN -DWITH_MURDER As I type this email, im wondering if it could have been something I did: 1.) I actually edited the Makefile and changed the BDB_VER line from 3 to 41. Looking on my command line option, I specified 41, but I did it with -DWITH. Not sure if that would cause any problems. Anyone have any ideas on why im getting the no user in db entry in my log? I'm at a loss here. Thanks Jason ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cyrus-imapd2 installed through ports question
On Monday 12 January 2004 06:59 pm, Jason Williams wrote: Hello everyone. I was having a problem after I installed cyrus-imapd2 through the ports tree. Everything on the installation went well. However, im seeing a error pop up in my log that I cannot figure out. Thus, I thought i'd ask here, see if anyone had any similiar problems. Note, this is on a FreeBSD 4.9 box: Cyrus-imapd-2.1.16 Cyrus-sasl-2.1.17 BerkeleyDB-4.1.25 This is from my /var/log/auth.log Jan 5 23:54:39 obsidianbox imapd[8015]: OTP unavailable because can't read/write key database /etc/opiekeys: Permission denied Jan 5 23:54:43 obsidianbox imapd[8015]: no user in db I get this too in my logs, but the user is still there, and found by the operation that tries to find the user, and everything still seems to work, so I ignore it and chalk it up to a cyrus bug. -- Anish Mistry pgp0.pgp Description: signature
