Gary W said:
Thanks for your reply. So far, the new Outlook warning is an
annoyance, but it means I must say yes to 10-minutes of access in
order for Spam Inspector to do its thing. I hate to disable the
program, because I receive at least 300 spams per day. Problem is, I
leave for a week vacation soon and ISP may not accept and store that
many emails while I'm gone.
I question why MS didn't give me the option to identify the suspect
program and then say I want it always to be able to access Outlook
Contacts. Why is it just a yes or no? Norton Internet Security gives
me the option to allow access for specific programs, why didn't MS do
the same?
With a plug-in to Outlook, that's the only e-mail client the plug-in
will work with. Outlook Express doesn't support plug-ins. A plug-in
author may not produce versions for every e-mail client that does have
support for plug-ins.
Does Spam Inspector have an option to run as a local proxy? You then
configure your e-mail client to connect through the local proxy and have
it tag any messages it thinks are spam.
http://www.giantcompany.com/kbArticle.aspx?prodID=20&articleID=82 and
http://www.giantcompany.com/kbArticle.aspx?prodID=20&articleID=81 seems
to indicate that Spam Inspector might run as a local proxy (they hide
that function by saying it is an application called their Gateway). The
latter link indicates how to reconfigure an e-mail account's settings to
direct it to go through their proxy. So instead of using the plug-in,
you could use their proxy. I suspect you then have to define a rule (or
maybe they add one when you configure it) that will trigger on messages
that got marked with a tag in the Subject header or a special header got
added to the message to identify the spam. Outlook Express cannot test
on but a few headers (Subject, To, Cc, From, etc.) so you cannot have it
test on a special header, like "X-SpamInspector: SPAM", so the spam
proxy has to add a tag to the Subject header, like "**SPAM**", so an OE
rule can catch it.
So what you could do is configure Spam Inspector for Outlook Express and
then migrate those modified e-mail account settings in OE into Outlook.
I always find 127.0.0.1 a bit obtuse in that it really doesn't tell me
to what proxy the e-mail client will connect. So I would define a
"127.0.0.1 SpamInspector" entry in my hosts file and then use
"SpamInspector" (instead of 127.0.0.1) as the mail server in my e-mail
client's accounts. If you chain multiple proxies together, it's handy
to see which one is which. I do have more than one proxy in the chain
for my Yahoo accounts and I use SpamPal for spam filtering (Outlook <--
SpamPal <-- YahooPOPs <-- Yahoo) so it helps to know for which one I'm
configuring in what fields in my e-mail client. But if you only have
one proxy then it might not be worth the extra effort.
