On Mon, Jun 18, 2018 at 03:41:11PM -0700, Brandon Long wrote: > I'm not sure of a good solution to this. One solution would be a mechanism > for delayed evaluation of the config options, the other would require > more advanced support of OAUTH2, where we would have separate config > entries for the various bits > [...]
> As for changes to the config handling, I could add new > smtp_oauth_token_command/imap_oauth_token_command config vars, and do the > evaluation in-line with that, that's probably the cleanest way to handle > this as specific to this issue and not try for larger changes. If I understand correctly, the quick and clean fix is to add the [smtp|imap]_oauth_token_command. Assuming that obviates the first paragraph (embedding the https fetch, json support etc, or adding dynamic config options), I think that's the best idea. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
