Attached assets for email notifications are silently dropped over 15 mb

[MoritzLost]

Describe the bug

Our client reported an issue that they have attached an asset to an email notification, but the attachment isn't sent with the email.

I found that Formie has a hardcoded limit for attachments at 15 mb:

// Check if the asset it over 15mb (a reasonable threshold)
if (($asset->size / 1000000) > 15) {
    Formie::info('Not attaching “' . $asset->filename . '” due to large file size: ' . $asset->size . '.');

    continue;
}

Looks like the attachment is just silently dropped if the attachment is larger than the specified size.

I can understand the intention – a lot of email servers will reject emails with large attachment. However, the implementation needs some work.

Some suggestions:

• Make this limit configurable, so we can specify the maximum allowed attachment size.
• Enforce the limit (whether it's the current or the newly configurable limit) in the interface. If the selected asset is above the limit, prevent the notification from saving and show an actionable error message.
• Provide alternatives for large attachments – for example, have an option to just inject a link to the selected assets into the email?

Steps to reproduce

1. In any form, open the Email Notifications tab and create a notification.
2. In the notification, open the Advanced tab and select an asset with a size over 15 mb under Attach Assets.

Form settings

N/A

Craft CMS version

5.8.22

Plugin version

3.1.18

Multi-site?

No

Additional context

No response

[engram-design]

Agreed about making the limit configurable, it's a quick fix to prevent emails from not being delivered. I'd like to think this be set at the plugin level, rather than the individual notification. Purely, because it's an email provider-wide setting, rather than being dependent on a single notification.

The only concern at the moment is that this applies to both static assets you pick in the notification and File Upload field assets. I'll just need to do a little shifting of things.

Switching to an injected link is a neat idea, although possibly a little overkill and hard for content editors to manage. I'd probably recommend people to just add the link to the asset in the email content in that scenario. Then they can at least control where the link is, what text to show, etc.

[MoritzLost]

@engram-design Absolutely, this can be a global plugin setting. As long as the limit is displayed in the interface and enforced in some way that authors are informed about the problem, that's perfectly fine. I don't think I would even raise this limit, as many email providers won't let the email through then.

Switching to an injected link is a neat idea, although possibly a little overkill and hard for content editors to manage. I'd probably recommend people to just add the link to the asset in the email content in that scenario. Then they can at least control where the link is, what text to show, etc.

I did that for now, that works well. Advised the client to just get the direct asset link from the Assets library and then paste that into the email body. That's more reliably for large assets anyway 👍