Avoid redundant entries for accounts with multiple protos

Message ID
DKIM signature
Download raw message

I just stumbled across Himitsu and I really like the Idea behind it.
However, I see one "use case" that doesn't seem to be covered.  I find
it hard to explain that in a general manner, so I'll use an example:

If I want to log in to google.com with my google account and store the
credentials in the Himitsu key store, I'd create an entry like this:

proto=web host=google.com user=me@gmail.com password!=12345

However, if I'd like to also log in to my gmail account via IMAP to read
my email, the proto would be IMAP, the host would be imap.gmail.com, but
the credentials would remain the same. So IIRC, I'd have to create a
second entry like this:

proto=imap host=imag.gmail.com user=me@gmail.com password!=12345

This would make it necessary to create redundant data for every protocol
associated to one account, so if I'd change my google password, I'd have
to change it in at least three places, if I'm also storing my SMTP
credentials. Is there a way to avoid this? If not, is a feature to avoid
this planned? I'd imagine some kind of reference system.

Thank you for your work.
Message ID
<20220626150817.v7j6lun7xsum3p3x@PhilippN-Vostro-5490> (view parent)
DKIM signature
Download raw message
The format of each key differs depending on the protocol. A key with
proto=imap may have a port number defined which would conflict with the
port for proto=smtp, for instance. You should make multiple keys imo.
Reply to thread Export thread (mbox)