mirror of
https://github.com/axllent/mailpit.git
synced 2026-04-26 00:35:51 +03:00
[GH-ISSUE #648] Support 8BITMIME #403
Labels
No labels
awaiting feedback
bug
docker
documentation
enhancement
github_actions
invalid
pull-request
question
stale
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/mailpit#403
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @schutm on GitHub (Feb 23, 2026).
Original GitHub issue: https://github.com/axllent/mailpit/issues/648
According to https://www.rfc-editor.org/rfc/rfc6531#section-3.1 mailpit should support (announce the support of) 8BITMIME, because it announces SMTPUTF8. Is support for 8bit mime being considered (maybe it only needs to be announced?)
@axllent commented on GitHub (Feb 23, 2026):
Thanks @schutm. I strongly suspect you are correct here, however I am interested in what drew you to this conclusion?
@schutm commented on GitHub (Feb 23, 2026):
I'm implementing a mua and just reading the specs (which are a real mess) drew me to this conclusion. In addition checking the code/responses of several MTA's (postfix, exim, outlook.com and gmail), sendmail might differ.
@axllent commented on GitHub (Feb 23, 2026):
I admittedly do not understand much about 8BITMIME, however Clause (AI) agreed with your conclusion and suggested I simply add it in the list of existing EHLO responses. Are you using the Docker version of Mailpit in your environment? If so, then I have fixed this already in the
axllent/mailpit:edgeDocker image (if you could please test and confirm).@schutm commented on GitHub (Feb 24, 2026):
I don't understand a lot of it as well ;) I'm using the binaries. But try to test it nevertheless in a few days.
@axllent commented on GitHub (Feb 25, 2026):
This has been released now in v1.29.2 - so you should be able to confirm with one of the prebuilt binaries. Thanks.
@schutm commented on GitHub (Feb 27, 2026):
I just checked, and can confirm it's there. Unfortunately I can't test the full functionality right now (and I'm not even sure I'm implementing it the right way ;))