On 23/04/2014 7:43 PM, John Griessen wrote:
On 04/23/2014 04:07 PM, Ron Wheeler wrote:
Another approach to reduce SPAM would be to use fail2ban for a
"reasonable" period to shut out IP addresses for a "reasonable"
period that are sending a "lot" of SPAM in a "short" period.
Hi,
Are you mean
It sounds as if you want something like SPF and a policy daemon. Just
google it.
You can not try to start figuring out who is legit or not, it's a never
ending task and will cause you nothing but a headache.
Use SPF, DKIM and other traditional methods, utilize some RBL's.
I do block them using fail2ban for long periods of time, if someone is
identified as sending spam, there i
1) I am blocking sites that:
a) send SPAM to addresses in our domain
b) have broken one of our e-mail passwords and try to send bulk mail
through our server by faking an Artifact Software user.
If postfix or spamassassin detects this behaviour, it blocks it as best
as it can (without making legi
Another approach to reduce SPAM would be to use fail2ban for a
"reasonable" period to shut out IP addresses for a "reasonable" period
that are sending a "lot" of SPAM in a "short" period.
Ron
On 23/04/2014 3:56 PM, Larry Stone wrote:
On Wed, 23 Apr 2014, James B. Byrne wrote:
Does the idea o
On Wed, 23 Apr 2014, James B. Byrne wrote:
Does the idea of configuring Postfix so that external (to our network) smtp
connections are only accepted from servers identified with MX records for the
connecting IP address make any sense? Is it possible?
No, it makes no sense at all. MX records d
I am in the process of debugging an application to Postfix error and thus have
occasion to have the maillog tailed in a session window. The vast, vast
majority of the traffic I see is spam and attempted spam most of which is
being handled by amavis-new and spamassasin.
Does the idea of configurin
