Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am setting up a box with Slackware 10.0 (a 2.4 kernel), Sendmail 8.13.8 and Cyrus-SASL 2.1.19 to serve solely as an SMTP outbound MTA for customers, using SMTP AUTH. I have been able to build and install the above packages, and running "saslauthd -a shadow" with a few local test user accounts works like a champ just like it does on every other box I've ever set up. But when I take out those test user accounts and bind to NIS to get the real user data from the main server, SMTP AUTH breaks and I think it's because saslauthd is looking for a "real" shadow file, not the shadow-merged passwd file that NIS provides.
I ran across an article that said to switch the mech for saslauthd to PAM when using LDAP or NIS, but of course PAM is not installed on this Slackware machine and (although this may reveal my mid-to-intermediate skill level) I didn't think NIS had anything to do with PAM. Another article made a reference to being unable to publish just the shadow data, but that article was in a different context altogether than my current problem.
Does anyone know how to get saslauthd to play well on an NIS client so that I can maintain my customer accounts on the main server? My RADIUS servers play nicely with NIS. ;-)
Here are the syslog entries from "messages" when I try to use an email client to authenticate, but I don't get any clues from this:
I came across this question of my own while Googling and realized that I hadn't posted a note that I found the solution. For anyone else who runs across this, the problem was that my Makefile under /var/yp was set such that the passwd/shadow files should be combined. When I changed the MERGE_PASSWD parameter to "false" and ran "make" to publish the changes to the clients, everything started working just fine and my Sendmail SMTP-AUTH/TLS clients could authenticate. My FreeRADIUS servers apparently can handle authentication in either the passwd or shadow paradigm, whereas SASL on my Sendmail box was looking for a shadow file only.