shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

285
active users

#postfix

0 posts0 participants0 posts today

I recently added email to my mastodon instance, and with that success, I'm ready to finally cut email ties with Google. I bought a new domain name and I'll set that up with postfix/dovecot/etc, then start moving all of my various internet accounts over to it.

The new domain has a .net TLD instead of the current .com TLD, and that's nice; it's more appropriate since I'm not running a business. Now I'm just waiting for the DNS changes to propagate.

Well, after a lot of swearing… I *think* I have a Raspberry Pi 400 running #AlpineLinux … tethered to my 4G phone hotspot … acting as a crude WiFi router/bridge for my border router running #OpenBSD which is tunnelling to my OpenBSD VPS at Binary Lane.

Over that tunnel, I now have #Postfix on the home mail server, relaying over the VPN to #OpenSMTPD on the VPS.

Should be useful the day I have to leave Internode… but for now, it's bypassing the rather dead NBN service (thank-you #CycloneAlfred).

Installed #Postfix and configured #DKIM and got #DNS configured and I can send an email from the server to my proton email and it no longer goes to the spam folder, it actually shows up in my inbox and I think cool, got it all set correctly.

But now I notice that it seems like any other address I try to email (not my proton email address) I get a bounce message saying the email address doesn't exist.

Any #email gurus got a suggestion for what I should be looking at?

Replied in thread

There's an awful lot of "change these two settings and things Just Work™" and not a lot of "You need to make sure that these settings exist".

Apparently part of the "not signing emails" is because I'm using SASL auth, so it comes from an "external" server (my local machine). But it's locked down. But Amavis sees it as external. And all the blogs and tutorials and docs either do nothing or go "yeah, just change this setting (that's not in your config)" 😐

#Email #Postfix #DNS

Anybody have a link to a resource that talks about setting up DNS entries to authenticate a VPS Postfix server for sending registration emails that are authenticated properly? I feel like I'm just going in circles and everything I'm finding is like use the settings provided by your email service. But that's not what I'm trying to do.

Email spam delivery is off the charts for the last week. I have no idea whats driving it, but the numbers for RBL blocks, SASL login spam, and scam mail are at an all time high.

Attempted distraction campaign during Trump trial? Cyber warfare ramping up as retaliation for war funding (or not)? Hard to say, all I know is there is some push happening right now.

#email#spam#smtp

#selfhosting #mta #postfix

# telnet mx2.ipoac.nl 25 -4
Trying 86.80.166.233...
telnet: Unable to connect to remote host: Network is unreachable

# telnet mx2.ipoac.nl 25 -6
Trying 2a02:a46f:95b7::1...
Connected to mx2.ipoac.nl.
220 mx2.ipoac.nl ESMTP Postfix

Just amazing that my cable #isp #ziggo blocks tcp dport 25 outbound over #ipv4, but #ipv6 is fine apparently.

Still not very useful with a fixed reverse #DNS that ends in cable.dynamic.v6.ziggo.nl that #spamfilters seem to love.