constant message saying that my email message has inappropriate content and I cannot send it

[TessieTS]

Sorry your email could not be delivered due to content policy reasons. Please check your message content for URLs, content and subject matter that could be construed as Malware, Spam or Phishing before retrying. (6-1-1-1) ID 

OK

The message I am trying to send which keeps being blocked with the above pop up  is to trustees of a charity and deals with letters to a bank - I cannot think what content policy it could possibly contravene!

Any ideas as to how to solve this welcome!

[Christopher_G]

Hi @TessieTS 

Welcome to the community.

Is there an error code attached to that '(6-1-1-1)' message? Do you have a VPN activated? If so, could you try with it switched off please?

Chris

[TessieTS]

Yes, I do have an error code.  Do you need it?

I switched off the VPN and it made no difference.  I despair, it is just a simple message and now I shall have to phone everyone.

[licquorice]

.....or simply email them using a Gmail address

[TessieTS]

Thanks, I was thinking that I would have to resort to that and I shall take your advice but what is wrong with BT, I wonder?

[Christopher_G]

Yeah, what is that code, @TessieTS?

Have you tried changing the subject field? Sometimes some phrases can be picked up by the spam filters.

Chris

[TessieTS]

Tried the VPN approach and it did not work.  I set up a gmail account and send the message with no problems.

What's wrong with BT?!

[Peter_W]

Hi again @TessieTS.

How many people are you trying to send this email to simultaneously, and are you using Webmail or a separate client?
There have been a few previous threads where users have had trouble sending out to multiple people at once, as this it's triggering the spam filters thinking it's some form of circular.

Peter

[TessieTS]

Thanks for the response.  I was trying to send it to just 3 people, so not a round-robin type list.

[Peter_W]

Thanks @TessieTS, that definitely shouldn't be a problem in that case. 

Have you tried sending each email individually to see if it gives the same error?

Also which mail app are you using when sending these?
Peter