The discussion revolves around issues with the mail-receiver feature in Discourse. eextra reports multiple problems: inability to view or reply to emails, lack of bounce logs for non-existent addresses, and unexpected auto-replies when sending to invalid addresses. itsbhanusharma clarifies that emails not associated with a topic can’t be viewed or replied to, and explains how to check mail-receiver logs via SSH. Bounce handling requires external ESP configuration. eextra asks if using a private mailbox for email reception conflicts with reply-by-email functionality. itsbhanusharma confirms that mail-receiver requires dedicated MX records, making it incompatible with shared mailboxes. Stephen emphasizes using a dedicated subdomain for Discourse to enable both email reception and regular email use. eextra seeks confirmation on redirecting the main domain to the forum subdomain, which is implied as a viable setup.
We’re sorry, but your email message to [“adsadsadasdsadasdasdasdasdsd@mydomain.com ”] (titled test adsaas) didn’t work.
None of the destination email addresses are recognized, or the Message-ID header in the email has been modified. Please make sure that you are sending to the correct email address provided by staff.
Is that how it’s supposed to work? Thank you for all your helpful entries !
Thanks.
I have one more question for you.
If I set the mx records for receiving a message (rejected/bounced) to my own email (which means I won’t be able to see them in the admin panel) then will work correctly answering by email / writing new topics by email?
So I have to choose:
or this useful function of answering / writing via email
or the possibility of conveniently receiving and replying to e-mails to/from a private mailbox?
If so, it is best if from the level of discourse/mail-receiver to possibility immediately reply (such a small mail client) because we have to choose either this or that
For reply-by-email, If you’re using POP3 Polling then you can technically use the same mailbox for other purposes but it is not recommended on the other hand, if You’re using mail-receiver, you need the MX records to be strictly dedicated to the mail-receiver and can not use that (sub)domain for sending/receiving emails
E.g. If I have example.com and I use mail@example.com for emails, my discourse is set up on discourse.example.com and mail-receiver is on the same sub domain then I can not use mail@discourse.example.com for sending regular emails but mail@example.com can be pointed to another MX.
Not in it’s current state, But I think it may be possible through a custom plugin.
If you absolutely need this and have a Good budget in mind then Marketplace is a good place to post your requirements and someone may be able to make it for You.
