1

Topic: could not having mx record cause undelivered mails?

==== Required information ====
- iRedMail version (check /etc/iredmail-release):  0.9
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): mysql
- Web server (Apache or Nginx): nginx
- Linux/BSD distribution name and version: centos6
- Related log if you're reporting an issue: 
====

hi guys,

today morning i was not getting any emails and i got very frantic and scared.
So tried to look up the logs and couldnt see anything wrong.
Disabled avasmid, jail2ban, etc just to pinpoint the problem.
Updated the server and then rebooted and yet could not get any emails

Later realized that I was missing mx records on my domain dns and thought that was the cause.
I recently added more subdomains and I think that might have caused a clash.

Could MX record be a cause for undelivered emails? (I am right now waiting for the MX record to propergate)
Feeling stressed out but hope this addresses it.

Please advise.

Thanks
Kevin

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2

Re: could not having mx record cause undelivered mails?

MX = Mail eXchange, other mail servers deliver email to the server specified in the MX record of your mail domain name, if no MX record found, they will try A record instead.

MX is VERY important.

3

Re: could not having mx record cause undelivered mails?

phew!
all sorted. : ) emails functioning.
turning back on all services.
that was scary.
thanks zhang