Ant wrote:
> VanguardLH typed:
>
>> You didn't mention which version you have. It's likely the same file(s)
>
> IIRC, the latest Office 2011 for Mac,
I have no experience using Outlook, any version, on a Mac so I cannot
attest to its behavior or which file(s) are used to store the keyword
database for Outlook's junk filter.
> work's 2010 Pro.,
Are you referring to MS Works?
Or that Outlook 2010 in Office 2010 Pro works okay (i.e., you don't get
the spam flag problem in Outlook 2010)?
> etc.
I don't know "etc".
Are you trying to say that the junk filter doesn't behave how you want
in Outlook from Office 2011 for Mac, Outlook from Office 2010 Pro, and
every other (etc) version of Outlook you have tried?
>> Have you found Outlook's junk (Bayes) filter really that useful to you?
>> Other than the server-side anti-spam filter putting suspect messages in
>> the Junk/Spam/Bulk folder up in your online account, has Outlook caught
>> any additional *real* spam e-mails (and not just e-mails that you don't
>> happen to like but actual spam, like that which is UBE or UCE)?
>
> Yes, it has caught real spams like those foreign ones (e.g., asian) that
> come once in a while. My work's e-mail address is over a decade old so...
As I recall, you don't even the junk filter for catching other-language
messages. There is a section solely for languages where you can reject
messages that use languages you don't understand. Even if I write to a
mobo maker in China, they reply in Engrisch; i.e., the encoding
specified in their reply is a character set that I can read. I think I
had about 3-4 charsets selected as acceptable and all the others would
get rejected (junked). That filtering works only on the encoding
charset specified by headers in the message, not on how someone might
use the characters in writing their message (i.e., like trying to use
ASCII-8 to write messages with umlauts, carats, and other character
punctuation characters).
At work and when using Exchange, the server-side anti-spam filtering
should be all you need. If it is missing spams then you need to notify
your IT folks about the omissions. They are using some anti-spam filter
up on their Exchange server, right?
For your friend's Outlook, his setup could be different than yours so I
wouldn't rely on behavior in his setup reflecting how to resolve
problems in your setup. Whether you friend uses POP or IMAP depends on
how he configured the server-side settings in his Gmail account. For
POP, items he sees in the Junk folder in Outlook would only be there due
to something in Outlook, like junk filtering, blacklist, rules, or an
add-on. He only has access to the server-side Inbox when using POP, so
retrieving them from the server Inbox into Outlook's Inbox and then
moving into Outlook's junk folder means Outlook did that. With IMAP,
items in the Junk folder could've been put there by the server so
Outlook simply reflects the current contents of the server's Junk
folder, or the message was in the server's Inbox, came to Outlook's
Inbox, but Outlook moved it into its Junk folder -- and due to IMAP
synchronization means that Outlook would sent a Purge command to remove
the message from the server's Inbox and send up a copy to the server's
Junk folder from Outlook's Junk folder. Your friend might also be
accessing his e-mail account using Outlook on one host, another e-mail
client on another host, or an app on a smartphone and all of which could
affect what is where in the server's folders when using IMAP.
POP only understands the concept of a mailbox. There are no folders
when using POP. There are no commands in POP to select or manipulate
folders. To POP, the server-side Inbox folder is the mailbox and the
only place from which a client can retrieve messages. If the server-
side anti-spam filter moved a message into the server-side Junk folder,
a POP client will never see that server-side junked message. So if POP
is used and a message shows up in the client's Junk folder then the
client moved that message from its Inbox (where all e-mails are first
delivered when using POP) into its Junk folder.
IMAP does understand folders (well, to those you configure the client to
subscribe to). An IMAP client will synchronize the contents of its
client-side folders to the matching server-side folders. So there are 2
possibilities on how a message got into Outlook's Junk folder. One is
the server's anti-spam filter put a suspect message into the server-side
Junk folder and then Outlook synchronizes with the server, pulls down a
copy of the message in the server-side Junk folder into its own local
Junk folder. Two is Outlook got the message in the Inbox folder, moved
it to its local Junk folder, and then Outlook synchronizes with the
server to upload a copy of that message in its Junk folder into the
server-side Junk folder. IMAP means synchronizing the contents of the
folders, so if the server moves a message or the client moves a message
then that move gets reflected at the other end after synchronization.
This also means other clients, like apps on smartphones or e-mail
clients in notebooks, connecting to the same account and making changes
will do their synchronization to match up client and server folders and
then your Outlook on your host will reflect those same changes when it
synchronizes. IMAP not only allows for use of folders but to maintain a
synchronized view of an account across multiple clients connecting to
the same account.
For Gmail or other e-mail providers, I'd disable Outlook's junk
filtering to see if the erroneous spam flagging is stopped. At work,
I'm not sure they even want you using a Bayes filter in the e-mail
client. Report ham flagged as spam to your IT folks to see if they have
a problem with their filter. Of course, if its the Bayes filter in
Outlook flagging ham as spam then the obvious cure is not to use
Outlook's junk filter. Your workplace's anti-spam filter should be
catching the spam, not the clients connecting to their network and using
their Exchange server.