starred/mailpit

Fork 0

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

[GH-ISSUE #146] Feature Request: Set HELO #98

New issue

Closed

opened 2026-03-15 12:32:31 +03:00 by kerem · 8 comments

kerem commented

2026-03-15 12:32:31 +03:00

Owner

Originally created by @kjake on GitHub (Jul 19, 2023).
Original GitHub issue: https://github.com/axllent/mailpit/issues/146

Within Docker, the HELO response seems locked into localhost, even though I've set a hostname when launching the container. Could you add an option for us to configure the HELO at runtime, or use the hostname automatically?

thanks!

Originally created by @kjake on GitHub (Jul 19, 2023). Original GitHub issue: https://github.com/axllent/mailpit/issues/146 Within Docker, the HELO response seems locked into localhost, even though I've set a hostname when launching the container. Could you add an option for us to configure the HELO at runtime, or use the hostname automatically? thanks!

kerem

2026-03-15 12:32:31 +03:00

closed this issue
added the
stale
label

kerem commented

2026-03-15 12:32:47 +03:00

Author

Owner

@axllent commented on GitHub (Jul 20, 2023):

Hi there. I'm confused because the HELO response isn't locked to "localhost", and it already uses the current hostname in the response, not that the response (beyond the 250) is mandatory.

telnet 192.168.7.2 1025
Trying 192.168.7.2...
Connected to 192.168.7.2.
Escape character is '^]'.
220 abf5fb0499d6 Mailpit ESMTP Service ready
HELO 192.168.7.2
250 abf5fb0499d6 greets 192.168.7.2

... where abf5fb0499d6 is the hostname of my docker container running Mailpit, and 192.168.7.2 is the IP of my docker server. It sounds to me that you are connecting to localhost so your client is sending a HELO localhost, and is thus receiving a ...greets localhost in the response.

What is it that you are trying to achieve exactly?

@axllent commented on GitHub (Jul 20, 2023): Hi there. I'm confused because the `HELO` response isn't locked to "localhost", and it already uses the current hostname in the response, not that the response (beyond the `250`) is mandatory. ``` telnet 192.168.7.2 1025 Trying 192.168.7.2... Connected to 192.168.7.2. Escape character is '^]'. 220 abf5fb0499d6 Mailpit ESMTP Service ready HELO 192.168.7.2 250 abf5fb0499d6 greets 192.168.7.2 ``` ... where `abf5fb0499d6` is the hostname of my docker container running Mailpit, and `192.168.7.2` is the IP of my docker server. It sounds to me that you are connecting to `localhost` so your client is sending a `HELO localhost`, and is thus receiving a `...greets localhost` in the response. What is it that you are trying to achieve exactly?

kerem commented

2026-03-15 12:32:52 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 10, 2023):

This issue is stale because it has been open for 21 days with no activity.

@github-actions[bot] commented on GitHub (Aug 10, 2023): This issue is stale because it has been open for 21 days with no activity.

kerem commented

2026-03-15 12:32:57 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 18, 2023):

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions[bot] commented on GitHub (Aug 18, 2023): This issue was closed because it has been inactive for 7 days since being marked as stale.

kerem commented

2026-03-15 12:33:02 +03:00

Author

Owner

@daqqad commented on GitHub (May 1, 2024):

It would actually be useful to be able to override HELO string @axllent

My specific use case is GMail's relay service which rejects any HELO string that isn't configured as one of the domains on the account.

I made a few simple changes to implement this via an extra variable in config file for relay and it is working in my environment.

Can I push a branch for you to check out the changes and hopefully approve?

@daqqad commented on GitHub (May 1, 2024): It would actually be useful to be able to override HELO string @axllent My specific use case is GMail's relay service which rejects any HELO string that isn't configured as one of the domains on the account. I made a few simple changes to implement this via an extra variable in config file for relay and it is working in my environment. Can I push a branch for you to check out the changes and hopefully approve?

kerem commented

2026-03-15 12:33:07 +03:00

Author

Owner

@axllent commented on GitHub (May 1, 2024):

@daqqad I'm not sure what impact your approach would have, so maybe best you sent a PR so I can see. Can't promise anything, but we can continue the discussion there. Please note that I'm currently very busy, so it may take a couple of days to review and get back to you, thanks.

@axllent commented on GitHub (May 1, 2024): @daqqad I'm not sure what impact your approach would have, so maybe best you sent a PR so I can see. Can't promise anything, but we can continue the discussion there. Please note that I'm currently very busy, so it may take a couple of days to review and get back to you, thanks.

kerem commented

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

Author

Owner

@petek commented on GitHub (Aug 22, 2025):

@daqqad @kjake Don't know if you still have this issue, and the fix has been committed to the project for the next release.

@petek commented on GitHub (Aug 22, 2025): @daqqad @kjake Don't know if you still have this issue, and the fix has been committed to the project for the next release.

kerem commented

2026-03-15 12:33:18 +03:00

Author

Owner

@kjake commented on GitHub (Aug 22, 2025):

Docker image with digest sha256:df042c2c685a3be6a35e11f9ca82c87941483c9d4c96e727713beea7e45179a is currently not responding with localhost, but my FQDN. I'm not sure when this changed, but thank you!

@kjake commented on GitHub (Aug 22, 2025): Docker image with digest `sha256:df042c2c685a3be6a35e11f9ca82c87941483c9d4c96e727713beea7e45179a` is currently not responding with localhost, but my FQDN. I'm not sure when this changed, but thank you!

kerem commented

2026-03-15 12:33:23 +03:00

Author

Owner

@daqqad commented on GitHub (Aug 22, 2025):

@daqqad @kjake Don't know if you still have this issue, and the fix has been committed to the project for the next release.

I totally missed this reply, but thank you.

@daqqad commented on GitHub (Aug 22, 2025): > [@daqqad](https://github.com/daqqad) [@kjake](https://github.com/kjake) Don't know if you still have this issue, and the fix has been committed to the project for the next release. I totally missed this reply, but thank you.

kerem referenced this issue

2026-03-15 14:19:05 +03:00

[PR #98] [CLOSED] Bump bootstrap-icons from 1.10.4 to 1.10.5 #440