Right now I'm still waiting for the ducks to decide if they want the
exceptions made by address or domain.

 

If it's by address, I think it's going to be a matter of adding the
exceptions as Contacts, adding those to a DL, and then adding a rule
exception for anything from that DL.  

 

If it's by domain, then the exception is going to have to be a regex
applied to the From: field.

 

If we do it by address it's more granular and higher maintenance, but I
can delegate the maintenance to someone else.

 

If' it's by domain then there's less maintenance, but I'm not handing
modification of regex's in transport rules over to the Help Desk.

 

________________________________

From: Don Andrews [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 27, 2008 11:20 AM
To: MS-Exchange Admin Issues
Subject: RE: Question about Exchange 2007 Transport Rules

 

I like your attitude about the ducks - we have similar issue but with
e2k3, but it is limited to service accounts (functional rather than
individual accounts) which we can identify via naming conventions - and
we handle it via a gateway product.

 

________________________________

From: Campbell, Rob [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 27, 2008 7:57 AM
To: MS-Exchange Admin Issues
Subject: RE: Question about Exchange 2007 Transport Rules

 

The external denied list is only about 8-10% of the users. We handle the
email for about 15 different companies within the org.  Some are more
demanding than others.

 

They got Exchange 2007 because Microsoft's salesmen did a really go job.

 

My job is to solve puzzles, and insane ducks seem to be pretty good at
coming up with them.

 

 

 

________________________________

From: Kevin Miller [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 27, 2008 9:48 AM
To: MS-Exchange Admin Issues
Subject: RE: Question about Exchange 2007 Transport Rules

 

So your problem is that you really need to find a new job, because your
ducks are drinking water outside of some toxic waste dump or something,
and they have done nuts.

 

 So they want an internal only email system, except for a few people?
And or a few external addresses. Why did they even get Exchange 2007? 

 

You can turn on off all SMTP email for X users if you want. Do your
ducks also block web access, and cell phone usage in the building?

 

From: Campbell, Rob [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 27, 2008 7:40 AM
To: MS-Exchange Admin Issues
Subject: RE: Question about Exchange 2007 Transport Rules

 

Mgmt decided that sending/receiving internet email was too much of a
distractionfor some people,  so they asked for a way to keep them from
sending or receiving email from outside the org.

 

No problem, create a DL, add a couple of transport rules, and it's done.

 

Then they started coming up with exceptions.  

 

 

 

________________________________

From: Kevin Miller [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 27, 2008 9:31 AM
To: MS-Exchange Admin Issues
Subject: RE: Question about Exchange 2007 Transport Rules

 

What problem are you trying to solve?

 

From: Campbell, Rob [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 27, 2008 6:03 AM
To: MS-Exchange Admin Issues
Subject: Question about Exchange 2007 Transport Rules

 

In the Exchange 2007 transport rules, are Contacts considered to be
Inside the organization, or Outside the organization?


************************************************************************
************************** 
Note: 
The information contained in this message may be privileged and
confidential and 
protected from disclosure. If the reader of this message is not the
intended 
recipient, or an employee or agent responsible for delivering this
message to 
the intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this communication is strictly prohibited. If
you 
have received this communication in error, please notify us immediately
by 
replying to the message and deleting it from your computer. 
************************************************************************
**************************

 

 

 


************************************************************************
************************** 
Note: 
The information contained in this message may be privileged and
confidential and 
protected from disclosure. If the reader of this message is not the
intended 
recipient, or an employee or agent responsible for delivering this
message to 
the intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this communication is strictly prohibited. If
you 
have received this communication in error, please notify us immediately
by 
replying to the message and deleting it from your computer. 
************************************************************************
**************************

 

 

 


************************************************************************
************************** 
Note: 
The information contained in this message may be privileged and
confidential and 
protected from disclosure. If the reader of this message is not the
intended 
recipient, or an employee or agent responsible for delivering this
message to 
the intended recipient, you are hereby notified that any dissemination, 
distribution or copying of this communication is strictly prohibited. If
you 
have received this communication in error, please notify us immediately
by 
replying to the message and deleting it from your computer. 
************************************************************************
**************************

 

 

 


**************************************************************************************************
 
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**************************************************************************************************
~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~
~             http://www.sunbeltsoftware.com/Ninja                ~

Reply via email to