On Tue, Sep 13, 2022 at 6:41 AM Henning Follmann <hfollm...@itcfollmann.com>
wrote:
>
> >
> > So I guess my question is, do I need one now on the Bullseye server, if
> > saslauthd always worked for this before?
> >
>
> OK, that's an option too.
>
> Now I would check if sasl works. There is an little helper program; try:
> testsaslauthd -u <username> -p <password>
>
> you might have to specify the location (-f path) of the unix socket if it
> is located
> somewhere uncommon.
>
> If your authentication works then the communication between sendmail and
> saslauthd
> is not working.
>
Hello,
The testsaslauthd utility was also working, so the break was between
Sendmail and SASL. I finally got it working, though. A Google search led
me to these three commands, and running them indeed fixed gthe issue:
/usr/share/sendmail/update_tls
/usr/share/sendmail/update_sendmail
sendmailconfig
All of the config and .m4 files involved here still look the same between
the old and new server, with the exception of some updated comments. So,
I'm not exactly sure what this did to fix the underlying problem, but it's
fixed nonetheless.
Thanks!
Dave
--
Dave Parker '11
Database & Systems Administrator
Utica University
Integrated Information Technology Services
315-792-3229
He/Him
