Matthias Pfeifer wrote:
> My problem is, NO outlook (outlook and outlook express) user
> can authenticate and i get alway a relaying denied in the logfile.
> It's weird, because other Email programms i've tested works fine
> (Pegeasus, Thunderbird, uebimiau webail, sylpheed, bat ..) with the
> same email account.
What settings are your lookOut clients using for AUTH? lookOut and its ilk have
very poor RFC AUTH support (preferring their own perverted M$loth methods). In
particular, you will not be able to support "Secure Password Authentication"
which only works with Exchange servers. The only method that is supported in
lookOut is LOGIN, which transmits the password in open text (nearly), so you are
strongly encouraged to use TLS/SSL in addition to LOGIN.
> The authentication works fine (I've printed out every shit to see if
> it is working properly)
No it isn't; see below.
> Then, I've found that the rcpt_ok matches this else statement:
>
>
> else
> {
> # default of relaying_denied is obviously DENY,
> # we use the default "Relaying denied" message...
> return Qpsmtpd::DSN->relaying_denied();
> }
>
>
> But I don't know why.
The only reason this else would fire is if the preceding block had failed:
if ( $self->qp->connection->relay_client ) { # failsafe
return (OK);
}
Since this is set upon successful authentication, it is clear that your
authentication is not succeeding. QED.
We need more information to resolve this issue. Liberally sprinkle
$self->log(LOGERROR, "'ere we arem 'enry"); # or something like that
lines throughout plugins/auth/auth_vpopmail_sql so you can show which code path
is taken. The auth_vpopmail_sql is dead simple; all of the AUTH handshaking
bits take place in the core Qpsmtpd::Auth class. Show us the full log lines for
an AUTH failure, rather than just describe it...
John
