Page 1 of 1

Can't get SMTPS working

Posted: Tue Aug 22, 2006 6:59 pm
by WizmanG
I followed the instructions on configuring multiple IPs on the same NIC for SSMTP but still can't get it working. I do have IMAPS and POP3S working.

Any help is appretiated.

When I try and connect I get the cert and I am prompted for my password but I never get authenticated.

Here are some bits from /var/log/messages that I think are relevant.

Aug 22 18:10:37 scalix pam_timestamp_check: pam_timestamp: `/var/run/' owner GID != 0
Aug 22 18:10:42 scalix pam_timestamp_check: pam_timestamp: `/var/run/' owner GID != 0
Aug 22 18:10:47 scalix pam_timestamp_check: pam_timestamp: `/var/run/' owner GID != 0
Aug 22 18:10:49 scalix sendmail[4310]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Aug 22 18:10:49 scalix sendmail[4310]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Aug 22 18:10:49 scalix sendmail[4310]: no secret in database
Aug 22 18:10:52 scalix pam_timestamp_check: pam_timestamp: `/var/run/' owner GID != 0


here are the relevant bits from my stunnel.conf

[pop3s]
accept = 995
connect = 110

[imaps]
accept = 993
connect = 143

[ssmtp]
accept = 192.168.10.205:465
connect = 25


Posted: Fri Sep 08, 2006 9:26 pm
by dkelly
The log extracts that you've posted are not relevant to SMTPs or Scalix, they should be ignored.

The first thing to do is to enable SMTP Relay logging in /var/opt/scalix/sys/smtpd.cfg by adding DEBUG_LOG=TRUE and restarting the SMTP Relay.

This will create a file called /var/opt/scalix/tmp/smtpd.log and will log the entire SMTP conversation when your client attempts to authenticate.

Please capture that logging and post it here.

Cheers

Dave

Posted: Wed Sep 13, 2006 11:29 pm
by WizmanG
I enabled loggin and it looks like it isn't even trying to authenticate to the scalix server and it isn't logging anything to the smtp.log file.

I am getting these entries in the /var/log/messages file that leads me to beleive that something isn't correct with the configuration and it might be trying to authenticate to the local machine somehow.
Sep 13 22:58:01 mail su(pam_unix)[5030]: session opened for user root by (uid=500)
Sep 13 22:58:01 mail su(pam_unix)[5030]: session closed for user root
Sep 13 22:58:01 mail su(pam_unix)[5035]: session opened for user root by (uid=500)
Sep 13 23:08:24 mail sendmail[5229]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:08:24 mail sendmail[5229]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:08:24 mail sendmail[5229]: no secret in database
Sep 13 23:08:35 mail sendmail[5229]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:08:35 mail sendmail[5229]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:08:35 mail sendmail[5229]: no secret in database
Sep 13 23:23:43 mail sendmail[5613]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:23:43 mail sendmail[5613]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:23:43 mail sendmail[5613]: no secret in database
Sep 13 23:23:52 mail sendmail[5613]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:23:52 mail sendmail[5613]: unable to open Berkeley db /etc/sasldb2: No such file or directory
Sep 13 23:23:52 mail sendmail[5613]: no secret in database