From: Bill White <billw@mchsi.com>
To: info-gnus-english@gnu.org
Subject: Re: gmail and gnus
Date: Sun, 29 Apr 2007 22:49:47 GMT [thread overview]
Message-ID: <m3irbe6bjp.fsf@mchsi.com> (raw)
In-Reply-To: <871wi2g6o6.fsf@gmail.com>
On Sun Apr 29 2007 at 17:24, Hadron <hadronquark@gmail.com> wrote:
> Bill White <billw@mchsi.com> writes:
>> Unfortunately, gmail doesn't do IMAP:
>> https://mail.google.com/support/bin/answer.py?answer=10339 but
>> there are some workarounds I'll look into (google "gmail imap"
>> without the quotes).
> You are probably better off in gnu.emacs.gnus
Yes, thanks.
> Why use IMAP? You can access using pop3. Works for me.
I'm sure no expert but unless I'm missing something, POP3 won't modify my
gmail repository to reflect changes I would make locally to my downloaded
email in gnus.
I read email from 2 computers on ordinary days, more when we travel or
when I'm in the office. It's necessary for my sanity that my main
universally-accessible email repository be up-to-date wrt
read/archived/ticked marks, etc.
AIUI, this is what would happen with pop3:
- 200 messages arrive in my gmail account
- I download them to gnus on my linux box
- I happily read, delete, tick, archive, move, reply to various messages
from my linux box
- later I access gmail from my windows box - all 200 messages are still
marked unread or all are archived by the pop3 process I ran via gnus
- I snap.
Cheers -
bw
--
Bill White . http://members.wolfram.com/billw
"No ma'am, we're musicians."
next prev parent reply other threads:[~2007-04-29 22:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2427.1177394454.7795.help-gnu-emacs@gnu.org>
[not found] ` <1177802542.833069.30440@q75g2000hsh.googlegroups.com>
[not found] ` <m33b2i7sdz.fsf@mchsi.com>
2007-04-29 22:24 ` Hadron
[not found] ` <871wi2g6o6.fsf@gmail.com>
2007-04-29 22:49 ` Bill White [this message]
2007-04-30 2:19 ` Joel Reicher
2007-04-30 3:04 ` Bill White
2007-04-30 13:07 ` Joel Reicher
2007-05-09 8:32 ` Gernot Hassenpflug
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=m3irbe6bjp.fsf@mchsi.com \
--to=billw@mchsi.com \
--cc=info-gnus-english@gnu.org \
/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).