re. No need for any initial technical mumbo-jumbo. Soooo...

[bordoodle]

re.  No need for any initial technical mumbo-jumbo.

Soooo if there is a problem with server to server communications within Roger's / Shaw's data center in Calgary such as we're seeing with IMAP  then we, as users, can solve that problem by power cycling (turning off and back on) our gateways at home.  

The symptoms range from various users are:

- no symptoms and everything working fine.

- one IOS works and another beside it doesn't.

- duplicated contacts or messages.

- delete a message and there is a strike thru of the sender's name but the message doesn't move to the trash.

- an error message stating that, on a send, there was no password provided.

- there may be many more that I don't know of.

This may just be a sampling of the problems users are facing.  Based on that it's unlikely any one solution would help all users experiencing problems.  I applaud people like covkid that in spite of no help from customer service or poor / ineffective suggestions from others in this forum have managed to find a solution.

So all the user systems that have been running and stable for years and with no config changes all of a sudden its their fault when the data center hiccups?  

As for customer service it seems their script sentence 2 (or maybe sentence 3 but I'm not sure) is to ask users to unplug and then plug back in (power cycle) devices.  Imagine Google, Microsoft or Facebook IT power cycling all gateways, routers and firewalls rather than looking at the symptoms first.  As for mdk, Shaw customer service has a position for you.  It seems you don't have to read the script as you know sentence 2 already.  Its already proven, by other users here, that this is not the solution to the problem.  Just like the freezing / repeating video on many TV channels a couple of years back.

As for the IMAP problems Microsoft is having.  They have / were having IMAP issues with the NEW Outlook that they are trying to push people to and away from the older Windows Mail.  This is not to be confused with the present Rogers IOS and Outlook issues with IMAP.  Some Rogers / Shaw supervisors do not understand the distinction either.

So let's everyone take a deep breath, read EVERYONE'S comments and really, really, really understand what's going on before coming up with a mumbo jumbo solution.  Again, a tip of the hat to covkid.

[bordoodle]

Just thought everyone should know in case you don't know.

Finally got to another supervisor, this Sunday morning, who wasn't blaming users or Microsoft for the recent email problems.  She admitted not being heavy technical but knew enough to say the problem had been officially designated fixed Thursday last week and it was a CONFIGURATION issue.  Like that never happens (tongue in cheek).  

We decided that the next time someone makes a config change and it fails like this one then they can't leave the computer room until its fixed.  You can only leave for a bio break, no going home, nothing.  You stay !!!!  Also, you only get diet coke and cold pizza with bad toppings until you correct your mess.

Merry Christmas to all.

[mdk]

@bordoodle wrote  an error message stating that, on a send, there was no password provided.

If your portable device, such as a notebook computer or an iPhone, is connected to your home WiFi, then you can send an E-mail message through Shaw's mail-server. The IP-address assigned by Shaw to the cable-modem/router is within Shaw's network, and that "authenticates" you to send without using a password.

However, if your iPhone is connected through a non-Rogers cellular network, or a non-Rogers WiFi Access Point (such as TimHortons, Starbucks, et cetera) you must use your E-mail password as authentication when sending an E-mail.

So, if a user cannot send, it is their E-mail configuration that is causing their issue.

[mdk]

@bordoodle wrote: We decided that the next time someone makes a config change and it fails like this one ...

A previous employer had a "Quality Assurance Board'.  If someone wanted to make a change, they would create a document to define the change, its priority, and, most important, complete the "fallback" section of the document to describe what happens in any SNAFU. Changes were never allowed to be made on Friday -- so that nobody need be called-in on Saturday/Sunday.  Everybody on that Q.A.B. would assess the proposed change, and 100% approval needed to be granted.

That is a "best practises" approach to control I.T. -- using pizza & carbonated 0% beverage is no way to run a business.