2 ms·

My own mail policy is simple: - a hosted service because host one myself is too much work CAUSED by anti-spam measure by some "self-appointed sheriffs" of the

by kkfx 4y ago

My own mail policy is simple: - a hosted service because host one myself is too much work CAUSED by anti-spam measure by some "self-appointed sheriffs" of the net; - mail fetched from remote via fetchmail, no messages left on the server, filtered on my homeserver via maildrop, indexed via notmuch, muchsync-ed over SSH to desktop(s)/laptop. That's is.

midenginedcoupe 4y ago
I think we have very different understandings of the word "simple".
- kkfx 4y ago
  Simple meaning: I'm not tied to anyone specifically (personal domain name) and I own my data. They are also on someone else iron, but also on mine and I use them locally. Composing a new mail is just hitting a key on my keyboard, searching my messages like GMail is another key for search&narrow results a modifier+the same key for notmuch-emacs UI. All mails can be linked on all my org-mode/org-roam managed docs equally. It's FAR simpler and FAR more powerful than any modern crapware UI, BUT is hard to setup due to the little development compared to the mainstream UI.
uselpa 4y ago
I like that, any pointers for a Linux-based fetchmail/getmail setup?
- kkfx 4y ago
  So far I've not documented much my setup (but feel free to ask specific questions) I found nice to bookmark: - https://www.howtoforge.com/procmail_tips_recipes https://www.howtoforge.com/procmail_tips_recipes - https://dnns.no/switching-from-procmail-to-maildrop.html https://dnns.no/switching-from-procmail-to-maildrop.html Who have a little fetchmail part. I've nerve used getmail, before I've used OfflineIMAP (buggy but support IMAP IDLE) and mbsync. The only issue is fetching from multiple accounts that demand firing up multiple instances, but that's not much of an issue. You just set FETCHMAILHOME before any invocation pointing to the right config dir and set a different --pidfile for concurrent* fetching if you wish so. MailDrop is a (very) little (very) big setup since you need filters for anything if you are not a piler and that take MUCH time. Normally here my suggestion is fetch anything on a zfs volume, clone it, test on the cloned maildir or snapshot and revert after any test until you get nothing in the INBOXes. A slow step at a time you'll add the rest.

by kkfx 4y ago

midenginedcoupe 4y ago

I think we have very different understandings of the word "simple".

kkfx 4y ago
Simple meaning: I'm not tied to anyone specifically (personal domain name) and I own my data. They are also on someone else iron, but also on mine and I use them locally. Composing a new mail is just hitting a key on my keyboard, searching my messages like GMail is another key for search&narrow results a modifier+the same key for notmuch-emacs UI. All mails can be linked on all my org-mode/org-roam managed docs equally. It's FAR simpler and FAR more powerful than any modern crapware UI, BUT is hard to setup due to the little development compared to the mainstream UI.

uselpa 4y ago

I like that, any pointers for a Linux-based fetchmail/getmail setup?

kkfx 4y ago
So far I've not documented much my setup (but feel free to ask specific questions) I found nice to bookmark: - https://www.howtoforge.com/procmail_tips_recipes https://www.howtoforge.com/procmail_tips_recipes - https://dnns.no/switching-from-procmail-to-maildrop.html https://dnns.no/switching-from-procmail-to-maildrop.html Who have a little fetchmail part. I've nerve used getmail, before I've used OfflineIMAP (buggy but support IMAP IDLE) and mbsync. The only issue is fetching from multiple accounts that demand firing up multiple instances, but that's not much of an issue. You just set FETCHMAILHOME before any invocation pointing to the right config dir and set a different --pidfile for concurrent* fetching if you wish so. MailDrop is a (very) little (very) big setup since you need filters for anything if you are not a piler and that take MUCH time. Normally here my suggestion is fetch anything on a zfs volume, clone it, test on the cloned maildir or snapshot and revert after any test until you get nothing in the INBOXes. A slow step at a time you'll add the rest.