by xparadigm on 12/9/24, 1:17 PM with 97 comments
by djha-skin on 12/9/24, 3:48 PM
by cfiggers on 12/9/24, 5:16 PM
A little while ago I wrote my own little TUI tool using Textual that interfaces with Outlook using pywin32. I really only needed (need) one specific feature above and beyond what Outlook already does. And that is, I wanted a Vim-like UX for assigning categories to emails and archiving/deleting them. What I have now works surprisingly well and it's very satisfying to have made my own thing that suits my own needs precisely the way I want it to.
by xyst on 12/9/24, 5:52 PM
From strictly reading the docs, I love these features:
* oauth2 * json output
But do I need to run the "himalaya ..." command every so often to get fresh e-mails? Or can I leave TUI open and it will refresh in the background?
When composing messages, does anybody know if the "From" header can be re-written like in Thunderbird? I am able to send from ad-hoc aliases with my mail server, but need to re-write the "From" header first. For example, I can receive mail sent to "xyst.hn@example.com" and delivered to mailbox at "xyst@example.com". In order to reply with same e-mail address, I must re-write the "From" header to match.
by jedisct1 on 12/9/24, 2:55 PM
Being able to select emails using regular expressions is super useful.
IMAPFilter is also simple and powerful to quickly sort email.
by aynawn on 12/9/24, 9:11 PM
Edit: there is a separate tool for this for gmail https://github.com/mbrt/gmailctl
by jonstewart on 12/9/24, 2:35 PM
by alberth on 12/9/24, 2:54 PM
by vigonotion on 12/10/24, 10:24 PM
#!/bin/bash
while true; do
# Run the command and capture its exit code
result=$(himalaya envelope list --folder INBOX --page 1 --page-size 100 --output json not flag Seen | \
jq -r '.[] | "\(.id) Seen"')
exit_code=$?
# Check the exit code of `himalaya`
if [[ $exit_code -ne 0 ]]; then
echo "No more unseen emails to process or an error occurred."
break
fi
# Check if result is empty
if [[ -z "$result" ]]; then
echo "No more unseen emails to process."
break
fi
# Process unseen emails
echo "$result" | xargs himalaya flag add
echo "Processed unseen emails. Checking for more..."
done
Another idea I had was to use it to sort mails into folders by the receipient address suffix (my.name+amazon@example.com would sort into the amazon folder), which should be possible if I have read the man pages correctly.
Anyway, thanks for this, not sure if this is the "best" way for me to work with mails but it absolutely is the first tool that made me start automating my inbox.
by brink on 12/9/24, 2:32 PM
by MikeTheGreat on 12/9/24, 6:17 PM
I do see
$ himalaya envelope list --account posteo --folder Archives.FOSS --page 2
I guess my question is: is this different than PINE (or any other terminal-based, interactive email client)?
by tempfile on 12/9/24, 4:22 PM
by JeremyHerrman on 12/9/24, 6:17 PM
by jarbus on 12/9/24, 2:33 PM
I'd love to see a blog or some post on the roadmap for this project (and the org in general).
by delusional on 12/9/24, 8:58 PM
Edit: That is indeed exactly what this is. It's wonderful :)
by gorgoiler on 12/10/24, 1:42 AM
The “MML” MIME markup language is new to me. It is strange that it’s neither markdown based nor does it automatically build the plain text part for you.
On the few occasions these days where I compose an email in mutt (via vim) I find I end up writing markdown _anyway_* so supporting it as an authoring format would be fantastic.
Alas, a lot of professional interactions require HTML emails. I don’t want to come across as awkward nerd to everyone all the time.
*!:)
by pydry on 12/9/24, 3:50 PM
by taylorbuley on 12/9/24, 7:37 PM
by jxf on 12/9/24, 8:28 PM
by nixosbestos on 12/9/24, 3:46 PM
by hk1337 on 12/9/24, 3:16 PM
by szajbus on 12/9/24, 2:40 PM
by alchemist1e9 on 12/9/24, 6:41 PM
by szundi on 12/9/24, 5:53 PM
by oldpersonintx on 12/9/24, 2:40 PM
by zerop on 12/9/24, 2:59 PM