Steven J Lamb schrieb:
I know I am probably just flustered cause I have a production email server
with no authentication support running... But for some reason I cant get
this one figured out.
In my logs I see this line
Messages:
Jul 18 08:42:36 ws3 saslauthd[29665]: main : no authentication
mechanism specified
Jul 18 09:39:49 ws3 saslauthd[10416]: main : no authentication
mechanism specified
Jul 18 09:54:06 ws3 saslauthd[11345]: main : no authentication
mechanism specified
Jul 18 09:55:20 ws3 sasl2-shared-mechlist: sql_select option missing
Jul 18 09:55:20 ws3 sasl2-shared-mechlist: auxpropfunc error no mechanism
available
You somehow borked the saslauthd init script, which has a default for
the mechanism to use, which can be overridden by /etc/sysconfig/saslauthd.
SASLv2 then tries to fall back to default auxprop/sasldb2, which isn't
configured (as not intended to use i guess).
Maillog
Jul 18 09:57:56 ws3 postfix/smtpd[11409]: warning: SASL authentication
failure: cannot connect to saslauthd server: No such file or directory
Jul 18 10:00:57 ws3 postfix/smtpd[11666]: warning: SASL authentication
failure: cannot connect to saslauthd server: No such file or directory
Jul 18 10:07:52 ws3 postfix/smtpd[11997]: warning: SASL authentication
failure: cannot connect to saslauthd server: No such file or directory
Jul 18 10:13:17 ws3 postfix/smtpd[11669]: warning: SASL authentication
failure: cannot connect to saslauthd server: No such file or directory
Your saslauthd does not run - see above error cause.
I am a loss for what this is telling me ... Which probably makes sense since
it is kinda telling me I don't have a path somewhere
Alexander
