On Wed, Apr 08, 2009 at 03:32:19AM -0600, LuKreme wrote:
> On 7-Apr-2009, at 18:07, Victor Duchovni wrote:
>> You may be running into Berkeley DB cache consistency issues, using
>> SQL is probably a better idea. Does pbs support SQL?
>
> I don't think so.
That's too bad because concurrent R/O readers and writers of Berkeley DB
tables don't always work as well as one might hope with modern Berkeley
DB versions. NetBSD ships 1.86 in good part because it is plain/simple
Berkeley DB and probably does not have mmapped tables, page pools, ...
and will probably not exhibit cache coherence issues. PBS wants to
do incremental updates of the database, so build/rename is not a good
option. Focus your energies on SASL.
>> In any case, PBS is a hack, use SASL.
>
> Yeah, I've been trying to get SASL working for quite a long time. I have
> passwords stored in MySQL in md5-crypt and have been trying to get some
> sort of authentication to work other than via courier-imap-imapd-ssl. Still
> no luck on that score.
The best way to bootstrap SASL is to first get it working with the sample
server and client outside the MTA. Once you have a working SASL system,
integrate that with Postfix. Don't do everything at the same time.
MySQL can be a tricky back-end for SASL, consider other options, LDAP,
Kerberos, rimap, ...
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
