4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Auth
FromSent OnAttachments
LikonJan 27, 2006 1:36 pm 
Sam VarshavchikJan 27, 2006 3:31 pm 
LikonJan 28, 2006 4:22 am 
Gordon MessmerJan 28, 2006 12:57 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] AuthActions...
From:Gordon Messmer (yiny@eburg.com)
Date:Jan 28, 2006 12:57:46 pm
List:net.sourceforge.lists.courier-users

Likon wrote:

I did read documentation, but I still dont know what to do. I just dont understand it. Could you point me excatly on what should i focuse on? I`m not such good in mail servers so I dont know exactly how it works. I dont know if I should configure PAM, or add some option to authdaemonrc or something else. Please tell me what should I focuse on?

This is a good starting point: http://www.courier-mta.org/?install.html~esmtpauth

Basically, in current versions of Courier-MTA, you just have to specify what login methods you want users to be able to use.

Note, however, that even with authentication turned on, users will still be able to set the From: header to whatever they want. Headers are, for the most part, informal, and should never be trusted. If you're especially worried about making sure that users can only put their own return address in the From or Reply-To headers, you'll have to write your own code to do so. Frameworks for perl and python are available, and the filter you'll have to write should be very simple.

You'll also need to set up SPF records in DNS to prevent users from putting the "root" address in their From header, and using a mail server other than yours. However, since very few mail servers are currently supporting SPF, this will only be partially effective. Users will still be able to send messages "from" your root account to most of the servers on the internet.