The only work around I found is to not include http://, just use the bare domain.
Personally, I find this behavior of my SMS provider reprehensible.
The only work around I found is to not include http://, just use the bare domain.
Personally, I find this behavior of my SMS provider reprehensible.
Cut and pasted the list and the message wouldn't send.
Narrowed it down to one. Typed just the bare domain. Wouldn't go through. (It was something incredibly benign like n17.org)
Couldn't find a history on that domain name for why it would have been filtered.
At least messenger responded with 'couldn't send message' but still no clue as to why... and it took me sending each domain name individually until I found the one that was failing the entire message.
A true hacker would have used binary search ;)
Well, from their perspective. Not from any reasonable perspective; I have a few obviously-spam emails in my gmail spam folder right now, but I've had plenty of problems with gmail refusing to deliver completely legitimate email to me.
I suspect any more than you see
They need to tune whatever they're doing down to the point that legitimate personal communication at least shows up in the spam folder. If a lot more spam shows up in the spam folder too, so what? A spam folder that contains mostly spam and also some misclassified personal messages is significantly better than a spam folder that contains nothing but spam because it automatically dropped your misclassified personal messages.