So I finally have some time to configure our dev dbmail
config to use LDAP.
Can't seem to get it right though.
Can you take a look at my config file and maybe let me know
what I might be doing wrong, or even if it is an ldap
issue.
Thanks... error and config below
error
www:/etc/ini
If it's the LDAP configuration that's not working, you'd see an error
message about not being able to connect to authentication. If you switch
to authdriver=sql, does it start without error?
Aaron
On Thu, 2006-04-06 at 00:27 -0700, Kevin Baker wrote:
> So I finally have some time to configure our
The following issue has been SUBMITTED.
==
http://www.dbmail.org/mantis/view.php?id=321
==
Reported By:kaname
Assigned To:
===
Perhaps some postgres dba/guru here knows how to do this gracefully:
in dbmail-2.1 the type for the messageblk column in dbmail_messageblks
has been changed from TEXT to BYTEA to accomodate true binary data.
I'm beginning to suspect this may/will lead to problems for people
upgrading from 2.0 to
On Thu, Apr 06, 2006 at 06:53:25PM +0200, Paul J Stevens wrote:
> Perhaps some postgres dba/guru here knows how to do this gracefully:
>
> in dbmail-2.1 the type for the messageblk column in dbmail_messageblks
> has been changed from TEXT to BYTEA to accomodate true binary data.
>
> I'm beginning
I get the same error with both "sql" and "ldap" set to
authdriver.
This is a new install, so I have never had dbmail up on
this machine.
I have all the database tables and permissions set. I can
log into the mysql server with the user perms I created.
strange
Figure I'll try to get everythi
Kevin, did you verify the database parameters? Basically, the error your
seeing is 'dbmail-users -l' failing. If that fails with authdriver=sql,
then I'm guessing your database user hasn't been granted the right
permissions.
Kevin Baker wrote:
> I get the same error with both "sql" and "ldap" set
Ok, I'll go through the perms. I might have missed
something... thanks guys.
Once I get the mysql settings working, I might need a hand
getting the LDap settings right.
--- Paul J Stevens <[EMAIL PROTECTED]> wrote:
>
> Kevin, did you verify the database parameters? Basically,
> the error your