8 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Invalid User
FromSent OnAttachments
Dan HorneMar 13, 2006 1:31 pm 
Sam VarshavchikMar 13, 2006 3:41 pm 
Joey TeelMar 13, 2006 3:56 pm 
Dan HorneMar 14, 2006 6:07 am 
Devin RubiaMar 14, 2006 7:46 am 
Dan HorneMar 14, 2006 8:42 am 
Dan HorneMar 14, 2006 10:09 am 
Sam VarshavchikMar 14, 2006 2:59 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Invalid UserActions...
From:Devin Rubia (dev@thezone.net)
Date:Mar 14, 2006 7:46:42 am
List:net.sourceforge.lists.courier-maildrop

On Tue, Mar 14, 2006 at 09:07:30AM -0500, Dan Horne wrote:

-----Original Message----- From: cour@lists.sourceforge.net [mailto:cour@lists.sourceforge.net] On Behalf Of Joey Teel Sent: Monday, March 13, 2006 6:56 PM To: Sam Varshavchik Cc: cour@lists.sourceforge.net Subject: Re: [maildropl] Invalid User

[...]

If I'm right and the OP is using the ports system they need to remove both ports and cd into the ports directory for courier-authlib first and run make config to reconfigure the port to include mysql support as (unless this changed recently) it only includes userdb support if you tell it install as part of the maildrop install rather than as its own step.

Once the courier-authlib port is installed, the maildrop port should then be reinstalled with the WITH_AUTHLIB="yes" option set.

You are right, I am using the ports system. I have already done exactly as you suggested. Courier-authlib has mysql support, as my OP indicated that an "authtest" worked and that I could log into the same accounts using courier-IMAP (which of course uses courier-authlib). So courier-authlib has a good configuration because it can auth the mysql-based accounts perfectly. I'm guessing the problem is one of two things:

1) incorrect maildropmysql configuration file (as I said I don't know where this file should go, nor what it should be named, nor how to tell maildrop where to find it. I can't find any documentation on it, I don't even know if it is used. I see it in many How-To's though.)

As Sam has already said YOU DON'T NEED THOSE FILES. If authlib works and authlib support is built into maildrop, it should work.

Run "maildrop -v" and see if authlib support is actually enabled.

2) missing files: My OP stated that a ktrace on "maildrop -d us@example.com" showed maildrop trying to find files called nss_nis.so.1 and nss_compat.so.1. It wasn't able to find either of these files anywhere in the path. I think this is probably the most likely cause of the problem, but those files aren't on my system anywhere.

Run "ldd `which maildrop`". That will tell you if any libraries are missing. Those files won't be in your path; they're libraries and will be in places like /lib /usr/lib, among others.