Hi Odhiambo.
The AUTH is incorrectly advertised. A correct setup would announce all the
mechanisms available for authentication.
So, a correct answer at smtp will be, for example:
250-AUTH PLAIN LOGIN
And what the office 365 servers are answering is:
250-AUTH
This is incorrect and that is the point of the problem because exim search
for the correct credential when acting as a client, based on the mechanisms
available (and in this case, there are no one mechanism available because
no one mechanism was announced).
This is what I search and asked if someone else has or had the same problem
because I think that the two ways to fix this is:
1 - make the office 365 do the right answer when receive the EHLO verb (but
it's exchange and it's microsoft - what means that this probably will never
be fixed).
2 - make the exim do the authentication using some fallback-style-schema
when you already had setup hosts_require_auth for some of the office 365
servers).
Had any other idea?
Thank's
And... Ya... It's friday... My brain is exhausted too!
------------------------------
From: odhiambo@???
Date: Fri, 14 Jun 2013 17:02:18 +0300
Subject: Re: [exim] exim acting as client on office365
To: ramatukuma@???
CC: exim-users@???
How can you use AUTH when it's not advertised? Or maybe it's Friday my
brain is already tuned to something.
On 14 June 2013 16:54, Reinaldo Matukuma <ramatukuma@???> wrote:
Hi all.
I had a situation today where i need that exim act as client on office365
server with authentication.
So, i have configured two authenticators (one for PLAIN and other for
LOGIN) that will be sent after TLS.
The problem that i found is that the office365 server isn't doing the
correct announce of AUTH mechanisms....
Running exim in debug mode i saw this:
SMTP<< 250-pod51028.outlook.com Hello [189.74.52.32] 250-SIZE
36700160 250-PIPELINING 250-DSN
250-ENHANCEDSTATUSCODES 250-STARTTLS 250-AUTH
250-8BITMIME 250-BINARYMIME 250 CHUNKING
They are announcing only that has auth capability, right? So... the exim
don't find the correct authenticator data to use:
207.46.4.237 in hosts_require_auth? yes (matched
"pod51028.outlook.com")scanning
authentication mechanismsskipping server_plain authenticator: not
configured as a clientskipping server_login authenticator: not configured
as a client SMTP>> QUIT
So... My doubt is... There are a way to configure exim to use for example
LOGIN mechanism as fallback when it don't find any valid mechanism for auth
as client? Someone had the same problem? How to fix this? Or maybe this is
something to send to bug list?
Thanks
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
"I can't hear you -- I'm using the scrambler."
