-- It just doest work across any mail app. Which mail app...

[mdk]

@ThisIsJimmy -- It just doest work across any mail app.

Which mail app are you using?

The whole concept, namely "authenticating" to Shaw's mail-server, before trying to send through Shaw's mail-server, is supposed to work, when your device is NOT connected through Shaw Internet. 

Authentication is there to prevent spammers/scammers, connecting via their non-Shaw Internet access, from abusing Shaw's mail-server to spread their content.

Your E-mail client will need to support such "authentication". Which client?

[rinrat86]

I can't say for others having the problems - especially since some seem to be unable to send over data, where my problems have been sending over wifi (usually). I've had problems with gmail client, samsung email client, thunderbird for android, and whatever the mail client on iPad is.  All of them have had sections where I configure the authentication, all of them have had problems.

At some point maybe Shaw should stop pointing the finger at everybody and everything else and admit that there is some kind of problem with their authentication process.

If they had a mail client perhaps I'd use it, but I don't use webmail unless I am absolutely forced to because it really, really sucks, especially on a mobile device.

[nevinet]

Having same problem and tech support ladies have no clue. They say it's a third party and not their problem. 🤐

[mdk]

@nevinet -- when your device is connected to the Shaw network, your computer can send E-mail to Shaw's mail-server, without the need for any additional "authentication" that authorizes you to send to Shaw's mail-server.

When your device is connected to some other network, your E-mail program needs to authenticate, by sending your Shaw ID and password to Shaw's mail-server, before that mail-server will accept your messages.

So, check the configuration of your E-mail program, to add that authentication.

[dimaio]

unable to access my computer nor the E-MAIL, unless i go to incognito with I.D and Password, Shaw was unable to fixt my problem

it is been months frustrating ..................

[Aquagem1030]

cannot authenticate and CHANGE PASSWORD OF R THE SERVER OUTGOING.

[mdk]

@Aquagem1030 -- what went wrong when you followed Shaw's instructions:

    https://support.shaw.ca/t5/internet-articles/how-to-set-up-your-shaw-email/ta-p/6497

?

[lbaron321]

I had SUCH issues with this - and I couldn't figure it out at all!   

Until I changed one setting - I don't know why but my phone had been set to not roam.  when I turned on roaming again, my email was no longer rejected by the Shaw server...   Not sure why - but there it is :).  I hope that helps someone out there! 

[mdk]

@lbaron321 wrote: when I turned on roaming, my email was no longer rejected by the Shaw server... Not sure why ...

Did you "roam" onto a ShawOpen (or RogersOpen) wireless access point, and thus get connected to the Shaw/Rogers network, to validate your connection to Shaw's mail-server?

[BCatBC]

My wife and I were having this exact same problem with our Samsung phone and trying to send emails while on our cell network rather than Wi-Fi where it worked.

After reading this thread and trying a million different items I tweaked to the fact that when you're going through Wi-Fi you are not authenticating because you're already on Shaw's Wi-Fi at least we are. But when you're on a cell network they are authenticating.

So even though I hadn't changed my password in many months I decided to go to the password section in the outgoing server settings and type in my password again. Voila it worked!

My wife had not changed her shaw password in years but we tried the same trick and indeed it worked.  Somehow the password had got corrupted or some such and it was not passing it correctly to the shaw servers. Having said this Shaw support should have tried to figure this out just like I did so they are useless. In addition they should try to figure out why it happened in the first place since once again we have not changed our passwords in forever. So it obviously could happen again. 

Also Shaw email should have given a much clearer error message that the password is not correct not rather than just sticking the message in the outbox with a could not send message.  If I had received an incorrect password message I would have had this solved a long long time ago