On Fri, 2003-02-21 at 08:17, Mark Crispin wrote:
On Thu, 21 Feb 2003, Timo Sirainen wrote:
I'd like to know how you can make a client efficiently handle sequence
numbers. If internal message structure contains just the sequence
number, it has to be updated every time an older message is
I find it interesting, if not disturbing, that some members of the
usenet community seem to think that mail messages and usenet articles
are not the same thing. AFAICT, from reading the relevant standards,
writing server code for SMTP/LMTP/IMAP/POP3/NNTP, and everyday use, mail
messages and news
On 21 Feb 2003 07:34:59 +0200 Timo Sirainen [EMAIL PROTECTED] wrote:
I'd like to know how you can make a client efficiently handle sequence
numbers. If internal message structure contains just the sequence
number, it has to be updated every time an older message is deleted.
Since it's just
Charles Lindsey wrote:
In [EMAIL PROTECTED] Mark Crispin
[EMAIL PROTECTED] writes:
But clients that interoperate with IMAP usually also have the capability
to interoperate with POP3, SMTP, NNTP and maybe even UUCP. I have never
seen any suggestion that those other servers are in any
On Fri, 2003-02-21 at 17:33, Simon Josefsson wrote:
Not really, why would you _need_ to get a list of all messages? Client
can request the messages from server only when they become visible in
screen. Scrollbar sizes and such can be generated from just the total
amount of messages. Before
Not really, why would you _need_ to get a list of all messages? Client
can request the messages from server only when they become visible in
screen. Scrollbar sizes and such can be generated from just the total
amount of messages. Before the message is loaded from server, client
could just
Hi Timo,
--On Friday, February 21, 2003 7:34 AM +0200 Timo Sirainen [EMAIL PROTECTED]
wrote:
| Actually in some situations relying on sequence numbers could even lose
| messages. Suppose a client (maybe a webmail) showing messages 1..10 on
| screen. Next-button would load the next 10. If the
On 21 Feb 2003 19:02:26 +0200, Timo Sirainen wrote:
OK, I looked through c-client and Pine code. It looks just as difficult
as I expected. It uses multiple arrays for seq - message lookups.
Bullshit. There is one cache. Don't get confused by the sortcache which is
not seq-message lookup.
It
D J Bernstein [EMAIL PROTECTED] writes:
Actually, there's very little opposition (especially among implementors)
to requiring all MTAs, MUAs, etc. to handle UTF-8 messages. Eventually
we will all be using UTF-8; all relevant bugs must be fixed. Only the
wildest ``7 bits forever!'' proponents,
On Fri, 21 Feb 2003, Russ Allbery wrote:
D J Bernstein [EMAIL PROTECTED] writes:
Actually, there's very little opposition (especially among implementors)
to requiring all MTAs, MUAs, etc. to handle UTF-8 messages. Eventually
we will all be using UTF-8; all relevant bugs must be fixed. Only
On Fri, 21 Feb 2003, Timo Sirainen wrote:
But whenever sorting is done, there is the sort array that has to be
updated and accessed slowly whenever you get fetch envelope reply
(pine_imap_envelope - mn_raw2m() - msgno_in_sort()).
Wrong. What you are seeing in Pine is a mapping from a view.
On Fri, 21 Feb 2003, Russ Allbery wrote:
Usenet's restrictions on the syntax of message ID headers are very
specific and very precise, and much stronger than those of RFC 2822, in
part because message IDs are used as part of the NNTP protocol.
What are those restrictions?
Comments
in
On Thu, 20 Feb 2003, Russ Allbery wrote:
| 1 2 3 4 5 6 7 8 9 10 11 12 13 14
-+--
A| D C N N D Y N N N Y N D Y D
B| Y Y C Y Y N N N N N N N C D
C| D C C C
On Fri, 21 Feb 2003, Timo Sirainen wrote:
I don't know anyone who accesses their mail from more than a few
computers.
In a typical day, I use from three to five different computers to access
my mail. So do my co-workers.
I use IMAP only at home for accesssing my mails, elsewhere I
just ssh
Mark Crispin [EMAIL PROTECTED] writes:
On Fri, 21 Feb 2003, Russ Allbery wrote:
Usenet's restrictions on the syntax of message ID headers are very
specific and very precise, and much stronger than those of RFC 2822, in
part because message IDs are used as part of the NNTP protocol.
What are
On Fri, 21 Feb 2003, Timo Sirainen wrote:
I don't know anyone who accesses their mail from more than a few
computers. I use IMAP only at home for accesssing my mails, elsewhere I
just ssh into my server and read the mails there. Good and secure ssh
clients are easier to find and setup than
Mark Crispin [EMAIL PROTECTED] writes:
Now, let's factor out the items in which all three choices are
equivalent, and the superiority of choice C becomes even more
apparent.
| 1 2 3 4 5 6 10 12 13
-+---
A| D C N N D YY D Y
On Fri, 22 Feb 2003, Timo Sirainen wrote:
Well, you stated your problem: you don't use a good IMAP client.
That could be it. Installing and running would have to be as easy as
sshing with putty though. Meaning you could get imapclient.exe from web
page which you can run directly, only
Ken Murchison [EMAIL PROTECTED] writes:
OK. As I suspected there is nothing inherent in RFC [2]822 that makes
it unsuitable for news.
Spaces in message IDs make them unsuitable for news. This really, really
does break things, honest, I swear. I'm not just making this up. :)
In general,
The wildmat problem is a red herring. Wildmat implementations need to be
cognizant of Unicode in far more substantial ways than merely overcoming
punycode issues. A well-thought-out stringprep requirement will help
some, but then the stringprep has to be implemented.
This last point of
20 matches
Mail list logo
