Apex and Shaw

Simons · #1 05-09-2015, 05:21 PM

I have noticed suddenly that I am not getting email or txt alerts from either of my Apex units (I have two). Nothing has changed in there settings, I have checked that the email passwords are valid etc. I attempted to do the email test option in the network setup and I do not receive any emails. Apex Fusion is logging alerts but I am not getting notified of them.

I thought maybe it was something to do with my router (I didn't change any setting on it either) so I put one of my APex units in the DMZ zone, just to be sure there isn't any port issues and still I am not receiving anything from my units.

All the web functionality is working, I can connect to them easily, control outlets etc...I know that my setting are correct, been running same setting for years now with no issues..why would BOTH my apex units suddenly not be able to send email alerts? If they are being logged in Fusion I know it is communicating...

I am not a novice with networking or port forwarding etc so I am really baffled. The only way I noticed is when I do a water change my temp on my probe can go below the alarm setting because it is out of the water, I noticed I got no email or txt notifying me of this. I ran tests on my other tank, and sure enough I am not getting anything from it either....

has shaw changed something on their end? SMTP ports? did they change their mail server from shawmail.cg.shawcable.net??

Can someone else on shaw do an email test from their Apex to see if you are getting them?

Aquattro · #2 05-09-2015, 05:35 PM

Just sent a test. Waiting. I did get some alerts last month, but it's not something that triggers often. I'll update in a few..

Aquattro · #3 05-09-2015, 05:41 PM

nothing yet

Simons · #4 05-09-2015, 05:46 PM

I know it isn't my networking settings, fusion is connected and I can control everything..just the email / txt portion isn't working...must be shaw is all I can think of....

there appears to be someone else having issue with 'shaw' email I noticed on the Neptune forum.

https://forum.neptunesystems.com/sho...highlight=shaw

Aquattro · #5 05-09-2015, 06:08 PM

Ya, all my remote stuff works, just email. Like I said, I got a warning last month, so if they changed something, it's recent. I use mail.shaw.ca, tried both 25 and 587, no luck.

Simons · #6 05-09-2015, 06:13 PM

I just spoke with Shaw, they said they are now requiring SSL and port 587

Aquattro · #7 05-09-2015, 06:15 PM

Just used a SMTP tester to send test to the config as detailed in Apex and it works fine. Not a Shaw thing

Myka · #8 05-10-2015, 04:07 AM

Bummer

Reyphox · #9 01-07-2017, 08:33 PM

Shaw is not pulling the plug on SMTP. Most of the Shaw representatives have zero clue about anything and read of a screen, that or they simply offer a solution that would work and say it's has to be that's way to save time on trouble shooting. The reason it stopped working is simply because the setup was not bullet proof. Because I don't know what the provider of the sending address the was I will provide the two most likely reason why it had stopped working and the solutions, one of which the Shaw representative did offer but gave a stupid explaination why.

Scenario #1:

Emails bounced of Shaw SMTP server with a Shaw domain sender address. This is a simple one. Shaw allows you to send unauthenticated emails of their SMTP server on port 25. Reasons for sent emails are either too many none authenticated emails are being sent, the Shaw address is spoofed or Shaw has updated spam filters ( usually makes them more aggressive ) resulting in the emails being tossed on the server end.

The solution is simple, just have the apex login to Shaw before sending which does require SSL. This is what the representative offered but they explained the reason poorly.

Scenario #2:

Emails bounced of Shaw SMTP server with a Gmail ( or other providers ) domain sender address. This issue is rather decieving because you think it's Shaw when it's not. In actuality it's gmail blocking the email. Here is why. Google and other providers such as Microsoft have updated SPF records indicating that any email sent with their domain must be sent thru their servers. So when you bounce an email that looks like it's sent of an Gmail address thru a Shaw server, google flags it as spam and either places it in junk or eventually tosses them before you even recieved it.

Again the solution is rather simple, have the machine login to gmail ( or whatever the provider is ) instead of Shaw and the problem is resolved.

One other solution for both:

Another solution as mentioned by another poster is to use a 3rd party email relay service such as SMTP2GO. This still breaks SPF rules but the emails should never be completely filtered because 3rd party relays are trusted and run thier own filters so worst case scenario your emails get placed in junk but but never completely filtered out. And usually the 3rd party relay gives you notifications in thier control panel if some of your emails are being suspected as junk so you can rectify the problem before it gets worse.

Sent from my SM-G920W8 using Tapatalk

Lesteraction · #10 03-08-2023, 05:27 PM

I am pretty perplexed because I am not uninitiated with networking or port forwarding, etc. The only thing I noticed is that my probe's temperature can drop below the alert setting when I change the water because it is out of the water. I also noted that neither an email nor a text message notified me of this. I performed testing on my other tank, and sure enough, I am seeing the same problem there.