From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Gmail question
Date: Mon, 21 Dec 2009 18:45:14 -0500 [thread overview]
Message-ID: <1261438895-sup-2073@ntdws12.chass.utoronto.ca> (raw)
In-Reply-To: <1261414173-sup-9168@masanjin.net>
[-- Attachment #1.1: Type: text/plain, Size: 1173 bytes --]
Excerpts from William Morgan's message of Mon Dec 21 11:56:19 -0500 2009:
> I believe that Gmail exposes those types of things to IMAP clients as
> IMAP folders with funny names. (If you see these messages in Sup's
> inbox, then I am wrong about that.)
Yes, it definitely does. I had to migrate 300+ accounts out of gmail
via IMAP. If you're doing offlineimap for this task, I'd suggest
mapping each 'folder' to a separate Maildir and, if possible, use hard
links for messages that land in multiple 'folders.' An md5sum of the
headers is the heuristic I used to detect this.
> sup-add imaps://imap.gmail.com/%5BGmail%5D%2FSent+Mail
> sup-add imaps://imap.gmail.com/%5BGmail%5D%2Flabelname
Depending on the age and 'type' of account, you may also see things
like .../%5BGoogle%20%5B%2Flabelname.
> Anyone more familiar with Gmail+Sup, please correct me if I'm wrong.
I don't use sup for any of my gmail needs, this is all based on my
export experience.
HTH.
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302
GPG Key Id: 8E89F6D2; Key Server: pgp.mit.edu
Contact me to arrange for a CAcert assurance meeting.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 140 bytes --]
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-12-21 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 16:28 Joel Esler
2009-12-21 16:56 ` William Morgan
2009-12-21 23:45 ` Ben Walton [this message]
2009-12-27 15:45 ` Joel Esler
2009-12-27 15:48 ` William Morgan
2009-12-27 23:05 ` Joel Esler
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=1261438895-sup-2073@ntdws12.chass.utoronto.ca \
--to=bwalton@artsci.utoronto.ca \
--cc=sup-talk@rubyforge.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