Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/yugo412/laravel-maily/llms.txt

Use this file to discover all available pages before exploring further.

The limitations described on this page are determined by the Maily.id API, not by this package. yugo/laravel-maily passes through every capability the API exposes; as the API adds new capabilities, support for them will be added to the transport layer. This page documents the current state so you can plan your integration accordingly.

​
Unsupported features

Attachments

The Maily API does not currently accept file attachments. Any attach() call on a Mailable is silently ignored at the transport layer because the API payload has no attachment field.

Multiple recipients

Only a single to address is accepted per API request. Passing more than one To recipient causes MailyTransport to throw a MailyException before any HTTP call is made.

CC recipients

Carbon-copy (CC) recipients are not supported. The API payload does not include a cc field, so any addresses added with ->cc() will not receive the message.

BCC recipients

Blind carbon-copy (BCC) recipients are not supported. Like CC, the API has no bcc field and any addresses added with ->bcc() will be silently dropped.

​
Sending to multiple recipients

Because the API only accepts a single to address, you must send individual requests for each recipient. The simplest workaround is to iterate over your address list and call Mail::to() once per recipient: 
$recipients = ['alice@example.com', 'bob@example.com'];

foreach ($recipients as $recipient) {
    Mail::to($recipient)->send(new WelcomeMail());
}
For large recipient lists, replace send() with queue() to push each message onto a queue worker instead of dispatching all HTTP calls synchronously during the web request:
foreach ($recipients as $recipient) {
    Mail::to($recipient)->queue(new WelcomeMail());
}
This prevents long-running loops from blocking the request cycle and allows Laravel’s queue system to handle retries and backoff automatically.

​
Why these limitations exist

These are API-level constraints imposed by the Maily.id platform. The yugo/laravel-maily package cannot add support for attachments, CC, BCC, or multiple recipients until the underlying API exposes those fields.To stay informed about upcoming capabilities, follow the Maily.id roadmap. If a missing feature is blocking your use case, you are welcome to open an issue on the GitHub repository to signal demand and track progress.

Build docs developers (and LLMs) love

Get started for freeTalk to us