Exchange 2010

Protect users from spam from your own domain in Exchange 2010 and Exchange 2007

One of the common complaints from users and many messaging folks is spam received from senders that appear to be from your own domain. SMTP mail is exchanged with anonymous Internet hosts without any authentication. Headers can be and are effortlessly spoofed. Rather than using an unregistered or invalid domain in the From: header, many […]

More →

HOW TO: Convert a user mailbox to a resource mailbox

When creating a new mailbox (or a mailbox-enabled user) in Exchange Server 2010/2007, you have the option of creating a user mailbox or a resource mailbox — the latter for conference rooms, or equipment such as projectors, etc. to allow your users to book these resources. If you’ve already created a user mailbox instead, and […]

More →

RFC 2821, HELO again: Validating the HELO/EHLO domain

RFCs 2821 and 1869 specify the format of HELO/EHLO commands issued by a SMTP client to initiate a SMTP session. RFC 2821 on HELO/EHLO command: 4.1.1.1 Extended HELLO (EHLO) or HELLO (HELO) These commands are used to identify the SMTP client to the SMTP server. The argument field contains the fully-qualified domain name of the […]

More →

Exchange Server 2007: Managing And Filtering Anti-Spam Agent Logs

Exchange 2007 includes a number of anti-spam agents to filter spam. The anti-spam agents log their actions in (anti-spam) agent logs. The default agent log locations: Exchange 2010: \Exchange Server\V14\TransportRoles\Logs\AgentLog Exchange 2007: \Exchange Server\TransportRoles\Logs\AgentLog Agent Log Configuration You can’t change the agent log location. Here are the available config options: Enable/Disable agent log: On transport […]

More →

Send as alternate email address in Outlook and Exchange

This is one of the more frequently asked questions in different forums and still a major annoyance – how do I send as an alternate address (aka proxy address or alias)? In most organizations, users have multiple email addresses to meet business requirements such as multiple business units, business names and domain names, mergers, acquisitions […]

More →

Exchange Server 2007: Why aren’t Managed Content Settngs applied?

In Exchange Server 2010 and Exchange 2007, you can apply Managed Folder Mailbox Policies to mailboxes to control message retention. Conceptually, this is somewhat similar to Recipient Policy with Mailbox Manager settings in Exchange Server 2003, which is commonly used by administrators to accomplish tasks like emptying users’ Deleted Items folders after a specified period […]

More →

How to turn off Back Pressure on Exchange Server

In Exchange Server Transport error: 452 4.3.1 Insufficient system resources we learned how the Back Pressure (Previous versions: Exchange 2010 | Exchange 2007) feature monitors resource consumption on Exchange Server and stops accepting new message submission if it’s low on resources. Update: In Exchange 2013, when the Transport service on a Mailbox server or an […]

More →

Back Pressure and Exchange Server Transport error 452 4.3.1 Insufficient system resources

In my hotel room in Orlando, getting ready for an Exchange 2007 transport presentation tomorrow morning at TechMentor. When trying to telnet to the SMTP port of an Exchange 2007 Hub Transport server, I got the following error: 452 4.3.1 Insufficient system resources Not a good thing the night before a presentation – Murphy’s law […]

More →

Locating Exchange Server 2007 CAS role in the perimeter?

Where should you locate Exchange Server 2007 servers with the Client Access Server (CAS) role? Is it more secure to locate them in perimeter network (aka “DMZ” or demilitarized zone)? Security folks in many organizations insist that any server that needs to be accessed from external networks (i.e. the Internet) should reside in perimeter networks. […]

More →

Add additional email addresses to a mailbox

In Exchange 2010/2007, you can use Email Address Policies to generate email addresses for your recipients (mailbox users, mail users, distribuiton groups, public folders, etc.). In Exchange 2003/2000, this was done by Recipient Policies. Policies are a great way to assign standardized email addresses across your organization – for example: <firstinitial><lastname>@<domain>. Users frequently request additional […]

More →

← Previous Entries

Next Entries →