Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Visit Stack Exchange
Stack Internal
Knowledge at work
Bring the best of human thought and AI automation together at your work.
Explore Stack Internal I have beenwas suffering from the same problem. The solution I preferchose is to disable auto-save-mode in mu4e-compose so that drafts do not accumulate.:
(add-hook 'mu4e-compose-mode-hook #'(lambda () (auto-save-mode -1))) Plus obviously, set mu4e-sent-messages-behavior to delete, as suggested by previous answers (especially in Gmail since GamilGmail takes care of sent messages):
(setq mu4e-sent-messages-behavior 'delete) I have been suffering from the same problem. The solution I prefer is to disable auto-save-mode in mu4e-compose so that drafts do not accumulate.
(add-hook 'mu4e-compose-mode-hook #'(lambda () (auto-save-mode -1))) Plus obviously, set mu4e-sent-messages-behavior to delete, as suggested by previous answers (especially in Gmail since Gamil takes care of sent messages)
(setq mu4e-sent-messages-behavior 'delete) I was suffering from the same problem. The solution I chose is to disable auto-save-mode in mu4e-compose so that drafts do not accumulate:
(add-hook 'mu4e-compose-mode-hook #'(lambda () (auto-save-mode -1))) Plus obviously, set mu4e-sent-messages-behavior to delete, as suggested by previous answers (especially in Gmail since Gmail takes care of sent messages):
(setq mu4e-sent-messages-behavior 'delete) I have been suffering from the same problem. The solution I prefer is to disable auto-save-mode in mu4e-compose so that drafts do not accumulate.
(add-hook 'mu4e-compose-mode-hook #'(lambda () (auto-save-mode -1))) Plus obviously, set mu4e-sent-messages-behavior to 'deletedelete, as suggested by previous answers (especially in Gmail since Gamil takes care of sent messages)
(setq mu4e-sent-messages-behavior 'delete) I have been suffering from the same problem. The solution I prefer is to disable auto-save-mode in mu4e-compose so that drafts do not accumulate.
(add-hook 'mu4e-compose-mode-hook #'(lambda () (auto-save-mode -1))) Plus obviously, set mu4e-sent-messages-behavior to 'delete, as suggested by previous answers (especially in Gmail since Gamil takes care of sent messages)
(setq mu4e-sent-messages-behavior 'delete) I have been suffering from the same problem. The solution I prefer is to disable auto-save-mode in mu4e-compose so that drafts do not accumulate.
(add-hook 'mu4e-compose-mode-hook #'(lambda () (auto-save-mode -1))) Plus obviously, set mu4e-sent-messages-behavior to delete, as suggested by previous answers (especially in Gmail since Gamil takes care of sent messages)
(setq mu4e-sent-messages-behavior 'delete) I have been suffering from the same problem. The solution I prefer is to disable auto-save-mode in mu4e-compose so that drafts do not accumulate.
(add-hook 'mu4e-compose-mode-hook #'(lambda () (auto-save-mode -1))) Plus obviously, set mu4e-sent-messages-behavior to 'delete, as suggested by previous answers (especially in Gmail since Gamil takes care of sent messages)
(setq mu4e-sent-messages-behavior 'delete)