Exchange 2007 transport rule, exemt an email address from max send limits

Posted on 2009-04-09
Medium Priority
Last Modified: 2012-05-06
I have recently installed Exchange 2007 SP1 and I have a Send Connector created on the Exchange 2007 server.  I have not yet moved over any mailboxes to the new server.  

By default, I know that the mail will prefer the new send connector.  

A couple of days ago I set a maximum message size limit to be 25 MB. (it was set as the default until that time). Soon after that I received a call that somebody was having trouble scanning to email.  I did some investigating and I found out that this person was using a scanner to send documents to their email address.  I did notice that the attachment sizes were greater than 25 MB.  

I disabled the maximum message size limit on the Send Connectors for the time being.  The receive connectors for the new Exchange server still has a 25 MB limit on it, I haven't changed that.  I don't think the receive connector will make a difference anyway.

The from address is HSCOPIER@TEST.COM  This email address is not in my AD domain as a valid address.

I'm kind of surprised that it hadn't failed before with the default settings and then just started having issues right after I changed it to 25 MB.

I would like to create some kind of transport rule that says: Emails coming from this copier can exceed the max send limit.  I went thru the Transport Rules wizard but I couldn't find any options to do what I'm trying to do.

How do I create a Hub Transport Rule to send email from the scanner to anybody and be exempted from the max send limit??
Question by:Florescu
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
LVL 65

Expert Comment

ID: 24115419
If the scanner is sending the email to an internal user then the Send Connector has nothing to do with the delivery of that email. Send Connectors are for outbound email FROM your server only.

If you want the scanner to be able to send messages to users on the server that are over the usual limit then I would suggest a new Receive Connector specifically for the scanner to use. With Exchange 2003 this is the same thing we would so with a second SMTP virtual server.


Author Comment

ID: 24116211
How would I set that up?  What settings in the Receive connector do I need to setup?  

I looked in the Properties sheet but couldn't really figure out how to set it up properly.
LVL 65

Expert Comment

ID: 24117311
The size restriction is not in the GUI.
You can setup the additional receive connector in the usual way, but to change its size restriction you need to use EMS:

Set-ReceiveConnector "Connector Name" -MaxMessageSize 50MB

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.


Author Comment

ID: 24117496
How is the receive connector going to know that it should be used for a particular user??  
How is the server going to know that it should use the new connector for the copier?

LVL 65

Expert Comment

ID: 24117779
You cannot restrict connectors to a specific user.

You would need to use some other means for the connector to be differentiated - separate IP address, custom port, something like that.

As long as the connector cannot be seen from the internet it cannot be abused.


Accepted Solution

Florescu earned 0 total points
ID: 24143798
I ended up calling Microsoft Tech support on this and we figured out that it was Trend Antivirus that was causing this.  I unloaded it and reset iis, then it started working just fine.  I did have exclusions setup for Trend but apparently they weren't working right.  I'll have to call Trend support on this.

One thing to note is that it was all going thru the old Exchange 2003 server, it wasn't even using Exchange 2007.  All of my email accounts are still on the old Exchange 2003 server, I haven't migrated any users yet.

I found out a few interesting things from Microsoft support.  The server looks at the send/receive limits this way:

1.      Exchange checks the Global settings (Send/Receive connectors, etc.)
Both incoming and outgoing email is first check by the Global level and proceed for categorization and at this level step 2 is followed
2.      Exchange then checks Transport Rules if any
3.      Exchange checks the user mailbox restriction

Note: which ever size restriction is less will take priority

Also, they said that I could setup a receive connector as a "relay" so that the copier could relay messages outside of the organization.  You can restrict the receive connector by specifying the IP address of the copier machine in the Remote section.  That's how the copier knows to use that connector.  You can in fact restrict the connector size in the GUI.  

The easiest solution for what I will be trying to do is to setup the global settings at 50 MB for example, then create transport rule that says "send a NDR if message size is greater than 25 MB", unless it's from the copier email address.  I did have to add the copier as a Mail Contact.  

Microsoft did recommend that I should set the 50 MB on all the receive/send connectors and globally as well under Hub Transport, Global Settings, Transport Settings.  Then you can restrict it down via the transport rules or at the user level.

Featured Post

 [eBook] Windows Nano Server

Download this FREE eBook and learn all you need to get started with Windows Nano Server, including deployment options, remote management
and troubleshooting tips and tricks

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If you troubleshoot Outlook for clients, you may want to know a bit more about the OST file before doing your next job. IMAP can cause a lot of drama if removed in the accounts without backing up.
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
This video discusses moving either the default database or any database to a new volume.

719 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question