# WP Mail SMTP + Mailhog **URL:** \ **Category:** WordPress Questions\ **Tags:** mailhog\ **Created:** [April 24, 2021, 5:55pm UTC](https://community.localwp.com/t/wp-mail-smtp-mailhog/25346 "2021-04-24T17:55:47Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![Nick-B](https://sea1.discourse-cdn.com/flex019/user_avatar/community.localwp.com/nick-b/32/16140_2.png) [@Nick-B](https://community.localwp.com/u/Nick-B)\ **Post date:** [September 16, 2023, 2:57pm UTC](https://community.localwp.com/t/wp-mail-smtp-mailhog/25346/3 "2023-09-16T14:57:14Z")
The issue isn’t really so much a Local one as it is the way their plugin overrides WordPress functions. We always try and go above and beyond, but there is a limit to what we can solve for within Local. As Ben mentions in a thread below, “I’d reach out to their support and see if there are any settings or recommended workflows for using their plugin and working on a site that isn’t in production. You can’t be the only person that wants to use their plugin but also wants to do development on a site in a non-production environment.” > [@How to Use Local Without Sending Emails via SMTP](https://community.localwp.com/t/how-to-use-local-without-sending-emails-via-smtp/25022/2): > > I think the terminology that the “WP Mail SMTP” plugin is using on their plugin page makes this topic a bit confusing. Plain SMTP is just an [internet protocol](https://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol) and is the default way that WordPress (and most machines really) uses to send email. If the WordPress site is using “plain smtp” to deliver email, then Local will capture all of those emails and you don’t have to worry about anything. But reading through the description of the [WP Mail SMTP](https://wordpress.org/plugins/wp-mail-smtp/) plugin definitely muddies these waters: WP Mai… --- _[View the full topic](https://community.localwp.com/t/wp-mail-smtp-mailhog/25346)._