On Monday 10 of August 2020 00:52:37 David C. Rankin wrote:
On 8/9/20 4:08 AM, Slávek Banko wrote:
yes, the accounts from the original SCM were not migrated, so you had
to create a new one. However, there seems to be a problem with your
mail server. Attempts to deliver the confirmation email are still
-----Q-ID----- --Size-- -----Q-Time-----
------------Sender/Recipient----------- 07878jc2031134 1796 Sat
Aug 8 07:08 <gitea(a)localhost.localdomain> (Deferred: Connection timed
out with 3111skyline.com
Note: Address <gitea(a)localhost.localdomain> is during delivery
rewritten to <gitea(a)mail.trinitydesktop.net>et>.
Thank you Slavek,
There is something funny, because I got somebody's test mail to that
<quote with .. added>
Don't see a problem. Hmmm.
That message came through fine.
I know what it is!!!
# iptables -nvL --line-numbers
Chain INPUT (policy ACCEPT 3651K packets, 548M bytes)
num pkts bytes target prot opt in out source
11 3074 182K DROP all -- * * 184.108.40.206/8
Why on earth is the IP from RIPE? The IP for mail.trinitydesktop.net
220.127.116.11. The 37 IP block is the top 3 offending block. 182K of
script-kiddie attempts since last boot alone.
I've opened a hole in my firewall for 18.104.22.168 Let's see if the
confirm mail comes through now.
Aug 9 22:55:14 localhost sm-mta: 07878jc2031134: to=<trin(a)3111skyline.com>om>,
ctladdr=<gitea(a)localhost.localdomain> (107/113), delay=1+15:46:29, xdelay=00:00:01,
. [22.214.171.124], dsn=2.0.0, stat=Sent (Ok: queued as 6633FF3A60)
(that explains why I saw nothing in my logs -- it
wasn't allowed to get