Great suggestion, Vanguard! I ran Outlook with /SAFE and
unfortunately, it appears that Outlook is ignoring the "no automatic
filtering" selection in the Junk email options window.
When the first spam arrived, I got this pop-up:
"Outlook has downloaded a message that appears to be junk email.
This message was automatically moved to the junk folder."
So, now I'm at my wit's end. It seems that there is no way to tell
Outlook not to apply its own spam filtering rules. And, in fact, I
DO want it to apply its rules... but only after my rules are
applied.
Have you sny further thoughts?
I'm out. Unless maybe you are in a domain and a GPO is getting pushed
to your host. However, although the policy gets foisted onto your
host, I thought that was only during login. Sounded like you had
logged in and then changed the junk filter which means that setting
should stick during the rest of your current Windows session. If the
IT folks don't know about some trick they used to enforce junk
filtering (I recall something to do with Office policies but never got
into them or got afflicted with them to then figure out how to
circumvent them), I'd try doing a repair (under the Help menu in
OL2002 - you'll probably need the install CD, a network install path,
or the subdir left behind called, I think, c:\msoffice or something
like that, where the cab files were stored to perform later
customizations of the install) or do an uninstall and reinstall.
In fact, a trick I use to get around some policies (those that effect
registry changes), is to simply put a "regedit /s <regfile>" event in
Task Scheduler to run on login (or I could use a shortcut in the
Startup group under the Start menu). For example, some companies
enforce a scree saver timer of 15 minutes but on a shared host this
resulted in having to divulge the login password to too many users in
case the password-protected (another GPO setting) screen saver got
activated, or someone with the password had to be found and go visit
the shared host. So the GPO got pushed during login, we weren't
logging off (to login again), GPOs are effected only during login, so
they pushed their policy when we started the host but then we (with
admin privs) would change the registry to what we wanted. Wouldn't
work unless we had admin rights (on the domain to that host), in
Development of Software QA we always had to have those privileges. We
couldn't get them to have different policies for our hosts (i.e., it
was a company-wide policy to which they allowed no exceptions). We
told them what we planned to do and they okayed it so it was a way for
us to modify the policies for our hosts and with permission.
