Apex and Shaw

[Simons]

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

[Aquattro]

Originally Posted by Simons

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

Nope, just sent a test on 25, non authenticated

[Aquattro]

download smtp tester and try 25, works fine

[Aquattro]

As a second test, I just drove my temp down to 74 and immediately got an email alarm. I suspect the "test" function isn't working in the networking config.

[Aquattro]

Although, the email came from fusion, not base unit. Not sure if that's by design, or two separate systems.

[Aquattro]

My base is set to send via smtp thru Shaw. Email gets sent to gmail account. Fusion is sending me email to gmail account, not sure if that's tied to the base unit config, or something I set up initially with fusion.
Shaw mail does relay to gmail using port 25, no SSL using SMTP applet.

If you're using all Shaw, maybe there's a problem with your account?

[Simons]

according to the shaw guy I spoke to they are initiating all these changes globally at various times. It is possible that your area just might not be affected yet.

For now I can setup an email alert in Fusion, but are you able to txt? I do not see Telus in the list of carriers?

[Simons]

Originally Posted by Aquattro

As a second test, I just drove my temp down to 74 and immediately got an email alarm. I suspect the "test" function isn't working in the networking config.

I just turned my email alert to on and got an email only from fusion not from the Apex and I didn't get a txt.

[Aquattro]

I don't use the text feature, email works the same.

[Simons]

I want everyone to know that shaw is migrating their email settings, I have posted this issue on the neptune website here:



https://forum.neptunesystems.com/sho...3640#post73640


BE WARNED, you must take action or you will not get notifications directly from your Apex base unit.