starred/mailpit

Fork 0

mirror of https://github.com/axllent/mailpit.git synced 2026-04-26 00:35:51 +03:00

[GH-ISSUE #129] Improve Documentation to show how to send an HTML format file as an email #85

New issue

Closed

opened 2026-03-15 12:28:29 +03:00 by kerem · 6 comments

kerem commented

2026-03-15 12:28:29 +03:00

Owner

Originally created by @maza256 on GitHub (Jun 24, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/129

The documentation currently only shows how to send a plain text email. It would be wonderful if it could be used to send a fully formatted HTML file.

Originally created by @maza256 on GitHub (Jun 24, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/129 The documentation currently only shows how to send a plain text email. It would be wonderful if it could be used to send a fully formatted HTML file.

kerem closed this issue

2026-03-15 12:28:34 +03:00

kerem commented

2026-03-15 12:28:40 +03:00

Author

Owner

@axllent commented on GitHub (Jun 25, 2023):

The example in the documentation is purely intended to briefly test whether sendmail & Mailpit is working. Fully formatted HTML emails are typically not sent from the commandline, but rather send via applications using (for example) PHP, Ruby, Java, Go, etc which often then use sendmail to relay the message. This falls completely outside of the scope of Mailpit and/or the documentation.

If you do specifically wish so send an HTML email via the commandline, a simple Google search returns the following example:

echo "From: me@xyz.com
To: them@xyz.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary='PAA08673.1018277622/server.xyz.com'
Subject: Test HTML e-mail.

This is a MIME-encapsulated message

--PAA08673.1018277622/server.xyz.com
Content-Type: text/html

<html> 
<head>
<title>HTML E-mail</title>
</head>
<body>
<a href='http://www.google.com'>Click Here</a>
</body>
</html>
--PAA08673.1018277622/server.xyz.com
" | sendmail -t

@axllent commented on GitHub (Jun 25, 2023): The example in the documentation is purely intended to briefly test whether sendmail & Mailpit is working. Fully formatted HTML emails are typically not sent from the commandline, but rather send via applications using (for example) PHP, Ruby, Java, Go, etc which often then use sendmail to relay the message. This falls completely outside of the scope of Mailpit and/or the documentation. If you do specifically wish so send an HTML email via the commandline, a simple Google search returns the following example: ```shell echo "From: me@xyz.com To: them@xyz.com MIME-Version: 1.0 Content-Type: multipart/alternative; boundary='PAA08673.1018277622/server.xyz.com' Subject: Test HTML e-mail. This is a MIME-encapsulated message --PAA08673.1018277622/server.xyz.com Content-Type: text/html <html> <head> <title>HTML E-mail</title> </head> <body> <a href='http://www.google.com'>Click Here</a> </body> </html> --PAA08673.1018277622/server.xyz.com " | sendmail -t ```

kerem commented

2026-03-15 12:28:45 +03:00

Author

Owner

@ilhamsyahids commented on GitHub (Mar 22, 2025):

Hello @axllent

I'm trying to send email with multipart/alternative like as you do, however it appear as Text in web ui and not showing anything, I use latest axllent/mailpit:v1.23 and with only config MP_SMTP_AUTH_ACCEPT_ANY, MP_SMTP_AUTH_ALLOW_INSECURE. Can you help me for this?

Thanks

@ilhamsyahids commented on GitHub (Mar 22, 2025): Hello @axllent I'm trying to send email with `multipart/alternative` like as you do, however it appear as Text in web ui and not showing anything, I use latest `axllent/mailpit:v1.23` and with only config `MP_SMTP_AUTH_ACCEPT_ANY`, `MP_SMTP_AUTH_ALLOW_INSECURE`. Can you help me for this? Thanks <img width="408" alt="Image" src="https://github.com/user-attachments/assets/130610e1-8cef-4d2d-bcaa-370430f96dd6" />

kerem commented

2026-03-15 12:28:50 +03:00

Author

Owner

@axllent commented on GitHub (Mar 22, 2025):

@ilhamsyahids That would be because that example does not contain a text part. Try something like this:

echo "From: Example Company <news@example.com>
To: Joe User <joe.u@example.net>
Date: Sat, 21 May 2011 17:40:11 +0300
Subject: Multipart message example
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=asdfghjkl

--asdfghjkl
Content-Type: text/plain; charset=utf-8

This is the text part.

--asdfghjkl
Content-Type: text/html; charset=utf-8

<body>
This is the <b>HTML</b> part.
</body>

--asdfghjkl--
" | sendmail -t

@axllent commented on GitHub (Mar 22, 2025): @ilhamsyahids That would be because that example does not contain a text part. Try something like this: ```shell echo "From: Example Company <news@example.com> To: Joe User <joe.u@example.net> Date: Sat, 21 May 2011 17:40:11 +0300 Subject: Multipart message example MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=asdfghjkl --asdfghjkl Content-Type: text/plain; charset=utf-8 This is the text part. --asdfghjkl Content-Type: text/html; charset=utf-8 <body> This is the <b>HTML</b> part. </body> --asdfghjkl-- " | sendmail -t ```

kerem commented

2026-03-15 12:28:55 +03:00

Author

Owner

@ilhamsyahids commented on GitHub (Mar 22, 2025):

I see, I know the issue was. Apparently, mailpit cannot detect it html and text part if the the boundary has <>, please see the image below:

echo "From: Example Company <news@example.com>
To: Joe User <joe.u@example.net>
Date: Sat, 21 May 2011 17:40:11 +0300
Subject: Multipart message example
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=MIME_boundary_<asdfghjkl@example.net>

--MIME_boundary_<asdfghjkl@example.net>
Content-Type: text/plain; charset=utf-8

This is the text part.

--MIME_boundary_<asdfghjkl@example.net>
Content-Type: text/html; charset=utf-8

<body>
This is the <b>HTML</b> part.
</body>

--MIME_boundary_<asdfghjkl@example.net>--
" | mailpit sendmail -t

I also tried when its not contain the prefix (boundary=<asdfghjkl@example.net>), the result was email not appear in the mailpit.

I confirmed in gmail, both are works:

Can you confirm on your end? @axllent

@ilhamsyahids commented on GitHub (Mar 22, 2025): I see, I know the issue was. Apparently, mailpit cannot detect it html and text part if the the boundary has `<>`, please see the image below: <img width="617" alt="Image" src="https://github.com/user-attachments/assets/1fdea204-1b7f-42e4-aee2-1837b385f274" /> ```sh echo "From: Example Company <news@example.com> To: Joe User <joe.u@example.net> Date: Sat, 21 May 2011 17:40:11 +0300 Subject: Multipart message example MIME-Version: 1.0 Content-Type: multipart/alternative; boundary=MIME_boundary_<asdfghjkl@example.net> --MIME_boundary_<asdfghjkl@example.net> Content-Type: text/plain; charset=utf-8 This is the text part. --MIME_boundary_<asdfghjkl@example.net> Content-Type: text/html; charset=utf-8 <body> This is the <b>HTML</b> part. </body> --MIME_boundary_<asdfghjkl@example.net>-- " | mailpit sendmail -t ``` I also tried when its not contain the prefix (`boundary=<asdfghjkl@example.net>`), the result was email not appear in the mailpit. I confirmed in gmail, both are works: <img width="528" alt="Image" src="https://github.com/user-attachments/assets/a4c3a95e-ea4d-4fc2-bfba-3812dd12ce94" /> <img width="697" alt="Image" src="https://github.com/user-attachments/assets/420d0970-b3c8-402d-8eca-2355b9a75fac" /> Can you confirm on your end? @axllent

kerem commented

2026-03-15 12:29:00 +03:00

Author

Owner

@axllent commented on GitHub (Mar 22, 2025):

@ilhamsyahids I would suggest that it is because you're using invalid characters. I don't think< & > are legally allowed. See https://stackoverflow.com/a/147467

@axllent commented on GitHub (Mar 22, 2025): @ilhamsyahids I would suggest that it is because you're using invalid characters. I don't think`<` & `>` are legally allowed. See https://stackoverflow.com/a/147467

kerem commented

2026-03-15 12:29:05 +03:00

Author

Owner

@ilhamsyahids commented on GitHub (Mar 25, 2025):

Thats make sense, thanks for your confirmation @axllent

@ilhamsyahids commented on GitHub (Mar 25, 2025): Thats make sense, thanks for your confirmation @axllent

kerem referenced this issue

2026-03-15 14:18:49 +03:00

[PR #85] [MERGED] config: update listen regex to allow IPv6 addresses #433