Trying hard to enable replies by email using the mail-receiver container. I consistently get errors: NOQUEUE: reject: RCPT from ... 454 4.7.1 : Relay access denied Why is this? How can I get into the mail-receiver container and examine the postfix config and debug it? I have disabled the postfix server on the system on which this is running, because of clash with port 25. Is that wrong? I am reasonably sure DNS MX records are right, and this happens from any server sending mail inbound, I am using Amazon SES for outbound in the app container and that works fine. I am a Discourse newbie and I dont know how to debug the ecosystem. I am an expert in postfix, but I don’t know how to configure it in this containerized universe.

I don’t agree with this at all, the benefit of the mail-receiver is that emails are pushed via the API, rather than polled. There’s a significant difference in the time taken for email to arrive in Discourse using the mail-receiver (minutes versus seconds). There’s also a huge difference in simplicity in configuration, mail-receiver requires three lines of a yml file be updated, the postfix OOBE requires… more. [image] Andro: NOQUEUE: reject: RCPT from … 454 4.7.1 : Relay access denied That error implies the mail domains don’t match. As you’re obfuscating parts of the message we can’t easily troubleshoot this for you.

[image] Andro: NOQUEUE: reject: RCPT from … 454 4.7.1 : Relay access denied If you’re getting any mail delivered as you expect, then this implies that someone is trying to use your mail server to deliver mail to some other domain. If, for example, someone pointed their MX record to your IP address. Or, and I’ve never heard of this :wink: , someone was trying to nefariously have your mail server deliver unwanted mail. Are all of these errors from the same IP? Can you see in the logs what domain they the errant messages are intended for? The easiest thing to do is to ignore it.

I had this issue on a previously working mail-receiver which I’d made some changes to. I had thought I’d rebuild the container but clearly something hadn’t gone right as I got multiple ’ Relay access denied’ errors for all recipients. DNS was correctly configured. In the end a good old git pull and launcher rebuild mail-receiver fixed it. Just posting this in case it works for anyone else.

Have this same error with mail-receiver reports: Relay access denied (in reply to RCPT TO command). Mail receiving isn’t working for new install but have got this to work before. Believe all settings are correct but might have missed something.

This usually means that the mail is being delivered to a domain that’s not the one the receiver is configured to accept.

I have it set for the same sub-domain as the discourse site. For the MX record value is “subdomain.domain,” and host is supposed to just be “subdomain” or @?

Does anyone know what causes the “Relay access denied” error? [image] Mail-receiver relay access denied Self-hosting Have this same error with mail-receiver reports: Relay access denied (in reply to RCPT TO command). Mail receiving isn’t working for new install but have got this to work before. Believe all settings are correct but might have missed something.

It happens when the recipient domain doesn’t match with the domain configured in the mail-receiver.yml.

[image] Architect: I have it set for the same sub-domain as the discourse site. Is that the address you’re sending the mail to?

Same address, is working now after rebuild of mail-receiver. Believe had rebuilt that before but wasn’t working, good that works now.

Mail-receiver relay access denied

Product Support Self-hosting

Ethsim2 (Ethan ) January 26, 2025, 6:19pm 19

better solution might be to only allow the relevant IP address though?

Topic		Replies	Views
Mail-receiver won’t deliver mail to Discourse Self-hosting mail-receiver	16	706	January 26, 2023
Getting relay access denied errors in email replies Self-hosting mail-receiver	2	933	July 26, 2020
Mail-receiver and/or Discourse are not posting email replies Self-hosting mail-receiver	6	1063	September 28, 2020
Incoming e-mail not received Self-hosting	20	2618	February 11, 2022
Email receive issue Bug mail-receiver , fixed	29	1329	April 13, 2026

Mail-receiver relay access denied

Related topics