All rights reserved.
188 | Chapter 5: Authentication and Encryption
Another possible problem might be that the SASL library cannot be found. In that
instance, an error message such as the following might appear:
ld: cannot open -lsasl: No such file or directory
To correct this problem, simply add the following line to your Build m4 file:*
APPENDDEF(`confLIBDIRS??, `-L/disk/3/packages/sasl/lib??)
?†‘
the path to where the SASL library is located
But be careful about where you locate this library. The SASL library is a shared
library and as suchis subject to security restrictions. When sendmail runs, it ignores
LD_LIBRARY_PATH and so cannot find shared libraries that are not in your operating
system??™s default locations. Typically, that trusted location is /usr/lib, and sometimes
/usr/local/lib. If sendmail appears to build correctly, but doesn??™t produce the
AUTH keyword as shown next, the problem might be that your location for the SASL
library is bad.
5.1.2.1 Test SASL support in sendmail
Before you install sendmail, test it to be sure the added SASL support has worked.
You can do this by running sendmail from the directory in which it was built. Note
that you must do this as root:
# obj.*/sendmail/sendmail -bs -Am
Here, we run the newly built sendmail relative to the source directory. The -bs tells
sendmail to speak SMTP on its standard input.
Pages:
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361