I see a lot of support requests where folks do not understand where the problem is when mail is not delivered. So this little short primer will hopefully shed a lot of light on how to resolve these.
The first thing to do is, search the rejection notice for the following text “exchangedefender.com”
If that does not provide any results, then the problem is that the email is not coming to ExchangeDefender. This can be a DNS record has not expired OR you have a different MX record in addition to inbound30.exchangedefender.com receiving the email.
If that finds a match then it’s likely making it to use but then it’s being rejected. From that point we only have 3 rejection types.
1. Rejected due to being a SPAM Botnet, this means the sending server is a KNOWN spam bot net (willingly or not) and needs to address that issue. We provide the details in the rejection
2. Rejected with a rejection “Relaying Denied”. This means the domain does NOT exist in admin.exchangedefender.com OR it does exist and it has not propagated yet. All you have to do is either add them if you don’t see it listed OR wait if it’s already listed.
3. Rejected with “ExchangeDefender does NOT protect this address.” This means the domain exists BUT the particular address in question does not. Again, as above, if it doesn’t exist in admin.exchangedefender.com add it, if it does then wait for propagation.
I hope these tips help you in resolving situations for your clients in a faster manner.
VP Support Services, ExchangeDefender
(877) 546-0316 x737