>> I doubt Outlook servers are just sending random garbage out
What, they cannot tell if the connection is encrypted or not because
they've ignored the handshake result ?
Typical m$ . "Now you all align with what we say is right ... or else" ?
On Thu, May 22, 2025 at 3:41 PM Cley Faye via mailop <mailop@mailop.org>
wrote:
> This may sound too simple, but isn't that just a garbled TLS handshake? A
> case where the remote server is expecting IMAPS (IMAP over TLS, usually on
> port 993) and is just starting the handshake while the IMAP server does not
> handle it, and interpret everything as raw commands?
>
> What's shown in these logs does not look like the usual TLS handshake
> converted to ASCII, but aside from that, I doubt Outlook servers are just
> sending random garbage out.
>
>
> Le jeu. 22 mai 2025 à 16:03, Nate Burke via mailop <mailop@mailop.org> a
> écrit :
>
>> Has anyone had success getting the "New" Outlook to talk to an Icewarp
>> Server? With both IMAP and POP3, my server records garbled IMAP/POP3
>> commands in the connection log from the Microsoft servers. And outlook
>> just displays the generic 'Cannot log into server' error.
>>
>> I'm not looking to start a debate about the merits of MS proxying the
>> connections through their servers. We're primarily an ISP who also
>> offers Email, so I have no control over the end users software
>> decisions. And this is affecting only a small number of my clients.
>> For my clients using outlook, they have other accounts with O365, and
>> want to just add their email account with me into their existing outlook
>> instance. MS just forced them to upgrade to the "New" Outlook, which
>> broke only the connections to my server.
>>
>> I've opened a ticket with Icewarp, but their reply was just that it was
>> an MS problem, as they're sending bad commands. I know that the
>> internet is full of IMAP/POP3 issues and the new outlook, but I was
>> wondering if anyone has actually got it working with Icewarp.
>>
>>
>> This is what's recorded in my IMAP log when outlook tries to
>> authenticate an IMAP account.
>>
>>
>> 52.96.64.245 [1184] 08:11:50 Connected
>> 52.96.64.245 [1184] 08:11:50 >>> * OK IceWarp Epos Update 1 build 11
>> IMAP4rev1 Thu, 27 Mar 2025 08:11:50 -0500
>> 52.96.64.245 [1184] 08:11:50 <<< ‹~H…â§Óˆj‘eƒÀ‡ƒB3ùœ#¯â'c|s€à²²
>> _ ÜØ Ê!1bs(Û½"·|ãM( u3¬j4œ: (À0À/À(À'À,À+À$À#ÀÀÀ
>> 52.96.64.245 [1184] 08:11:50 >>> ‹~H…â§Óˆj‘eƒÀ‡ƒB3ùœ#¯â'c|s€à²² BAD
>> No such command as "_ ÜØ Ê!1bs(Û½"·|ãM( u3¬j4œ:"
>> 52.96.64.245 [1184] 08:11:50 <<< À œ = < 5 /
>>
>> 52.96.64.245 [1184] 08:11:50 >>> * BAD Command unknown
>> 52.96.64.245 [1184] 08:11:50 Disconnected
>> 40.97.127.205 [1184] 08:11:52 Connected
>> 40.97.127.205 [1184] 08:11:52 >>> * OK IceWarp Epos Update 1 build 11
>> IMAP4rev1 Thu, 27 Mar 2025 08:11:52 -0500
>> 40.97.127.205 [1184] 08:11:52 <<< { wÞ-‘xN‚<ÊDzd úm¢JwZdô«†§Ÿ#Ui …Hé§z
>> 40.97.127.205 [1184] 08:11:52 >>> + Go ahead
>> 40.97.127.205 [1184] 08:11:52 >>> { wÞ-‘xN‚<ÊDzd úm¢JwZdô«†§Ÿ#Ui BAD
>> No such command as "…Hé§z"
>> 40.97.127.205 [1184] 08:11:52 <<< ôPq<Çö$•†)fºcûm› ~ „b
>> À0À/À(À'À,À+À$À#
>>
>> 40.97.127.205 [1184] 08:11:52 >>> * BAD Command unknown
>> 40.97.127.205 [1184] 08:11:52 Disconnected
>>
>>
>>
>> Nate Burke
>>
>> Blast Communications
>>
>>
>> _______________________________________________
>> mailop mailing list
>> mailop@mailop.org
>> https://list.mailop.org/listinfo/mailop
>>
> _______________________________________________
> mailop mailing list
> mailop@mailop.org
> https://list.mailop.org/listinfo/mailop
>
--
--
Paulo Azevedo
_______________________________________________
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
