> > The solution: > > 1) Do not enable SASL authentication on port 25. This is > used for mail from the Internet. > > 2) Enable SASL authentication on the submission port. This is > used for user mail clients. An example submission service is > commented out in the default master.cf file. > > As required by RFC 2554, the SMTP server must announce the names > of the available SASL authentication mechanisms in the EHLO response. > Therefore, don't enable SASL authentication on a server that must > be available while the authentication server is down. > > Wietse >
Thank you Wietse for your quick reply as well as for giving us a very nice smtp software. I'll look into configuring via master.cf. Best mr.wu
