حل مشكلة The mail server detected your message as spam and has prevented delivery 50

[Rise Company]

حل مشكلة The mail server detected your message as spam and has prevented delivery 50
Fixing the Error “The mail server detected your message as spam and has prevented delivery”?
Mail delivery failed: returning message to sender

https://www.rise.company/forum/images/imported/2021/11/7.jpg

Whitelisting can be done, however rejected email looks very unprofessional and causes costly delays. It should goto the spam folder, not be rejected.

المشكلة :

عند ارسال احد ايميل الى السيرفر يحدث reject اى bounce وهو ارتداد الايميل فى الحال
ومكتوب ان الايميل المرسل رفض استلامه من طرف السيرفر المرسل اليه بسبب ان الايميل مصنف سبام
ولا يظهر فى track delivery لانه حدث له reject من الاصل فلم يستلمه السيرفر المستقبل
ولكن يظهر فى track delivery فى السيرفر المرسل ان الايميل خرج بشكل سليم.

حل المشكلة :

قم بالغاء خاصية الارتداد من Apache SpamAssassin” reject spam score threshold
داخل Exim Configuration Manager حتى لا يحدث ارتداد نهائيا وهو الافتراضى
ولكن اطمئن فمن داخل اعداد cpanel هيصنف انه اسبام و هيخذن فى spam
او هيحدث auto delete اذا كنت مفعل عند قمية 8 واكثر مثلا
ولكن اهم ميزه من الغاء bounce هو تجنب Mail delivery failed: returning message to sender
وان تشاهد الايميل فى Track Delivery وهى ميزه رائعة.

شاهد ايضا
حل مشكلة 550 "The mail server detected your message as spam and has prevented deliver (https://www.rise.company/forum/threads/33694-%D8%AD%D9%84-%D9%85%D8%B4%D9%83%D9%84%D8%A9-550-The-mail-server-detected-your-message-as-spam-and-has-prevented-deliver) المرجع:
https://hoststud.com/resources/fixing-the-error-%E2%80%9Cthe-mail-server-detected-your-message-as-spam-and-has-prevented-delivery%E2%80%9D.676/

[Rise Company]

Fixing the Error “The mail server detected your message as spam and has prevented delivery”?

Email admins often have to deal with email bounce and bounce backs. High bounce rates means something is wrong with your email server. If you’re regularly seeing the bounce error message that reads “The mail server detected your message as spam”, then you have to fix the issue before you start sending further messages. In this article, we’ll explain how to fix this error.

Why an Email Bounces After Panel Updates?

Emails are sent from one server to another through the SMTP or Simple Mail Transfer Protocol. The email is sent from the sender to sender’s MX to the recipient’s MX and the finally to the recipient. So you can say there’s four layer of transmission. If an error occurs at any of these level, you’ll receive a DNS message also known as a bounce message explaining what went wrong.

The message you receive is an “email bounce back”. This contains information on why your email bounced and not delivered to the intended recipient. In this case, the message you sent from your mail server was detected as spam by the recipient's mail server.

How to Fix the Spam Message Error?

To fix this problem, you need to use a tool called Apache SpamAssassin. This is a proprietary tool that checks for spam characteristics, conducts network tests, and then automatically discards messages.

To use the SpamAssassin, follow the steps:



[*=center]Login to your Web Host Manager (WHM)
[*=center]Navigate into your Exim Configuration Manager.


https://www.rise.company/forum/images/imported/2021/11/6.jpg



[*=center]Next inside the Manager, go under the Filters tab in Basic Editor Mode


https://www.rise.company/forum/images/imported/2021/11/7.jpg



[*=center]You’ll find the “Apache SpamAssassin” reject spam score threshold. Set it to 4 or less. In this way, whenever the spam score is above 4, it’ll mark the message as spam. By default this is set to no bouncing. Even the recipient server can view this as a spam source since there is no filtering in place.


https://www.rise.company/forum/images/imported/2021/11/8.jpg



[*=center]Finally, click the “Save” button which will save the changes made.


This should fix the error and you’ll not be receiving those annoying bounce back messages. When making these changes, you should keep in mind that the changes will affect to the entire server. You should aware all your users of the applied changes.

If the problem persists, it’s better to get in touch with your hosting provider regarding this.