I have many emails sent to me (as a reply) with *** SPAM *** in the subject line (because the emails we send out sometimes get triggered as SPAM by some school divisions and they are just replying).
I have then replied (sometimes forgetting to removing the "*** SPAM ***" in the subject line) and it hasn't been a problem so far.
The last email we sent with SPAM in the subject line was 2015-01-09.
1) We do have a static IP so that might be different? 2) We also have a Shaw business account (as opposed to home/personal)? 3) Maybe this is just new as of this week/month? 4) Maybe your client was legitimately sending SPAM and Shaw just blocked them until it stopped?
Bradford C. Vokey - Director ============================== Fortress Software Incorporated ============================== 390 Provencher Blvd Unit F Winnipeg, Manitoba, Canada R2H 0H1 ----------------------------------------------- Phone: (204) 231-3969 or 1-800-665-0396 FAX: 1-800-513-9356 ----------------------------------------------- mailto:fortress2014@matchomatics.com matchomatics.com spiritoos.com
On 2015-04-25 12:00 PM, roundtable-request@muug.mb.ca wrote:
Even funnier, what triggered it seems to be this: I'm trying to help my customer with Spam problems and the RT ticket he made (and hence email subject) had the word "Spam" and Shaw barfed it back and started the blocking without warning:
On 2015-04-25 Bradford C. Vokey wrote:
I have many emails sent to me (as a reply) with *** SPAM *** in the subject line (because the emails we send out sometimes get triggered as SPAM by some school divisions and they are just replying).
I have then replied (sometimes forgetting to removing the "*** SPAM ***" in the subject line) and it hasn't been a problem so far.
Yes, that should trigger it, based on what I just saw. Unless the Re: (yours would have had) changes things.
The last email we sent with SPAM in the subject line was 2015-01-09.
This is definitely something new Shaw is doing. The bounce format has changed, there's that weird domain in the error message, etc.
- We do have a static IP so that might be different?
- We also have a Shaw business account (as opposed to home/personal)?
For sure this would not apply to business/static. This is probably just personal only. Of course, you could test it using your home computers if you want to see if you get blocked :-)
I'd love for someone else with a home box using sendmail and smarthosts (and preferably a From: that isn't @shaw.ca) to send an email with SPAM in the subject :-) Prove me wrong...
- Maybe this is just new as of this week/month?
Yup
- Maybe your client was legitimately sending SPAM and Shaw just
Nope, impossible. I was monitoring exactly what was going out when they cut me off and since it was 1am almost nothing had gone out for hours.
Was their another reason they blocked me? Sure, maybe, who knows. But from what I can see, all emails went out fine, then one with SPAM in the subject then BOOM, blocked for about 18 hours.