Just a tiny heads up for -dev. I noticed config.c will bail out when an empty
line is encountered in dbmail.conf.
If we want to provide a well documented dbmail.conf, I think we should allow
empty lines that do not indicate a block ending.
diff -r1.15 config.c
162,163c162,164
< if (strlen(line) == 0 && !isCommentline)
< break; /* empty line specifies ending
*/
---
> // if (strlen(line) == 0 && !isCommentline)
> // break; /* empty line specifies ending
*/
Paul J Stevens wrote:
Actually. It's in better shape than I first thought. I'll start testing
more extensively tomorrow. Don't expect to use dbmail-user as a
replacement for your ldap tools though. Better look at cpu for a compact
commandline tool. But if we can authenticate against ldap, and hookup
the delivery-chain as well, we're all set.
I've designed a example dbmail.schema and have provided a config stanza
in the debian packages dbmail-XXsql-ldap.
Please note that the OID used for the schema is qmail's really. Perhaps
when this is finished I'll reserve a OID in my OID space, or we could
request a dedicated OID from IANA.
Keep you posted.
Paul J Stevens wrote:
Ldap support is currently broken. I've been looking into it this week,
and I've fixed some minor issues.
I don't think anyone is using this at the moment. But I really need
this too.
Sergey Spiridonov wrote:
Hi,
Is there any dbmail+ldap auth documentation? Or at least some examples?
--
Best regards, Sergey Spiridonov
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens [EMAIL PROTECTED]
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands_______________________________________www.nfg.nl
