social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

490
active users

#mu4e

1 post1 participant0 posts today

#emacs folks, do you have an email spam handling config you're happy with with?

While I'm a fan of #email management via #emacs #mu4e, I kinda gave up pretty soon on integrating any sort of spam handling. Honestly didn't put much effort into it.

Today, I mostly rely on email provider spam filtering, and pick up whatever sifts through myself from mu4e. I'd love to minimise this further if possible.

#notmuch #gnus #rmail and any other solutions welcome too!

I want to use my #Emacs as the email client too, and I want these essential features:
1. multiple accounts
2. tagging/labeling emails

I have so far tried #notmuch and #mu4e, but neither of them seem to support both requirements. Any suggestions by fellow Emacs folks?

To all users of #CLI apps to manage their emails, like #neomutt, #gnus, #notmuch, or #mu4e.

What email provider would you recommend that works well with our good old #terminal based applications? I recently learned that the CEO of #proton has decided to praise some authoritarian leader in the USA and I'm considering switching to another mail provider. Also, even though I appreciated the fact that I could make #mu and mu4e work with their bridge app, there were some issues, like the fact it tangled with messages (see github.com/ProtonMail/proton-b).

I'm considering going back to Posteo or maybe switch to Mailbox which seems to offer interesting features. Do anyone knows good alternative that are somewhat privacy focused? Having the option to use a personal domain name would also be great, so I can stop switching email adresses.

Messages sent with a Content-Type header set to text/plain; format=flowed arrive at their destination with their Content-Type header set to text/plain; charset=utf-8. The copy in ProtonMail's Sent ...
GitHubformat=flowed removed from Content-Type header · Issue #119 · ProtonMail/proton-bridgeBy jakecoble
Replied in thread

@zrzz I work at a company that uses O365. Forwarding emails with attachments in #notmuch doesn’t match Outlook’s format. That is, a message with attachments becomes a new message with a bunch of attachments, including the message text, the attachment under a different name, etc.
In #mu4e, I had managed to get this working perfectly.

Finally managed to receive and send emails with all my email accounts through #emacs and #mu4e . At last there was one stupid thing that I didn't consider that my auth file needs an entry for the smtp and the imap server.
Somehow @posteo_de manages to have the same servername for smtp and imap
so it worked immediately.

The show notes github.com/daviwil/emacs-from- of @daviwil were very helpful in this regard. Signing and encrypting are the open points on my list now and then I am happy.

GitHubemacs-from-scratch/show-notes/Emacs-Mail-01.org at master · daviwil/emacs-from-scratchAn example of a fully custom Emacs configuration developed live on YouTube! - daviwil/emacs-from-scratch

Looks like it is time to re-evaluate email clients again. I've been using #thunderbird for a while but it just feels clunky. I switched from #evolution because I wanted plugins and unified inbox. I switched from #emacs and #mu4e because my messages kept going to spam.

My wishlist:
- GPG
- Unified inbox
- Good calendar integration (replying sending invites etc )
- Extend-ability
- Markdow/Org-mode support
- Work with G-mail/ Google cal
- Doesn't require me to use the mouse.

#linux
TIA!

After using #mu4e for a few weeks now I am happy to report that this is an absolutely awesome email client! Almost reason enough to start using #emacs, even without all the other amazing things that can be found in that lispy operating system....

Outlook365 and #Emacs #mu4e is still a bridge too far. 😫

Local modifications are not synced.
Sending complains about failed authentication.

What’s worse is the lack of documentation. Each involved piece has some, but I am not able to understand and apply what I read.