Nikola Milutinovic <[EMAIL PROTECTED]> wrote:
250-AUTH=NTLM PLAIN LOGIN DIGEST-MD5 CRAM-MD5
I don't have this second line on Sendmail 8.12.9 - am I missing something?
No, it is for (again) broken clients which are using "AUTH=". Some kind of
legacy auth.
Is it for sure that O and OE cannot use D
> So I would have to disable all but NTLM to be sure AUTH=NTLM is the first
> or only "AUTH" visible. No I won't do this for Microsoft users only because
> of their broken clients.
Maybe there is a way... Basically the ordering of the clients is the ordering of how
the *.la files are picked up
Rob Siemborski <[EMAIL PROTECTED]> wrote:
Mostly Randomly. Somewhat based on the order the plugin is loaded.
Security requirements of SASL basicly dictate that the client ignore the
order they are advertised.
The problem arises (again) with Microsoft Outlook and Outlook Express.
Outlook breaks w
Pascal Gienger wrote:
We have some kind of - problem.
We try to understand HOW the different SASL plugins are ordered when
doing an announcement (. CAPABILITY).
The problem arises (again) with Microsoft Outlook and Outlook Express.
Outlook breaks when "AUTH=NTLM" is not the FIRST method annou
On Fri, 12 Sep 2003, Pascal Gienger wrote:
> We have some kind of - problem.
>
> We try to understand HOW the different SASL plugins are ordered when doing
> an announcement (. CAPABILITY).
Mostly Randomly. Somewhat based on the order the plugin is loaded.
Security requirements of SASL basicly d
We have some kind of - problem.
We try to understand HOW the different SASL plugins are ordered when doing
an announcement (. CAPABILITY).
The problem arises (again) with Microsoft Outlook and Outlook Express.
Outlook breaks when "AUTH=NTLM" is not the FIRST method announced! It gives
me an er
