| Author |
|
Sever
Newbie
Joined: 04 August 2016
Location: United States
Online Status: Offline
Posts: 11
|
| Posted: 04 August 2016 at 6:21am | IP Logged
|
|
|
We have a customer experiencing odd behavior connecting to office365.
On one machine they can successfully connect and retrieve emails.
On a second machine they can not.
The successful machine, connects, gets a list of capabilities, and logs in using SASL PLAIN (over SSL). (We are configured to use "Auto" for authentication.)
The failing machine generates the following trace:
[10:35:29.74] [INFO] Assembly version: 7.2.4.366.
[10:35:29.74] [INFO] Will resolve host "outlook.office365.com".
[10:35:29.74] [INFO] Host "outlook.office365.com" resolved to IP address(es) 40.96.5.66, 132.245.39.226, 132.245.73.178, 132.245.31.50, 132.245.64.34, 132.245.39.242, 132.245.17.50, 132.245.17.34.
[10:35:29.74] [INFO] Will connect to host "outlook.office365.com" on port 993.
[10:35:29.84] [INFO] Socket connected to IP address 40.96.5.66 on port 993.
[10:37:00.14] [RECV] * OK The Microsoft Exchange IMAP4 service is ready. [QgBOADMAUABSADEANgBDAEEAMAAwADYAMwAuAG4AYQBtAHAAcgBkADEANgAuAHAAcgBvAGQALgBvAHUAdABsAG8AbwBrAC4AYwBvAG0A]\r\n [Total 160 bytes received.]
[10:37:00.17] [INFO] Get the list of IMAP4 capabilities via CAPABILITY command.
[10:37:00.17] [SEND] MBN00000001 CAPABILITY\r\n
[10:37:00.17] [RECV] * BYE Connection is closed. 13\r\n [Total 32 bytes received.]
[10:37:00.20] [INFO] Error: Socket connection was aborted by remote host.
[10:37:00.20] [INFO] Will disconnect from host "outlook.office365.com".
[10:37:00.20] [INFO] Disconnected from host "outlook.office365.com".
Notice the time delay (90 seconds) between:
[10:35:29.84] [INFO] Socket connected to IP address 40.96.5.66 on port 993.
[10:37:00.14] [RECV] * OK The Microsoft Exchange IMAP4 service is ready.
Both machines are running the same version of our software. These are test and dev machines so should be the same environment.
Customer believes our code is encountering a certificate issue. I am not sure how to prove or disprove that because MailBee and the Mail Server are what negotiate the SSL/TLS communication.
Customer reports that our product is making a series of connection to various IP Addresses on port 80 during this time. There is nothing in our code that attempts to connect to port 80. Not sure if MailBee would do this.
Can anyone suggest any diagnostic steps to figure out why the second machine does not work?
Thank you
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6103
|
| Posted: 04 August 2016 at 6:27am | IP Logged
|
|
|
You're using a very old version of the assembly, released in May 2012. Check if the problem persists with the latest build, you can get a compatible trial key here.
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
Sever
Newbie
Joined: 04 August 2016
Location: United States
Online Status: Offline
Posts: 11
|
| Posted: 04 August 2016 at 6:49am | IP Logged
|
|
|
Thank you for responding so quickly. That was a impressive response time.
Yes, we are aware that this version of our software is running an older version of Mailbee. And we are using more recent versions of Mailbee in other versions of our product. Upgrading the customer to the most recent version of our software is not possible at this time.
My question was asking if someone might have more insight into why this version of Mailbee successfully connects on one machine and not the other.
Thank you
|
| Back to Top |
|
| |
Igor
AfterLogic Support
Joined: 24 June 2008
Location: United States
Online Status: Offline
Posts: 6103
|
| Posted: 04 August 2016 at 8:45am | IP Logged
|
|
|
The customer may be correct regarding certificate issue. My guess is, once the certificate is obtained from the server, Windows runs a check of the certificate against remote certificate centers, that would explain both the delays and the requests sent via port 80. This isn't, however, something done by MailBee, we're talking about things working deep inside of Windows. In current version of MailBee.NET Objects, SSL functionality relies solely on .NET Framework so there's a good chance that upgrade will solve the problem.
We understand that upgrading the application and making it work with a new version of MailBee may be complicated, so we'd recommend to create a simple self-contained application which does nothing but connecting to specific IMAP server and logs into specific account, and see if it works on customer's system.
Note that, in order to switch to the latest version, you would need to update your maintenance contract and request key update via HelpDesk.
--
Regards,
Igor, AfterLogic Support
|
| Back to Top |
|
| |
MailBee.NET Objects 
MailBee.NET Queue 
MailBee Objects 
WebMail Pro PHP 
AfterLogic Aurora 
MailSuite Pro for Linux 
Unified Messaging Solution 
Search
Register
Login
Topic: IMAP to office365
Privacy policy |
Refund policy