Was mucking around and decided to send some large files (over 10 mb) between email systems, but they didn’t arrive. Hmmm

After checking that all the standard settings for message limits where okay, things still weren’t working.

A bit of Googling stumbled on to this Basically each connector (both send and receive) in Exchange 2007 has a 10mb limit by default.

Get-SendConnector | list and Get-ReceiveConnector | list show this very clearly (ish)

Time to change that!

On the Internal Exhange 2007 box from Powershell:

Set-SendConnector –IDENTITY “Internet” -MaxMessageSize 50MB

SET-ReceiveCONNECTOR –IDENTITY “EX\Default EX” –MaxMessageSize 50MB

Then on the Edge Connector server

Set-SendConnector –IDENTITY “Sending to Internet” -MaxMessageSize 50MB

Set-SendConnector –IDENTITY “Sending to LAN” -MaxMessageSize 50MB

SET-ReceiveCONNECTOR –IDENTITY “External Inbound” –MaxMessageSize 50MB

SET-ReceiveCONNECTOR –IDENTITY “Intenal Outbound” –MaxMessageSize 50MB

Well, that sorted the bugger! I was freely sending up to 50MB files backward and forward.

(-IDENTITY is the name of the exact connector displayed from the Get commands above)

Certain file types, mainly .exe were being deleted and replaced with a simple .txt with the name of the deleted file attached to the original email. So I got evil.exe.txt rather than evil.exe.

I turned to Google for Powershell commands on how to configure the Edge server, since the GUI showed nothing active in the Transport rules tab.

Found this command Get-TransportAgent cmdlet to view the configuration of a transport agent on a computer that has the Edge Transport server role or the Hub Transport server role installed in a Microsoft Exchange Server 2007 organization.
http://technet.microsoft.com/en-us/library/bb123536(EXCHG.80).aspx

[PS] C:\Documents and Settings\Elvis>Get-TransportAgent

Identity Enabled Priority
——– ——- ——–
Connection Filtering Agent True 1
Address Rewriting Inbound Agent True 2
Edge Rule Agent True 3
Content Filter Agent True 4
Sender Id Agent True 5
Sender Filter Agent True 6
Recipient Filter Agent True 7
Protocol Analysis Agent True 8
Attachment Filtering Agent True 9
Address Rewriting Outbound Agent True 10

This lead me to believe my naughty server was blocking by default and this proved me right:
http://technet.microsoft.com/en-us/library/aa997139(EXCHG.80).aspx

By the magic of changing Enable to Disable, I modify the Powershell command and ran it.

Disable-TransportAgent -Identity “Attachment Filtering agent”

[PS] C:\Documents and Settings\Elvis>Get-TransportAgent

Identity Enabled Priority
——– ——- ——–
Connection Filtering Agent True 1
Address Rewriting Inbound Agent True 2
Edge Rule Agent True 3
Content Filter Agent True 4
Sender Id Agent True 5
Sender Filter Agent True 6
Recipient Filter Agent True 7
Protocol Analysis Agent True 8
Attachment Filtering Agent False 9
Address Rewriting Outbound Agent True 10

And as if by magic, my .exe came through to Outlook untouched.

Hopefully, a useful reference if other oddities happen again!

Should reaaaaaallllly think about learning PowerShell sooner rather than later …