SMTP authentication with saslauthd against PAM
\ Gianluca Culot (13 Apr 2007)
. \ Mario Casola (13 Apr 2007)
. . \ Gianluca Culot (13 Apr 2007)
. . . \ Mario Casola (13 Apr 2007)
. . . . \ Gianluca Culot (13 Apr 2007)
. . . . . \ Mario Casola (13 Apr 2007)
. . . . . . \ Gianluca Culot (13 Apr 2007)
. . . . . . . \ Gianluca Culot (13 Apr 2007)
. . . . . . . . \ Noel Jones (13 Apr 2007)
. . . . . . . . . \ Gerard Seibert (13 Apr 2007)
. . . . . . . . . \ Gianluca Culot (17 Apr 2007)

7 msgError in SMTP sequence
2 msgdkim-milter on relay server unknown-jobid exter...
11 msgStubborn Cert issue
3 msgProblems with false positives
4 msgreject_unverified_recipient case sensitive?
3 msgdkim=fail (verification error: invalid key gran...
5 msg? Using header checks on (Postini) X-pstn-levels
2 msgCan't find error in my config file. Can you?
1 msgchroot postgresql ssl problem
15 msgWhat cert to buy
3 msgAddress re-writing
9 msgMail Rejected when we relay for a client.
8 msgQueueing up archive messages
2 msgCannot send e-mails from any e-mail clients
1 msgRe: outbound mail failure - need to fix asap -S...
4 msgoutbound mail failure - need to fix asap
3 msgPostfix alias problem
2 msgproblem to send a mail to a command in aliases
3 msgsmtpd_auth
Subject:solved : SMTP authentication with saslauthd against PAM : thanks
Group:Postfix-users
From:Gianluca Culot
Date:17 Apr 2007


 
-----Messaggio originale-----
Da: owner-postfix-users
[mailto:owner-postfix-users]Per conto di Noel Jones
Inviato: venerdi 13 aprile 2007 20.32
A: postfix-users
Oggetto: Re: R: SMTP authentication with saslauthd against PAM


At 08:13 AM 4/13/2007, Gianluca Culot wrote:
>I'm positive that postfix looks for a file , which name is in
>smtpd_sasl_path key of main.cf
>
>smtpd_sasl_type = dovecot
>smtpd_sasl_path = smtp.conf
>
>in fact whichever filename i write in the main.cf the error listed
>in syslog changes
>
>Apr 13 15:06:10 mail postfix/master[66107]: reload configuration
/etc/postfix
>Apr 13 15:06:13 mail postfix/smtpd[66173]: warning: SASL: Connect to
>smtp.conf failed: No such file or directory
>Apr 13 15:06:13 mail postfix/smtpd[66173]: fatal: no SASL
>authentication mechanisms
>Apr 13 15:06:14 mail postfix/master[66107]: warning: process
>/usr/libexec/postfix/smtpd pid 66173 exit status 1
>Apr 13 15:06:14 mail postfix/master[66107]: warning:
>/usr/libexec/postfix/smtpd: bad command startup -- throttling
>Apr 13 15:06:37 mail postfix/postfix-script: stopping the Postfix mail
system
>Apr 13 15:06:37 mail postfix/master[66107]: terminating on signal 15
>
>I'm just wondering if the name is not only for a configuration file,
>but also for a named pipe to contact saslauth Daemon
>Which would mean I must change the configuration file to the name of
>the namedpipe created by saslauthd

Please post in plain text only.
Please do not top post.

Please stop making symbolic links all over the place. This isn't
necessary and will only confuse things further.

It looks as if you are mixing up config from cyrus sasl and dovecot
sasl. As you already use dovecot, it's far easier to continue using
dovecot and forget about cyrus. If you use dovecot, you will not be
using saslauthd or any lib/sasl or lib/sasl2 stuff.

When using dovecot, the smtpd_sasl_path specifies the socket that
dovecot-auth creates.
http://www.postfix.org/SASL_README.html#server_dovecot

>mail# /etc/postfix/sasl > postconf -a
>dovecot

Good, your postfix supports dovecot auth. If you really want to use
cyrus saslauthd you will need to recompile postfix.

>dovecot (dovecot-0.99.14 compiled from ports)

Note dovecot auth with postfix requires a dovecot version higher than
0.99. Any dovecot 1.0.* version should do. You should be able to
run "portupgrade dovecot", but note that the dovecot.conf file format
and syntax has changed considerably since the 0.99 days. You will
need to configure your dovecot using the new syntax, but that
shouldn't be too hard.

If you can't upgrade dovecot, your other choice is to recompile
postfix with cyrus sasl support and configure postfix to use
cyrus. Doing that seems like a waste of time since you already have
dovecot working.

--
Noel Jones




Thanks Noel

it worked!
I complitely missed the note (not so noticeable :-D ) about dovecot 1.0

At first testing I tried out the Dovecot 1.0 RC29 but then I had to go back
to ports (which are currently updated at 0.99, portupgrade dovecot stiil
downloads 0.9* on freebsd) because sources from doveot.org do not create a
lot of stuffs about automatic daemons starting at boot time (too much for me
to fill by hands).

So I reverted to ports sources... missing compatibility...
Thanks a lot for your help





© 2004-2008 readlist.com