Incoming Emails going Straight to Hard Delete

[Steve]

I have been trying to find out why some incoming emails will appear in the
inbox for a few seconds, then disappear. They are not in the Deleted Items
folder.

From the Inbox, If I go to Tools:Recover Deleted Items, the missing Emails
are there. If I recover them, they go back into the inbox for a few seconds
then get hard deleted again.

We use Trend Micro Worry Free Advanced for Spam and Such, but it does not
have the option to hard delete anything. It marks as Spam and Delivers to the
Spam Folder. It is the latest version.

MS SBS 2003 Std with all service packs and updates. Outlook 2007 as Exchange
Client in cached mode on Windows XP/SP3 with latest updates. Autoarchive is
turned off. View Filters are set to view 'Messages'.

Since I had one available, I even moved the user to a brand new box with a
fresh install of XP3 and MS Office 2007 Small Business.

Other Apps: Latest Blackberry Desktop, all settings are to Not Reconcile.

Besides Exchange, the user has a secondary pop account (aol.com) configured
and incoming messages are sent to his exchange inbox. The outgoing smtp
server for this account is the internal exchange server.

How do I prevent auto hard-delete of emails from happening?

 

[Steve]

One other thing to add: Sporadically, all emails in his inbox, except for
maybe the last 20 or 30, get hard-deleted, no matter if they were aol or
exchange sourced. When these particular emails are recovered from deleted
items, they will stay in the inbox until the next time this happens.

 

[k-man]

Have you found a solution yet? I have the same issue. One of my users is
experiencing the problem where any new messages arrive her mailbox, but
within 30 - 60 seconds they are "Hard" deleted. The only way to get them back
is to "Recover Deleted Items". I have created a new mailbox for the user and
it is still happening! I have no rules setup and no filters are in place. We
use Symantec for Exchange Server; however it is not set to delete or
quarantine any messages, I have even disabled. Any help would be greatly
appreciated.

 

[K. Orland]

Does this happen if the user opens Outlook in safe mode?

Start > Run > outlook.exe /safe

 

[Brian Tillman [MVP - Outlook]]

Have you found a solution yet? I have the same issue. One of my users is
experiencing the problem where any new messages arrive her mailbox, but
within 30 - 60 seconds they are "Hard" deleted. The only way to get them
back
is to "Recover Deleted Items". I have created a new mailbox for the user and
it is still happening! I have no rules setup and no filters are in place. We
use Symantec for Exchange Server; however it is not set to delete or
quarantine any messages, I have even disabled. Any help would be greatly
appreciated.

One prime cause is synching with a handheld device.

 

[k-man]

Thanks for your responses. My problem had to do with a third party software
vendor who setup "Event Manager" which will perform specific tasks at
specific times to the accounting system. I found that there was an even that
was not configured properly, thus deleting ALL unread messages for my
specific every 10 minutes. I removed this task and the mailbox seems to be
working properly again. Thanks for your suggestions.

 

[Di]

Hi all, we are still having this issue but now it is starting to be a larger
issue with more users experiencing it.
Does anyone have any other ideas on how to fix/stop this happening.
looking at 2 of the machines they are running basic same software but not
any additional software is the same.

 

[K. Orland]

Have you checked all the troubleshooting steps already offered in this
thread?

 

[Brian Tillman [MVP - Outlook]]

Hi all, we are still having this issue but now it is starting to be a larger
issue with more users experiencing it.
Does anyone have any other ideas on how to fix/stop this happening.
looking at 2 of the machines they are running basic same software but not
any additional software is the same.

Outlook simply does not do this on its own, ever. You must have a rule or
some add-in causing the problem. See K. Orland's earlier post.