---

1.4 Becoming a mu4e user ¶

If mu4e sounds like something for you, give it a shot! We’re trying hard to make it as easy as possible to set up and use; and while you can use elisp in various places to augment mu4e, a lot of knowledge about programming or elisp shouldn’t be required. The idea is to provide sensible defaults, and allow for customization.

When you take mu4e into use, it’s a good idea to subscribe to the mu/mu4e mailing list.

Sometimes, you might encounter some unexpected behavior while using mu4e, or have some idea on how it could work better. To report this, you can use the bug-tracker. Please always include the following information:

• What did you expect or wish to happen? what actually happened? Please describe in detail what you saw; what did you expect to happen and what actually happened? Also, please try some related scenarios and whether the problem either always happens, or only sometimes. E.g., the issue might happen with only one particular type of message
• Provide some exact steps to reproduce? In particular, some minimal steps, starting from emacs -Q and with minimal configuration. If the problem is easily producible, it may be easily fixable as well; but if it’s some subtle interaction in a highly complex setup, we cannot do much.
• What version of mu4e and emacs were you using? What operating system? Always try with up-to-date versions. And please use the ’normal’ mu4e for reproducing your problem, not the “remix” version that some Emacs “distributions” use, such as “Doom Emacs”.
• Can you reproduce it with emacs -q and only loading mu4e?
• If the problem is related to some specific message, please include the raw message file (appropriately anonymized, of course)

In general, imagine you would be the person receiving the bug-report, and think about the information you would need to diagnose the problem.