ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Updates kill Office365 IMAP

    Scheduled Pinned Locked Moved News
    office 365microsoftupdatesimap
    12 Posts 5 Posters 2.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • scottalanmillerS
      scottalanmiller
      last edited by

      All depends on what you call an interruption. Is an account based failure an interruption? Is just IMAP an interruption?

      DashrenderD 1 Reply Last reply Reply Quote 0
      • stacksofplatesS
        stacksofplates @Dashrender
        last edited by

        @Dashrender said:

        This makes how many service interruptions for O365 since January 2015?

        Ha I've had one outage with Zoho in two years and it was from a DDOS attack, and I'm not even paying for it.

        1 Reply Last reply Reply Quote 0
        • Deleted74295D
          Deleted74295 Banned
          last edited by

          Not noticed a service interruption here, not for a couple of years.

          IMAP broken is annoying though.

          1 Reply Last reply Reply Quote 0
          • DashrenderD
            Dashrender @scottalanmiller
            last edited by

            @scottalanmiller said:

            All depends on what you call an interruption. Is an account based failure an interruption? Is just IMAP an interruption?

            you live in a state of interruption - so you no longer count.

            I would say that the IMAP problem is a service interruption - if users never used OWA, why would they start now because IMAP is broken. True some might, not sure if by now they all have moved over.

            JaredBuschJ 1 Reply Last reply Reply Quote 2
            • JaredBuschJ
              JaredBusch @Dashrender
              last edited by

              @Dashrender said:

              @scottalanmiller said:

              All depends on what you call an interruption. Is an account based failure an interruption? Is just IMAP an interruption?

              you live in a state of interruption - so you no longer count.

              I would say that the IMAP problem is a service interruption - if users never used OWA, why would they start now because IMAP is broken. True some might, not sure if by now they all have moved over.

              A year after going through and setting everyone up to use OA on the SBS2008 server i turned off IMAP at the firewall. I got calls quickly about broke email.

              DashrenderD 1 Reply Last reply Reply Quote 0
              • DashrenderD
                Dashrender @JaredBusch
                last edited by

                @JaredBusch said:

                @Dashrender said:

                @scottalanmiller said:

                All depends on what you call an interruption. Is an account based failure an interruption? Is just IMAP an interruption?

                you live in a state of interruption - so you no longer count.

                I would say that the IMAP problem is a service interruption - if users never used OWA, why would they start now because IMAP is broken. True some might, not sure if by now they all have moved over.

                A year after going through and setting everyone up to use OA on the SBS2008 server i turned off IMAP at the firewall. I got calls quickly about broke email.

                I plan to move people away from Outlook proper when I migrate them to Windows 10 and Office 2016. I won't even install Outlook, OWA or nothing.

                JaredBuschJ 1 Reply Last reply Reply Quote 0
                • JaredBuschJ
                  JaredBusch @Dashrender
                  last edited by

                  @Dashrender said:

                  I plan to move people away from Outlook proper when I migrate them to Windows 10 and Office 2016. I won't even install Outlook, OWA or nothing.

                  This is why I use Outlook
                  img

                  1 Reply Last reply Reply Quote 0
                  • DashrenderD
                    Dashrender
                    last edited by

                    There are always fringe cases. but most of my users are not such cases.

                    JaredBuschJ 1 Reply Last reply Reply Quote 0
                    • JaredBuschJ
                      JaredBusch @Dashrender
                      last edited by

                      @Dashrender said:

                      There are always fringe cases. but most of my users are not such cases.

                      My users either. Sadly two of those boxes are on premise still. One is Exchange 2007 and the other is Exchange 2010 and OWA sucks there.

                      I circle the O365 question back to the people involved every few months.

                      DashrenderD 1 Reply Last reply Reply Quote 0
                      • DashrenderD
                        Dashrender @JaredBusch
                        last edited by

                        @JaredBusch said:

                        @Dashrender said:

                        There are always fringe cases. but most of my users are not such cases.

                        My users either. Sadly two of those boxes are on premise still. One is Exchange 2007 and the other is Exchange 2010 and OWA sucks there.

                        I circle the O365 question back to the people involved every few months.

                        On premise at customer sites? Yeah mine too, and I'll be upgrading to Exchange 2016 very soon to give the better OWA experience before we move to O365.

                        1 Reply Last reply Reply Quote 0
                        • 1 / 1
                        • First post
                          Last post