milano

Thanks again, migrated and documented all over the place so users already woke up to their homeland's music and morning news. There's just no way to remote-patch the server initially queried at the moment, so you may still see some hits to .org for a while.

Thanks a lot, the most recent logs tell me about remaining daily users too.👍 These are on devices abandoned by their vendor 15 years ago, but popular among expats, and more recently, kids. Keeping the .org TLD might spare them the hassle of reflashing to a new server's address.

Thanks again, it didn't let me pick heliohost.org anymore though: Can it be recovered (or files restored if need be into the new path for US TLD) ?

Apologies, I've sent you by Personal Message another mail address to reactivate milano with. @Krydos "Newer files ... recoverable from the crashed server as well" would be very welcome of course, if not on restored into the file system anyway through recreating the account.

As http://milano.heliohost.org had been active until just before this month's crash, and https://helionet.org/index/forum/91-email-support/ shows other subdomains getting 2024 backups as well for which support may have more recent files recoverable, if unsuspending the the account won't help, I'd also much appreciate whatever you can get from this year or the last.

Sorry if the mail used needs replacing: Sure enough https://heliohost.org/status/?u=milano keeps telling me "That account is awaiting validation... Resend" without any mail coming, but when using for parameter "u" the mail address now out of favor instead: "That account has been backed up and then taken offline due to inactivity." I got a backup tarball this way, from 2024 though. So if you can enable the account for long enough to change the mail address, I'll be happy to do so.

Wasn't that disposable given it's been the same for many years, but how do I set another then?

...so can't even see why (got no mail or anything): It never had much activity, let alone any that might trigger suspension

Apparently not all the time: letsencrypt.org "recommend renewing certificates automatically when they have a third of their total lifetime left" i.e. 30 out of 90 days, accordingly their Expiry Bot has mailed me too, 20 & 7 days before expiration, for a certificate which now says "Valid To July 13, 2023 Will be automatically renewed". Should renewal happen (earlier) automatically these days, or do I have to click "Reissue Certificate" in Plesk every quarter?

Installing LWP:Protocol:https might be a good idea indeed (also to make the message in the subject line go away), as it used to be part of LWP until a few years ago anyway, which is more feature-rich (incl. safer with full host verification) and commonly used than HTTP::Tiny (though rewriting to use the latter overnight did the trick for my own little pieces of code).

With most of the world gone SSL/TLS, there seems to be a need for https://metacpan.org/release/GAAS/LWP-Protocol-https-6.04/view/lib/LWP/Protocol/https.pm these days. https://wiki.helionet.org/tutorials/perl suggests that "All CPAN libraries can be installed from within your control panel." Is this still the case on Plesk, or could this Perl module be provided by an admin? On the other hand, https://metacpan.org/pod/HTTP::Tiny works (around) for me.

Options is accepted in .htaccess now.? The subdomain's root (when created in Plesk from scratch rather than migrated) has changed from public_html to httpdocs, and it no longer seems to be below /home/milano, nor /etc/psa/psa.conf's default vhosts_dir like /var/www/vhosts/milano.heliohost.org, but /home/milano.heliohost.org instead. Below it there is also a logs folder which stays empty for now, but access and errors can be seen through Plesk > Websites & Domains > Logs. Hope this helps others adapt their scripts as well.

Thanks @Krydos, account recreated, sure enough I'd like the original milano.heliohost.org back

Thanks, I've downloaded both ZIP and tar (the latter incl. the dovecot maildirs) via Plesk, so please feel free to delete and (let me) recreate the account. This can be done under the same name and path(s)?

The moment I uncomment Options +ExecCGI from .htaccess (even if it is its only line), I get 500 Internal Server Error, even for Perl (without file type extension) in cgi-bin, i.e. where it otherwise works by default. Log says [core:alert] /home/milano.heliohost.org/public_html/.htaccess: Options not allowed here Apache error

Any news on this option?

Plesk's https://johnny.heliohost.org:8443/smb/file-manager/list doesn't seem to support setting (sym)links, so can't check whether those into cgi-bin would work either (as https://support.plesk.com/hc/en-us/articles/115003276605-Perl-or-cgi-script-cannot-be-executed-500-Internal-Server-Error implies). https://support.plesk.com/hc/en-us/articles/115001125289-A-website-hosted-in-Plesk-shows-500-Internal-Server-Error-Option-FollowSymLinks-not-allowed-here suggests Options are an, erm, option even in current Plesk.

Restored and moved to Plesk as one of the final accounts, as hinted by the error_log I had to comment out the leading Options +ExecCGI line from my .htaccess that needs to SetHandler cgi-script to use Perl outside cgi-bin (for hardcoded clients that can't be changed). Could it be that Tommy's httpd.conf before its outage had "AllowOverride Options" which hasn't been reinstated yet?

Many thanks Krydos & team, and sorry for inadvertantly triggering that countermeasure with the Bcc in the first place. So every recipient was treated as if he or she had been sent an individual email, and only the first 50 were delivered?

Surely haven't tried to mess with anything there: All I did send manually, innocuously enough, were 3 mails with about some 40 recipients each in Bcc (unaware of a hard limit on these) right after uploading milano to Tommy again. So I think there are not actually any new mails being detected (but rather some defense overreacting) as nothing in my code sends any either. The only other thing trying to generate mail "from" my account I could think of would be your process to create SSL keys that I recall used to be on Tommy before the crash.

I'm afraid https://www.heliohost.org/status/?u=milano keeps saying "suspended". Neither me nor any process of mine have been sending any more mails; I suppose it's some automation "punishing" one of the 3 initial mails with approx. 40 Bcc recipients (each of which seem to be counted as a "mail out of 50") that might still be outbound from your mail server (and I have no way of removing it).

https://www.heliohost.org/status/?u=milano keeps saying suspended, though I haven't (i.e. couldn't) send any more mails. I suppose it's the same "offending" outbound email (my apologies for that!) which is already on your mail server and makes the system auto-suspend milano again, maybe once for every Bcc recipient - but how could I remove that?

Moments after being restored, https://www.helionet.org/index/topic/37357-backed-up-milano-would-like-to-make-a-comeback-on-tommy/, milano got suspended, came back to life for a minute and is shown as suspended since, apparently because of too many recipients on the mail announcing its comeback triggering some automated spam defense. Maybe that outbound mail needs to be cancelled, nothing a suspended user can do. Thanks for unsuspending: a. milano b. Tommy c. milano.heliohost.org

Or isn't it? Keeps showing suspended (though I haven't sent any more than the initial 3 mails of course - can't rule out you did queue one of course)...

Thanks, so it's the number of recipients (each counted as a mail of its own, and not queued for the next day anymore in excess of 50?): I'll bear this in mind.