-- Even when I send to my own Shaw address from the resid...

[mdk]

@dvrich -- Even when I send to my own Shaw address from the residents association email address (I'm the secretary of the association) as part of a bulk email message, it gets blocked.  

What E-mail program are you using to send from that R.A. ID?

Is that computer connected to a Shaw cable-modem, or to a TELUS device?

Can you please post that "blocked" message -- after blanking-out the "username" field of each Shaw recipient, to let us see "all" the E-mail headers, including any error-message that references "blocked" ?

[dvrich]

The email is through "web names.ca".  The computer, my home computer, is connected to a Shaw cable-modem.  This particular email went to only eight Shaw email customers, including my own Shaw email, all as Bcc, and still got delayed and eventually was not delivered after three hours.  Here's the email:

From: postmaster To: XXXX@erans.ca

Warning: could not send message for past 1 hour

03 May, 22 2:21:42 PM

   **********************************************
    **      THIS IS A WARNING MESSAGE ONLY      **
    **  YOU DO NOT NEED TO RESEND YOUR MESSAGE  **
    **********************************************

The original message was received at Tue, 3 May 2022 13:18:18 -0700
from:
<XXXX@erans.ca>

   ----- Transcript of session follows -----
... while talking to shw-central.mx.a.cloudfilter.net.:
>>> RCPT To:<AAAA@shaw.ca>
<<< 421 4.1.1 lzxknAsOzykZUlzxlnCu00 internal error AUP#SMTP
<AAAA@shaw.ca>... Deferred: 421 4.1.1 lzxknAsOzykZUlzxlnCu00 internal error AUP#SMTP
<BBBB@shaw.ca>... Deferred: 421 4.1.1 lzxknAsOzykZUlzxlnCu00 internal error AUP#SMTP
<CCCC@shaw.ca>... Deferred: 421 4.1.1 lzxknAsOzykZUlzxlnCu00 internal error AUP#SMTP
<DDDD@shaw.ca>,<EEEE@shaw.ca>,<FFFF@shaw.ca>,<GGGG@shaw.ca>,<HHHH@shaw.ca>... Deferred: 421 4.1.1 lzxknAsOzykZUlzxlnCu00 internal error AUP#SMTP
Warning: message still undelivered after 1 hour
Will keep trying until message is 3 hours old

Reporting-MTA:Arrival-Date:

dns; mx1.webnames.ca

Tue, 3 May 2022 13:18:18 -0700

Final Recipient:Action:Status:Last-Attempt-Date: RFC822; AAAA@shaw.ca delayed 4.2.0 Tue, 3 May 2022 14:21:42 -0700

Final Recipient:Action:Status:Last-Attempt-Date: RFC822; BBBB@shaw.ca delayed 4.2.0 Tue, 3 May 2022 14:21:42 -0700

Final Recipient:Action:Status:Remote-MTA:Diagnostic-Code:Last-Attempt-Date: RFC822; CCCC@shaw.ca delayed 4.1.1 DNS; shw-central.mx.a.cloudfilter.net SMTP; 221 2.0.0 shw-ibgw-4003a.ext.cloudfilter.net cmsmtp closing connection Tue, 3 May 2022 14:21:42 -0700

Final Recipient:Action:Status:Remote-MTA:Last-Attempt-Date:Will-Retry-Until: RFC822; EEEE@shaw.ca delayed 4.2.0 DNS; shw-central.mx.a.cloudfilter.net Tue, 3 May 2022 14:21:42 -0700 Tue, 3 May 2022 16:18:18 -0700

Final Recipient:Action:Status:Remote-MTA:Last-Attempt-Date:Will-Retry-Until: RFC822; DDDD@shaw.ca delayed 4.2.0 DNS; shw-central.mx.a.cloudfilter.net Tue, 3 May 2022 14:21:42 -0700 Tue, 3 May 2022 16:18:18 -0700

Final Recipient:Action:Status:Remote-MTA:Last-Attempt-Date:Will-Retry-Until: RFC822; FFFF@shaw.ca delayed 4.2.0 DNS; shw-central.mx.a.cloudfilter.net Tue, 3 May 2022 14:21:42 -0700 Tue, 3 May 2022 16:18:18 -0700

Final Recipient:Action:Status:Remote-MTA:Last-Attempt-Date:Will-Retry-Until: RFC822; HHHH@shaw.ca delayed 4.2.0 DNS; shw-central.mx.a.cloudfilter.net Tue, 3 May 2022 14:21:42 -0700 Tue, 3 May 2022 16:18:18 -0700

Final Recipient:Action:Status:Remote-MTA:Last-Attempt-Date:Will-Retry-Until: RFC822; GGGG@shaw.ca delayed 4.2.0 DNS; shw-central.mx.a.cloudfilter.net Tue, 3 May 2022 14:21:42 -0700 Tue, 3 May 2022 16:18:18 -0700