Frequently Asked Questions
Connecting to Gmail
Google now requires email clients implement its proprietary protocol to sign in by default. As a result, you may need to update your Google settings to allow Geary to connect to your Gmail account via IMAP. The setting to change depends on whether you have 2-Step authentication enabled for your Google account:
If 2-step verification is enabled, you should create an App Password, and use that in your Geary account settings
If 2-step verification is not enabled, you will need to allow access for “Less Secure Apps”
A future version of Geary will support Google’s proprietary protocol, see Bug 746705 for more information.
Not running GNOME 3?
Geary is designed for the GNOME 3 desktop, and as such depends on a number of standard desktop services provided by GNOME by default. While it is possible to run Geary under other desktop environments such as KDE, XFCE, Mate, and so on, you may need to ensure that the services Geary depends on are installed and correctly configured for your desktop yourself.
With these services installed, Geary will use your desktop's standard settings to determine your user interface language, writing direction, notifications, date and time format, GTK+ theme, icon theme, proxy settings, and so on. Consult your desktop environment's user manual for help in setting these, and Geary will pick up any changes you make automatically.
The following is the list of services that Geary expects to be present and configured correctly when you log in:
- Desktop Services
- Your login session should start or make it possible to activate a D-Bus session bus so that Geary can communicate with other desktop services, including those listed below.
- Spell checking
- Enchant is used for spell-checking emails in the composer and works with a number of different spell checker programs. To enable spell checking, ensure a spell checker program such as GNU Aspell and appropriate dictionaries for it in your preferred languages are installed.
- Password Storage
An implementation of the XDG Secret Service API must be listening on D-Bus so that Geary can store and retrieve passwords in a safe manner. One such implementation of this is the GNOME Keyring daemon, which your desktop may already use, and KDE is working on support for it.
- TLS Certificate pinning
- The GCR library is uses for pinning TLS certificate exceptions, which is particularly important for mail servers that use self-signed certificates. GCR in turn uses p11-kit for securely storing certificats, and this requires a writable PKCS#11 store configured, which could be provided by either software (e.g. GNOME Keyring daemon) or hardware (e.g. a smartcard).
- Proxy support
- Geary uses glib-networking for establishing connections to remote servers, which in turn uses libproxy for looking up proxy configuration. Ensure you have the correct libproxy plugin installed for your desktop.
- A notification daemon is required to display notifications of new messages on your desktop. Your desktop will likely already provide a notification daemon, if not you will need to install one yourself.
Geary crashes when I run it. What I can do to help the developers?
How do I turn on logging with Geary?
To enable logging, run Geary with the --debug (or -d) command line parameter:
This enables some basic debug output that can be used to track down what Geary is doing.
While debugging mode is active, there are several logging options to log network activity, etc. These options can be listed by running:
Note that the logs may contain personal information like email address and the contents of your messages. Some logging options (such as --log-serializer) dump all information indiscriminantly, including usernames and passwords, so beware when using.
Under the Hood
How do I backup Geary mail?
Geary’s configuration is stored in ~/.config/geary (that is, /home/<username>/.config/geary), backing up that or (even better) your entire ~/.config directory will make a copy of Geary’s account information that can be restored later by moving it back into place.
The mail Geary pulls from your server(s) is stored in ~/.local/share/geary. Since mail is retrieved from your mail server it is safe to not back up this directory, however if it is deleted then your mail will need to be re-downloaded again.
The conversation viewer uses WebKit to display an HTML page. To inspect the HTML interactively with WebKit, run Geary with --inspector. Right-click on the conversation viewer to open the WebKit Inspector window.
Customize message CSS
You can customize the display of messages in Geary’s conversations via CSS. Place your custom CSS in a file at ~/.config/geary/user-message.css. If this file exists when Geary starts, it will be loaded and added to message web views as a user stylesheet when displaying messages.
Note that if you have the preference Always watch for new mail enabled, Geary may already be running when you log in, hence use geary --quit first to see any changes to your CSS.
This is supported as of version 0.12.
Why can’t I examine the Geary MessageSearchTable with an SQLite explorer tool (or the sqlite3 command-line app)?
Geary uses SQLite’s full-text search (FTS) feature as well as a Unicode tokenizer and stemmer to improve search performance and results. In order to examine the FTS virtual table, the stemmer/tokenizer must be loaded. Geary is linked with this tokenizer. In order to use the tokenizer/stemmer with another tool or the sqlite3 console program, you must install the tokenizer and load it into memory.
- Run the following from Geary source code directory:
$ cd src/sqlite3-unicodesn $ make $ sudo make install
- With the SQLite command-line application:
$ sqlite3 -cmd '.load unicodesn.sqlext' geary.db
- Check other application’s documentation for instructions on loading SQLite extensions at runtime.
How is “Geary” pronounced?
Geary is pronounced with a hard G. It should sound like the word “gear” followed by a long “e” sound.
For an audio example, visit this website.