SpamAssassin -is there a way to apply to incoming mails only
SpamAssassin -is there a way to apply to incoming mails only
Can we apply SpamAssassin for incoming mails alone and not for outgoing mails. Using enterprise version 7.8
-
- Site Admin
- Posts: 9738
- Joined: Mon Mar 22, 2004 4:44 am
- Location: Melbourne, Victoria, Australia
Re: SpamAssassin -is there a way to apply to incoming mails only
Hi,
Version 9.x has an option to "Bypass SpamAssassin checks for authenticated users" under the "SpamAssassin" integration properties.
Version 9.x has an option to "Bypass SpamAssassin checks for authenticated users" under the "SpamAssassin" integration properties.
Regards,
Ian Margarone
MailEnable Support
Ian Margarone
MailEnable Support
-
- Posts: 6
- Joined: Mon Mar 07, 2016 7:18 pm
Re: SpamAssassin -is there a way to apply to incoming mails only
Just white list your own domain.
Add the following to the local.cf file.
# whitelist Local Server:
whitelist_from *@your.domain
Then all emails from your own domain (outbound) will avoid being filtered.
Add the following to the local.cf file.
# whitelist Local Server:
whitelist_from *@your.domain
Then all emails from your own domain (outbound) will avoid being filtered.
Re: SpamAssassin -is there a way to apply to incoming mails only
Paul,
that would work but the fakers who use your @domain.com address will get a free pass I have tried adding some of my domain internal ip addresses under
trusted_networks x.x.x (and have obscure internal addresses e.g. 172.32.32 ).
Otherwise, It would need to be scripted somehow so that there was something in the header that guaranteed it was from your real domain.
I havent worked out how to do that. I thought I saw something about this being added as a feature recently to differentiate your real domain mail from the fakers. I think Ian is hinting at this in his email above this using the internal Spam Assassin that comes with ME.
Scott
that would work but the fakers who use your @domain.com address will get a free pass I have tried adding some of my domain internal ip addresses under
trusted_networks x.x.x (and have obscure internal addresses e.g. 172.32.32 ).
Otherwise, It would need to be scripted somehow so that there was something in the header that guaranteed it was from your real domain.
I havent worked out how to do that. I thought I saw something about this being added as a feature recently to differentiate your real domain mail from the fakers. I think Ian is hinting at this in his email above this using the internal Spam Assassin that comes with ME.
Scott