I recently pushed out an outlook 2003 update from my WSUS server to about 100 clients. Out of those clients only 1 has show an issue. All of their Junk mail is being sent to their inbox and all the mail from their inbox is goign to their Junk Mail Box. We have tried to Detect and repair the program, we have also deleted configuration files on the exchange server linked to their account, we even turned off junk mail filtering for the user but it still continued to happen. The user has no other rules configured, they just use the junk mail filter and safe sender list. Our next step is to completely re-install outlook 2003. Our only concern is that the users pst file may have something corruptted in it that may re-create the same issue. Has anyone experienced this issue and/or any thoughts on it.


--Zac

Dani AI

Generated

— nice troubleshooting so far, and ’s idea about folder renaming is exactly the sort of thing to keep in mind. Here are focused, practical checks that add to what has already been tried and avoid a full reinstall unless absolutely needed.

Start by confirming where the decision to move messages is happening. View the same messages in Outlook Web Access (or any server-side view). If the messages appear in the same (wrong) folders on the server, the problem is mailbox/server-side; if they are correct on the server but wrong in the client, it is client-side. Inspect message headers (in Outlook: open message -> File -> Properties -> Internet headers) for any SCL or transport-agent stamps that show server-side classification.

Rule out client add-ins and profile corruption next. Launch Outlook in safe mode with outlook.exe /safe to see if behavior changes. Disable any non-Microsoft COM add-ins and antivirus/antispam Outlook plugins and retest. If the client view is the issue, create a fresh Outlook profile and test before reinstalling Outlook.

If the trouble looks mailbox-level, special-folder mapping or folder properties can be the culprit. A folder can have its special role (Inbox/Junk) lost or mis-tagged. Use a low-level mailbox tool (for example, MFCMAPI) to compare the suspect folder’s properties with a working mailbox, or create a correctly-typed mail folder and move items into it. Do not edit mailbox properties without a backup — MFCMAPI is powerful and risky.

Also run the Inbox Repair tool on any local PST (scanpst.exe) or delete and let Outlook rebuild the OST to rule out local file corruption. If server-side classification is shown in headers, check Exchange/antispam logs or any front-end spam appliance for rules or transport agents affecting a single mailbox. Back up data before changes and escalate to Exchange/antispam vendor support if the server is stamping SCLs incorrectly.

Recommended Answers

All 3 Replies

Ok, so my next step was to install SP2m hoping that would fix the problem. So far it has done nothing to solve the issue. So moving on to step 2 I have un-installed the Junk Mail update completely. So we will see if that fixes the problem. Im still puzzled as to why only 1 person out of a 100 had issues with the update. If this doesn't solve the problem I may have to look into programs the user is running that are not corporate approved applications.


--Zac

I know this is a wild suggestion but has your user managed to rename the folders, so they are reversed ?

I know you may regard this has daft but I have seen users do al sorts of daft things!!

Good luck

Denis

Lol, He very well could have, but we created a new mailbox for him and everything seems to be working just fine now. Today we are going to turn his cached mode back on and see what will happen next. Before we made a new mailbox we turned cached mode off and the junk mail was still affecting where his mail was being placed.

--Zac

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.