Page 1 of 1
How to avoid this....
Posted: 16 May 2009, 16:09
by reactorh
How can i prevent spam from spammer that use same domains hosted in my server to send garbage to my clients.
I need to block this, and need to add this domains to the whitelist cause real emails some times gets blocked.
Thx
Posted: 17 May 2009, 11:41
by Sarah
It would be much better to find out and resolve the reason that legitimate emails are being marked as spam rather than blanket whitelisting a domain, for the very reason you have discovered. However, if you are unable to avoid whitelisting the domain, then there is nothing at all you can do in MailScanner to stop getting the type of spam you are getting. That's what whitelisting does.
You could look into SPF, which is something we don't use or support so can't offer any advice on it.
Posted: 18 May 2009, 17:28
by reactorh
Ok,
I will try SPF.
How can i prevent that the file spam.whitelist.rules change itself, i always set a domain in no and when i look back it change to yes.
Thx
Posted: 18 May 2009, 18:38
by Sarah
You need to always edit the whitelist via either the WHM or cPanel front-end, not by editing the file directly.
Posted: 18 May 2009, 23:21
by reactorh
Ok, but via whm only has two options white list and black list.
I just need spam.whitelist.rules To: domain1.com and From domain1.com no
But it changes it self .
Thx
Posted: 19 May 2009, 23:19
by reactorh
Any light on this issue...?
Thx
Posted: 21 May 2009, 10:49
by Sarah
You can't do what you want while using our front-end. If you are just using a *domain* (rather than a specific email address) in the whiltelist or blacklist file, any lines that were modified or added manually will be overwritten by the MSFE back-end scripts. How the lines are written by the script is controlled by your settings for "Spam whitelisting (IP addresses are always set to From:). Either - From: FromOrTo:" etc. in WHM > ConfigServer MailScanner FE > MailScanner Front-End > Advanced Settings. Double conditions like "From x and To x" are not supported in the front-end.
That's just the way it is. We do it that way because the front-end is designed to include the most commonly desired configuration options and avoid the need for direct editing of the configuration and rules files.