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 post…

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 simplic…

[imagen] 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 I…

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…

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? [imagen] Mail-receiver relay access denied Installation Have this same error with mail-receiver reports: Relay access denied (in reply to RCPT TO command). Mail receiving isn’t working for new insta…

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

[imagen] 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.

Acceso denegado para reenvío de Mail-receiver

Soporte Instalación

Jagster (Jakke Flemming) 26 Enero, 2025 18:28 21

Aquí está la situación cuando solo 22 estaban abiertos por ufw y mi foro todavía funcionaba perfectamente.

Tema		Respuestas	Vistas
Mail-receiver won’t deliver mail to Discourse Self-hosting mail-receiver	16	399	26 Enero 2023
Getting relay access denied errors in email replies Self-hosting mail-receiver	3	859	25 Agosto 2020
Mail-receiver and/or Discourse are not posting email replies Self-hosting mail-receiver	7	948	28 Octubre 2020
Incoming e-mail not received Self-hosting	20	2213	11 Febrero 2022
Email receive issue Bug mail-receiver , fixed	30	440	13 Abril 2026

Acceso denegado para reenvío de Mail-receiver

Temas relacionados