Anyone having issues sending to comcast.net addresses using mailgun? <SOLVED>

Product Support Self-hosting
1

I switched to mailgun after mandrell went away as suggested in discourse. However, now all of my emails sent to comcast.net email addresses are failing with: “550 5.1.0 Invalid sender domain”. It works for every non comcast customer though.

This obviously isn’t an issue with discourse, but I was hoping someone might have some insight. I called comcast and they were completely useless and have opened a ticket with Rackspace. We will see what they say. In the meantime…

Thanks for any help!

2

I figured it out. I thought I would document it here in case anyone else needs help in the future.

The sender of the email was coming across at comcast as ‘xx@mg.mydomain.com’, which comcast was trying to verify.

I needed an additional MX record. I use Google Apps for normal emails, but also Mailgun. I had all the Google Apps MX records, but what I had to do was add an additional MX record with a subdomain of “mg” for mailgun, which I just pointed at google server. Here are my MX records, which seem to now be working:

MX Records
Mail Server	Preference	Subdomain	TTL	
aspmx.l.google.com	1		Default	
alt1.aspmx.l.google.com	5		Default	
alt2.aspmx.l.google.com	5		Default	
alt3.aspmx.l.google.com	10		Default	
alt4.aspmx.l.google.com	10		Default	
aspmx.l.google.com	20	mg	Default
3

야, 고마워 친구! 오늘 콕사트(Comcast) 사용자와 메일건(Mailgun)에서 같은 문제를 겪었어. 이제 MX 레코드를 어떻게 처리하는 게 최선인지 알아봐야겠다.

4

여기서 답변을 공유해 주셔서 감사의 말씀을 드리고 싶었습니다! 쉽게 해결할 수 있었습니다.