~areotwister

Recent activity

Re: Can't figure out how to get OAuth2 working a month ago

From Areotwister to ~rjarry/aerc-discuss

> App Passwords are new to me. Thanks didn't knew about this other
> option before ^_^
I've now actually gone for App Passwords, OAuth2 is too much effort xD
Thank you for mentioning App Passwords, App Passwords have turned out to
be a actually even better solution for my problem. Now i can sleep again
peacefully, waiting for 30. May to pass over n_n

I put a small provisional tutorial in here for others stumbling over
this Email exchange:

- First 2-Step Verification has to be activated, but you actually don't
have to hand your phone number over to Google. Do the following:
"Security" / "Signing in to Google" -> "2 -Step Verification" ->
!Continue! -> "Use you phone...", "continue" -> "Almost there! Add a

Re: new-email setting not working with example a month ago

From Areotwister to ~rjarry/aerc-discuss

> have you tried sh -c "echo stuff > /tmp/works && touch /tmp/works" (the
> second just to be sure) This should *definitely* not be necessary
> though.
I tried it out, but no file "/tmp/works" appeared there. Manually
running the command in the commandline works.

> Can you check the log in that regard? Not sure if we're logging there,
> but might be worth a shot,
Oki, I checked it ^_^ The log file was quite long. I searched for
"works" and for "new-email" (and some other search words i don't
remember) but they only appeard in the email contents that appeared in
the log.

> Oh and regarding the block below this paragraph, please take a look at

Re: new-email setting not working with example a month ago

From Areotwister to ~rjarry/aerc-discuss

Thanks for your reply ^_^

> I had to prefix it with an exec for it to work, but my setup might be
> considered odd.

Ok, i've know tried out quite a few things:

```bash
1) new-email=exec echo 12 > /home/areo/email_test
2) new-email=exec "echo 12 > /home/areo/email_test"
3) new-email=exec /usr/bin/echo 12 > /home/areo/email_test
4) new-email=echo 12 > /home/areo/email_test
5) new-email=/usr/bin/echo 12 > /home/areo/email_test
6) new-email=exec "/usr/bin/echo 12 > /home/areo/email_test"

Re: Can't figure out how to get OAuth2 working a month ago

From Areotwister to ~rjarry/aerc-discuss

> Hi, the easiest way to get a Google Account to work is an App Password.
> You can generate one on the Google Account page[0].
> I know that it's far from optimal to how exactly OAUTH2 is used, I have
> to refer you to someone else.
App Passwords are new to me, thanks didn't knew about this other option before ^_^
I just don't want, in no way to have to use a gui application for my mails as it's just so convinient to have everything clean und simple in the terminal with tmux, so i might even live with the 2-Factor-Authentification that this option would enforce on me. I will definetily go for it, when i finally resign on trying to get OAuth2 working. So i have at least one working solution, thank you very much!

> For your client_{id,secret} you should probably just use the website[1]
> as well, I can't really help you more in that regard though. (Scope
> should probably be https://mail.google.com [2]
I have doubts about my google skills, more precisely my duckduckgo skills, that's exactly the kind of official site i was looking for xD Thx ^_^

Thank you very much for taking your time to deal with my problem and for working on aerc ^_^
I'm rly amazed by aerc. For such a long time I've been searching for a way to get rid of neomutt and it's ugly configs. And then i finally found aerc yesterday. A true gem. I will definitely recommend it everywhere i can, to convert more people over to aerc!

new-email setting not working with example a month ago

From Areotwister to ~rjarry/aerc-discuss

- I just tried out the new-email setting with the example from the manual: `new-email=exec notify-send "New email from %n" "%s"`, but no message showed up in https://github.com/dunst-project/dunst. But the command `notify-send "New email from %n" "%s"` executed  from the commandline works. The folder that received the email within aerc, was selected.
- I tried if the `new-message-bell=true/false` affects it somehow, but it didn't.
- But a interesting detail is, that there was no bell sound to hear, neither with `new-message-bell=true` nor `new-message-bell=false`. But there was a signal recieved from the workspace in i3 that something happened.
- The reason could propably be that Gmail isn't writing the \Recent flag as Robin mentioned in one of his answers: https://lists.sr.ht/~rjarry/aerc-devel/<fcd88f4e-cad1-4b99-801b-fb3c790c5647%40www.fastmail.com>#<CHXOH8OVR7LC.2RI1NALZT2PX3@diabtop>
- It would be nice to maybe have a trigger not dependand on this flag, but that just triggers if a message is received, because it's a rly usefull feature to just zap through the messages in dunst to get the info if new emails were received

Re: Can't figure out how to get OAuth2 working a month ago

From Areotwister to ~rjarry/aerc-discuss

(I gave the email a proper formatting, such that it won't be so hard to read
on the webpage.)
- It would be rly great if a little help could be provided on how to get OAuth2
running for Gmail, as Gmail is going to stop supporting access for
authentification over only username and password at May 30 this year 2022.
- The manpage for aerc-imap gives a few hints:
imaps+oauthbearer://
    IMAP with TLS/SSL using OAUTHBEARER Authentication

    oauth2_params:

		If specified, the configured password is used as an refresh token that is
		exchanged with an access token

Can't figure out how to get OAuth2 working a month ago

From Areotwister to ~rjarry/aerc-discuss

- It would be rly great if a little help could be provided on how to get OAuth2 running for Gmail, as Gmail is going to stop supporting access for authentification over only username and password at May 30 this year 2022.
- The manpage for aerc-imap gives a few hints:
imaps+oauthbearer://
    IMAP with TLS/SSL using OAUTHBEARER Authentication

    oauth2_params:

    If specified, the configured password is used as an refresh token that is exchanged with an access token

    -   token_endpoint (required)
    -   client_id (optional)
    -   client_secret (optional)
    -   scope (optional)