Outlook 2003 and Junk E-Mail filter

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi Folks,

Having an issue with the Junk E-Mail fitler catching something that is NOT
junk email. I'm aware of how to tell it something is not junk but in this
particular instance that will not work.

We have a Linux based email server and it sends out even logs. It is hit and
miss that the Junk E-Mail filter catches these. Probably 80% of the time it
doesn't. Unfortunately there are a lot of these logs so that leaves a good
number in the Junk E-Mail folder.

Here is the problem. When I right click on one and select Mark as Not Junk I
get the box:

Mark as Not Junk

This message will be moved back into the Inbox Folder.

Always trust e-mail from "root" is Checked.

Always trust e-mail sent to the following address:

admin and the box to the left of it is not checked.

Whether I check both boxes or not and then click on OK I get:

Microsoft Office Outlook

The e-mail address or domain name you entered is not valid.
Vaild entries include: (e-mail address removed) or example.com


I understand that the email is not coming with the standard wrapper but it
is legit.

Is there no way to handle this ?

Thanks !

Chuck
 
Chuck said:
I understand that the email is not coming with the standard wrapper
but it is legit.
Click to expand...

No, it's not legit. The address "root" is not replyable. There's no
domain. Your Linux mailer is configured improperly.
 
Why? Because Microsoft chose to design their filter to support only a minimal amount of user customization -- thus, in theory, providing a useful filter for beginner to advanced users that takes very little user productivity time to understand, operate, and maintain. SpamBayes targets a narrower audience of more advanced users who want to analyze the spam content they receive and finetune with their filters.

Different strokes for different folks.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Chuck said:
I understand what you are saying and don't mean to quible but there
is no way to change that configuration; it is embeded in their
programs.
Click to expand...

Their programs violate the long-standing SMTP RFCs which state that all
sending addresses must be replyable. Outlook is RFC-conformant. The Linux
program isn't. Which one has the problem? I know which I'd pick, and it's
not Outlook.
 
Chuck said:
This wouldn't even have some up if Outlook hadn't decided in the last
week or so (after months of ignoring these) to start catching one
every so oftern. Why would it do that ?
Click to expand...

I have no idea, unless some Junk E-mail filter update changed the behavior.
 
Outlook JunkMail Filtering is NOT rfc compliant - it will not allow the use
of a domain such as [123.45.6.78] which is prefectly valid.
We receive logs from our router in which the sender is router@[123.4.6.78]
these are always detected as junk and we have so far been unseccessful in
convincing outlook otherwise.

We are leaning towards disabling outloonk junk mail filtering and going back
to our inhouse spam-bayes implementation ( w training )
 
gerry said:
Outlook JunkMail Filtering is NOT rfc compliant - it will not allow
the use of a domain such as [123.45.6.78] which is prefectly valid.
We receive logs from our router in which the sender is
router@[123.4.6.78] these are always detected as junk and we have so
far been unseccessful in convincing outlook otherwise.
Click to expand...

I never claimed that Outlook was RFC-compliant in all aspects, only in the
one covered in the thread from which you are quoting and that has nothing to
do with what you describe.
 
Back
Top