Shaw seems to have gotten personal and business mixed together in a single action. They are probably cracking down on Shaw personal accounts that are "playing SMTP server", which is a common violation in the ISP world.

As for relaying, they ought to accept the use of their mail server for relaying as long as you're only doing it from equipment connected to your Shaw internet service (and otherwise, they could accept uid/pw authenticated access to their mail server).

easyDNS addresses this problem with their "SMTP port forwarding" feature:

https://easydns.com/features/smtp-port-forwarding/

easyDNS, just like Tucows/OpenSRS, is another totally Canadian gem based in Toronto.

Hartmut W Sager - Tel +1-204-339-8331

On Tue, 21 Jan 2020 at 12:27, Gerald Brandt <gbr@majentis.com> wrote:

Hi,

I've been fighting with Shaw for days on this. I have what they call a
business account with 8 static IPs.

I can telnet mail.shaw.ca 25 and get a connection. So, inside their
network, SMTP works.

If I try to telnet to any other server on port 25, i get no connection.
e.g. telnet to google email servers fails, telnet to my server in
Montreal fails.).

To test that port 25 was open, they had me start Firefox, login to
gmail, and send an email from my gmail to my gmail account. that was
proof they weren't blocking port 25... Yeah.

Right now, in order to get email out, i am using mail.shaw.ca as a
relay. That is not supported, so they are asking me to not do that. I
told them if I don't use them as a replay, i can't get email out. They
did not understand.

Does anyone have any idea how to get these guys to understand what is
going on? Am i using the wrong terminology? I can't see how I can make
it any clearer to them that they are blocking port 25 access to any
system outside of their network.

Gerald

_______________________________________________
Roundtable mailing list
Roundtable@muug.ca
https://muug.ca/mailman/listinfo/roundtable