Question Locked

E-mail problems

0 helpful
15 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hello all, new poster here, and I apologize for asking a question right when I get on here, but I have tried everything in my power to fix this.

I am having problems sending e-mails from my Exchange 2003 server. It is only to certain domains, so I am not sure if I am blacklisted or not. What are some steps that I should try to remedy this situation?

15 replies

by sgt_shultz

Hi, what is the exact message you receive when you try an email to one of the domains in question.

by jeroden

Your message did not reach some or all of the intended recipients.

Subject: Test
Sent: 4/30/2007 2:31 PM

The following recipient(s) cannot be reached:

'ristar5611@hotmail.com' on 4/30/2007 2:31 PM
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.

I know that the address works because it is one of mine.

Does it ring a bell?

by churdoo

Is a hotmail server, or is one of your servers that generated that NDR? If it's your server, then your exchange org thinks it's responsible, or "owns" @hotmail.com, and is looking for that email addy in your own active directory, hence the failure.

If this is the case, go into RUS -- System Manager / Recipients / Recipient Policies / and check through all of the policies and see if @hotmail.com is listed in any of your policies, and/or any other of the domains that you're having trouble sending to.

Remove any email domains that your exchange server does not "own" and then go to Recipient Update Service and Rebuild the Domain and Enterprise RUS.

Give a few minutes or hours depending on the size of the org, and send a test message.

by churdoo

Are you getting any NDR's or errors of any kind or do the messages seem to go, and you get no errors nor NDR's, but the recipient never receives the message(s)?

Is it the same recipient domains all the time and every time?

Use the message tracking tool to make sure that the messages leave your Exchange Org. If so, then you may not comply with email sending best practices and may be blocked by anti-spam rules. Chances are if you are truly blacklisted, you'd know it by now, but individual organizations could be denying delivery due to lack of compliance and wouldn't necessarily notify you.

It's kindof a broad assumption at this point, so I won't go into the detail yet -- HELO/EHLO server name, reverse DNS, sending from static IP vs. dynamic IP, etc., etc.

--C

by jeroden

I posted the message that I receive in a previous reply, I hope that rings a bell with you and you are able to see something noticeable. Where would I check message tracking? Forgive me being green, I will google it until I get a reply.

by jeroden

That is what happened, it thinks it "owns" all of these domains, and it is a lot of them. How do you suppose that it started thinking that it owns these domains? Do you think a virus could have done this? I was told before I inherited this network, that there was a pretty big virus outbreak.

by churdoo

Not likely; I've never seen nor heard of a virus populating the recipient policies with domains.

I suspect that it may be related to the reason that your predecessor is no longer there and that you've "inherited" this network. And I'll go out on a limb and say that this probably isn't the first weird configuration that you've come across. :-)

Glad to have helped.
--C

by jeroden

LOL so very very true, hope I can do things better

by jeroden

I gave it overnight to update, but it doesn't seem to update, I think it may be because of the replication problem, but I want to make sure I am deleting the policies right.

What I did was tested hotmail first. I went to policies, and removed @hotmail.com from the list. It was on two policies, so I made sure to get both, then I hit rebuild. The next day, I tried it, and it gives me the same message. I am gonna try to demote this W2K server and see if it makes it better

by jeroden

I have now successfully demoted the Win2k server found the policy that had hotmail in it (so I think) and removed it, and rebuild again, gave it overnight, and I am still getting bounceback.

Anyone have any other suggestions?

by churdoo

Glad you got your W2K server demoted and that you've cleaned up your AD and replication.

How many recip policies are there? Hotmail could be listed in more than one, make sure you remove it from all policies. The only domains listed in any Recipient Policies are email domains that this server delivers mail to.

I suppose it may be important too, that a hotmail addy is not listed as the primary addy for any user, folder, or distro group object.

Also, are there any connectors, and how many?
--C

by jeroden

Ok, I am really Green, but I am learning fast. I am not sure what connectors are, or I know what they are, but not by name.

There are 3 Recipient Policies, and two have e-mail properties, and I removed it from both.

Will I have to check each and every user to find out if Hotmail is primary?

New finding: I ran nslookup, and it let me know that it cannot find the server name for my address, but we can get outside mail. Could this make a problem?

by jeroden

I have sent an e-mail out now. What I did was activate the E-mail tab on the policy that didn't have an E-mail property and there it was, another list of e-mails that were set to be "owned" by us. (For anyone using this to try and fix a similar problem, I right-clicked on the policy that didn't show e-mails, selected Change property pages, and selected e-mail)

After I unchecked all of these domains to let Exchange know that we didn't control these, I used the Apply this Policy Now selection (also a right click on the policy) and rebuilt everything on RUS and told it to Update now. After a while, I was no longer stuffed :D Thanks Churdoo

This discussion is closed to new replies.