[Pkg-exim4-users] smtp authentication (exim as a client) problem
marcopar at gmail.com
marcopar at gmail.com
Thu Apr 5 08:38:02 UTC 2007
Aurelian Melinte wrote:
> -maybe your new smarthost does not asks for for TLS - you need to explicitely enable PLAIN authentication - see the Debian Exim specific FAQ
i don't think this is the case. as i said i tweaked the template. the
tweak consists in forcing the client_send variable at the end of the script:
===========================
plain:
driver = plaintext
public_name = PLAIN
.ifndef AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS
# client_send = "${if !eq{$tls_cipher}{}{\
# ^${extract{1}{::}\
#
{${lookup{$host}lsearch*{CONFDIR/passwd.client}{$value}fail}}}\
# ^${extract{2}{::}\
#
{${lookup{$host}lsearch*{CONFDIR/passwd.client}{$value}fail}}}\
# }fail}"
client_send = *^theuser at thedomain.eu^thepassword
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
.else
client_send =
"^${extract{1}{::}{${lookup{$host}lsearch*{CONFDIR/passwd.client}{$value}fail}}}^${extract{2}{::}{${lookup{$host}lsearch*{CONFDIR/passwd.client}{$value}fail}}}"
.endif
==============================
this way works so i think is a matter of how client_send is
initializated in the original script.
> -maybe the smarthost advertises itself under a different name when you connect to (though the * should catch everything)
> -maybe the IP of the smarthost resolves to a different domain name (same obs)
yes, the smarthost resolves to different ip but as i understood * should
take care of that. when using the new provider i only switch default
routing but not DNS so why the behaviour should be different?
> -you want only as much debugging info as you need, something like -d-all+transport - see the Debian Exim specific FAQ
here's the cleaned up log as you asked:
http://cl1p.net/lesslogsmtpauth/
ciao
More information about the Pkg-exim4-users
mailing list