# MailHog settings?

**URL:** <https://community.kinsta.com/t/mailhog-settings/4397>\
**Category:** Questions\
**Created:** [November 15, 2024, 7:55pm UTC](https://community.kinsta.com/t/mailhog-settings/4397 "2024-11-15T19:55:39Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mediaryte](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/mediaryte/32/3615_2.png) [@mediaryte](https://community.kinsta.com/u/mediaryte)\
**Post date:** [November 15, 2024, 7:55pm UTC](https://community.kinsta.com/t/mailhog-settings/4397/1 "2024-11-15T19:55:39Z")

</div>

Hello, I could not find any information on this subject, so I am starting this topic. I have been using DevKinsta successfully for the last couple of years on a daily basis. There have been no issues for quite a while, but for the last several months I have been required to force stop the MailHog process from running on my workstation when working in any environment. Unless I stop MailHog, it will proceed to grow and use all CPU cores/threads and RAM (12 core CPU, 64GB RAM, Ubuntu 24.04) on the machine, until the OS crashes and the machine needs to be restarted.

It is only a minor inconvenience, but it has become so persistent, I thought I’d share the issue here in hopes of finding a possible solution. I cannot find any documentation for managing MailHog, but it would be nice to have some control. Even if MailHog ran within the Docker containers, instead of externally, I could limit the resources available to the container and just let it run.

---

<div class="post-metadata">

**Author:** ![ShawnC](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/shawnc/32/880_2.png) [@ShawnC](https://community.kinsta.com/u/ShawnC)\
**Post date:** [November 16, 2024, 6:15pm UTC](https://community.kinsta.com/t/mailhog-settings/4397/3 "2024-11-16T18:15:25Z")

</div>

Howdy @mediaryte 👋,

I see this is your first time posting friend. Welcome to the community. We appreciate you using DevKinsta.

You mentioned…

> Even if MailHog ran within the Docker containers, instead of externally, I could limit the resources available to the container and just let it run.

As far as I know, unless this was configured externally somehow, MailHog is deployed from DevKinsta:

> **[How to Use MailHog to Test Emails Locally (Step-by-Step Guide)](https://kinsta.com/blog/mailhog/#devkinsta-and-mailhog-hasslefree-local-email-testing)**
>
> Learn how to use MailHog to test emails locally in this detailed step-by-step guide. Use DevKinsta to get started with MailHog right away!

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/0/0ee2b34f4aba13ecf49ed381ef5940a4e77db5d0.jpeg)

Also, you mentioned documentation. Please see the link below re: DevKinsta + MailHog commands:

> **[Site Management - Email Inbox - Kinsta® Docs](https://kinsta.com/docs/devkinsta/devkinsta-site-management/email-inbox/#manipulate-e-mail)**
>
> With the email inbox feature you have a separate inbox for every site. Find out how you can make use of this feature with DevKinsta.

 ![image](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/2X/5/596bc5516c26a94de5811bd8e78b0b0a1be6aa0d.png)

If the above link doesn’t cover what you’re looking for, please let us know which version of DevKinsta you’re currently using.

kindly,  
Shawn C.