[GH-ISSUE #285] log in webgui #191

New issue

Closed

opened 2026-03-15 13:07:01 +03:00 by kerem · 2 comments

kerem commented

2026-03-15 13:07:01 +03:00

Owner

Originally created by @q16marvin on GitHub (Apr 25, 2024).
Original GitHub issue: https://github.com/axllent/mailpit/issues/285

Hi again,

i think it would be realy helpful to have the full log visible anywhere in gui, because for me its intresting "who" tries to connect to the smpt:

mailpit | time="2024/04/25 12:39:38" level=warning msg="[smtpd] deny LOGIN login:"test" from:113.239.202.119"

but this currently i only see in the shell :)

What do you think about it?

Originally created by @q16marvin on GitHub (Apr 25, 2024). Original GitHub issue: https://github.com/axllent/mailpit/issues/285 Hi again, i think it would be realy helpful to have the full log visible anywhere in gui, because for me its intresting "who" tries to connect to the smpt: mailpit | time="2024/04/25 12:39:38" level=warning msg="[smtpd] deny LOGIN login:\"test\" from:113.239.202.119" but this currently i only see in the shell :) What do you think about it?

kerem closed this issue

2026-03-15 13:07:06 +03:00

kerem commented

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

Author

Owner

@axllent commented on GitHub (Apr 25, 2024):

Whilst I can understand you for wanting an easy-to-see overview of logs in the web UI, there are some reasons this is also a bad idea. Mailpit is used in many different environments, and exposing the log files via the API (what the web UI uses) can be seen as a security flaw as it exposes those logs to the network too (and more than just who failed to connect to SMTP, but if you set to verbose you'll see a lot more and maybe understand what I mean).

Mailpit is not a monitoring system, those logs (via the shell) are meant as an audit-log to try debug Mailpit issues. Failed SMTP attempts should be handled/reported properly via the application trying to send, not the application receiving :-)

Does this make sense to you?

@axllent commented on GitHub (Apr 25, 2024): Whilst I can understand you for wanting an easy-to-see overview of logs in the web UI, there are some reasons this is also a bad idea. Mailpit is used in many different environments, and exposing the log files via the API (what the web UI uses) can be seen as a security flaw as it exposes those logs to the network too (and more than just who failed to connect to SMTP, but if you set to verbose you'll see a lot more and maybe understand what I mean). Mailpit is not a monitoring system, those logs (via the shell) are meant as an audit-log to try debug Mailpit issues. Failed SMTP attempts should be handled/reported properly via the application trying to send, not the application receiving :-) Does this make sense to you?

kerem commented

2026-03-15 13:07:18 +03:00

Author

Owner

@q16marvin commented on GitHub (Apr 26, 2024):

yes you are right, so forgot please my idea :)

@q16marvin commented on GitHub (Apr 26, 2024): yes you are right, so forgot please my idea :)