Hi,

I think i might have found the problem

>From the documentation:
send_cyrus_sasl_authzid (default: no)
When authenticating to a remote SMTP or LMTP server with the default setting
"no", send no SASL authoriZation ID (authzid); send only the SASL
authentiCation ID (authcid) plus the authcid's password. 
The non-default setting "yes" enables the behavior of older Postfix
versions. These always send a SASL authzid that is equal to the SASL
authcid, but this causes inter-operability problems with some SMTP servers. 
This feature is available in Postfix 2.4.4 and later. 

I run postfix 2.3.3.
>From the above it seems that I sends authzid: authcid: password for AUTH
PLAIN 
In my case 
authzid =authcid = user
password = password
so the whole AUTH PLAIN becomes useruserpassword which does not validate

is that correct? How can I stop postfix from sending authzid without
upgrading postfix?


Regards Gijs



-----Original Message-----
From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of lst_ho...@kwsoft.de
Sent: den 10 maj 2011 10:14
To: postfix-users@postfix.org
Subject: Re: postfix smarthost authentification error (incorrect token:
useruserpassword)

Zitat von Gijs Koppers <g...@koppers.se>:

> Hi all,
>
> I am trying to relay my outgoing mail and I receive a authentification
> error.
> I followd the relevand guides for setting up a smarthost
>
> smtp_sasl_mechanism_filter = plain
> smtp_sasl_security_options = noanonymous
> smtp_sasl_auth_enable = yes
> relayhost = [smtp.myrelay.se]:submission
> smtp_sasl_password_maps = static:user:password
> broken_sasl_auth_clients = yes
>
> I sniffed the network traffic between my server and the relayhost and I
> think it all boils down to that postfix tries to authenticate incorrectly
> with
>
> AUTH PLAIN dXNlcgB1c2VyAHBhc3N3b3Jk
> (which is AUTH PLAIN useruserpassword)
>
> Instead of
>
> AUTH PLAIN AHVzZXIAcGFzc3dvcmQ=
> (which is AUTH PLAIN userpassword)
>
>
> Included an excerpt of my network traffic
>
> 250-SIZE 20971520
> 250-PIPELINING
> 250-AUTH PLAIN LO
> 1:123:123.5286 IP host.66301 > se.submission: P 31:68(37) ack 245
> '.._5.o.AUTH PLAIN dXNlcgB1c2VyAHBhc3N3b3Jk
>
> 1:123:123.5586 IP se.submission > host.66301: P 245:280(35) ack
> 5.o.'.._535 Incorrect authentication data
>
>
> Decoding the authetification line
>> perl -MMIME::Base64 -e 'print decode_base64("dXNlcgB1c2VyAHBhc3N3b3Jk");'
>> useruserpassword
>
> so it seems that my password_map "static:user:password" is incorrect send
to
> the
> relay host (should be \0user\0password instead of useruserpassword)
> (i tried with a password file/db but that gives the same result)
>
> from here I am stuck. I cannot find how to correct this.
>
> Regards Gijs

Have a look here:
http://www.postfix.org/DATABASE_README.html#types

static (read-only)
Always returns its lookup table name as lookup result. For example,  
the lookup table "static:foobar" always returns the string "foobar" as  
lookup result.

so in your case static:password should be correct. In this case the  
result is always "password".

Regards

Andreas




Reply via email to