"Tim" wrote in message
news
It's not likely on your end. First thing that comes to mind is have
your customer check her Junk e-mail folder. I have had Outlook
"suddenly" decide that e-mail from someone should now be routed to
Junk even after working fine for a period of time. Don't know what the
cause was...I just added that address to the "Safe" list in Outlook
and the problem went away.


Ah, the benefits of using someone else's Bayesian database for junk mail
filtering. Every so often Microsoft shoves another spam database as a
Windows update. The database is obviously not one that you created that
reflects your personal history of experience regarding spam but someone
else's (i.e., a database that Microsoft built, not you). That means it
is entirely possible that the externally generated Bayesian database has
a set of weighted words or phrases that happens to trigger on what are
good e-mails for you.

I didn't bother upgrading to OL2003. No bang for the buck and I have
better anti-spam solutions than what Microsoft stuck in OL2003. Isn't
there a way in OL2003 to mark a mail that got shoved into the Junk
folder as "not spam" to remove or reduce the weighting of the trigger
words so that future similar mails don't get similar identified as spam
(i.e., doesn't the user get an option to unmark a mail as spam and
unweight the database)?

Also, maybe the OP should check the Blocked Senders list.