Page 1 of 1

Authentication: SMTP Relaying

Posted: Mon Jul 03, 2006 11:42 am
by dotbill
I need to be able to offer pop3 to the user base, which means I need to make relaying decisions based on auth first. I also want to be able to use specific x-headers that require authentication.

Currently, I'm not seeing how authentication is enabled. The only SMTP relay restrictions I'm able to impose are IP-based.

Posted: Mon Jul 03, 2006 11:53 am
by ScalixSupport
This has been discussed in a number of threads. The short answer is that you don't need to do anything.

The slightly longer answer can be seen in http://www.scalix.com/community/viewtopic.php?t=2406

Cheers

Dave

Posted: Mon Jul 03, 2006 1:58 pm
by dotbill
Thank you Dave.

I'm still not sure how the auth piece works. In smptd.cfg, I have:
RELAY accept 127.0.0.1
RELAY accept host.fqdn
RELAY Log_Reject ALL

I only want an authenticated user, or the scalix host itself to be able to relay. As it is now, I cannot send mail from a pop client. So, is it using authentication?

Thank you.

-bill

Posted: Mon Jul 03, 2006 2:17 pm
by ScalixSupport
Hi Bill,

Check your POP client's outgoing mail (i.e. SMTP) server and see if you've enabled authentication. That will normally require you to enter a user name that you'll be authenticating with. Then, when you send a message for the first time, you'll be prompted for a password. Given that you can't send with your POP client it sounds like these steps haven't been performed yet or your POP client doesn't support AuthSMTP.

Thanks,
Rachel

Posted: Mon Jul 03, 2006 2:36 pm
by dotbill
I just found the same advice on another related post.

Thank you.

-bill