212188RE: SASL vs. M$ Outlook and Outlook Express
- Jan 1, 2007Maybe a good idea to send the info on my config and the relevant parts
of the log file:
mynetworks = 192.168.0.0/24, 127.0.0.0/8
smtpd_sasl_auth_enable = yes
smtpd_recipient_restrictions = permit_mynetworks
smtpd_sasl_authenticated_header = yes
broken_sasl_auth_clients = yes
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
debug_peer_list = 220.127.116.11
And the relevant parts of the log file (skipping the address parsing and
rewriting info) in attachment.
[mailto:owner-postfix-users@...] On Behalf Of Magnus Bäck
Sent: Monday, January 01, 2007 1:42 PM
Subject: Re: SASL vs. M$ Outlook and Outlook Express
On Monday, January 01, 2007 at 13:34 CET,
Tom Kovar <postfix_list@...> wrote:
> I have been using successfully Postfix since good one year, and now Ibackground
> have extended it with SASL, using dovecot, with MySQL in the
> for all authentications. Everything seems to be working fine, when Idenied".
> send the SMTP commands manually, authentication is successfull and
> sending e-mail works according to the rules.
> Not so from Micro$oft clients, where I always get "Relay access
> Inspecting the Postfix-Syslog, after enabling debug, reveals thesource
> of the problem - even if I enabled the "SMTP server requiresthe
> authentification" check box in these clients, they still do not send
> SMTP AUTH message. The sequence of SMTP messages isPerhaps you're forgetting this:
> MAIL FROM:
> RCPT TO:
> and this inevitably leads to the failure.
> Can anybody help me what the problem with M$ might be?
- << Previous post in topic Next post in topic >>