SASL authentication failure: No worthy mechs found about docker-postfix HOT 2 CLOSED

Thank you for the ticket. Do you have any commits on how to fix the issue?

Thanks,
B

from docker-postfix.

No I don't.

This is thing I think everyone must decide their situation. Maybe best will be not specify at all and let postfix default. But this scenario I not tested. Even do not know if I can unset that variable from ENV vars

Basically if there will be replaced rhat grep from plugins to sasl mech, then it will fill all available sasl. But based on documentationc that can be achieved by using 'static:all' and if there is need to disable somec then use '!disabled-one'

Actually i did not check that oauth2 one, ifnis spelled right.

Actually it works somehow in others because 'plain' is same for plugin name and for mechanism, but for example that crammd5 is different from cram-md5 tbus it not works.

Do not know how other solve that, if they simple goes thru postfix not-recommended way and enables less secure 'plain' auth, so it start work, because of plugin name and sasl mech are same name, thus allowed.

So I think this is more for discussion.

Problem is, many administrators goes just easier way than secure one. Amount of stupid answers on stack overflow proofs that

from docker-postfix.