9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: [9fans] nupas imap4d
Date: Mon, 18 May 2009 22:04:43 -0400	[thread overview]
Message-ID: <952d06e9094f121880829d8d5ecf5cbb@quanstro.net> (raw)

i put a new version of imap4d up on sources that should
eliminate uid sequence error messages with outlook.
(and the oh-so-helpful dialog boxes that go with them.)
thunderbird and apple mail don't seem to care about this
problem.

for those who care, the problem is ...
each imap message is identified by an ephemerial sequence
number and a perminant uid.  imap4 takes the nonsensical
position that while result sets may be returned in any order,
uid_a < uid_b <=> seq_a < seq_b; being able to return
things in any order is no help at all if you have to sort the
messages to sequence them anyway.

so that's what i did.  but at least i didn't like it.

- erik



             reply	other threads:[~2009-05-19  2:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-19  2:04 erik quanstrom [this message]
2009-05-19 13:52 erik quanstrom

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=952d06e9094f121880829d8d5ecf5cbb@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.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;
as well as URLs for NNTP newsgroup(s).