Splunk Dev

Escaping / Lifting Message size fixed limit

Barty
Explorer

Good afternoon all,

Hoping this will be a very quick fix - one of our business users has a scheduled report that when run, produces an email attachment (CSV) of around 12MB in size. However, the email is not generating despite the success of the schedule due to the following:-

ERROR:root:(552, '5.3.4 Message size exceeds fixed limit

I have searched through here and can see varying responses as to how to increase the action.email.maxresults, but this isn't the issue, the issue seems to be a limit of around 10MB on the email / attachment from the resulting report. Our internal mail size limit is 25MB so i'm fairly confident that it is not our internal throttle controls.

Could someone advise me as to where this default limitation could be lifted / increased? I cannot see an obvious entry within the limits.conf (but leads me to believe i need to therefor add one?).

Bart

Tags (1)
0 Karma
1 Solution

xpac
SplunkTrust
SplunkTrust

Hey, that's actually a message from your mail server.
SMTP error 552 relates to the mail being too big. CSVs can get quite big, as they get no compression, and also because of how data attachments in mails work, the actual mail is about 33% bigger than the CSV that's attached to it.

Long story short - your attachment is too big for your mailserver, so you either have to get your mail server admin to raise that limit, or reduce the size of the report.

Hope that helps - if it does I'd be happy if you would upvote/accept this answer, so others could profit from it. 🙂

View solution in original post

0 Karma

Barty
Explorer

Spot on! Thank you for confirming, I'll go back to the business as there is no way that I will get the mail limit increased

0 Karma

xpac
SplunkTrust
SplunkTrust

PS: You can contact Splunk support and put your vote to enhancement request SPL-142222, that I field a few days ago.
It's asking to allow having attachments to alert mails compressed, which would most likely reduce their size a lot. 🙂

0 Karma

xpac
SplunkTrust
SplunkTrust

Hey, that's actually a message from your mail server.
SMTP error 552 relates to the mail being too big. CSVs can get quite big, as they get no compression, and also because of how data attachments in mails work, the actual mail is about 33% bigger than the CSV that's attached to it.

Long story short - your attachment is too big for your mailserver, so you either have to get your mail server admin to raise that limit, or reduce the size of the report.

Hope that helps - if it does I'd be happy if you would upvote/accept this answer, so others could profit from it. 🙂

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Event Series: Telemetry Pipeline Management

Balancing Scale and Spend: Gaining Control Over High-Volume Metrics in Splunk Observability Cloud As ...

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...