public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Christopher Moore <christopher.h.moore@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Fetching from gmail
Date: Wed, 11 Nov 2009 20:24:39 -0500	[thread overview]
Message-ID: <20091112012438.GA5901@arch> (raw)
In-Reply-To: <20091110055117.GC5619@lnx3.holmesgrown.com>

Steve,
How do you tell mutt to copy a message to trash.  Would you do something 
like:
C =Trash

Maybe this could be assigned to the d key.  I'd also like to assign 
something similar to ctrl+d to remove an entire thread.

Cleaning out the "all maiil" folder may be quite labor intensive.  We'd 
want to delete all conveersations without an assigned label.  This would 
take quite a while using the web interface.  Perhaps there are some 
python bindings for gmail which could be used.  
I don't really mind that mutt removes the messages from the inbox if we 
had a utility to clean out the "all mail" folder once in a while.

Chris
On Mon, Nov 09, 2009 at 10:51:17PM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
> 
> Yes, I use mutt to get gmail from two different accounts and I support
> multiple folders on each of them.  The mutt setup is actually pretty
> easy as I've used imap for some time on other systems prior to gmail.
> The important thing to realize with gmail and IMAP is when deleting
> unwanted messages, you need to copy them to '=Trash' (exclude the
> quotes and realize that is capital T on Trash).  If you just delete
> them like on standard IMAP systems and then expunge them with mutt's
> 'x' command, the Inbox label will be removed and the messages will end
> up in your 'All Mail' folder forever! that happened to me for a long
> time before I realized what was happening and I still have over 8,000
> messages to eventually clear out on one of my accounts.
> 
> Otherwise, gmail with IMAP is quite cool.  I never use POP.
> 
> On Wed, Oct 28, 2009 at 09:06:20AM -0400, Christopher Moore wrote:
> > Hello,
> > The best way I've found to use gmail on linux is via mutt with a special 
> > config file to access the imap server.  
> > 
> > I found info in this through google.  
> > 
> > Chris
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> 
> iEYEAREDAAYFAkr4/1UACgkQWSjv55S0LfHBJwCfSAwbSxDuA6YPQyiXr4uJoqpT
> GtkAnjrjFpCzfj6VVj5ouS3D3U3riqnW
> =PHMW
> -----END PGP SIGNATURE-----
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

  parent reply	other threads:[~ UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Trevor Saunders
   ` Cheryl Homiak
   ` Tony Baechler
     ` Christopher Moore
       ` Steve Holmes
         ` Gaijin
           ` Steve Holmes
         ` Christopher Moore [this message]
           ` Steve Holmes
             ` Steve Holmes
               ` Christopher Moore
                 ` Steve Holmes
           ` Gaijin
             ` Steve Holmes

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=20091112012438.GA5901@arch \
    --to=christopher.h.moore@verizon.net \
    --cc=speakup@braille.uwo.ca \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).