Robert,
sasl is working on that server. I'll have to access the phone again
(find the user) and try to send another mail to see if a specific sasl
entry appears close to the reject.
Jul 27 11:47:29 www postfix/smtpd[13115]: AEED912825AD:
client=unknown[192.168.1.103], sasl_method=PLAIN,
sasl_username=hraboga...@hrabogados.com
Jul 27 12:49:41 www postfix/smtpd[14832]: EAA131282521:
client=unknown[192.168.1.103], sasl_method=PLAIN,
sasl_username=hraboga...@hrabogados.com
Dominique
On 27/07/2012 12:40, Robert Schetterer wrote:
Am 27.07.2012 11:37, schrieb Dominique:
The phone smtp part is configured - I guess correctly.
you should be sure by this, after all, i didnt see any sasl login try in
your posted log, try
grep sasl /var/log/mail.log
etc
your conf does not look that bad, for short overflow
anyway read
http://www.postfix.org/SASL_README.html
---snip
Testing saslauthd authentication
Cyrus SASL provides the testsaslauthd utility to test saslauthd
authentication. The username and password are given as command line
arguments. The example shows the response when authentication is successful:
% testsaslauthd -u username -p password
0: OK "Success."
Note
Sometimes the testsaslauthd program is not distributed with a the
Cyrus SASL main package. In that case, it may be distributed with
-devel, -dev or -debug packages.
Specify an additional "-s smtp" if saslauthd was configured to contact
the PAM authentication framework, and specify an additional "-f
/path/to/socketdir/mux" if saslauthd establishes the UNIX-domain socket
in a non-default location.
---snipend
