AndreaS Schamanek skrev den 2013-07-03 21:52:
Only if I also add 172.31.38.210 (private address from a reserved
block) it
works as I expected it.
Looks like I will use trusted_networks to save some CPU cycles but
I'll also
keep my meta rules.
yep, rfc1700 is default listed in spamassassin,
rules.
--
-- Andreas
--
View this message in context:
http://spamassassin.1065346.n5.nabble.com/Spam-via-whitelists-tp105635p105643.html
Sent from the SpamAssassin - Users mailing list archive at Nabble.com.
On Wed, 3 Jul 2013 12:52:43 -0700 (PDT)
AndreaS Schamanek wrote:
Anyway, using trusted_networks I found that it doesn't work fully
unless I manage to list their complete mail infrastructure. I didn't
know that IPs from trusted_networks can actually be subject to evals.
...
Only if I also add
Hi SA fellows,
I sometimes disagree with whitelists such as DNSWL_MED,
chaosreigns.com/iprep/ or JMF-WHITE. There are 2 main issues:
1) Less often recently, but I did see freemail MTA IPs from Google,
Yahoo! and other big players showing up on whitelists. Considering the
amount of spam
On Tue, Jul 2, 2013 at 7:09 PM, Andreas Schamanek
scham...@fam.tuwien.ac.at wrote:
2) What's currently more annoying are colleagues of mine operating
large mail servers (tu-graz.ac.at and ethz.ch are 2 examples) who
forward their former users' mail to external addresses without prior
Andreas Schamanek skrev den 2013-07-02 19:09:
Any better ideas?
disable dnseval plugin, the above meta is workaround that also works,
just remember most of them use spf/dkim, there is a dkim-repution
plugin, part of opendkim, one could start make repution reporting to
ones own opendkim
