|author||Daniel Kahn Gillmor <email@example.com>||2020-03-18 22:07:33 -0400|
|committer||Sean Whitton <firstname.lastname@example.org>||2020-03-19 13:23:09 -0700|
imap-dl: use retriever.authentication configuration
After discussion with Sean Whitton and Robbie Harwood, I think makes more sense to have a straight "retriever.authentication" configuration setting rather than a rather odd boolean "use_kerberos". This is a divergence from getmail, but that seems OK at this point. The implementation now also makes it pretty straightforward to add new authentication mechanisms if someone wants to add them. One additional thing that would be nice would be for imap-dl to be able to dynamically choose the "best" available authentication method. Signed-off-by: Daniel Kahn Gillmor <email@example.com>
Diffstat (limited to 'imap-dl.1.pod')
1 files changed, 5 insertions, 5 deletions
diff --git a/imap-dl.1.pod b/imap-dl.1.pod
index 5864267..88e3129 100644
@@ -43,14 +43,14 @@ options:
B<retriever.server> is the dns name of the mailserver.
+B<retriever.authentication> is either "basic" (the default, using the
+IMAP LOGIN verb) or "kerberos" (IMAP AUTHENTICATE with GSSAPI,
+requires the python3-gssapi module).
B<retriever.username> is the username of the IMAP account.
B<retriever.password> is the password for the IMAP account when using
-B<retriever.use_kerberos> (boolean) requests that Kerberos (through GSSAPI) is
-to be used instead of password-based auth. There is no need to specify
-password when using Kerberos. This requires the python3-gssapi module.
+B<retriever.authentication> is set to "basic".
B<retriever.ssl_ciphers> is an OpenSSL cipher string to use instead of the
defaults. (The defaults are good; this should be avoided except to work