Another possible reason for this error might be that you have not set
up any mechanisms yet. Consider running the saslpasswd2(8) or saslpasswd(8) program
as described in ?§5.1.1 on page 184.
If no SASL lines appear in your syslog file, look for errors relating to permissions.
One possible error might be that the /etc directory is unsafe.* Another might be that
the directory pointed to by the symbolic link /usr/lib/sasl2, or /usr/lib/sasl, is unsafe.
Revise any offending permissions and rerun the test until it succeeds.
If no problems appear in your syslog file, and AUTH still fails to appear, consider
increasing the LogLevel setting in sendmail to 13, while running the test again:
# obj.*/sendmail/sendmail -OLogLevel=13 -bs -Am
Then recheck your logfile for additional error information.
5.1.2.2 Watch authentication in action
To debug authentication before using it to send and receive real email, we recommend
you first set up an authenticating sendmail test daemon that listens on a nonstandard
port and is bound to the loopback interface. That way, you can test without
interfering withreal email on your system. To begin, set up the following minimal
mc configuration file in the cf/cf directory under the sendmail source and call it
test.mc:
OSTYPE(linux)
FEATURE(no_default_msa)
DAEMON_OPTIONS(``A=localhost, P=26, N=authsmtp, M=a????)
MAILER(smtp)
Here, you should replace linux withth e type of your operating system (?§17.
Pages:
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363