Page 1 of 1

Secure Authenticated SMTP server on Scalix 10.0.1

Posted: Wed Oct 31, 2007 9:43 am
by jgravert
Currently we have SMTP blocked at our firewall so spammers can't use our mail servers SMTP function. Back when we had hosted mail spammers happily used our server and managed to get us blacklisted on a few companies email servers. Since having our own server and locking out incoming SMTP traffic we have had a clean setup.

However now I'm getting more and more requests to use mail on PDA phones and some people are asking to use other email clients because they only need simple mail. That will require me opening up the SMTP ports on our firewall. Right now using POP3 or IMAP email clients can download mail we just can't send through the same server using SMTP.

Before I open up those ports on our firewall I need to setup the Scalix Server to Authenticate SMTP and I would prefer to enable encryption as well. All other SMTP requests that do not authenticate or are not encrypted I want the Scalix Server to drop those messages. Thereby securing our SMTP server so spammers cannot use our server to send their spam mails via our domain.

I've done some searches on the forum and find some of the info but nothing is really clear on the process of setting this up correctly. Most people have attempted to implement these features and come on here with failed configurations trying to get help. I don't want to try then fail. I don't know where to start so I am hoping someone out there can help with a step by step process of setting this up and securing the server.

Version of Scalix we are running is 10.0.1
This is running on a SUSE version of Linux.

Any and all help is appreciated.
Thanks,
James

Posted: Thu Nov 01, 2007 6:31 am
by Valerion
I am not sure if the Scalix 10 SMTPD supported auth or not, I can't remember it supporting that (sorry, too long ago). What I did back then was to set up SASL Auth in sendmail and use the rimap auth method. This does not support the hashed methods (eg. CRAM-MD5). You can set up a local password cache, or pull it from somewhere like /etc/password.