- Previous message: (no name): "Re: "sql_select option missing" without reason"
- Maybe in reply to: Peter I. Hansen: "sasl2 authentication on port 26"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
|
|
|
From: Peter I. Hansen (no email)
Date: Thu Apr 07 2005 - 07:45:51 EDT
On Wed, Apr 06, 2005 at 10:36:05PM +0200, Peter I. Hansen wrote:
> Hello
>
> I'm using postfix and cyrus-sasl for authentication of users on
> my mailsever on both port 25 and port 26.
>
> Since I went from sasl(1) to sasl2, the authentication on port 26
> gets refused. The log goes like this: (sorry about the wrapping)
>
> Apr 6 22:32:25 dhcppc1 postfix/smtpd[25335]: warning: SASL
> authentication failure: Could not open db
> Apr 6 22:32:25 dhcppc1 postfix/smtpd[25335]: warning: SASL
> authentication failure: Could not open db
> Apr 6 22:32:25 dhcppc1 postfix/smtpd[25335]: warning: SASL
> authentication failure: no secret in database
> Apr 6 22:32:25 dhcppc1 postfix/smtpd[25335]: warning:
> unknown[192.168.1.37]: SASL CRAM-MD5 authentication failed
> Apr 6 22:32:26 dhcppc1 postfix/smtpd[25335]: lost connection
> after AUTH from unknown[192.168.1.37]
> Apr 6 22:32:26 dhcppc1 postfix/smtpd[25335]: disconnect from
> unknown[192.168.1.37]
>
> When I use port 25 everything is fine. The problem is that many
> ISPs is blocking port 25 these days...
>
> Well, any help on this will be highly appreciated.
>
> thanks, Peter
I'm sorry for the noise, it seems I didn't have the correct
permissions on the sasldb.db file. It's hard to spot though since
it works with port 25...
well, just disregard this question :)
-Peter
|
|
|