Carlos E. R. wrote:
Well, I will eventually be setting up TLS encryption for the session, but I'd like to be able to test and make sure SMTP AUTH is working first, it's more of a pain to debug problems when you have 2 variables, as opposed to just one. Having to worry about SASL *and* TLS problems at the same time (possible) is not what I would prefer.
I can not certify that this is the case, but if it is, you have no option. At some point, the developers or suse decided that plain passwords were simply not acceptable, and compiled several packages removing plain password support. If you insist, you have to recompile.
I'm not sure if that happened since SuSE 8.2 or 9.0.
Can't remember for sure if I set up TLS first or if SASL worked before I integrated TLS. Though it won't do harm. Just put the IP address of your test client in the mynetworks in main.cf so you won't have to worry about SASL while you set up TLS. Then, when you have successfully set up TLS you can return to the task to make SASL work. If that does the trick please post the solution to the list. (^-^) Sandy