Microsoft Exchange Server related News and Articles

Mostly we create Exchange Transport Rules Condition using the criteria’s like “when FROM address ...”, When recipient ...” “When user from inside/outside organization” etc. Recently I have come across to create a rule for filtering the emails from internet groups, and the from address will always shown as the primary email address of the sender which could be always well known internet domains like gmail.com, yahoo.com etc, not the news group domain name. Most of the company wanted the email traffic from those public domains, by restricting the email traffic which are send to common groups (news group, community groups and other non-business groups).

To work with such request in transport rule, you can use the condition “When the message header matches text patterns”. Before we create any rule, let’s look at the header of one such email and decide on the parameter which can be used for filtering such emails (common criteria for all such emails).

Look at the part of a header; I have selected the “Reply-To” field to create the condition for the transport rule. You can see that the from address will be always(mostly) the sender address, hence the filteration is not that easy using the common conditions, as that can cause stopping the entire email from the common public email domain.

Tags:

• exchange 2007
• exchange 2010
• hub transport rule
• message header

Read more... Add new comment

If there’s one thing an Exchange admin is used to doing, it’s monitoring disk utilization on their mailbox servers. Users hoard email like gold, and as mailbox databases increase in size, backups take longer, restores can exceed recovery time objectives (RTO), and servers can run out of disk space. Admins might look to quotas to reign in runaway mailbox sizes, but those that implement quotas soon find that all this does is force users to move email to PST files, which brings a whole new crop of problems. Performance problems, corrupt files, and data loss all pop up, all that email is still consuming disk space; they’ve simply shifted the load from the mailbox servers to the fileservers. Fortunately, there’s a better answer to the problem of email storage. Email archiving can solve all of these issues without introducing any of the problems associated with other ways to manage email storage. By bolting on email archiving to an existing Exchange infrastructure, users can continue hoarding email, database sizes can remain manageable, and admins can focus on more important issues. Let’s look at three of the best reasons why you need email archiving.