Thread: Apex and Shaw
View Single Post
  #29  
Old 01-07-2017, 08:33 PM
Reyphox's Avatar
Reyphox Reyphox is offline
Member
 
Join Date: Jul 2015
Location: Vancouver, BC
Posts: 94
Reyphox is on a distinguished road
Default

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
Reply With Quote