aerc status
GitHub macOS CI status

aerc is an email client for your terminal.

This is a fork of the original aerc
by Drew DeVault.

A short demonstration can be found on

Join the IRC channel: #aerc on
for end-user support, and #aerc-dev
for development.


On its first run, aerc will copy the default config files to ~/.config/aerc
on Linux or ~/Library/Preferences/aerc on MacOS (or $XDG_CONFIG_HOME/aerc if set)
and show the account configuration wizard.

If you redirect stdout to a file, logging output will be written to that file:

$ aerc > log

For instructions and documentation: see man aerc and further specific man
pages on there.

Note that the example HTML filter (off by default), additionally needs w3m and
dante to be installed.


Binary Packages

Recent versions of aerc are available on:

And likely other platforms.

From Source

Install the dependencies:

Then compile aerc:

$ make

aerc optionally supports notmuch. To enable it, you need to have a recent
version of notmuch, including the header
files (notmuch.h). Then compile aerc with the necessary build tags:

$ GOFLAGS=-tags=notmuch make

To install aerc locally:

# make install

Contribution Quick Start

Anyone can contribute to aerc. First you need to clone the repository and build
the project:

$ git clone
$ cd aerc
$ make

Patch the code. Make some tests. Ensure that your code is properly formatted
with gofmt. Ensure that everything builds and works as expected. Ensure that
you did not break anything.

  • If applicable, update unit tests.
  • If adding a new feature, please consider adding new tests.
  • Do not forget to update the docs.

Once you are happy with your work, you can create a commit (or several
commits). Follow these general rules:

  • Limit the first line (title) of the commit message to 60 characters.
  • Use a short prefix for the commit title for readability with git log --oneline.
  • Use the body of the commit message to actually explain what your patch does
    and why it is useful.
  • Address only one issue/topic per commit.
  • If you are fixing a ticket, use appropriate
    commit trailers.
  • If you are fixing a regression introduced by another commit, add a Fixes:
    trailer with the commit id and its title.

There is a great reference for commit messages in the
Linux kernel documentation.

Before sending the patch, you should configure your local clone with sane

$ git config format.subjectPrefix "PATCH aerc"
$ git config "~rjarry/[email protected]"

And send the patch to the mailing list:

$ git send-email --annotate -1

Wait for feedback. Address comments and amend changes to your original commit.
Then you should send a v2:

$ git send-email --in-reply-to=$first_message_id --annotate -v2 -1

Once the maintainer is happy with your patch, they will apply it and push it.


Send patches and questions to
~rjarry/[email protected].

Instructions for preparing a patch are available at

Subscribe to release announcements on
~rjarry/[email protected]

Submit bug reports and feature requests on


View Github