22.12.2024 11:53, Peter via Postfix-users wrote: [people treat dovecot sasl as part of dovecot]
I realize that, but it's fairly easy to implement and easy to configure dovecot to only provide the SASL backend plus it does appear to be the most comprehensive, easiest to implement solution for SASL that Postfix can use at the moment. Perhaps we should make an effort to advertise this as it would seem to alleviate a lot of your concerns.
This is why I thought about using dovecot auth protocol within postfix, dropping everything else, and implementing other solutions if any, like cyrus sasl with its plugins, in a separate postfix daemon, which speaks the same dovecot auth protocol but on the server side. That would be difficult to configure though, having in mind current practices. It's just a thought, I didn't think about it, I just asked (in this thread) if what I feel matches reality of others, and this is something to actually think about or just my imagination. Note again: I didn't know anything about SASL before yesterday.
On a related note, what do you think of libgsasl as an option? Would implementing it give added value to Postfix? Would it be worth the effort and why?
Heh. No idea whatsoever -- this is the first time in my life I see this name :) At least I did see the name SASL (Cyrus and Dovecot) before, so I knew about Dovecot SASL and Cyrus SASL significantly more before yesterday than I do now bout libgsasl :) /mjt _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
