Prev: Junk Mail Filter (KB981432) for Outlook 2003 Feeds ALL Mail to Inb
Next: Outlook will not open
From: Mltwwlco on 6 May 2010 15:40
Update: I found one user that uses OWA exclusively and the message was not
marked as Junk in their mailbox, so this means the problem is with either
Outlook 2007 or the 2007 Junk filter updates.


<Mltwwlco(a)noemail.noemail> wrote in message
news:O3%23m7DV7KHA.4508(a)TK2MSFTNGP06.phx.gbl...
> James, thank you for the reply and suggestions I will try them next
> week. My answers are inline below.
>
> "James Luo" <v-jaluo(a)microsoft> wrote in message
> news:bFdpDjo6KHA.4272(a)TK2MSFTNGHUB02.phx.gbl...
>> Does the junk mail filter into the Junk folder before you launch the
>> outlook? Please reproduce the issue, and then locate the junk mail via
>> OWA
>
> Excellent idea to test/confirm that the Outlook 2007 Junk Email filter is
> causing the issue. If Outlook 2007 is not running on the mailbox and a
> message is sent to that mailbox that is normally classified as junk, using
> only OWA to view the mailbox and check the location of the message will
> determine if Outlook 2007 and the April 2010 Junk Email Filter is the
> culprit. If it is still in the Junk Email folder, then Exchange (or an
> Exchange rule) is moving the message, otherwise Outlook is moving it.
>
>> So, your exchange server doesn't install IMF, does the message pass any
>> other routing exchange server that installed the IMF before your mailbox
>> server?
>
> No other routing exchange servers or SMTP servers are involved, this is
> the message flow:
> 1. Web Server App writes email message as text file and places it into
> the outgoing SMTP queue folder on the webserver
> 2. SMTP running on webserver sends message to Exchange server via SMTP
> directly, note both servers are on the same local subnet
>
>
>>
>> Resources:
>> Where to install IMF (and other miscellaneous IMF explanations)...
>> http://blogs.technet.com/evand/archive/2004/05/31/145134.aspx
>> IMF and the Junk E-mail folder in Outlook
>> http://blogs.technet.com/evand/archive/2005/01/31/363935.aspx
>>
>

From: James Luo on 6 May 2010 22:34
Quote: "found one user that uses OWA exclusively"
Actually, I would suggest testing on a problematic user. If the automate
mail doesn't filter in OWA, but filter to Junk folder when the problematic
user launch the outlook. It would isolate the root cause to the outlook
client completely

Quote: "last several weeks many of our users are reporting"
Can you confirm whether the issue happens to all users?
Are there any users who don't filter the same automate mail that has been
filtered to the problematic users' Junk folder? If have, you can check if
there's any difference between the working machine and the problematic
machine, like the outlook version, and other third party software

From: Mltwwlco on 28 May 2010 17:51

"James Luo" <v-jaluo(a)microsoft> wrote in message
news:u1uVj3Y7KHA.2348(a)TK2MSFTNGHUB02.phx.gbl...
> Quote: "found one user that uses OWA exclusively"
> Actually, I would suggest testing on a problematic user. If the automate
> mail doesn't filter in OWA, but filter to Junk folder when the problematic
> user launch the outlook. It would isolate the root cause to the outlook
> client completely

I agree, since the OWA exclusive user does not have the issue, which makes
me conclude that the Outlook 2007 junk email updates are responsible for
classifying the message as junk and moving it into the Junk Email folder.

> Quote: "last several weeks many of our users are reporting"
> Can you confirm whether the issue happens to all users?
> Are there any users who don't filter the same automate mail that has been
> filtered to the problematic users' Junk folder? If have, you can check if
> there's any difference between the working machine and the problematic
> machine, like the outlook version, and other third party software

The issue occurs with all Outlook 2007 users that have not already added
the domain or email address to the safe senders list in Outlook 2007. I am
preparing to deploy the safe senders list via group policy to all domain
users, but have run into problems since the Outlook 2007 SP2 ADM template
does not include the necessary registry key
HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\Options\Mail
"JunkMailImportLists"=dword:00000001. Also once this key is added manually
and the GPO appears to run, there is no indication in the Outlook 2007 Safe
Sender user interface that the central list has been successfully merged
with the original users list.

References
GPO to append to Safe Senders -- need two extra registry keys
http://social.technet.microsoft.com/Forums/en/exchangesvrclients/thread/3d3abee5-ebf2-4dae-9f48-300b93af07c8
Deploy Junk E-mail Lists Throughout Your Organization
http://blogs.technet.com/b/asiasupp/archive/2007/04/26/how-to-deploy-junk-e-mail-lists-throughout-your-organization.aspx

From: James Luo on 1 Jun 2010 02:56
"Also once this key is added manually and the GPO appears to run"
How did you add it manually? Do you upload the template into the GPO as
suggested by Mike Shen in the link?
Copy the custom template into a text file, and then name it as
OL2K7JunkMail.ADM. Use it on the GPO

First  |  Prev  | 
Pages: 1 2
Prev: Junk Mail Filter (KB981432) for Outlook 2003 Feeds ALL Mail to Inb
Next: Outlook will not open