[162794] in North American Network Operators' Group
RE: Could not send email to office 365
daemon@ATHENA.MIT.EDU (Ryan Finnesey)
Wed May 1 16:35:27 2013
From: Ryan Finnesey <ryan@finnesey.com>
To: Tony Patti <tony@swalter.com>, 'JoeSox' <joesox@gmail.com>,
"nanog@nanog.org" <nanog@nanog.org>
Date: Wed, 1 May 2013 20:35:06 +0000
In-Reply-To: <09e301ce4690$0259fd50$070df7f0$@swalter.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
We have fixed the problem. I had to complete a clear install of Outlook an=
d remove the credentials that where on the computer in the control panel un=
der credential manager. This may also fix/help with your issue.
Cheers
Ryan
-----Original Message-----
From: Tony Patti [mailto:tony@swalter.com]=20
Sent: Wednesday, May 1, 2013 1:19 PM
To: Ryan Finnesey; 'JoeSox'; nanog@nanog.org
Subject: RE: Could not send email to office 365
After our "upgrade", we started to see the body of received PLAIN TEXT emai=
ls truncated at less than 256 bytes, which frequently truncated emails in t=
he middle of a word, the fix was a "setting change".
Since being standardized in 1982 with RFC 822, you would think PLAIN TEXT e=
mails would just work "out of the box".
Tony
-----Original Message-----
From: Ryan Finnesey [mailto:ryan@finnesey.com]
Sent: Wednesday, May 01, 2013 11:42 AM
To: JoeSox; nanog@nanog.org
Subject: RE: Could not send email to office 365
I am also having the some issues going on 3 weeks now. I cannot access my =
e-mail via Outlook and my MX records keep changing. It is nuts support has=
been unable to help. =20
________________________________________
From: JoeSox
Sent: Wednesday, May 01, 2013 9:24 AM
To: nanog@nanog.org
Subject: Re: Could not send email to office 365
The company I work for has been having Outlook connectivity issues (intermi=
ttent for only a few end users) for the past 7 days for Office 365.
We are in an upgrade status (on the 18th days or so; have been told it can =
last 30 days) and they changed our MX records without formal notification.
We updated those on a Thursday or Friday and it worked until the following =
Monday where we observed it again, then magically fixed itself late afterno=
on that Monday. We had some more reports yesterday. The Microsoft technical=
support has not been helpful troubleshooting this for us.
I am hoping it is related to our upgrade status but I cannot get an answer =
from anyone.
--
Thanks, Joe
On Wed, May 1, 2013 at 2:21 AM, ISHII, Yuji <you@ugec.net> wrote:
> Hello folks,
>
> Have you ever seen DNS issues on Office 365?
>
> MX record of Office 365 is example.mail.eo.outlook.com.
> I can get the MX record, however, I could not get the A record of the=20
> MX record, got Timeout.
>
> Does anyone have the same issue?
>
> Sincerely,
> Yuji
>
>
