(Use https://dev.mutt.org/ for encrypted access to this site.
Brendan Cully has pgp signed http://www.mutt.org/brendan.key the self-signed SSL certificate. See Attachments at the bottom of this page)
Mutt developer resources
Bug tracking system
This trac exists primarily for bug tracking: see report:3
- You can register immediately using the link on the menu bar.
- Note: a valid email address is required (the registration page incorrectly states it is optional).
- A confirmation link will be emailed to you. Sorry about that, we'd turn it off if the spammers would let us.
- You must be logged in to add new tickets, or ticket comments, as an anti-spam measure.
- Note: bug entries are forwarded to the mutt developer's list, making the email address you register with public.
For all new ticket reports please include:
- a short meaningful summary
- a procedure to reproduce the problem
- careful selections of the priority, component and type property fields
- the keyword "patch" if you have a proposed solution
See DebugTips for diagnostic methods to speed resolution of the bug.
Browse the manual for the development version, updated nightly.
hg clone http://dev.mutt.org/hg/mutt
This will default to the default branch, where mainline development happens. Afterwards, hg pull -u should keep you up to date.
There is also the stable branch where the latest stable version of mutt is tracked. Bugfixes are committed into stable and then merged back into default, while new features go into default.
Download a nightly snapshot of the mutt distribution here
The mutt source contains some developer resources in the contrib/ subdirectory, namely:
When preparing/maintaining 3rd patches, see:
This lists topics that we're currently collecting ideas for:
- NewMailHandling overhaul
- UnifyMailboxInterface (more issues than only new mail handling)
- MailboxDriverCleanup and MAPI support
An overview of mailing lists (for devs, users and others) can be found at http://www.mutt.org/mail-lists.html.