From: marcus-sup@bar-coded.net (Marcus Williams)
Subject: [sup-talk] [PATCH] IMAP fixes
Date: Tue, 06 Nov 2007 10:05:42 +0000 [thread overview]
Message-ID: <1194343383-sup-7427@tomsk> (raw)
Hi -
And another. This is the IMAP fixes without the marked_read? stuff.
This adds:
* unread status fix
* save message fix (same as maildir fix in last patch sent)
* capability checks before using auth methods (note that if your
server does not advertise an auth capability, even if it supports it
it will not be used. Check log buffer for messages on login to double
check what method you use)
Marcus
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imap-diffs
Type: application/octet-stream
Size: 1872 bytes
Desc: not available
Url : http://rubyforge.org/pipermail/sup-talk/attachments/20071106/a124b40f/attachment.obj
next reply other threads:[~2007-11-06 10:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 10:05 Marcus Williams [this message]
2007-11-07 1:55 ` 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=1194343383-sup-7427@tomsk \
--to=marcus-sup@bar-coded.net \
/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