# Reply-by email pop3 auth failure

**URL:** <https://meta.discourse.org/t/reply-by-email-pop3-auth-failure/297873>\
**Category:** Product Support\
**Tags:** email\
**Created:** [March 4, 2024, 8:34pm UTC](https://meta.discourse.org/t/reply-by-email-pop3-auth-failure/297873 "2024-03-04T20:34:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![sadie](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sadie/32/367253_2.png) [@sadie](https://meta.discourse.org/u/sadie)\
**Post date:** [March 4, 2024, 9:40pm UTC](https://meta.discourse.org/t/reply-by-email-pop3-auth-failure/297873/3 "2024-03-04T21:40:57Z")

</div>

Jay, I’ve also tried that, perhaps my attempt to make an MX record is inaccurate .. I get and OK config at Mxtoolboxdotcom: (no PTR record, no support for TLS, otherwise all green)

We have to have a DNS record that directs our TLD email to our outgoing mail server, that seems to override my attempt to send mail to the server / subdomain, viz: sending test email to nobody@discourse.TLD,domain shows up in the mail receiver logs as:

reject: RCPT from outgoinghost.otherdomain 454 4.7.1 \<nobody@TLD,domain\>: Relay access denied; from=[ME@otherdomain](mailto:ME@otherdomain) to=[nobody@TLD.domain](mailto:nobody@TLD.domain)

I have this MX record:

MX Record HOST discourse.TLD,domain VALUE discourse.TLD,domain. PRIORITY 10 TTL 1 min

---

_[View the full topic](https://meta.discourse.org/t/reply-by-email-pop3-auth-failure/297873)._
