552 message size exceeded

Hi,
We are having a problem with just one particular company sending attachments to us. Normal email with no attachments is coming in fine. email with attachments is not.
The sender (i.e at the other company) is getting the following message when they try to send to us :
"The e-mail system was unable to deliver the message, but did not report a specific reason. Check the address and try again. If it still fails, contact your system administrator. #5.0.0 smtp; 552 size limit exceeded"
The message attachment is small about 900K and we regularly receive stuff up to 20Mb. If the same attachment is sent from a different email system to us it comes straight in.
Has anyone got any advice ?
cheers
Chris

Check your host access table. This one company probably has a lower reputation score, matching a different rule in the HAT than the other companies.
If i'm not mistaken, the default maximum message size for the throttled policy is 1M. With the overhead you get when sending email attachments, this will probably block files of 900K.

Similar Messages

552 Message size exceeds maximum message size

[Dell Inspiron 560 desktop;
MS Windows 7 Home Premium SP1 64bit; Windows Live Mail 2011; MS Word Pro 2003; Mozilla Firefox 22.0; Adobe FP 11,8,800,94; Adobe Reader 11.......]
Hello, I have the same problem, 10 emails I sent out bounced with the following same error message:
">>>xxxxxxxxxatxxxxxxxx.co.il(reading confirmation): 552 Message size exceeds maximum message size"
And they also sent the headers....which is all Greek to me. Being a very beginner computer user, I can't execute the good advice given here.
This is very strange since the emails so bounced only had 5 small pictures I had taken in my small, cheap dig camera, while other messages I had sent out
successfully before were probably 4 times as big.
Also, whose fault is it: my server RCN? Microsoft? I wonder...
I hope there's something easier for me to do to fix this problem?
Thanks ever so much for any help! :) Adela

It says to me that the message you sent was rejected along the way because it was too big. Ask the e-mail administrator of the system that's bouncing it.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

ORA-29279:SMTP permanent error:552 5.3.4 Message size exceeds fixed maximum

Hi,
I can send attachments smaller than 25MB.
But my attachment is 27MB and it fails. Don't ask why I need to send this big file by email, I have to.
Where can I change this maximum size?
- any parameter in utl_smpt?
- any parameter in server where DB is located? (Linux 2.6.18-238.1.1.el5)
- any parameter in smtp machine server?
Thanks.
Joaquín González
Edited by: Joaquin Gonzalez on Apr 12, 2012 11:46 AM

The actual error, "+552 5.3.4 Message size exceeds fixed maximum+", is from the smtp server. Oracle expects a 0 return code and instead get a 522 return code in the smtp server's response (to the DATA command). So Oracle throws an exception that in turn contains the error response of the smtp server.
Interesting that you did not get the error earlier - many smtp servers have the ceiling set a lot lower and you can expect this error after sending around 5MB of data.
There are ways around this. Send the attachment as multiple fragments using a compression technology like zip or rar (where it is fairly easy for the recipient to reconstruct the source from the pieces send).
There's also another problem. The 20+ MB e-mail may be accepted by the smtp server, but the POP3, IMAP (or Exchange?) account (mail drop) may not accept an e-mail of that size.
Success is also assuming that you are delivering that mail directly to the correct/target smtp server. If not, then that e-mail needs to be relayed via a number of intermediate smtp servers before reaching the target smtp server and domain.
And there is a good chance that one of these relay servers will object to the size of the e-mail and trigger a hard bounce response.
Keeping an attachment size down to at most 3 to 5 MB is IMO the better approach as that guarantees a better chance of delivery than a 20+ MB e-mail.

Incoming message size exceeds the configured maximum size for protocol t3

Hi All,
I've encountered an error as follow:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size 50004000 bytes exceeds the configured maximum of 50000000 bytes of protocol t3.
But the request message is only 3MB, why it is enlarged to over 50M?
There is a For Each loop section in main flow, is it because for one loop, there will be a copy of request message?
How to enlarge message size for protocol t3?
Go to server/protocol and change 'Maximum Message Size' for AdminServer, OSB Servers and SOA servers?
Thanks and Regards,
Bruce

Hi,
1) After setting -Dweblogic.MaxMessageSize to 25000000
<BEA-000403> <IOException occurred on socket: Socket[addr=ac-sync-webserver1/172.24.128.8,port=9040,localport=36285]
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '25002240' bytes exceeds the configured maximum of: '25000000' bytes for protocol: 't3'
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:174)
2) After setting -Dweblogic.MaxMessageSize to 50000000
<BEA-000403> <IOException occurred on socket: Socket[addr=ac-sync-webserver2/172.24.128.9,port=9040,localport=59925]
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '50000400' bytes exceeds the configured maximum of: '50000000' bytes for protocol:
't3'.
And even after setting various values for -Dweblogic.MaxMessageSize , issue weblogic.socket.MaxMessageSizeExceededException was observed.
To overcome the issue set Manual Service Migration Only as after several experiments and replicating the issue it was found out that in case of no available pinned services, must set the migration policies of the migratable targets on "Manual Service Migration Only".
And once it is corrected; it was noticed that weblogic.socket.MaxMessageSizeExceededException issue also resolved.
WebLogic Server can fail over most services transparently, but it's unable to do the same when dealing with pinned services.
Pinned Services : JMS and JTA are considered as pinned services. They're hosted on individual members of a cluster and not on all server instances.
You can have high availability only if the cluster can ensure that these pinned services are always running somewhere in the cluster.
When a WebLogic Server instance hosting these critical pinned services fails, WebLogic Server can't support their continuous availability and uses migration instead of failover to ensure that they are always available.
Regards,
Kal

Maximum message size problem

Hello,
I'm trying to send a message of 30MB and the log reports:
"552 5.2.3 sorry, that message size exceeds the maximum "
After configuring sourceblocklimit and blocklimit in channels parameters the message still apears.
I have compiled :/opt/SUNWmsgsr/sbin/imsimta cnbuild
/opt/SUNWmsgsr/sbin/imsimta restart dispatcher
and restarted services.
What else should I change to send the message?
Thanks in advance.

the log looks like:
31-Mar-2005 18:31:45.20 tcp_intranet tcp_local E 36763 [email protected] rfc822;[email protected] [email protected]
31-Mar-2005 18:31:48.89 tcp_local R 36763 [email protected] rfc822;[email protected] [email protected] dns;gsmtp185-2.google.com (TCP|200.12.176.35|43298|64.233.185.114|25) (mx.gmail.com ESMTP 16si699150wrl) smtp;552 5.2.3 sorry, that message size exceeds the maximum
The messages is enqueued, so this tells me that limitation is outside?

WLS7 JMS Max Message Size

          I have done a search and found many questions on Max Message size, but I didnt
          find any relating specifically to WLS7.
          Q1: Is there a JMS Message Size limit the same as the T3 Max Message size?
          Q2: Does the WLS JMS implementation "chunk" large JMS messages into multiple T3
          messages?
          Cheers,
          Nick


Hi Nick,
          The performance is hard to predict. It is highly dependent on message
          type, application overhead, persistence, store type, CPU and network
          speed, etc., so you will need to measure it yourself. I think you will
          find that once message size exceeds 100K, perhaps less, perhaps more,
          JMS throughput is directly proportional to message size. (eg. it takes
          the same amount of time to send 10 100K messages as it does to send 1
          1MB message.)
          I understand what your "chunking" question were about now. You may
          find it useful to know that since its earliest releases, WebLogic
          outbound requests from one JVM to another are "single threaded" from a
          layered application's point of view: outbound traffic from one
          application must wait until previous requests posted by other apps are sent.
          Tom, BEA
          Nick Minutello wrote:
          > Thanks Tom, for the answers.
          >
          > My questions, I guess, are getting to the bottom of whether I can send huge messages
          > over WLS JMS - in the region of 10's of megabytes.
          >
          > Naturally, I can always send smaller messages - but there are occasions where
          > I have very large messages (files, in fact) and I prefer to have all processing
          > on the server side rather than the JMS client side.
          >
          > What are your thoughts?
          >
          > -Nick
          >
          >
          > Tom Barnes <[email protected]> wrote:
          >
          >>Hi Nick,
          >>
          >>Nick Minutello wrote:
          >>
          >>>I have done a search and found many questions on Max Message size,
          >>
          >>but I didnt
          >>
          >>>find any relating specifically to WLS7.
          >>>
          >>>Q1: Is there a JMS Message Size limit the same as the T3 Max Message
          >>
          >>size?
          >>
          >>Up to 7.0 there is no configurable for JMS max message size. In 8.1
          >>
          >>(public beta soon) it can be configured on the JMS server and/or on the
          >>
          >>JMS destination. In either case, the T3 max message size is a limiting
          >>
          >>factor.
          >>
          >>One thing to be aware of is that WL JMS aggregates asynchronous messages
          >>
          >>when pushing from server to asynchronous consumers - producing larger
          >>T3
          >>messages which can hit the T3 max limit. The number of messages that
          >>
          >>get aggregated is configurable on the WL connection factory
          >>(MessagesMaximum).
          >>
          >>
          >>>Q2: Does the WLS JMS implementation "chunk" large JMS messages into
          >>
          >>multiple T3
          >>
          >>>messages?
          >>
          >>Yes and No. (WebLogic "chunks" internally at the T3 layer, not the JMS
          >>
          >>layer.)
          >>
          >>
          >>>Cheers,
          >>>Nick
          >>
          >>Tom, BEA
          >>
          >
          >

MSG size exceeded

Hello ,
i hope i become an answer to this problem:
we use C600 Machines , and every time a msg size is exceeded
the customer becomes a Notification that your msg size is exceeded.
BUT i cant see any entry in Ironport Log files
ONLY this:
New SMTP ICID xxxxxxxx
ICID xxxxxxxx RELAY SG CUSTOMER match IP .....
ICID xxxxxxxx close
is there any possibility in this case , that i see msg's in Logfiles ?
THX in advance
buzz

I believe both of these happen on the IronPorts, it depends more on the sending MTA than the recieving IronPort.
It all depends on if the sending MTA honors the EHLO SIZE limit feature and does not attempt a message larger than the advertize max. In this case you have a simple ICID xxx close, because the sending MTA did not hit the size limit it simply closes the connection and generated a NDR to the sender saying the message size was beyond what the recieving MTA would accept before it even attempted to send the message.
Second case is when the sending MTA does not use the EHLO SIZE limit feature and sends the message forcing the IronPort to hard reject the message once it hit the max size limit, hence the ICID xxx Receiving Failed: Message size exceeds limit. Same NDR gets generated, but after the wasted bandwidth. :(
Erich

Exchange 2007 send connector does nor respect Maximum message size (sometimes...)

Hi to all
We have 9 email server, 5 Mailboxes, 2 CAS and 2 HT, We began to have problems to send and receive from internet; so I checked the queues and I discovered that some users are sending messages with a size greater than 16 MB, althought internally can send
until 40MB, if they send externally, only until 16MB.
I revised all the configuration:
Organization Configuration/Hub Transport/Global Settings/ Maximum send size (KB):40960
Server Configuration/Hub Transport/HT01/Receive Connectors/Default HT01/Maximum message size(KB): 40960 (only this server can send outside, the other server is in spare)
Organization Configuration/Hub Transport/Send Connector/SendMailOuside/Maximum message size(KB) 16386
We send by an Smart host that is used only by the HT01 to a Symantec server.
With this, we have this situations:
In the queue, I see some users are sending emails with a size more than 16MB outside the organization, I revised their configuration and the "maximun send size" is clear the checkbox (just like my account), the weir is if I try to send an email
with a size more than 16MB, I got the message: "#550 5.3.4 ROUTING.SizeLimit; message size exceeds fixed maximum size for route ##", this is not sense because their account configuration is the same like mine, so the Exchange must not let
them to put the email in the queue...
If between internal users try to send an email with size more than 16MB, this is allowed and it's send without any problem
So I don't know where is the misconfiguration, is permited to send mails with size less than 40MB internally, but externally only until to 16MB, but I din't know why the Exchange system let some users to send (or at least put in the queue) this kind of messages,
my account is in the same DB like the other users...
I hope to be clear in the description of the situation, maybe a patch or some thing, the HT server has the January patch and in april will be applied the last patchs.
Doc MX

Hi DocMX,
Thank you for your question.
We could run the following command:
Get-TransportConfig | FL max*size
Then, we could check the send connector by the following command:
Get-SendConnector | FL Identity,MaxMessageSize
We could run the following command to check an individual user maximum size.
Get-Mailbox <username> | FL Name,Max*size
In my solution, we could rebuild the user profile that those users could send emails more than 16MB to check if the issue persist.
We could also restart the service of “Microsoft Exchange Transport”.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

#5.3.4 message header size exceeds limit

Hi !
We are getting this bounce error message from our customers trying to send emails to our newly built C370 Ironport box.
Here is the error message;
"The following message to [email protected] was undeliverable.
The reason for the problem:
5.3.0 - Other mail system problem 552 - '#5.3.4 message header size exceeds limit'"
Hope is Delivery Satus Notification will help to identify what the problem is about.
Appreciate your kind response on how to fix this issue.
Best Regards,
Ruveni

Hi Ruveni,
Please check our following knowledge base article which explains this error and provide solution for it.
Message Bounces with "552 #5.3.4 message header size exceeds limit"
http://tinyurl.com/2yw579
Hope this helps!
Regards,
Viquar
Customer Support Engineer

Outlook 0x80040610 exceeds message size

I am using outlook 2003 to connect to exchange and when I send an email
with attachment that is over 10MB I get error 0x80040610 "the message
size being sent exceeds the message size established for this user"
get-sendconnector shows all send connectors have a maxmessagesize of 150MB
get-recieveconnector shows all recieve connectors have a maxmessagesize of 150MB
get-transportconfig shows MaxSendSize is unlimited
get-Mailbox shows MaxSendSize is unlimited.
I can recieve large emails fine. I am pulling my hair out over this....
Any help would be appreciated.
Mike

From my recent experience "Unlimited" means "Unlimited" up to the Global Message Delivery Limit
You can change this from either the Exchange 2003 console in a mixed 2003/2007 environment or ADSIEDIT in a pure Exchange 2007 environment.
More information can be found here:
http://technet.microsoft.com/en-us/library/bb124345.aspx
http://technet.microsoft.com/en-us/library/bb310771.aspx
Cheers,
Rhys

The following files weren't attached because adding them would cause the message to exceed the maximum size limit of 35 MB: MALAWI .pptx.

The following files weren't attached because adding them would cause the message to exceed the maximum size limit of 35 MB.
I have had my macbook pro since June and have had no problems sending an email until I have tried to send a presentation today. The above message is what I keep receiving even after using 3 email accounts.

Email providers often set file size limitations to conserve bandwidth and prevent service overload. Most common seems to be a limit on the order of 21 MB. If possible, break your presentation into two parts and send as two messages.

The following files weren't attached because adding them would cause the message to exceed the maximum size limit of 10 MB

Dear sir/madam
I installed exchange server 2013
my clients want to attache more than 10 MB
when they attache more than 10 MB they got this massage "The following files weren't attached because adding them would cause the message to exceed the maximum size limit of 10 MB"
so how can you help me to increase the attachment size and the way to do that
how can I change the default 10 MB
Please can you help me as soon as
Rawa Zangana

Hi Rawa,
You can use EAC or EMS to set the MaxSendSize. The default value of MaxSendSize is 10 MB.
If you use EAC, here is the steps:
Logon to EAC -> Mail flow -> Receive connectors -> settings-> type the Maximum send message size you want to set
If you use EMS, please use the cmdlet Rajith provided.
Hope it helps.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Essbase Error:Set is too large to be processed. Set size exceeds 2^64 tuple

Hi,
we are using obiee 11.1.1.6 version with essbase 9.3.3 as a data source . when I try to run a report in obiee, I am getting the below error :
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 96002] Essbase Error: Internal error: Set is too large to be processed. Set size exceeds 2^64 tuples (HY000)
but if I run the same query in excel add in, I am just getting 20 records . wondering why I am getting this error in obiee . Does any one encountered the same issue ?
Thanks In advance,

Well if you want to export in I think you have to manually do it.
The workaround it to open your aperture library by right clicking it and show contents...
Then go into your project right click show contents...
In here there are sub folders on dates that the pictures were added to those projects. If you open the sub folder and search for your pictures name it should be in that main folder.
You can just copy it out as you would any normal file to any other location.
Voila you have manually exported out your file.
There is a very similar post that has been close but again you can't export the original file that you are working on - FYI http://discussions.apple.com/thread.jspa?threadID=2075419

One of the BizTalk Server processes in the affected computer is being throttled for significant periods because of high database size exceeding the threshold

Hello Experts,
I have complex Biz Talk 2013 farm having 20 servers,15 Hosts. In my production environment even if there is no traffic i am getting throttling errors from SCOM for my all the production hosts.
Error : One of the BizTalk Server processes in the affected computer is being throttled for significant
periods because of high database size exceeding the threshold
I checked following things:
1. MsgBoxDB size 748732 KB
2. Spool table size 53 MB
3. Tracking DB size 26724 KB
4. Host settings -- Message Queue Size = 100, MsgCount = 50000 , Spool MP = 10 , Tracking MP = 10
5. Ran Message Box viewer and did not found any error related to DB size. (which counter i should focus on in MBV)
Note -- for DB i am sharing full backup size because it does not have log file size.
Please suggest where i should focus?
Is SCOM reporting correctly because everything is fine in biztalk ?
Thanks
Yagya
https://www.mcpvirtualbusinesscard.com/VBCServer/card.aspx?tag=YagyaDattMishra&wa=wsignin1.0

Hi Yagyam
I remember this error from SCOM when you use the standard SCOM BizTalk pack.
Check the eventlog of the server, do you see any errors in event log, this could give some clue to the root cause. Whenever you have this alert from SCOM, you must have
some entries in eventlog relating to the alert raised by SCOM.
Is your message processing by BizTalk hosts are normal? Run the performance monitor to see the bottleneck. Check if there is really throttling.
As mentioned in this blog, check the state of the SQL Agent on BizTalk's SQL database server, may be try restart the SQL Agent on BizTalk's SQL database server.
http://blogs.msdn.com/b/timdel/archive/2008/11/19/why-i-love-scom.aspx
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

SOAP message size limitation for sender soap adapter

Hi All,
We are facing critical production issue in case of sender SOAP Adapter,
If the sender soap message is having 114359 Bytes than the Third party is getting exception and SOAP request is not reaching XI.
If the message size is less then 100kbytes then no exception will come.
Is this a limitation that SOAP message size should not exceed 100kbyte?
Thnaks in advance
Best Regards,
Harleen Kaur Chadha

Hi ,
Thanks for your inputs,Could you please tell me which hardware configurations are you talking about?
Are you people talking about harware configurations for XI?
Best Regards,
Harleen Kaur Chadha

552 message size exceeded

Similar Messages

Maybe you are looking for