9 Aug
2020
9 Aug
'20
10:52 p.m.
On 8/9/20 4:08 AM, Slávek Banko wrote:
Hi David,
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 unsuccessful:
-----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.)
<trin(a)3111skyline.com>
Note: Address <gitea(a)localhost.localdomain> is during delivery rewritten to
<gitea(a)mail.trinitydesktop.net>et>.
Cheers
Thank you Slavek,
There is something funny, because I got somebody's test mail to that
account, e.g.:
<quote with .. added>
m..-trinity(a)yosemite.net
Don't see a problem. Hmmm.
</quote>
That message came through fine.
WAIT!!!!!
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
destination
11 3074 182K DROP all -- * * 37.0.0.0/8 0.0.0.0/0
Why on earth is the IP from RIPE? The IP for mail.trinitydesktop.net is
37.205.10.16. 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 37.205.10.16 Let's see if the confirm
mail comes through now.
(that explains why I saw nothing in my logs -- it wasn't allowed to get there...)
--
David C. Rankin, J.D.,P.E.