Mutt/Neomutt Maildir not saving sent email

Mutt and Neomutt fail to save sent messages when the maildir variable is misconfigured or conflicts with the record setting. The most common cause is that the client sends mail successfully but drops the copy because it cannot write to the specified directory, often due to incorrect path syntax, missing permissions, or a mismatch between the folder and record variables in the configuration file.

Understanding the Maildir Record Mechanism

To solve this issue, you must understand how Mutt handles the storage of sent items. By default, Mutt attempts to save a copy of every outgoing message to a designated folder. This behavior is controlled by two primary variables: folder, which defines the base directory for your mailbox, and record, which specifies where sent mail should be stored. If these are not aligned correctly, Mutt may silently fail to save the email, leaving you with no trace of what you sent. In a standard Maildir setup, the folder variable typically points to the root of your Maildir structure (e.g., ~/Maildir). The record variable should then point to the specific subdirectory within that structure where sent messages belong. For Maildir, this is almost always the .Sent directory inside your main Maildir path. If record is left undefined, Mutt might attempt to use a default value that does not match your current folder configuration, leading to a silent failure.

Verifying Your Configuration Variables

The first step in troubleshooting is to inspect your muttrc or neomuttrc file. Look for lines starting with set folder= and set record=. A correct configuration for a user whose home directory is /home/user would look like this:

set folder = "~/Maildir"
set record = "+.Sent"

Notice the use of the plus sign (+) before .Sent. In Mutt syntax, the plus sign indicates that the following string is relative to the folder variable. Without it, Mutt interprets .Sent as an absolute path from the root of your filesystem, which will likely result in permission denied errors or non-existent directories. If you see set record = ".Sent" without the plus sign, this is a primary suspect for why your emails are disappearing after sending.

Checking Directory Permissions and Ownership

Even if your configuration syntax is perfect, Mutt will not save sent emails if the target directory lacks the necessary write permissions. Maildir formats rely on creating individual files for each message in the .Sent/new subdirectory. You must ensure that the user running Mutt has full read, write, and execute access to the ~/Maildir/.Sent directory and its subdirectories. You can verify permissions using the ls -ld command on the terminal:

ls -ld ~/Maildir/.Sent
ls -ld ~/Maildir/.Sent/new

If the output shows that the owner is not your current user, or if the write bit (w) is missing for the owner, Mutt will fail to create the new message files. To fix this, you can recursively change the ownership and permissions:

chown -R $USER:$USER ~/Maildir
chmod -R u+rwX ~/Maildir

Be cautious when applying recursive changes to ensure you do not inadvertently alter permissions on other sensitive files in your home directory. The X flag ensures that only directories and executable files get execute permissions, while regular files get read and write permissions.

Distinguishing Between Send Errors and Save Failures

It is crucial to determine whether the email is actually being sent or if it is failing at the storage stage. If you receive an error message immediately after pressing Enter, such as "Could not send the message," the issue lies with your SMTP server configuration, not the local saving mechanism. However, if the email appears to send normally but simply vanishes from view, the problem is almost certainly the record path or permissions. You can test this by configuring Mutt to log its actions. Add the following line to your configuration file temporarily:

set debug_file = "/tmp/mutt_debug.log"

After sending a test email, check the log file for any warnings related to writing to the record folder. Look for lines indicating "Permission denied" or "No such file or directory." This diagnostic step provides concrete evidence of where the process breaks down, allowing you to apply the correct fix rather than guessing. For users who need to manage their email infrastructure remotely, understanding local client configurations is just as important as network connectivity. If you are setting up a complex environment, you might also find it helpful to review how to connect a mail server securely over a private network, as detailed in our guide on connecting mail servers with Tailscale.

Handling Alternative Storage Formats

While Maildir is the modern standard, some legacy systems still use mbox format. If you have accidentally switched your folder variable to an mbox-style path while keeping record configured for Maildir, conflicts will arise. Conversely, if you are migrating from mbox to Maildir, you must ensure that all existing sent messages are converted to the Maildir structure before enabling the save feature. If you are strictly using Maildir, avoid mixing mbox-specific commands like append with Maildir paths. Ensure that your IMAP sync tools (if used) are aware of the .Sent folder location. Some IMAP clients assume sent mail is in a top-level Sent folder rather than a hidden .Sent folder. If you use a webmail interface alongside Mutt, verify that both clients are pointing to the same physical directory to prevent synchronization conflicts.

Resetting the Record Variable Temporarily

If you are unable to resolve the issue immediately, you can disable the automatic saving of sent mail to prevent further confusion. Add the following line to your configuration:

set record = ""

This tells Mutt not to save copies locally. While this solves the immediate error, it means you will lose a local archive of your sent correspondence. Use this only as a temporary measure while you debug the underlying path or permission issues. Once you have corrected the record path and verified permissions, remove this line to restore normal functionality. Remember that Mutt is highly configurable, and small typos in path definitions can lead to significant operational gaps. Always test your configuration changes with a single test email before relying on the system for critical communication.

Frequently Asked Questions

Why does my sent email appear in the IMAP server but not locally?

This indicates that the SMTP transmission was successful, but the local record variable is misconfigured. Check that your record path uses the plus sign prefix to reference the local folder directory correctly.

Can I save sent emails to a different folder than .Sent?

Yes, you can set record to any valid Maildir subdirectory, such as "+Archive/Sent". Just ensure that the directory exists and that you have write permissions to it before sending any mail.

What happens if the .Sent directory does not exist?

Mutt will fail to save the email and may print a warning to the screen or log file. It does not automatically create the directory for you. You must manually create ~/Maildir/.Sent and its new subdirectory.

Does Neomutt handle Maildir differently than Mutt?

No, Neomutt is a fork of Mutt and shares the same core configuration syntax for Maildir handling. The folder and record variables function identically in both clients.

How do I fix permission errors without changing global ownership?

You can use chmod to add write permissions specifically for your user on the .Sent directory. Run chmod u+w ~/Maildir/.Sent to grant write access to the owner without altering group or other permissions.