On 8/8/2006 9:20 AM, Gerard Seibert wrote:
FreeBSD 6.1 STABLE
I have SASL and Postfix installed and for the most part they seem to
work all right together. However, there is one small problem.
When attempting to send a message from one of the PC's on the network,
actually any PC on the network
Gerard Seibert wrote:
FreeBSD 6.1 STABLE
I have SASL and Postfix installed and for the most part they seem to
work all right together. However, there is one small problem.
When attempting to send a message from one of the PC's on the network,
actually any PC on the network except for the one
Paul Schmehl wrote:
Sasl is attempting to use sasldb2 *before* it uses /etc/passwd (or pam,
as the case may be.) It's harmless in any case. What do you have in
the smtpd.conf file? (/usr/local/lib/sasl2/smtpd.conf)
This is the contents:
## Global Values
pwcheck_method: auxprop
Greg Groth wrote:
On 8/8/2006 9:20 AM, Gerard Seibert wrote:
FreeBSD 6.1 STABLE
I have SASL and Postfix installed and for the most part they seem to
work all right together. However, there is one small problem.
When attempting to send a message from one of the PC's on the network,
This is the contents of the smtpd.conf file:
## Global Values
pwcheck_method: auxprop
auxprop_plugin: sasldb
log_level: 7
mech_list: PLAIN LOGIN
From postfix.org:
This will use the Cyrus SASL password file (default: /etc/sasldb in
version 1.5.5, or /etc/sasldb2 in version 2.1.1),
Gerard Seibert wrote:
Paul Schmehl wrote:
Sasl is attempting to use sasldb2 *before* it uses /etc/passwd (or pam,
as the case may be.) It's harmless in any case. What do you have in
the smtpd.conf file? (/usr/local/lib/sasl2/smtpd.conf)
This is the contents:
## Global Values
Paul Schmehl wrote:
Apparently you're using the sasldb2 database for logins? If so, the
sasldb2 database needs to be readable by postfix, and it has to be
populated with the [EMAIL PROTECTED] that you need. Have you populated
the db?
You would probably be better off using saslauthd as
On 8/9/06, Gerard Seibert [EMAIL PROTECTED] wrote:
Paul Schmehl wrote:
Apparently you're using the sasldb2 database for logins? If so, the
sasldb2 database needs to be readable by postfix, and it has to be
populated with the [EMAIL PROTECTED] that you need. Have you populated
the db?
--On August 8, 2006 7:40:20 PM -0400 Gerard Seibert [EMAIL PROTECTED]
wrote:
Paul Schmehl wrote:
Apparently you're using the sasldb2 database for logins? If so, the
sasldb2 database needs to be readable by postfix, and it has to be
populated with the [EMAIL PROTECTED] that you need. Have
Might want to send an email to the postfix list on this one... ;)
-Jordan
artware wrote:
Hello,
I seem to be having some issue with saslauthd and postfix on 5.3-R...
When I try to send mail out, it fails, and puts this in
/var/log/maillog:
Jan 4 05:56:17 n00330 postfix/smtpd[8103]: warning: SASL
On 01/03/05 04:13 PM, artware sat at the `puter and typed:
Hello,
I seem to be having some issue with saslauthd and postfix on 5.3-R...
When I try to send mail out, it fails, and puts this in
/var/log/maillog:
Jan 4 05:56:17 n00330 postfix/smtpd[8103]: warning: SASL
authentication
On Wednesday 10 November 2004 07:07 am, Svein Gullby wrote:
Hi !
I'm sending you this mail because you've fixed a postfix problem at
the same stage that I have problems now.
What ./configure parameters did you use to get Cyrus SASL2 to work
with MySQL ?
Mvh
Svein Gullby
ICT
Brent Wiese wrote:
I (tried) following the instructions at:
http://high5.net/howto/
I have postfix virtual users working in MySQL. I have courier imap/pop3
working w/ virtual users. I wanted to add SMTP auth.
I added the cyrus-sasl2 port (also chose support for it in postfix port)
WITH_MYSQL.
No
Brent Wiese wrote:
I (tried) following the instructions at:
http://high5.net/howto/
I have postfix virtual users working in MySQL. I have
courier imap/pop3
working w/ virtual users. I wanted to add SMTP auth.
I added the cyrus-sasl2 port (also chose support for it in
postfix
Hi Brent,
No go. Still getting no user in db in /var/log/maillog.
I get:
postfix/smtpd[23761]: sql_select option missing
postfix/smtpd[23761]: auxpropfunc error no mechanism available
In /var/log/messages
Oh typo :( SQL_Statement = SQL_Select)
Is SQL (MySQL) Support included within your
I added the cyrus-sasl2 port (also chose support for it in
postfix port)
WITH_MYSQL.
No go.
I added the following lines to
/usr/local/lib/sasl2/smtpd.conf (found this
in another faq/tutorial, so it may be incorrect)
sasl_pwcheck_method: auxprop
sasl_auxprop_plugin: sql
On 4/7/2004 12:32 PM Brent Wiese wrote:
Brent Wiese wrote:
I (tried) following the instructions at:
http://high5.net/howto/
I have postfix virtual users working in MySQL. I have
courier imap/pop3
working w/ virtual users. I wanted to add SMTP auth.
I added the cyrus-sasl2 port
I used those instructions, although I modified some for my specific
configuration. the username field in my database is
[EMAIL PROTECTED] however.
Yes, that is how mine is.
I had to create a
plain-text password
This is what I want to avoid. I think this is what the patch listed on the
Brent Wiese told a big fish story including the following on 04/06/2004
5:40 PM:
I (tried) following the instructions at:
http://high5.net/howto/
I have postfix virtual users working in MySQL. I have courier imap/pop3
working w/ virtual users. I wanted to add SMTP auth.
I added the cyrus-sasl2
synrat wrote:
can someone give me a few pointers on setting up this combination on free
bsd 4.7 ? I'm using the latest ports and already have postfix running.
http://www.postfix.org/docs.html lists a number of Postfix+SASL docs.
--
Dean C. Strik Eindhoven University of Technology
20 matches
Mail list logo
