From: marcus-sup@quintic.co.uk (Marcus Williams)
Subject: [sup-talk] [PATCH] Check IMAP capabilities before using auth methods
Date: Thu, 01 Nov 2007 09:02:57 +0000 [thread overview]
Message-ID: <1193907675-sup-9254@tomsk> (raw)
Hi -
Following patch speeds up IMAP logins if your server doesnt support
CRAM-MD5 or the LOGIN auth methods by checking the advertised
capabilities on the connection before trying to use them.
Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imap-diffs
Type: application/octet-stream
Size: 986 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071101/d9d0e2e4/attachment.obj
next reply other threads:[~2007-11-01 9:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-01 9:02 Marcus Williams [this message]
2007-11-01 17:06 ` Grant Hollingworth
2007-11-05 3:17 ` William Morgan
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=1193907675-sup-9254@tomsk \
--to=marcus-sup@quintic.co.uk \
/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