SOLVED Disable Outgoing Spam Filtering for One IP or User

GeekOnTheHill

Active Member
Feb 16, 2015
25
5
3
cPanel Access Level
Root Administrator
I would like to selectively disable all outgoing spam filtering for my own account or my own IP. I am the server admin.

I have disabled outgoing spam filtering for my (static) IP and whitelisted it everywhere I can find in the Exim configuration, but my outgoing mail is still being scanned, and mail identified as spam is being bounced back.

The reason I want to disable spam filtering from my IP or user account is so I can forward spam that I receive to SpamCop. I can't do that because the spam filtering is correctly identifying the spam as spam.

I have been forwarding spam to SpamCop through one of my off-server mail providers for about 10 years, but they recently stopped allowing it.

Thanks.
 

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,912
2,241
363
Hello,

You can modify the global SpamAssassin configuration file to whitelist the domain name. It's located at:

Code:
/etc/mail/spamassassin/local.cf
Once you make the changes, restart SpamAssassin with the following command:

Code:
/scripts/restartsrv_spamd
Information on the specific rules available for whitelisting are available at:

Mail::SpamAssassin::Conf - SpamAssassin configuration file

Thank you.
 

GeekOnTheHill

Active Member
Feb 16, 2015
25
5
3
cPanel Access Level
Root Administrator
Hello,

You can modify the global SpamAssassin configuration file to whitelist the domain name. It's located at:

Code:
/etc/mail/spamassassin/local.cf
Once you make the changes, restart SpamAssassin with the following command:

Code:
/scripts/restartsrv_spamd
Information on the specific rules available for whitelisting are available at:

Mail::SpamAssassin::Conf - SpamAssassin configuration file

Thank you.
Thank you. I'll give that a try. I was unaware that that the local.cf file affected outgoing scanning, as well.
 

GeekOnTheHill

Active Member
Feb 16, 2015
25
5
3
cPanel Access Level
Root Administrator
Okay, that worked. What I did was whitelist the recipient using this line in local.cf:

Code:
all_spam_to *@spam.spamcop.net
I whitelisted the recipient and used the wildcard, rather than whitelisting myself as a sender, in case any of my clients are also Spamcop reporters.

Thank again.
 
  • Like
Reactions: cPanelMichael

cPanelMichael

Administrator
Staff member
Apr 11, 2011
47,912
2,241
363
Hello,

I'm glad to see you were able to find a suitable solution. Thank you for sharing the outcome.