IMAP integration body limited to 2048, was not an issue for imap_email_content

[ez12a]

The problem

Migrated recently from the imap_email_content integration as recommended in the UI.

I built some automation and conditions based on the body of the email, which was available with imap_email_content integration.

With the migration to imap_content event, the body is now truncated to 2048 bytes. The email body is HTML all that the sensor gets is HTML and truncated before any useful information from the body can be obtained. Is there a workaround for this? The change to limit the body size was introduced here #92055

Thanks!

What version of Home Assistant Core has the issue?

core-2023.5.2

What was the last working version of Home Assistant Core?

core-2023.3.x

What type of installation are you running?

Home Assistant OS

Integration causing the issue

IMAP

Link to integration documentation on our website

https://www.home-assistant.io/integrations/imap/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[home-assistant]

Hey there @engrbm87, @jbouwh, mind taking a look at this issue as it has been labeled with an integration (imap) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of imap can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign imap Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

imap documentation
imap source
_{^{(message by IssueLinks)}}

[jbouwh]

I understand your concern, the new implementation uses events, and there is a limit to the size of events. We had to choose a safe size to work with. In an email has a plain text part it will return that part in favorit to an html part (truncated to 2048 bytes).
It might possible to allow a larger part, but we need to make sure that the other elements like the message headers also fit in the event.

[jbouwh]

I have opened a PR to allow to increase the maximum message size to be passed in the event data.