| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
| |
I think when I implemented this I didn't know about tmpfiles.d(5).
Now I do, so let's use that instead.
I don't think the imperativeNix option is necessary any more since the
home directory is created read-only, but if it turns out that
.nix-defexpr and .nix-profile are coming back, I can look into the
best way to solve that then.
|
|
|
|
|
|
|
|
|
|
|
| |
Fetching mail as a different user provided a pretty negligible
security benefit. It protects my IMAP password, but my IMAP password
only allows fetching mail, and all my mail is sitting right there
unprotected anyway.
Also, split mbsync and notmuch into multiple units. This would make
it possible to trigger notmuch at other times without having to fetch
mail first.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using a full MTA might seem like overkill, but it fixes my biggest
annoyance with msmtp -- not only can I now read mail while offline, I
can send it too, and postfix will just keep trying every so often
until it sends (or five days have passed, but at that point the
message is probably irrelevant anyway).
Postfix's defaults are surprisingly good for this use case. The
longest it will wait between attempts is 4000 seconds, and it'll keep
trying for five days before giving up and bouncing.
|
|
|
|
|
| |
Doesn't really make sense to call this service "mbsync" any more. It
might be better to run notmuch on inotify, though...
|
| |
|
|
|
|
|
| |
This ended up being way more trouble than it was worth, and the approach
just flat out didn't work for stuff like OpenSSH.
|
|
|