unable to receive emails with large file attachments, running exchange 2010

When outside senders send emails with attachments over 10mb, they get the following NDR:
 5.3.4 Message size exceeds fixed maximum (state 18)

I went into exchange management console, hub transport, global settings, right click on transport settings, properties, unchecked max recieve size, max send size, which i assumed would default the max recieve size and max send size to unlimited.  then i went into services and restarted the microsoft exchange transport service.

However i tried sending an email with a large attachment from an external email and still received the same NDR at that email.

Was there something I overlooked or am i not doing something right?

Thanks.
clloccAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

AmitIT ArchitectCommented:
First check the header information from which server you are getting it. If you are getting from ISP end, then  you need to request ISP to increase the limit.
0
uescompCommented:
Couple things.  By default on exchange 2010 the limit is 10mb, this is also mainly standard across most ISP's because large emails cause bottlenecks when transfering that much data.  The easiest method is to do this via some sort of FTP and link the file.  For instance I use dropbox which is free for 2gb of ftp space.  I upload the file, and link it to the email so I send the email with a link for you to download vs sending the huge email.

There are many other ways to transfer large files via email, this is just the easiest way to do so.
0
clloccAuthor Commented:
Here is the message from the NDR:

Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 552 552 Backend Replied [689d97f4.0.585920.00-2084.860582.p02c11m104.mxlogic.net]: 5.3.4 Message size exceeds fixed maximum (state 18).

I dont think its our ISP.  I checked our spam filter and its set to allow messages of any size.  That's why I'm thinking its a setting change on exchange management console
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

suriyaehnopCommented:
If your ISP allow more than 10mb and you also confirm on spam filter also allow any attachment size. Then please check on "Receive Connector". Please change the size as well and restart the MS Exchange Transport services.
0
AmitIT ArchitectCommented:
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
uescompCommented:
"Google tried to deliver your message, but it was rejected by the recipient domain"  This clearly states that the target domain which I am assuming is yours rejected it.  Take a look at your connectors and verify you are set to unlimited.  I would not say it was spam because the message was returned by your exchange server so that states you hit the server. Unless your spam filter is on the server itself and not in front of it.
0
clloccAuthor Commented:
http://exchangepedia.com/2007/09/exchange-server-2007-setting-message-size-limits.html

Went through all the steps in the kb you listed and even restarted our server however still getting the following NDR when I email from an external email address:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 552 552 Backend Replied [82fe97f4.0.1530058.00-2375.2134404.p02c12m092.mxlogic.net]: 5.3.4 Message size exceeds fixed maxim (state 18).

Will i need to give it additional time?
0
uescompCommented:
Well as stated before you would check your recieve connector.

Open up EMC (Exchange Management Console)
Server Configuration > Hub Transport > Client Recieve connector.   Open up properties, on the general tab look at Maximum Message Size, same goes for the default.

Next check the mailbox you are trying to deliver too.

Recipient Configuration > Mailbox > Open properties of targeted mailbox > Mail Flow Settings Tab > Message Size Restrictions.  Check the receiving message size limit.
0
clloccAuthor Commented:
Open up EMC (Exchange Management Console)
Server Configuration > Hub Transport > Client Recieve connector.   Open up properties, on the general tab look at Maximum Message Size, same goes for the default.

Next check the mailbox you are trying to deliver too.

Recipient Configuration > Mailbox > Open properties of targeted mailbox > Mail Flow Settings Tab > Message Size Restrictions.  Check the receiving message size limit.

That did it!  I was checking the hub transport options under organization, didnt think to check server configuration as well.  Once I set the limits under server configuration, I received my test email!

Also, I wouldnt mind the dropbox solution, but the main issue was that our users (dept heads actually) wanted to receive emails with large attachments from external emails.  Now that its working, i wont have to frantically scramble to configure these settings at the time of, they are already set in place, giving me one less headache.
:D

Thanks!
0
clloccAuthor Commented:
Thanks for the help.  I had followed half that guide (similar instructions found via googling) before posting on EE, but i felt that there was one setting that was missing.  user suriyaehnop mentioned to check the receive connector but didnt provide how to get there, and i assumed that I had already checked.  it was when user uescomp provided exactly how to get to the receive connector's settings was I able to configure the settings correctly.

Thanks for all the help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.