From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Trying to use gnus-cloud: what's the pinentry dialog? (and how can I get rid of it?)
Date: Sun, 26 Sep 2021 18:52:14 +0200 [thread overview]
Message-ID: <86ilynuvnl.fsf@dod.no> (raw)
In-Reply-To: <87bl4fibod.fsf@ucl.ac.uk>
>>>>> Eric S Fraga <e.fraga@ucl.ac.uk>:
> I don't use it nor have I ever tried it. I am not entirely sure what it
> would do for me, especially as I don't use IMAP, preferring to download
> all my emails to my own computers and keep them all in sync myself.
Gnus cloud is not for syncing email. Gnus cloud is for achieving nnimap
like functionality in NNTP: ensuring that what I read and respond to on
one computer, is also marked read and/or followed-up, when I use gnus on
a different computer.
Gnus cloud also syncs score setup/status for all backends. Or in my
case, so far: *tries* to sync score setup
(I think gnus sync actually tries to sync all config and setup stuff
found in .newsrc.eld, ie. config created interactively, but I'm not 100%
sure...?)
An IMAP folder is used for exchanging the synch data, with messages
saved in the folder holding the sync data, one new message created by
each sync save.
And the format of the content of the messages in the IMAP folder, used
to hold the sync info is what's in the variable gnus-cloud-storage-method
and can be one of:
- No encoding
- Base64
- Base64-gzip
- EPG (which is GPG encoding, I think...? This is the default)
And finding a value for gnus-cloud-storage-method that works for me, has
been a problem.
The default EPG method pops up a dialog twice, asking for a passphrase
on every save, and has problems decoding on the receiving end.
The Base64 encodings fail on decode, saying "This isn't base64".
And "No encoding" maybe works, sometimes...
>> Next step out is to read the source code and start debugging to see
>> what's actually going on (but that won't happen tonight).
> Good luck and do keep us posted.
Thanks! Will do!
next prev parent reply other threads:[~2021-09-26 16:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 13:50 Steinar Bang
2021-09-19 14:16 ` Steinar Bang
2021-09-19 14:30 ` Steinar Bang
2021-09-19 14:47 ` Steinar Bang
2021-09-23 15:07 ` Steinar Bang
2021-09-23 15:25 ` Steinar Bang
2021-09-23 17:17 ` Steinar Bang
2021-09-23 17:42 ` Steinar Bang
2021-09-23 17:58 ` dick
2021-09-24 8:40 ` Eric S Fraga
2021-09-24 20:18 ` Steinar Bang
2021-09-26 15:44 ` Eric S Fraga
2021-09-26 16:52 ` Steinar Bang [this message]
2021-09-27 14:54 ` Eric S Fraga
2021-10-02 11:27 ` Steinar Bang
2021-10-02 11:39 ` Steinar Bang
2021-10-02 14:59 ` Steinar Bang
2021-10-02 15:49 ` Eric Abrahamsen
2021-10-02 16:19 ` Steinar Bang
2021-10-03 8:46 ` Steinar Bang
2021-10-03 17:30 ` Steinar Bang
2021-10-04 14:43 ` Steinar Bang
2021-10-04 18:00 ` Steinar Bang
2021-10-04 19:19 ` Steinar Bang
2021-10-04 19:42 ` Steinar Bang
2021-10-04 20:09 ` Adam Sjøgren
2021-10-04 21:26 ` Steinar Bang
2021-10-05 8:41 ` Robert Pluim
2021-10-05 15:02 ` Adam Sjøgren
2021-10-05 15:41 ` Robert Pluim
2021-10-05 16:20 ` Adam Sjøgren
2021-10-05 15:14 ` Eric Abrahamsen
2021-10-05 16:17 ` Adam Sjøgren
2021-10-05 17:46 ` Eric Abrahamsen
2021-10-05 17:52 ` Adam Sjøgren
2021-09-23 17:14 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ilynuvnl.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).