Excuse my very basic question, but how do you manage spam when using mutt? Do you interface to a cloud-based service in mutt, or have some kind of other spam filter?

I’ve always liked the idea of moving my email to mutt and using personal domains, but not convinced I could manage spam well.

the same way you manage it with a GUI mail client. if you use a mailservice that includes a spam-filter, you can use mutt's imap support to access it, and thus access the filtered mailbox like any GUI or webmail client would.

for your own personal domain, either use a service that supports personalization. (gmail does, but there should be others) and you are covered again.

if you want to host your own mail server, then you'll probably want to run your own spam filter on that server. it works by having the mail server forward the mail to the filter (which can be local or remote) and then deal with the mail based on the response from the service.

greetings, eMBee.

there was a recent HN thread announcing the resurrection of Apache's Spam Assassin. the comments may provide some useful suggestions to you.

https://news.ycombinator.com/item?id=18458212

Amusingly, you can actually do all of that within emacs:

- email: notmuch/Rmail/Gnus/&c.

- password manager: pass.el (uses pass under the covers)

- navigate directories: shell or eshell, with autocompletion and/or Helm

- task management: Org Mode

- music: emms

Emacs is crazy-powerful!

dired-mode by itself is pretty excellent for navigating directories.

A few of these (all?) are TUIs and not CLIs.

CLIs are command driven. TUIs are driven by user interactions. I'm sure more/better distinctions between the two can be made.

that's a fair point, but i don't think that's what the OP meant. CLI is commonly used to cover TUI when pittet against GUI.

greetings, eMBee.

On one hand it's in the acronym command line interface and on the other

"was wondering if anyone had any solid recommendations for applications that one can use in a terminal window" it really looks like he meant to express console apps not cli I think you are correct.

I don't believe that's true. TUI has more in common with GUI than CLI.

I bet you five dollars OP was looking for TUI programs as well.

sure, conceptually it does, but that's not the point.

what matters for most is the fact that i can run the application in a text only terminal, on any machine (remote or local), from any device (be it linux, windows, mac or even a mobile phone (ok, that's rarely practical, but it's possible))

a GUI does not offer that advantage.

greetings, eMBee.

> what matters for most is the fact that i can run the application in a text only terminal, on any machine (remote or local), from any device (be it linux, windows, mac or even a mobile phone (ok, that's rarely practical, but it's possible))

> a GUI does not offer that advantage

Sure, not in the terminal, but X forwarding is a thing and works on every system I've had to use it on.

it doesn't work on the majority of systems i have to work with, which is servers that don't have the necessary tools installed.

it's also very susceptible to latency and most applications don't handle slow connections in a usable manner. (they are designed with the expectation that the gui always responds instantly)

to get something of a tmux/screen like experience, xpra is available, which is an awesome piece of work, but it doesn't help with the latency. even over just local wifi i have some applications become unusable over xpra when they work ok over plain remote X.

the problem is not necessarily X but in part GUI in general. i can't click the mouse anywhere until the respective UI item is visible, so i have to wait for that.

on a commandline on the other hand in most cases i can keep typing even on extremely slow connections because i can anticipate what will happen and i know what keys are appropriate to type next.

using mosh i even get something like editable typeahead which is a marvel and very hard to imagine on X.

greetings, eMBee.

Oh, I never said I _enjoyed_ X forwarding, or even use it frequently. My point was just that remote access in a similar way to a shell is possible with a GUI, and could be made even better if X had a means of not having to draw everything but left it up to the toolkit on the other end.

But yes, in general, a shell is just much better:)

> could be made even better if X had a means of not having to draw everything but left it up to the toolkit on the other end

that a thousand times!

does wayland work in that direction?

I wish more people made the distinction and more people made TUIs too...