I think what you are asking for are server side email filters.
The most common implementation is Sieve, which is supported by Dovecot, Cyrus, and Stalwart IMAP servers (and probably others I’m not aware of). There are a variety of clients that support it, including Thunderbird and Roundcube.
I see. I really want to use Vikjuna. If you’re mostly going to use native clients, you could swap out for a CalDAV server (NextCloud, Radicale or Baikal)?
I didn’t think that iOS was working at all?
In my opinion, they do different things.
SFTP/SCP are great ways of transferring files between computers. I prefer rsync for most things because it can resume transfers and checksum results. I’d never use FTPS because SFTP/SCP comes with SSH, and why run a separate service? SSHFS is another way to use SSH to transfer files (it mounts a remote file system to your local computer so you can use all your normal file management tools).
NextCloud (and similar) do a bunch of additional things:
If SFTP does everything you need, that’s awesome. Use it. :-)
The thing is, these sorts of losses aren’t limited to selfhosting. Selfhosting introduces some new risks and reduces some other risks.
Digital data is inherently fragile. It takes active work to preserve it.
That’s one of the reasons my wife and I make an actual physical photo book each year of our favourite photos.
Yes, Zotero and can a WebDAV backend.
I like using containers, but it doesn’t make any difference to the above. Containers can be exploited as well.
I don’t know why people feel the need to say this every time somebody asks about selfhosting email.
There’s no technical problem with running a mail server on the same server as websites. The only concern is simply that web applications are much more likely to have bugs and get hacked than your mail server. If a web app does get hacked, all of your mail is potentially compromised. If you don’t care about that, I’d say … go for it.
I’d guess that you have another DNS server on your network which is trying to get the list of root name servers (what the . means) via AdGuard.
I’d guess that there are so many queries because something is going wrong with it’s attempt to get the root name servers from AdGuard so it’s doing it over and over (because it can’t function without them).
Debian. Always Debian.
I understand why, I just wish there was a way to do notifications without a centralised, internet connected server.
One of the things I do is build communications systems for scientific crews who are often working in places with local wifi but no internet. They’d really like to have a Matrix server (or similar) they can use to send each other messages. But as far as I’ve been able to determime this is currently impossible. :-(
Deltachat is the best solution I’ve been able to find.
Sadly, I believe web push notifications still go through a centralised server provided by the browser developer.
You’re asking r/selfhosted where to not selfhost something.
I thought limits only worked in swarms?
I just checked the docs and didn’t see anything about ntfy accepting smtp? This would be useful, what am I missing?
You have climbed mountains and gained skills. Congratulations my friend, now bask in the soothing waters.
I managed OpenLDAP servers professionally for years. You don’t want to use OpenLDAP unless it’s something you want to learn about.
LLDAP (or GLAuth) does everything you need in a homelab context for a fraction of the effort, complexity, and hassle.
Assuming it’s a Linux server at home and you can use SSH on your work computer, there’s a couple ways to do this.
~/.ssh/config:Match host "*.cf"
ProxyCommand /usr/local/bin/cloudflared access ssh --hostname $(echo %h | sed 's/\.cf$/.homelab.nz/')
ForwardAgent yes
This is how NFS works. Making sure that usernames and userids match on all of your servers will fix this and is by far the simplest solution. If it didn’t work, you probably just made a typo somewhere.
Other options.
Use an LDAP serer (I like LLDAP) to provide a single user database for all your servers. This has lots of advantages (can provision users and change passwords for all servers in a single place). But it is fixing your problem in the same way as above (making usernames and user ids match on all of your servers).
Use Samba/CIFS instead of NFS. Because you authenticate with a user/pass all actions happen as the user you authenticate and so local user permissions don’t matter.