KamoCRM

Stop capping every send at 1MB, so a pasted image can actually go out

FixEmailService
Shipped
6 ஆகஸ்ட், 2026 அன்று 8:28 PM UTC
Author
Kamo
Commit
2b23346

Composing with a pasted image failed with a bare "Failed to send email". The composer inlines the paste into the body HTML as a base64 data URI, which rides in the multipart "email" JSON part, and Tomcat rejected that part at 1MB: FileSizeLimitExceededException: The field email exceeds its maximum permitted size of 1048576 bytes 1048576 is Spring Boot's default, not the 25MB both config files declared. The declarations were dead — MultipartProperties binds spring.servlet.multipart and nothing else, and the limits sat under server.servlet.multipart, which no binder reads. YAML that binds to nothing parses fine and logs nothing, so this capped every send with an attachment or inline image and never said why. Move the limits under spring.servlet.multipart in both the local config and the ConfigMap that actually runs in the cluster. The new test binds each file the way Spring Boot binds it, so a limit parked under a key nobody reads fails in CI instead of in production.

All changes

Like what you see shipping?

All of it arrives in your workspace on its own. Start on the free plan and read this page again in a month.

Start Free ForeverView Pricing