Configuring both direct delivery email and a forwarding rule

Product Support
3

@pfaffman Wowza! So you’re saying I can have my cake and eat it too :stuck_out_tongue_winking_eye: ! This sounds very encouraging, as I might be set up close to correct already…

  • My outbound email subdomain is simply mg and works fine, i.e. postmaster@**mg**.example.com (less the stars) on port 2525 per your suggestion. Works dandy. I must have given Discourse whatever it needs (webhooks?) as I see the bounces with this configuration.
  • The one-and-only MX record I have in my DNS settings points mail.example.com to example.com. I have absolutely no idea what it does, if anything at all. Emails do deliver, and bounces are apparent from within Discourse, and direct-reply is working with this configuration though. Yeehaw!
  • My containers/mail-receiver.yml shows MAIL_DOMAIN as mg.mydomain.com —which is same as mailgun (outgoing).

Perhaps that MX record is useless and/or should be renamed, because I haven’t a clue where I defined mail.mydomain.com beyond that MX record.
Where this gets a little hairy, is that I think I need to revert my DNS settings back to the registrar (from DigitalOcean) in order to regain use of the registrar’s email auto-forwarding which is free at NameCheap but only works if the DNS settings are there as well.

My workflow will be to move every DNS entry back to NameCheap exactly as they appear in DO right now, then create my email address i.e. admin@mydomain.com to forward to a gmail address that I just now created. In the end, “Straightforward direct-delivery incoming mail” can remain functional, and I gain an email inbox with the domain—without the need of establishing another subdomain—if I understand you right. Thanks again for helping me understand this stuff, Jay. Cheers!