I have been plowing through the knowledge base....
I have my external users (me included when on the road) doing SMTP auth. (the one user that was giving me grief turned out to have all SMTP out blocked except to the old mailserver!).
I have IP addresses that I can use, but I want to stay with a single IP address and implement spamassassin. I read that enabling SMTPFILTER for spamassassin results in loss of SMTP auth for external users?
I really also need to get SSL working for SMTP. There is a warning about this creating an open relay when done with a single IP address.
So I am trying to put together a basic plan of action. BTW, holidays start tomorrow so, not much complex will get done for a couple of weeks. So throw reading material at me, and I will check back with a plan of action before changing anything...
Do I move users to port 587 for SMTP? And implement SSL on that port? Where is it documented how to set up port 587 for SMTP (where is using port 587 for users documented?).
I see the tech note in the knowledge base for setting up spamassassin on a single IP address and the man pages for spamassassin. I **hope** I can set that up ok, provided I do not muck up users sending of mail....