I've done a bit of searching, but couldn't find a definate answer to this question.
Is it possible to configure SMTPD to run as a submission agent only? I've got a machine with Scalix on it that I need to run sendmail as the primary SMTP listener (I need to respond to ETRN requests by dequeuing a domain's email).
I had originally set up sendmail to use SASL authentication using the rimap mechanism, which works for non-MD5 authentication schemes, though it does work with LOGIN and PLAIN (after enabling TLS for security). I found that this doesn't work with SWA 11 as it uses DIGEST-MD5. I changed SWA to send mail to port 587, then enabled the submission agent in SMTPD, and it works perfectly.
However, I now get SMTPD listed as Partially Aborted (because sendmail already listens on port 25). I can set SMTPD to use an unused port, but I thought it would be better if there's a way to disable it listening for SMTP requests completely.
On a related note, I've got a different system where I have a better setup (Scalix on the internal LAN, with a sendmail relay on the DMZ). I don't allow any connections from the outside world directly to the Scalix box. However, I need to do SMTP authentication for smartphones connecting directly to my network. SASL and rimap from my DMZ sendmail to the Scalix server doesn't work if the client insists on using CRAM-MD5. Is there a better way to set up authentication? Currently I have created a seperate login mechanism that uses a locally-stored file, but it would be nice to use the same login credentials on IMAP and SMTP.