#stalwart — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #stalwart, aggregated by home.social.
-
A year ago I wrote a JMAP webmail for my Stalwart server. Audience of one.
Then I deleted it and started again, keeping only the joke domain.
A year on it's groupware: mail, calendars, contacts, files, real sharing, Sieve with a visual builder, ten languages, admin gated by the server's RBAC.
One rule survived: nothing gets built if it needs a datastore outside what Stalwart already gives me. No DB, no cache, nothing to back up.
-
A year ago I wrote a JMAP webmail for my Stalwart server. Audience of one.
Then I deleted it and started again, keeping only the joke domain.
A year on it's groupware: mail, calendars, contacts, files, real sharing, Sieve with a visual builder, ten languages, admin gated by the server's RBAC.
One rule survived: nothing gets built if it needs a datastore outside what Stalwart already gives me. No DB, no cache, nothing to back up.
-
A year ago I wrote a JMAP webmail for my Stalwart server. Audience of one.
Then I deleted it and started again, keeping only the joke domain.
A year on it's groupware: mail, calendars, contacts, files, real sharing, Sieve with a visual builder, ten languages, admin gated by the server's RBAC.
One rule survived: nothing gets built if it needs a datastore outside what Stalwart already gives me. No DB, no cache, nothing to back up.
-
A year ago I wrote a JMAP webmail for my Stalwart server. Audience of one.
Then I deleted it and started again, keeping only the joke domain.
A year on it's groupware: mail, calendars, contacts, files, real sharing, Sieve with a visual builder, ten languages, admin gated by the server's RBAC.
One rule survived: nothing gets built if it needs a datastore outside what Stalwart already gives me. No DB, no cache, nothing to back up.
-
A year ago I wrote a JMAP webmail for my Stalwart server. Audience of one.
Then I deleted it and started again, keeping only the joke domain.
A year on it's groupware: mail, calendars, contacts, files, real sharing, Sieve with a visual builder, ten languages, admin gated by the server's RBAC.
One rule survived: nothing gets built if it needs a datastore outside what Stalwart already gives me. No DB, no cache, nothing to back up.
-
I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.
Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).
I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.
I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.
#networking #badactors #firewall #automation #linux #selfhosting #homeserver
-
I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.
Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).
I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.
I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.
#networking #badactors #firewall #automation #linux #selfhosting #homeserver
-
I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.
Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).
I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.
I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.
#networking #badactors #firewall #automation #linux #selfhosting #homeserver
-
I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.
Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).
I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.
I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.
#networking #badactors #firewall #automation #linux #selfhosting #homeserver
-
I came across the #Fail2Ban #docker image from #linuxserverio and thought to myself that it's finally time to set up Fail2Ban. I admit i never used it before and it was a bit difficult to add it to my #playbook as all of my #servers have different services and therefore different #logfile paths, but that's nothing #jinja #templating can't fix.
Now that i've got #Discord notifications for banned #IPs, it's time to work on actual #IPblocking. I also want to use the #IPComplaint and #AbuseIPDB actions as i really like the idea of reporting abuse (even though i have no idea how effective that may be).
I may also want to replace the discord #webhook with #email notifications later as that's mostly the reason i've set up a #mailserver ( #stalwart ) in the first place.
I mean, most of my services are only accessible from #tailscale or my #homenetwork, but since #Ansible makes it so much easier to apply higher standards, i just can't resist. My #homelab is changing every day and i think setting up additional #security, even though i don't need it yet, is never a bad idea.
#networking #badactors #firewall #automation #linux #selfhosting #homeserver