From: David Leimbach <leimy2k@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Cc: russcox@gmail.com
Subject: Re: [9fans] gmail's new POP features + upas/fs
Date: Mon, 22 Nov 2004 19:23:24 -0800 [thread overview]
Message-ID: <3e1162e60411221923213554b7@mail.gmail.com> (raw)
In-Reply-To: <a8d521e026d2cc8a873eed33365214e8@plan9.ucalgary.ca>
On Mon, 22 Nov 2004 20:14:18 -0700, andrey mirtchovski
<mirtchov@cpsc.ucalgary.ca> wrote:
>
> > perhaps you've told gmail to delete
> > messages once pop downloads them.
> > (it's a gmail settings option in the pop section.)
> > the next time upas/fs logs in and looks
> > at your mail, they're not there, so it assumes
> > they've been deleted and forgets about them.
> >
> > russ
>
> i had them on archive first, then changed to 'leave in inbox'. gmail
> indicates that they're sending a 'copy to pop3', so don't think that's
> to blame.
>
> here's what i do:
>
> - kill all 'fs' in the current session, even better -- start a
> new one with drawterm and without starting upas/fs.
>
> - upas/fs -s -f/..../
>
> - mount /srv/upasfs.andrey and start acme Mail on that dir
>
> - send a message to myself on my gmail account
>
> - when the message appears in acme either do a new mount of
> /srv/upasfs... or wait about a minute and the message will be
> marked as 'deleted' in the old Mail. it never appears in the
> new one.
>
> exiting the original acme mail and restarting it doesn't show the
> message either, even though Mail wouldn't really delete the message
> unless its window has been 'Put'.
>
> i can verify that this problem doesn't exist with imaps and imap on
> other accounts i have.
>
> andrey
>
>
Andrey,
I am sitting here watching faces and I got your race... I just got one
of russco on my machine too... and now it vanished...
It must take things that are in a regular inbox and move them to some
other directory?
quite weird :). Perhaps Rob Pike can save us :)
Dave
next prev parent reply other threads:[~2004-11-23 3:23 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
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 [this message]
-- 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=3e1162e60411221923213554b7@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).