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

SBS2011 - Exchange 2010

Hey everyone,
I have the following problem with a customer using a SBS2011, means Exchange 2010 latest patch level:
there was a mail-enabled public mail folder. For several months it worked fine that one certain mail address was sorted into that certain public folder.
Since a few weeks some other mails dedicated to regular users are sorted into that folder too, but not always. sometimes they are directed into the folder sometimes they are sorted to the user they belong to.
Now I disabled the mail function on the folder and defined the mail address of this folder to a certain user as a additional address.
the result is, that now this user gets the mails according to the new assigned plus the mails that are wrongly assigned.
example:
mail enabled pubilc folder with address public@
user1@
user2@

mail for user1@ is wrongly directed by exchange??? to public@
next time same external sender is correctly directed to user1@

after disabling mail functionality for the public folder and adding the mail public@ to user2@:
mail for user1@ is wrongly directed by exchange??? to user2@
next time same external sender is correctly directed to user1@

I have definitely no idea cause in the Exchange Message Tracker the wrongly assigned mails already appear with the wrong "to" address.

If I open the mail from the public folder in outlook I definitely have the mail address user1@.

I appreciate any ideas leading to a solution of this weired symptom.

greetings
0
konga-frites
Asked:
konga-frites
  • 2
1 Solution
 
WORKS2011Austin Tech CompanyCommented:
I'm going out on a limb here but what happens if you reset IIS, does it begin working correctly? You can reset IIS from a elevated command prompt and typing iisreset.

There has been allot of issues with latest updates in .NET on SBS2011.
0
 
strivoliCommented:
Are there any Transport Rules defined on Exchange?
0
 
konga-fritesAuthor Commented:
Sorry guys - I forgot to close this request.
The issue was that the customer moved his hosting to another provider. The mx should point to another mail security provider.
With the move they forgot to set the mx in dns correctly. After solving this issue an waitung another 24 hours everything was fine.
Anyway - thanks to all who tried to help me.
Greetings
konga-frites
0
 
konga-fritesAuthor Commented:
it was no exchange, sbs2011 or .net issue
0

Featured Post

Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

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