As per your suggestion I streamlined my sasl2 smtpd.conf file.
As per someone else's suggestion I rechecked all the permissions and
found that /usr/local/var was 700 and changed it to 755. That fixed
the permission error.
Now that that's fixed I'm now trying to figure out why I can't
authent
Richard Secor wrote:
# cat /usr/local/lib/sasl2/smtpd.conf
pwcheck_method: authdaemond auxprop
log_level: 3
mech_list: PLAIN LOGIN
authdaemond_path: /usr/local/var/spool/authdaemon/socket
auxprop_plugin: sql
sql_engine: mysql
sql_hostnames: localhost
sql_user: sql_user
sql_password: sql_password
Richard Secor writes:
At this point it appears as though Courier Authdaemond is not trying
to querying the MySQL Database when being used from Postfix/Cyrus
SASL. It works fine with Courier IMAP/POP3.
authdaemond has no clue who's talking to it. All it knows is that someone
established
At this point it appears as though Courier Authdaemond is not trying
to querying the MySQL Database when being used from Postfix/Cyrus
SASL. It works fine with Courier IMAP/POP3.
Is there a way to make sure that SASL & Authdaemond are speaking with
one another?
I can't seem to find anything
Richard Secor writes:
At this point it appears as though Courier Authdaemond is not trying to
querying the MySQL Database when being used from Postfix/Cyrus SASL. It
works fine with Courier IMAP/POP3.
Richard,
Are you trying to authenticate outbound mail with SASL?
The setup I have used for
Sam,
Thanks I figured it out... I had an option set off when
compiling Cyrus SASL that I needed on.
Now Authdaemond is authenticating me... now I just have to get
postfix to be aware of it and allow me to replay.
Thanks again,
-Rich
On Mar 3, 2006, at 6:07 PM, Sam Varshavchik wrote:
Francisco,
I actually got it working.
I never use the ports... lol. I always download straight from the
sources and build from scratch. And I'm trying to not install
anything extra. It looks like I'll probably get around the need for
Pam; At least this time.
Thanks again,
-Rich
On Mar
