On 16/09/22 16:24, Peter wrote:
* Malicious users are much more likely to come from botnets than from
TOR, and botnets can connect from anywhere and are much *less* likely to
be malicious (People who run exit nodes tend to be knowledgeable enough
to know how to keep their computers from becomin
On 9/09/22 23:51, Simon Wilson wrote:
Noting that whilst some may consider that block excessive, it does
appear that some 'authorities', including at least the Australian
government's cyber security department, Fortinet, and others, recommend
these IPs are blocked.
E.g. "The Australian Cyber
Hello and good evening.
I am sorry to make a further, necessary release of this little
program, but i plugged a "miss" that could affect users.
(Anyone not doing the never announced "rm -f PG-SOCKET" in
a (pre-) postfix startup script.)
While i was there, i added a server --startup mode that can
This is a perfect example of why NOT to use Google for your first
resort
in asking questions! The linked howto is very bad, and it will make
your
new secondary MX host a spam magnet.
You are absolutely correct.
I wrongly assumed that antispam/antivirus measures was something that
everyone imp
On 9/15/2022 8:45 AM, I wrote:
The concept of "secondary MX" dates way back to pre-spam days. I think
it can safely be considered an outmoded idea at this point. But if you
insist on doing it, make sure that you use:
* Recipient validation
* Identical anti-spam controls on both hosts
On Wed, Sep 14 2022 at 07:10:57 PM +0800, Henrik Pang
wrote:
Hello,
Is there a guide for adding a secondary MX with postfix?
the secondary MX would forward messages to the main MX.
When the main MX was in failure, the secondary MX should hold messages
for some time.
On 9/14/2022 6:14 AM, Jon
