Thread: postfix + sasl
View Single Post

  #4 (permalink)  
Old 07-03-2004
Marc Wirth
 
Posts: n/a
Default Re: postfix + sasl

Julia Thorne <rimbaldi@nospam.tld> wrote:
> I didn't find the Docs on postfix.org to be ANY help whatsoever.
> Parts were out of date, last time I checked, and contained
> contradictory info.


There were quite a few changes from Postfix 1.x to Postfix 2.x.
I found that most documentation that seemed contradictory was
for different versions, so look for that information if possible.

Furthermore, Postfix supports quite a few options that are more
or less exclusive (E.g. mbox vs. Maildir/, Virtual users vs.
non-virtual users, ...).

> All I want is for some of our *12* users to be able to log in &
> send SMTP mail from a remote computer while traveling. I won't
> install encrypted LDAP/SQL/whatever just for that!


OK, no LDAP/SQL means you configure Postfix to use the users from
the system. (local_recipient_maps = unix:passwd.byname $alias_maps)

If you are using cyrus sasl2 on linux you should configure saslauthd
to use either the 'getpwent' or the 'pam' authentication module.
Configure means that you should simply start saslauthd with the
appropriate parameters (saslauthd -a getpwent). I don't know if Suse
provides some default startup script. If they do you might find some
configuration file in /etc/sysconfig/.

You want at least the following two entries in main.cf so that postfix
actually uses sasl:
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous

and you should permit authenticated users to send something early on:
smtpd_sender_restrictions =
permit_sasl_authenticated,
permit_mynetworks,
....

> IMO- Eventually, adding un-necessary applications & complications
> to a Linux/Unix system will turn it into some form of Windows!


Then why do you use Suse? ;-)

Hope this helps,
Marc
Reply With Quote