If you are upgrading from a pre 1.0 version you will have to remove the oldcachefile and create a new configuration.

Configure=========

For most users it will be enough to add an entry to your ~/.netrc::

machine google.com login your@google.email password secret

NOTE: The netrc implementation in Python don't support passwords with spaces, use the .goobookrc or keyring instead.

To get access too more settings you can create a configuration file::

goobook config-template > ~/.goobookrc

It will look like this::

# "#" or ";" at the start of a line makes it a comment. [DEFAULT] # If not given here, email and password is taken from .netrc using # machine google.com ;email: user@gmail.com ;password: top secret # or if you want to get the password from a commmand: ;passwordeval: gpg --batch -d ~/.mutt/pw.gpg # The following are optional, defaults are shown ;cache_filename: ~/.goobook_cache ;cache_expiry_hours: 24

If you set the password to "prompt" you will be prompted each time the password is neededbut this does not work well with mutt.

Instead of being a plain config file ``.goobookrc`` can be an executable,in which case it's output will be used as configuration.

For example if you want to store your configuration encrypted with GnuPG as ``.goobookrc.gpg``you can use a ``.goobookrc`` like this::

#!/bin/sh gpg --no-tty --use-agent -q -d ~/.goobookrc.gpg

You will need to have a appropriate gpg-agent/pinentry setup, you will not be promptedfor the gpg passphrase on the console.

Similarly, goobook supports authentication by keyring_. The keyring packagesupports multiple backends, depending on yourenvironment. You should configure it to point to the one you're using bydefault. To use this option, set your e-mail address in the config file butleave the password field commented out (or blank). You need to have a passwordfor the "gmail" service and your e-mail address stored in the keyring. Thereare several ways to achieve this, here is one::

1.4 2012-11-10----------------* No longer necessary to configure goobook to be able to generate a configuration template...* Fixed issue 28: No Protocol is set on GTalk IM* Fixed issue 32: Encoding problem of unicode chars on non unicode terminal.* Fixed issue 34: Unable to query due to keyring/DBus regression* Fixed issue 35: passwordeval* Fixed issue 36: When the contact has no title mutt will use the extra_str as the title.

* Added contacts are now added to "My Contacts", this fixes problem with searching now finding contacts you have added with goobook.* Searches also matches on phonenumber (Patch by Marcus Nitzschke).* Detailed, human readable, search results (Patch by Marcus Nitzschke).

1.4a2 2010-10-26----------------

* When a query match a email-address, only show that address and not all the contacts addresses.* Added option to filter contacts that are in no groups (default on).

* Support for executable .goobookrc (replaces direct GnuPG support)* Faster, more compact cache* dump commands no longer use the cache* Caching most contact data but not all

1.3a1 2010-04-21----------------

* Python 2.5 compability* Added flags --verbose and --debug* Added possibility to add a contact from the command-line.* Added possibility to prompt for password.* New command: dump_contacts* New command: dump_groups* New dependency, hcs_utils* Now caching all contact data.* Support for using a GnuPG encrypted config file (later replaced).* Fixed bug when checking for the config file.* Major refactoring

1.2, 2010-03-12---------------

* Issue 14: Only search in these fields: name, nick, emails, group name. In 1.1 the group URL was also searched, which gave false positives.* Auto create cache if it doesn't exist.

1.1, 2010-03-10---------------

* Use current locale to decode queries.* Encode printed text using current locale.* Added option to specify different configfile.* Some documentation/help updates.* The .goobookrc is now really optional.* Added config-template command.* Issue 13: Added support for contact groups.* New cache format, no longer abook compatible (JSON).