550 Dangerous attachment detected

Avatar
Anonymous
  • updated
  • Answered
New InMotion hosting account: whenever I reply to an incoming email that has an image (eg company logo) in the sender's signature my email is quickly bounced back by the In-Motion server advising "550 Dangerous attachment detected" even though there is no attached file (eg pdf, jpg etc). If I remove the signature image in the message then the InMotion server will deliver it. Why the problem?

Pinned replies
Avatar
0
anonymous
  • Answer
  • Answered

Hello, and sorry to hear that  you're having trouble with the outgoing spam filter. Sometimes the filter will trigger due to a false positive from something like an image file due to the filename or formatting. By any chance was the incoming message formatted or displayed with email HTML? In my experience that is more likely to cause the filter to register the outgoing message filter to treat the message as spam. 

If that is not the cause, does the same issue occur if you save the image file and attach it to an entirely new message devoid of other formatting? If not, then it's likely an email header issue. If so, are there any features of the image or its filename that could possibly be causing it? Hopefully one of those pieces of information will help us narrow down what is causing the problem. 

Replies 1
Avatar
0
anonymous
  • Answer
  • Answered

Hello, and sorry to hear that  you're having trouble with the outgoing spam filter. Sometimes the filter will trigger due to a false positive from something like an image file due to the filename or formatting. By any chance was the incoming message formatted or displayed with email HTML? In my experience that is more likely to cause the filter to register the outgoing message filter to treat the message as spam. 

If that is not the cause, does the same issue occur if you save the image file and attach it to an entirely new message devoid of other formatting? If not, then it's likely an email header issue. If so, are there any features of the image or its filename that could possibly be causing it? Hopefully one of those pieces of information will help us narrow down what is causing the problem.