9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] gmail's new POP features + upas/fs
Date: Tue, 23 Nov 2004 21:34:16 +0000	[thread overview]
Message-ID: <b520fd26307a28aaad4bce960dcff740@hamnavoe.com> (raw)
In-Reply-To: <ee9e417a041122191933083bdf@mail.gmail.com>

russcox@gmail.com says:

> Upas/fs really expects that it's manipulating
> a permanent mailbox.  It's not a typical usage
> of pop (the typical usage is download, perhaps delete
> from server, and keep locally even if the message
> disappears from the server) but it usually works.
> Gmail might be breaking the rules.

The upas/fs pop3 code uses message numbers, not UIDs,
to identify messages on the server, and expects that
messages will be in the same order each time the client
reconnects.  I found this expectation wasn't true with
the demon.co.uk server, and indeed it doesn't seem to
be stipulated anywhere in the RFCs.

I made a modification to upas/fs/pop3.c to use UIDs,
which seemed to work reliably with demon - can't
remember whether I submitted it to sources, but I
switched to a different provider soon afterwards so
I stopped using it.

The same modification might help with gmail - if I
had a gmail account I could try it and see ;)

-- Richard



  parent reply	other threads:[~2004-11-23 21:34 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23  3:14 andrey mirtchovski
2004-11-23  3:19 ` Russ Cox
2004-11-23  3:33   ` andrey mirtchovski
2004-11-23 21:34   ` Richard Miller [this message]
2004-11-23 21:45     ` andrey mirtchovski
2004-11-23 21:54       ` Christopher Nielsen
2004-11-23 22:13         ` andrey mirtchovski
2004-11-24  2:21     ` Russ Cox
2004-11-24  2:45       ` boyd, rounin
2004-11-24  3:46     ` boyd, rounin
2004-11-23  3:23 ` David Leimbach
  -- strict thread matches above, loose matches on Subject: below --
2004-11-24 10:10 Richard Miller
2004-11-24 13:44 ` Russ Cox
2004-11-24 14:01   ` Richard Miller
2004-11-24 16:24     ` David Leimbach
2004-11-24 16:57       ` Steve Simon
2004-11-22  6:07 David Leimbach
2004-11-22 13:05 ` Russ Cox
2004-11-22 19:37   ` David Leimbach
2004-11-22 20:25     ` Russ Cox
     [not found]       ` <b5a997b232d9134198a35ef32e607841@plan9.ucalgary.ca>
2004-11-22 21:01         ` Russ Cox
2004-11-22 21:03           ` David Leimbach
2004-11-23  1:24       ` David Leimbach
2004-11-23  1:36         ` andrey mirtchovski
2004-11-23  2:05           ` David Leimbach
2004-11-23  2:51             ` andrey mirtchovski
2004-11-23  3:06               ` David Leimbach
2004-11-23  3:08                 ` David Leimbach
2004-11-23  3:10                   ` David Leimbach
2004-11-23  2:46           ` Russ Cox

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=b520fd26307a28aaad4bce960dcff740@hamnavoe.com \
    --to=9fans@hamnavoe.com \
    --cc=9fans@cse.psu.edu \
    /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).