Elvith Ma'for

Well, now X11 lacks a feature you want…

They will be drowned in hundreds of „Thanks for your email, but we don’t do support via mail. Please open a ticket at $URL“ and „Thanks for your mail, we will get back to you shortly. Your ticket ID is #123456“. Also everything you add as an auto response will be distributed to all other victims in that group, so I chose to not be a dick.

Google Groups allows spammers to subscribe you to their groups in a workspace account, but doesn’t allow you to unsubscribe since you’re not part of that workspace account… Worse - all autoresponders for the spam will also be forwarded to all members of said group.

Since I do not participate in Google Groups, the nuclear option is to file all mails from Google Groups as spam with a Sieve script.

Note the require part may be too large as may sieve script also contains more rules than this one.

require ["body", "date", "editheader", "envelope", "fileinto", "imap4flags", "mailbox", "regex", "reject", "variables"];

if anyof(
    header :contains "List-Subscribe" "groups.google.com",
    header :matches "X-Google-Group-Id" "*"
   ) {
	if header :matches "Subject" "*" {
		set "subject" "${1}";
	} else {
		set "subject" "";
	}
	deleteheader "Subject";
	addheader :last "Subject" "[Google-Groups-Spam] ${subject}";

	fileinto "Junk";
}

My current setup for this:

I own a domain - say homelab.com - and use it exclusively in my internal network.

The public DNS records do only resolve to 127.0.0.1 (as my domain holster doesn’t want me to have no A record).

In my home network I have a pihole running that resolves this domain and it’s subdomains locally (say pihole.homelab.com, proxmox.homelab.com and so on).

For HTTPs: As this server is not publicly reachable, I use the DNS API of my domain host to get a let’s encrypt certificate with the DNS-01 challenge. That way, the internal systems do not need to be exposed to the internet.

Edit: Caddy can do DNS-01, but you usually have to compile it yourself to include the plugin for your provider. To circumvent that, I’m just using plain old certbot and told Caddy to use the certs that are already on the machine