> ## Documentation Index
> Fetch the complete documentation index at: https://docs.talario.eu/llms.txt
> Use this file to discover all available pages before exploring further.

# Limits

> Size, volume, retention and parser limits for receiving.

## Receiving limits

These limits apply per project. Contact us if you need higher limits.

| Limit | Value |
| - | - |
| Size of a message | 25 MiB (26,214,400 bytes) |
| Envelope recipients per message | 50 |
| Messages per rolling 24 hours | 500 |
| Storage of received messages | 100 MiB |
| Retention | 7 days |

A message counts once per project, however many recipients and webhooks it has. Webhook retries do not count. Storage is reserved until the message expires.

When a limit is reached, Talario rejects new messages **temporarily** during the SMTP session (`4xx`). Sending mail servers keep the message in their queue and try again later; nothing is lost on Talario's side.

## Parser limits

| Limit | Value |
| - | - |
| Nested MIME levels | 30 |
| MIME parts | 1000 |
| Attachments | 100 |
| Parsed content (JSON without links) | 8 MiB |

A message above a parser limit is still accepted and stored. Its parsed content has `parse_status: failed` with a [code](/receiving/parsed-content#parse-status-and-warnings) for the limit; the original message stays available.

## Webhook limits

| Limit | Value |
| - | - |
| Connection timeout | 10 seconds |
| Total time of an attempt | 120 seconds |
| Response body read | 64 KiB, then discarded |
| Automatic retries | until 24 hours after `received_at` |
| Inline content in payload version 2 | 1,000,000 bytes, see [`content_omitted`](/webhooks/payload-v2#large-messages) |

## API limits

See [rate limits](/authentication#rate-limits).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.