NEW in 0.6:
===========

Version 0.6 has many changes including several code cleanup changes,
the ability to enter your password when mounting instead of having to
keep it in a config file and the ability to easily use GmailFS with
EncFS, a FUSE based encrypted filesystem. All of these changes have
been written by the Debian package maintainer, Sebastien Delafond (who
I thank for his ongoing contributions to GmailFS). Please see the
ChangeLog file for further details.

gmailfs:
--------

(those notes were copy-pasted from
http://richard.jones.name/google-hacks/gmail-filesystem/gmail-filesystem.html,
and slightly reformatted/added to by Sebastien Delafond)

You can mount your Gmail filesystem either via fstab or on the command
line using mount. In either case, the fuse module needs to be loaded
prior to attempting to mount the Gmail filesystem. This module can be
built from the fuse-source package (it has also been merged into the
main kernel tree as of 2.6.14).

* To mount from the command line, do:

  mount.gmailfs none /mnt -o username=gmailuser@gmail.com,password=gmailpass,fsname=zOlRRa
or
  mount.gmailfs none /mnt -o username=gmailuser@gmail.com,fsname=zOlRRa -p

Warning: the first method has a serious security issue: if you run a
multi-user system, others can easily see your Gmail username and
password, so make sure you use -p to be prompted for your password.

* To use fstab, create an entry /etc/fstab that looks something like:

none /mnt gmailfs noauto,username=gmailuser@gmail.com,password=gmailpass,fsname=zOlRRa

The username and password fields speak for themselves. The fsname is
the name of this Gmail filesystem. It is important to choose a
hard-to-guess name here - because if others can guess the fsname, they
can corrupt your Gmail filesystem by injecting spurious messages into
your Inbox.

GmailFS also has a blocksize option. The default blocksize is
5MB. Files smaller than the minimum blocksize will only use the amount
of space required to store the file, NOT the full blocksize. Note that
any files created during a previous mount with a different blocksize
will retain their original blocksize until deleted. For most
applications you will make best use of your bandwidth by keeping the
blocksize as large as possible.

When you delete files, GmailFS will place the files in the
trash. libgmail does not currently support purging items from the
trash, so you will have to do this manually when logged into your
Gmail account.

To avoid seeing the messages created for your Gmail filesystem you
probably want to create a filter which automatically archives GmailFS
messages as they come into your Inbox. The best approach is probably
to search for the fsname value; it'll be in the subject of all GmailFS
messages.

 -- Sebastien Delafond <sdelafond@gmx.net>  Wed, 13 Oct 2004 17:29:58 -0700
