On Monday 10 of August 2020 00:52:37 David C. Rankin wrote: > 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@localhost.localdomain> (Deferred: Connection timed > > out with 3111skyline.com.) <trin@xxxxxxxxxxxxxxx> > > > > Note: Address <gitea@localhost.localdomain> is during delivery > > rewritten to <gitea@xxxxxxxxxxxxxxxxxxxxxxx>. > > > > 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@xxxxxxxxxxxx > > 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. > voila: Aug 9 22:55:14 localhost sm-mta[17320]: 07878jc2031134: to=<trin@xxxxxxxxxxxxxxx>, ctladdr=<gitea@localhost.localdomain> (107/113), delay=1+15:46:29, xdelay=00:00:01, mailer=esmtp, pri=21632322, relay=3111skyline.com. [66.76.46.195], 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 > there...) Cheers -- Slávek
Attachment:
signature.asc
Description: This is a digitally signed message part.
