On Sunday 09 of August 2020 10:26:50 David C. Rankin wrote:

On 8/8/20 10:45 PM, Michele Calgaro via trinity-devel wrote:

...

Hi David, your account is in the list of known users. Have you tried to login? also have you checked your junk folder just in case?

Thank you Michele,

Yes I checked my junk folder, nothing there. I have about 5 different Trinity accounts, so maybe I didn't try the right combination of user/pass. Let me double-check my mail folders, but before posting I did a global grep of the postfix log and nothing had come into my server to the `trin` e-mail address at all. I'll let you know what I find.

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@3111skyline.com

Note: Address gitea@localhost.localdomain is during delivery rewritten to gitea@mail.trinitydesktop.net.

Cheers

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@3111skyline.com

Note: Address gitea@localhost.localdomain is during delivery rewritten to gitea@mail.trinitydesktop.net.

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@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.

voila:

Aug 9 22:55:14 localhost sm-mta[17320]: 07878jc2031134: to=trin@3111skyline.com, 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

On 8/9/20 7:13 PM, Marvin Jones via trinity-devel wrote:

Be careful about blindly blocking /8 CIDRs that way.

My US-based web host/VPS host bought a /23 block about a year ago from in the RIPE 45.8.0.0/13 allocation.

I've seen a couple of issues such as yours with my VPS.

(Blocking with pf here....) Jonesy

Amen,

I usually try and limit to /22 or /24 at most, but after my MediaWiki install was abused several years back I started tracking and individually adding IP blocks to my config -- but there were so many from the 37 block I finally said to heck with it and blocked the whole thing :)

Over the past 5 or so years, I've only had a handful of issue (this being one). I've had trimming my block list on the "get around to it" list for a while. I'll have to bump it up in priority. It's just a shame the internet has become so polluted that such steps are necessary. Before Mosiac -- all was good in the FTP world of old...