>On postfix itself you can use regular blocklists to prevent such
obvious IPs.
For the other services like imap etc. it helps to use fail2ban.
I have all filtering that I know of off right now. I am just trying to
establish incoming communication with other SMTP clients right now. Once I get
Am Freitag, den 08.05.2020, 15:51 -0500 schrieb Thomas Strike:
> Matus: your right. I misused the word server. I thought that this was
> the test message being sent with gmail because every time I sent a
> new test, this IP came up in the maillog.
> This turns out to be a Russian IP. Geez, Louise!
Matus: your right. I misused the word server. I thought that this was the test
message being sent with gmail because every time I sent a new test, this IP
came up in the maillog.
This turns out to be a Russian IP. Geez, Louise! I have Russia trying to hack
me.
On 08.05.20 13:01, Thomas Strike wrote:
Subject: mail from external servers connecting but timing out after tls
established. t.s.
External smtp servers time out after tls v1.2 is established. the
following is from the maillog;
May 8 17:40:48 sleepyvalley postfix/smtps/smtpd[17534]: connect
On 08.05.20 13:01, Thomas Strike wrote:
Subject: mail from external servers connecting but timing out after tls
established. t.s.
External smtp servers time out after tls v1.2 is established. the
following is from the maillog;
May 8 17:40:48 sleepyvalley postfix/smtps/smtpd[17534]: connect
External smtp servers time out after tls v1.2 is established. the
following is from the maillog;
May 8 17:40:48 sleepyvalley postfix/smtps/smtpd[17534]: connect from
unknown[185.50.149.12]
May 8 17:40:50 sleepyvalley postfix/smtps/smtpd[17534]: Anonymous TLS
connection established from unkno
