Receive limit on Exchange 2007

could be due connection time out, what is the NDR.

Could you give an example of the bounce message that is received?

Can you give us a copy past of the result of this command in EMS: "Set-Transportconfig –maxreceivesize"
What's the maximum message size on the Mailbox DB?

Michael

Hi,
I've attached a read out of the get-transportconfig command, and below is part of the bounce back i get.

"Remote host said: 552 5.3.4 Message size exceeds fixed maximum message size."

Sorry here's the attachment!

Is it possible there is no attachment? :)

Ok, seems that the ReceiveSize is correct.

How about user limits? Take a look at the Get-Mailbox command and check if the user(s) has another limit.

No that's not possible, I'm sending them in myself and can confirm i have attached a 10MB PDF.
I've restarted the transport server after making sure all these settings were correct, but still no luck.

You mean that you're trying to send them internally?
Are there any AD Site links in place?

Take a look at this guide, it might help you :)

http://exchangeshare.wordpress.com/2008/04/24/exchange-2007-where-to-set-message-mail-size-limit/

I've just ran a get-mailbox "User name" and the only perimeter it comes up with is prohibitsendquotat = 2GB

Hi,
no it's an external sending (Like Gmail) trying to send into an account on their domain.

have you restarted the transport service to apply the config ?!

try this one:

get-mailbox "Mailboxnamewithissue" | ft name, *max*

this should give you some information on the maximum message size for that mailbox...

Yeah I've restarted that service but it didn't help.

do you have any SMTP filtering in front of the Exchange server

No, no smtp filtering

Have you checked all limits as described in the guide?

I have gone through the 5 known areas that you can set a limit for receiving mails and configured them accordingly, but it still doesn't let them through.
It does seem to be an exchange-related-problem as we have multiple customer domains that run exchange 2007, each with completely different routing and they all bounce back.

Id there are any other areas you feel i should check let me know and i'll have a look.

It's weird. Normally that error points to a limit that's not set correctly either in the transportconfig, receive-connector, user- or server limits.

If you've checked that, I might be out of options right now.

could you maybe enable protocollogging for SMTP. Thay might point out something else maybe.

Thanks.

this is accepted as it was my comment and i sorted it!