Re: Could not send email to office 365

2013-05-14 Thread JoeSox
h > non-IPv6-related issues -- I'm a network guy working on this one report.) > > Jason (dot) Sherron [at] Microsoft (dot) com > > > > -Original Message- > From: JoeSox [mailto:joe...@gmail.com] > Sent: Wednesday, May 8, 2013 4:35 PM > To: nanog@nanog.org

Re: Could not send email to office 365

2013-05-14 Thread Bernhard Schmidt
Jason Sherron wrote: Hello Jason, > I'm an engineer on the Microsoft Office365 Exchange Online > ("outlook.office365.com") network team. I'm gathering forensics > specific to IPv6 reports -- are people still experiencing IPv6-related > issues? I am interested solely in failures that are IPv6 con

RE: Could not send email to office 365

2013-05-14 Thread Jason Sherron
osoft (dot) com -Original Message- From: JoeSox [mailto:joe...@gmail.com] Sent: Wednesday, May 8, 2013 4:35 PM To: nanog@nanog.org Subject: Re: Could not send email to office 365 Just an update if list members are still experiencing this issue. I spoke on the phone with Escalation Manager

Re: Could not send email to office 365

2013-05-08 Thread JoeSox
Just an update if list members are still experiencing this issue. I spoke on the phone with Escalation Manager for Microsoft North America and they had meetings today and their Engineering team is putting a game plan together to roll out a fix for the Outlook connectivity issues. They were debatin

Re: Could not send email to office 365

2013-05-02 Thread JoeSox
Our Technical Support is reporting a big jump in Outlook connectivity issues about 5-10 minutes ago. Our resolvers are testing fine. -- Thanks, Joe On Thu, May 2, 2013 at 4:53 AM, Joe Abley wrote: > > On 2013-05-02, at 02:42, Cathy Almond wrote: > > > This may be a red herring, but I've heard

Re: Could not send email to office 365

2013-05-02 Thread Joe Abley
On 2013-05-02, at 02:42, Cathy Almond wrote: > This may be a red herring, but I've heard of some dropping of DNS > queries for the names within outlook.com domains where the queries are > all coming from source port 53 (i.e. your recursive server doesn't use > query source port randomization ..

Re: Could not send email to office 365

2013-05-01 Thread Cathy Almond
On 01/05/13 10:21, ISHII, Yuji 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 MX > record, got Timeout. > > Does anyone have the same issue?

RE: Could not send email to office 365

2013-05-01 Thread Ryan Finnesey
@nanog.org Subject: Re: Could not send email to office 365 Ryan, Is your Office 365 account also in an upgrade status? If not, have you completed the upgrade? -- Thanks, Joe On Wed, May 1, 2013 at 8:42 AM, Ryan Finnesey wrote: > I am also having the some issues going on 3 weeks now. I cannot

RE: Could not send email to office 365

2013-05-01 Thread Ryan Finnesey
are unable to connect. I thought the problem is fixed but now it is back. -Original Message- From: Warren Bailey [mailto:wbai...@satelliteintelligencegroup.com] Sent: Wednesday, May 1, 2013 12:12 PM To: JoeSox; nanog@nanog.org Subject: Re: Could not send email to office 365 Just another

RE: Could not send email to office 365

2013-05-01 Thread Keith Medcalf
Device > > > > Original message > From: JoeSox > Date: 05/01/2013 6:27 AM (GMT-08:00) > To: nanog@nanog.org > Subject: Re: Could not send email to office 365 > > > The company I work for has been having Outlook connectivity issues > (intermittent for only

Re: Could not send email to office 365

2013-05-01 Thread Jay Ashworth
- Original Message - > From: "Tony Patti" > After our "upgrade", we started to see the body of received PLAIN TEXT > emails truncated at less than 256 bytes, > which frequently truncated emails in the middle of a word, the fix was > a "setting change". > > Since being standardized in 198

RE: Could not send email to office 365

2013-05-01 Thread Ryan Finnesey
...@swalter.com] 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 emails truncated at less than 256 bytes, which frequently truncated emai

RE: Could not send email to office 365

2013-05-01 Thread Tony Patti
XT emails would just work "out of the box". Tony -Original Message- From: Ryan Finnesey [mailto:r...@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 n

Re: Could not send email to office 365

2013-05-01 Thread JoeSox
Ryan, Is your Office 365 account also in an upgrade status? If not, have you completed the upgrade? -- Thanks, Joe On Wed, May 1, 2013 at 8:42 AM, Ryan Finnesey wrote: > 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 changi

Re: Could not send email to office 365

2013-05-01 Thread Warren Bailey
27 AM (GMT-08:00) To: nanog@nanog.org Subject: Re: Could not send email to office 365 The company I work for has been having Outlook connectivity issues (intermittent 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 i

RE: Could not send email to office 365

2013-05-01 Thread Ryan Finnesey
: Re: Could not send email to office 365 The company I work for has been having Outlook connectivity issues (intermittent 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

Re: Could not send email to office 365

2013-05-01 Thread JoeSox
The company I work for has been having Outlook connectivity issues (intermittent 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 upd