Welcome to Lemmy Shitpost. Here you can shitpost to your hearts content.
Anything and everything goes. Memes, Jokes, Vents and Banter. Though we still have to comply with lemmy.world instance rules. So behave!
1. Be Respectful
Refrain from using harmful language pertaining to a protected characteristic: e.g. race, gender, sexuality, disability or religion.
Refrain from being argumentative when responding or commenting to posts/replies. Personal attacks are not welcome here.
...
2. No Illegal Content
Content that violates the law. Any post/comment found to be in breach of common law will be removed and given to the authorities if required.
That means:
-No promoting violence/threats against any individuals
-No CSA content or Revenge Porn
-No sharing private/personal information (Doxxing)
...
3. No Spam
Posting the same post, no matter the intent is against the rules.
-If you have posted content, please refrain from re-posting said content within this community.
-Do not spam posts with intent to harass, annoy, bully, advertise, scam or harm this community.
-No posting Scams/Advertisements/Phishing Links/IP Grabbers
-No Bots, Bots will be banned from the community.
...
4. No Porn/Explicit
Content
-Do not post explicit content. Lemmy.World is not the instance for NSFW content.
-Do not post Gore or Shock Content.
...
5. No Enciting Harassment,
Brigading, Doxxing or Witch Hunts
-Do not Brigade other Communities
-No calls to action against other communities/users within Lemmy or outside of Lemmy.
-No Witch Hunts against users/communities.
-No content that harasses members within or outside of the community.
...
6. NSFW should be behind NSFW tags.
-Content that is NSFW should be behind NSFW tags.
-Content that might be distressing should be kept behind NSFW tags.
...
If you see content that is a breach of the rules, please flag and report the comment and a moderator will take action where they can.
Also check out:
Partnered Communities:
1.Memes
10.LinuxMemes (Linux themed memes)
Reach out to
All communities included on the sidebar are to be made in compliance with the instance rules. Striker
It is great.
Mailcow protected by crowdsec, using SMTP2GO as outbound relay. No issues. I even have Addy.io running without issues.
I only allow inbound port 25. All other ports and access can only be done over WireGuard.
Best part is. My emails stay in my control on a server in Canada.
I just wish mailcow supported podman. Weirdly enough, apparently Docker Mailserver does, but I haven't had the energy to sink time into setting it up
Personally I use addy.io (previously anonaddy). Self-hostable and an easy way to get and control your own email @
AI slop yet again!
Given the amount of spam selfhosting your email sounds like the 7th circle of hell. Media servers should be enough, thankyouverymuch
Firewall with pfblocker and good feeds solves most of the problem. Spamassassin and URLBLs still work. It really isn't hard, once you set it up the config never changes. The static IP is by far the worst part.
I've actually been having a great time with simple-nixos-mailserver.
Running with a dedicated ipv4 at a highly reputable hoster, to my knowledge, I haven't landed in a spam folder yet!
https://lemmy.zip/comment/19712446
Reminder of this:
https://poolp.org/posts/2019-08-30/you-should-not-run-your-mail-server-because-mail-is-hard/
And that mailu.io (and other similar projects) makes self-hosting email almost trivial 😁 (at least for people that can run a pre-configured
docker-compose.ymland buy their domain etc)
Mailcow internal on Debian VM.
SMTP2Go free external relay.
Have had the occasional issue after an upgrade or reboot can't find my LetsEncrypt cert and will bork the system until I manually fix it. Perhaps my latest script update finally resolved that.
Otherwise, not that bad. Been running my own email for about 5 years or so. I don't sign up for many outside services with it. It's mainly for internal alerting or testing purposes but still works very well.
How do you handle backups?
The other side of email is that it has become the default identity provider for the Internet. If that VM becomes unrecoverable somehow, how would you get access to your past emails?
I was using Veeam when my stack was on VMware, but after moving to Proxmox I've been unable to get the Veeam agent working properly for VM recovery.
I tried Proxmox Backup at one point, and while it did work for base VM backup, the interface and capabilities of it just don't stack up to Veeam in my opinion, and I'm more concerned about file backup than VM recovery as I can easily recreate anything in my stack through my documentation.
I'm actually glad you mentioned that because I do need to revisit it. The few times I did have to recover the VM from backup I was able to do so when my backup process was working, but I've thankfully not had any recovery situations in the past 2 or so years since moving to Proxmox. And recovery doesn't help in situations where your cert is expired which is usually my issue historically.
As for past email recovery, Mailcow does have documentation on recovering from a failed server\database, but I consider my personal deployment volatile since I'm only using it for alerting and mostly internal only services.
I would fully switch over to it if I had more personal time, and if I knew I could make my family comfortable with accessing it. But right now I feel the risk is too great to move anything personally or financially important over. In the event something bad were to happen to me, I'm the only one with knowledge on how to recover the environment and I don't need my family to take on that burden if I were to become incapacitated or forbid, pass away suddenly.
I do fine.