Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 195
  • Last Modified:

Exchange 2003 Duplicate messages - Routing problem ?

I'm running SBS2003 and my exchange routing seems a little queer.

If a person sends a message to 10 different people at our company then each recipient receives it 10 times !! If sent to 5 recipients then all 5 people receive the message 5 times - I'm new to exchange and simply set it up using the wizards, have I missed something really obvious ?, any help appreciated as our mail boxes are filling up with duplicate messages.
2 Solutions
ubiquitasAuthor Commented:
anyone ???
It sounds like Outlook is getting it's knickers in a twist. Have you checked via owa if the same thing happens?
Also try turning on message tracking on the server and do a search for messages that match.

This may help you solve the issue.
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

ubiquitasAuthor Commented:
Thanks. I have message tracking on.

I just did a test and sent a message to the administrator & 1 other person. I checked the administrator email via OWA and the message is there twice.

In the message tracking it shows the server as having received 2 identical emails from me, and delivered each message only once to each recipient.  Any more ideas?, definitly seems like the problem is with exchange and not Outlook to me.
Can you post the full headers of these 2 mails?
ubiquitasAuthor Commented:
OK, little further investigation has revealed what is happening. We are set up to collect our company mail from a POP account with our ISP, i.e.  *@ourdomain.co.uk

It seems that the ISP creates duplicates of the message (1 for every recipient@ourdomain.co.uk) which our exchange server then downloads and dutifully sends out to all the recipients.

So my solution I suppose is either

1. Get exchange to remove duplicate messages (if this is even possible)
2. Get ISP to change MX records to point direct to our Exchange Server

I guess my question now is which of the above is the best solution, I suspect no. 2 though I've no idea how to set up exchange to deal with this
Chris DentPowerShell DeveloperCommented:

I'm not sure how you'd achieve number one, which isn't very helpful...

But If you have a permanent Internet connection then option 2 works quite well.

You need to check a few things. First that Exchange is setup to recieve messages either for your domain name or * (* is the default and represents everything). Exchange will still only accept inbound messages if the e-mail address is in the Global Address List - unless you've changed the setting.

The rest is down to network, you need to configure your Firewall to let Port 25 through to your Exchange Server. You can do that a number of ways including Port Forwarding and Network Address Translation, but which you use depends on your network firewall.

With any MX Change you should be aware that it takes time, the default TTL (Time to Live) for a DNS Record is 2 days, and I imagine yours is too. So any change you make the the MX could potentially take up to 2 days to get to everyone else.

Of course the TTL can be reset down if whoever holds the DNS will let you, if you do follow that option it should always be changed down at least as far ahead as the current TTL (that is, if your TTL is 2 days, you should change the TTL at least 2 days before you change the IP Address of the Mail Server).

I hope that makes sense, please let me know if not.

Featured Post

Free recovery tool for Microsoft Active Directory

Veeam Explorer for Microsoft Active Directory provides fast and reliable object-level recovery for Active Directory from a single-pass, agentless backup or storage snapshot — without the need to restore an entire virtual machine or use third-party tools.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now