Ok I have a ticket open about this that I opened up like 7 days ago and there
has been no response from Shaw on this. I sent all of this information via
email. Now I am a trained Network Admin myself and this is not a simple
settings issue or something like that.
This error seems to be occurring randomly sometimes mail goes though ..
other times I get this error.
"Task 'jamieresume -[at]- shaw.ca - Sending' reported error 0x800CCC6F 'Your outgoing (SMTP)
email server has reported an internal error. If you continue to receive this message
contact your server administrator or internet service provider (ISP).
The Server responded 554 mo22.dcs.int.inet.shaw.ca ESMTP server not available"
Now I did munge my email address above to prevent it from being harvested by spammers
Now a copy of the error can also be seen at Shaw Mail Error Aug 15 2018 — imgbb.com
And yes I know the password for the account and it is the correct one and I can
log into http://webmail.shaw.ca/ successfully using that login name and password
so I don't believe it is a password issue.
The ticket number is Incident: 180815-005566 now I have not heard any kind of a response
on this ticket either no one has contacted me about it. I did call in to the tech support
again about this problem because it is still occurring.
Now I have tried to google that error message number and there isn't really any kind of a
solution that fits my situation. This isn't a PC issue because I can get the same
error from two different machines I have here one running Windows 10 and a 2nd
running Windows 7. Two different PCs and the same error that rules out
that it is any kind of a PC issue.
This is not a configuration issue here either my outgoing mail server is
mail.shaw.ca and my incoming pop server is set to pop.shaw.ca
Now as per the information I found the settings are the same for Outlook 2013 and 2016
I have followed this to double check my settings I also removed
the account from my Outlook 2016 and re-added it right from the start
and I still get the same error message.
Now for a mail client I am running Outlook 2016
Microsoft Outlook 2016 MSO (16.0.10325.20082) 32 Bit
Now the funny part is that even if I telnet to mail.shaw.ca port 25 which
is the Shaw mail server with no SSL encyption on it I get the same error.
I have a Linux box sitting here as well as I said I am a trained network admin
myself and that was what I was using to telnet directly to the mail server
for this test.
Here is the output I get when I telnet directly to the mail server
telnet mail.shaw.ca 25
Connected to shawmail.glb.shawcable.net.
Escape character is '^]'.
554 mo21.dcs.int.inet shaw.ca ESMTP server not available
Connection closed by foreign host.
It shouldn't just immediately close it should sit at a prompt and wait
for a HELO or EHLO response to identify yourself. But instead the
mail server immediately spits out this error message.
This also rules out any kind of a mail client configuration issue as well.
So what gives Shaw everything I can see is pointing to a mail server issue on
your side. Maybe a load issue because as i said this is happening randomly
sometimes and email will send other times it will not from my Shaw email
address. It is totally random if the email is going to go. I have tried some with mail
attachments and some without mail attachments and it doesn't seem to
matter I have tried some with no attachments and get the same error.
This problem is still ongoing at this point and I have tried this from two different
machines here as well my main machine running Windows 10 and a 2nd machine
running windows 7 and both will get the same error. So that rules out any PC issues.
Also so you know that I do run Kaspersky Internet Security Version 22.214.171.1245(i)
on the PCs but I have totally disabled it and shut it down for testing purposes
and I still get the same error. So that kind of rules out any kind of security package
or Anti-Virus issue here.
Also yes I have tried setting up the secure mail connection as well using port 587 for the outgoing mail server and
port 995 for the incoming mail server and I still get the same error it doesn't seem
to matter what one I use.
I am not using any kind of a VPN and when I was on the phone I read him the IP I am currently
assigned and it does come back to being owned by Shaw Communications 126.96.36.199
"Shaw Communications Inc"
Not using a VPN or anything like that as I said the IP does belong to Shaw.
It is now August 25 2018 and still NO answer from Shaw.. I opened this ticket
(Incident: 180815-005566) on August 15 2018 and STILL 10 days later and NO
one has sent me a response to this ticket via email or even called me.
This is Absolute bullshit this is the WORST customer service I have EVER seen
You are absolutely horrible Shaw! You are a disgrace to the industry!
I have the same issue which is periodic.....
"...Your outgoing (SMTP) e-mail server has reported an internal error. If you continue to receive this message, contact your server administrator or internet service provider )ISP). The server responded: 554 mo22.dcs.int.inet.shaw.ca ESMTP server not available CSI block.."
I have a similar issue but it is with Activesync on Shaw's side. I use Activesync to keep my Android phone and two computer email clients in sync with contacts and calendars. Everything was working great until maybe 6 -8 weeks ago. I thought it was something on my side but I have confirmed that it is on the Shaw side.
If I add a calendar entry or edit a contact on Shaw Webmail it doesn't reliably send the entry to all devices. When I do the same on my devices' client Shaw Webmail is not reliably updated. I turned on the the Activesync logging for my computer email client and the follow error is logged:
Web exception: The remote server returned an error: (500) Internal Server Error.
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<title>Error 500 Mailbox access error</title>
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /service/extension/zimbrasync. Reason:
<pre> Mailbox access error</pre></p><hr><i><small>Powered by Jetty://</small></i><hr/>
Before you ask, the password and user name are all good. Set up is all good. Nothing on my side changed.