Block invalid addresses - Junk Mail filter doesn't allow them

F

FDD

Since the Junk Mail filter doesn't allow invalid address to be blocked, it
shouldn't accept them in the first place. Sample header follows:

Return-path: <[email protected]>
Received: from 201-36-103-111.jfa.megazon.com.br
(201-36-103-111.jfa.megazon.com.br [201.36.103.111]) by my.mail.server
(Rockliffe SMTPRA 4.5.6) with SMTP id <[email protected]>;
Wed, 4 Oct 2006 13:24:08 -0700
Date: Wed, 4 Oct 2006 13:24:08 -0700
Message-ID: <[email protected]>
From: "Cheap ViagraCialisValium_n[1

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...5b140e093555&dg=microsoft.public.officeupdate
 
M

Milly Staples [MVP - Outlook]

It is your server that accepts the messages, not Outlook. Contact your server folks to have that resolved.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, FDD asked:

| Since the Junk Mail filter doesn't allow invalid address to be
| blocked, it shouldn't accept them in the first place. Sample header
| follows:
|
| Return-path: <[email protected]>
| Received: from 201-36-103-111.jfa.megazon.com.br
| (201-36-103-111.jfa.megazon.com.br [201.36.103.111]) by my.mail.server
| (Rockliffe SMTPRA 4.5.6) with SMTP id <[email protected]>;
| Wed, 4 Oct 2006 13:24:08 -0700
| Date: Wed, 4 Oct 2006 13:24:08 -0700
| Message-ID: <[email protected]>
| From: "Cheap ViagraCialisValium_n[1
|
| ----------------
| This post is a suggestion for Microsoft, and Microsoft responds to the
| suggestions with the most votes. To vote for this suggestion, click
| the "I Agree" button in the message pane. If you do not see the
| button, follow this link to open the suggestion in the Microsoft
| Web-based Newsreader and then click "I Agree" in the message pane.
|
| http://www.microsoft.com/office/com...5b140e093555&dg=microsoft.public.officeupdate
 
F

FDD

Agreed, but for situations where this is not the case, in a world in which
best practices also suggests multi-layed filtering, as per the Exchange
Intelligent Mail Filter and Outlook's own Junk Mail Filter, and how they
inter-operate, having the option to set the blocking of invalid addresses at
the client level seems a logical addition. There are likely a great many
end-users, as well, whose ISPs are not filtering such messages. There will
always be new schemes for getting past the servers, in any case. Given that
Microsoft is going to have the largest sample of those schemes as they arise,
building that option into the filter would also result in a better, more
widely distributed solution than, say, an individual user's client rule that
filters out addresses that don't contain "@", for example.
 
M

Milly Staples [MVP - Outlook]

I disagree. Filtering as far upstream as possible without creating a load on the end-user client is more preferable.

--
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, FDD asked:

| Agreed, but for situations where this is not the case, in a world in
| which best practices also suggests multi-layed filtering, as per the
| Exchange Intelligent Mail Filter and Outlook's own Junk Mail Filter,
| and how they inter-operate, having the option to set the blocking of
| invalid addresses at the client level seems a logical addition. There
| are likely a great many end-users, as well, whose ISPs are not
| filtering such messages. There will always be new schemes for getting
| past the servers, in any case. Given that Microsoft is going to have
| the largest sample of those schemes as they arise, building that
| option into the filter would also result in a better, more widely
| distributed solution than, say, an individual user's client rule that
| filters out addresses that don't contain "@", for example.
|
| "Milly Staples [MVP - Outlook]" wrote:
|
|| It is your server that accepts the messages, not Outlook. Contact
|| your server folks to have that resolved.
||
|| --Â
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. All
|| unsolicited mail sent to my personal account will be deleted without
|| reading.
||
|| After furious head scratching, FDD asked:
||
||| Since the Junk Mail filter doesn't allow invalid address to be
||| blocked, it shouldn't accept them in the first place. Sample header
||| follows:
|||
||| Return-path: <[email protected]>
||| Received: from 201-36-103-111.jfa.megazon.com.br
||| (201-36-103-111.jfa.megazon.com.br [201.36.103.111]) by
||| my.mail.server (Rockliffe SMTPRA 4.5.6) with SMTP id
||| <[email protected]>; Wed, 4 Oct 2006 13:24:08 -0700
||| Date: Wed, 4 Oct 2006 13:24:08 -0700
||| Message-ID: <[email protected]>
||| From: "Cheap ViagraCialisValium_n[1
|||
||| ----------------
||| This post is a suggestion for Microsoft, and Microsoft responds to
||| the suggestions with the most votes. To vote for this suggestion,
||| click the "I Agree" button in the message pane. If you do not see
||| the button, follow this link to open the suggestion in the Microsoft
||| Web-based Newsreader and then click "I Agree" in the message pane.
|||
||| http://www.microsoft.com/office/com...5b140e093555&dg=microsoft.public.officeupdate
 
F

FDD

I agree that the farther upstream, the better. What I'm suggesting is simply
another net to catch what might slip through.

Milly Staples said:
I disagree. Filtering as far upstream as possible without creating a load on the end-user client is more preferable.

--Â
Milly Staples [MVP - Outlook]

Post all replies to the group to keep the discussion intact. All
unsolicited mail sent to my personal account will be deleted without
reading.

After furious head scratching, FDD asked:

| Agreed, but for situations where this is not the case, in a world in
| which best practices also suggests multi-layed filtering, as per the
| Exchange Intelligent Mail Filter and Outlook's own Junk Mail Filter,
| and how they inter-operate, having the option to set the blocking of
| invalid addresses at the client level seems a logical addition. There
| are likely a great many end-users, as well, whose ISPs are not
| filtering such messages. There will always be new schemes for getting
| past the servers, in any case. Given that Microsoft is going to have
| the largest sample of those schemes as they arise, building that
| option into the filter would also result in a better, more widely
| distributed solution than, say, an individual user's client rule that
| filters out addresses that don't contain "@", for example.
|
| "Milly Staples [MVP - Outlook]" wrote:
|
|| It is your server that accepts the messages, not Outlook. Contact
|| your server folks to have that resolved.
||
|| --ÂÂ
|| Milly Staples [MVP - Outlook]
||
|| Post all replies to the group to keep the discussion intact. All
|| unsolicited mail sent to my personal account will be deleted without
|| reading.
||
|| After furious head scratching, FDD asked:
||
||| Since the Junk Mail filter doesn't allow invalid address to be
||| blocked, it shouldn't accept them in the first place. Sample header
||| follows:
|||
||| Return-path: <[email protected]>
||| Received: from 201-36-103-111.jfa.megazon.com.br
||| (201-36-103-111.jfa.megazon.com.br [201.36.103.111]) by
||| my.mail.server (Rockliffe SMTPRA 4.5.6) with SMTP id
||| <[email protected]>; Wed, 4 Oct 2006 13:24:08 -0700
||| Date: Wed, 4 Oct 2006 13:24:08 -0700
||| Message-ID: <[email protected]>
||| From: "Cheap ViagraCialisValium_n[1
|||
||| ----------------
||| This post is a suggestion for Microsoft, and Microsoft responds to
||| the suggestions with the most votes. To vote for this suggestion,
||| click the "I Agree" button in the message pane. If you do not see
||| the button, follow this link to open the suggestion in the Microsoft
||| Web-based Newsreader and then click "I Agree" in the message pane.
|||
||| http://www.microsoft.com/office/com...5b140e093555&dg=microsoft.public.officeupdate
Click to expand...
 
Top