Shaw has blocked my emails from being recieved by Shaw users.

nmses
Grasshopper

We are a Not for Profit Society with over 300 members in Nanaimo and we send regular updates through our GSuite email to our membership.  (They have the option to opt out).  Our email address has been blocked by Shaw and none of our members with @shaw emails can receive our emails.  We are trying to let everyone know to add us to their save email list but that is hard to do when we cant email any of them.  Is there a way to have our email unblocked?

Any assistance is appreciated.

Labels (1)
5 Replies

Re: Shaw has blocked my emails from being recieved by Shaw users.

shaw-tony
Moderator
Moderator

Hey nmses,

Thank you for reaching out! There is a limitation on how many emails you can send out at once. I believe you can send up to 20 recipients before it gets marked as spam. I will recommend sending smaller batches to see if they go through for your members to update their spam settings similar to below and whitelist your email address with the steps here.

Hope that helps,

Tony | Community Mod.

0 Kudos
Reply
Loading...

Tony, this is a silly solution. This will put all spam in...

Kentabel
Grasshopper

Tony, this is a silly solution. This will put all spam into each person's inbox. Who would want to do that?

The  problem is not in each individual's email settings; rather, the problem is that the Shaw server is incorrectly marking emails from this domain as spam. The answer is simply for you (Shaw) to unblock the domain. Surely that's much easier for Shaw to do rather than to ask everyone to adjust settings. 

It's a problem that doesn't just affect this particular domain -- I'm on this string because I just tried to send an email from my work address (using the 1and1 domain) to my home address (a Shaw address) and it bounced. We had the same problem last week with a different domain. It seems that Shaw's settings are simply too sensitive. 

If Gmail can do it, so can you.

Kent

0 Kudos
Reply
Loading...

-- it bounced. What error-message was contained in that "...

mdk
Legendary Grand Master

@Kentabel -- it bounced.

What error-message was contained in that "bounce" message?  Please post it.

>>  I believe you can send up to 20 recipients before it gets marked as spam.

Once a month, I send a short E-mail to 130 subscribers, via Shaw WebMail. I do not get any "bounce" messages.  However, if I try to send the same E-mail to 140 subscribers, I get an immediate "rejection" pop-up, citing that one of the IDs (between #131 and #140) is invalid, and the message does NOT get sent.  If I remove #131 to #140, and send to them in a separate E-mail, they receive the message -- no "invalid ID" error-message.

None of the subscribers (including my ID) get the E-mail with the "suspected spam" prefix on the SUBJECT line.

 

0 Kudos
Reply
Loading...

Here's one of the error messages. Please forgive me if I...

Kentabel
Grasshopper

Here's one of the error messages. Please forgive me if I posted too much. And for the record... my messages did not bounce back today (I just tried). MDK, if that is your doing, I thank you!


-------- Forwarded Message --------

Subject:Date:From:To:

Mail delivery failed: returning message to sender
Thu, 17 Dec 2020 00:37:54 +0100
Mail Delivery System <mailer-daemon@perfora.net>
k.dykstra@credochs.com



This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of
its recipients. This is a permanent error. The following address(es)
failed:

kentabel@shaw.ca:
SMTP error from remote server for MAIL FROM command, host: smtp.glb.shawcable.net (64.59.136.136) reason: 550 5.1.0 <k.dykstra@credochs.com> sender rejected



--- The header of the original message is following. ---

Received: from [192.168.0.180] ([154.20.250.228]) by mrelay.perfora.net
(mreueus002 [74.208.5.2]) with ESMTPSA (Nemesis) id 0LufTy-1k7eQw0Ykq-00zoKy
for <kentabel@shaw.ca>; Thu, 17 Dec 2020 00:37:50 +0100
Subject: Fwd: Tonight'smeeting
References: <13e14519-25a4-8d8d-8c00-1aed23ddad49@credochs.com>
To: Kent and Belinda Dykstra <kentabel@shaw.ca>
From: Kent Dykstra <k.dykstra@credochs.com>
X-Forwarded-Message-Id: <13e14519-25a4-8d8d-8c00-1aed23ddad49@credochs.com>
Message-ID: <1aed3325-b823-fd73-0530-30c6cce335ca@credochs.com>
Date: Wed, 16 Dec 2020 15:37:49 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <13e14519-25a4-8d8d-8c00-1aed23ddad49@credochs.com>
Content-Type: multipart/alternative;
boundary="------------5988E3FE0B9CEF37A1865DBB"
Content-Language: en-US
X-Provags-ID: V03:K1:pjHxK9MymEFlnFPsBbWYBO1T60/NxaTTdZDshnZYHxiRXL/msOj
45ytO4lBFvAZ0Gw9H0Har8HfhnrdgCa+BkEklGPNIsXsEJ4s3LW+WkjhsjV7N61iOMwmD4G
P0hm7GGgPv1Xao6U1L+LO4X5gmf42mQwns4d3RH8TaJj5ApsmeVXZKOP3oKyTfvJWeARORC
fBucVgb5lqN4o87+IQFFA==
X-Spam-Flag: NO
X-UI-Out-Filterresults: notjunk:1;V03:K0:lGGAUCwN9XE=:UikLsV9q5Y8rdHkBp6O4oC
0Dq8VoTfdswF+0Cfv+AYo5ex/4PgmVtySxTxG23h2atHa9WsHxgnzuTR2aJRDjuU9sZTalmac
56WbHIYEob35a+nhWmzzaXON3XHsid6mevmmvelZvGfL1LIq0xHXvhdqEkPfZTbolpidMxKWt
Cugq5fm2PjR8/HtoH07gfgBqwC7acJEI1z1LLth/psijvWfsQfacfMxD5TSLEzQ4LQolvd9s6
KdvAi16IHjPSfuCnALpyolt56moXR6fElZN0QI+6yEU68YQy3el5LL7enZ3neLSKNVUQMkbKA
u2Uk9Lias0zDg9Ua/WeZ0/RoWVJOk0PfoSWhg0Vzm2WEMpOvfknDC854LRSf/e4aaGUGuh/5j
649kGIvRRQ3GvBnOiJfndQGWuHDGUQkEmgTkfLwdHhPCAurUu9s7IqdRLprGiP2HSHC2bKUp2
GCO/25+zOw==

0 Kudos
Reply
Loading...

-- MDK, if that is your doing, I thank you! No. Not me. I...

mdk
Legendary Grand Master

@Kentabel -- MDK, if that is your doing, I thank you!

No. Not me. I have never worked for Shaw; nor have I ever been employed by Shaw.  🙂

> Received: from [192.168.0.180] ( d154-20-250-228.bchsia.telus.net [154.20.250.228]) by mrelay.perfora.net ...

That looks perfectly normal: from a "private" IP-address connected to your Telus modem to a well-known "mail-relay" that connected to Shaw's mail-server.

Shaw's mail-server seems to NOT allow E-mail from non-registered domains, e.g., "spammer@not-trace-able.com". So, there might have been a "temporary failure" of Shaw's verification -- if some Internet segment was broken, or some DNS-server did not reply quickly enough.  So, a "no response" to Shaw's query could have been interpreted as "not valid".

 

0 Kudos
Reply
Loading...