CluPilotCloud/config/mail.php

<?php

use App\Services\Mail\MailCatalogue;

/*
| Ein Mailer je MAILART, aus derselben einen Liste erzeugt, aus der auch die
| Vorschau und die Wegwahl lesen (MailCatalogue).
|
| Warum es die zusätzlich zu den fünf Zweck-Mailern unten gibt: die Wegwahl
| (`mail.route.<mailart>`) verschob bisher nur den UMSCHLAG. Der Mailer blieb
| der des Zwecks, und `MailboxTransport` meldete sich mit dessen Zugangsdaten
| an — legte der Betreiber `security-block` auf `info@`, ging die Mail also mit
| `From: info@` durch die SMTP-Sitzung von `no-reply@`. Ein Server, der prüft,
| ob ein Konto seine Absenderadresse besitzt, weist das ab ("553 5.7.1 Sender
| address rejected: not owned by user"), und dann verschwindet ausgerechnet die
| Mail, die gerade umgelegt wurde. Wegwahl und Anmeldung müssen dieselbe Frage
| beantworten, also stellt der Mailer sie auch: er kennt die Mailart und fragt
| damit dieselbe MailRoute wie der Umschlag.
|
| Erzeugt statt aufgelistet, weil MailCatalogue ausdrücklich die EINE Liste
| ist — eine zweite hier wäre die, die beim siebzehnten Mail vergessen wird.
| Genauso statisch wie die fünf unten: ein reines Array, keine Datenbank, also
| auch unter `config:cache` unverändert.
*/
$perMailType = [];

foreach (MailCatalogue::all() as $mailKey => $entry) {
    $perMailType[MailCatalogue::mailer($mailKey)] = [
        'transport' => 'mailbox',
        'purpose' => $entry['purpose'],
        'mail_key' => $mailKey,
    ];
}

return [

    /*
    |--------------------------------------------------------------------------
    | Default Mailer
    |--------------------------------------------------------------------------
    |
    | This option controls the default mailer that is used to send all email
    | messages unless another mailer is explicitly specified when sending
    | the message. All additional mailers can be configured within the
    | "mailers" array. Examples of each type of mailer are provided.
    |
    */

    'default' => env('MAIL_MAILER', 'log'),

    /*
    |--------------------------------------------------------------------------
    | Mailer Configurations
    |--------------------------------------------------------------------------
    |
    | Here you may configure all of the mailers used by your application plus
    | their respective settings. Several examples have been configured for
    | you and you are free to add your own as your application requires.
    |
    | Laravel supports a variety of mail "transport" drivers that can be used
    | when delivering an email. You may specify which one you're using for
    | your mailers below. You may also add additional mailers if needed.
    |
    | Supported: "smtp", "sendmail", "mailgun", "ses", "ses-v2",
    |            "postmark", "resend", "log", "array",
    |            "failover", "roundrobin"
    |
    */

    'mailers' => [

        'smtp' => [
            'transport' => 'smtp',
            'scheme' => env('MAIL_SCHEME'),
            'url' => env('MAIL_URL'),
            'host' => env('MAIL_HOST', '127.0.0.1'),
            'port' => env('MAIL_PORT', 2525),
            'username' => env('MAIL_USERNAME'),
            'password' => env('MAIL_PASSWORD'),
            'timeout' => null,
            'local_domain' => env('MAIL_EHLO_DOMAIN', parse_url((string) env('APP_URL', 'http://localhost'), PHP_URL_HOST)),
        ],

        'ses' => [
            'transport' => 'ses',
        ],

        'postmark' => [
            'transport' => 'postmark',
            // 'message_stream_id' => env('POSTMARK_MESSAGE_STREAM_ID'),
            // 'client' => [
            //     'timeout' => 5,
            // ],
        ],

        'resend' => [
            'transport' => 'resend',
        ],

        'sendmail' => [
            'transport' => 'sendmail',
            'path' => env('MAIL_SENDMAIL_PATH', '/usr/sbin/sendmail -bs -i'),
        ],

        'log' => [
            'transport' => 'log',
            'channel' => env('MAIL_LOG_CHANNEL'),
        ],

        'array' => [
            'transport' => 'array',
        ],

        'failover' => [
            'transport' => 'failover',
            'mailers' => [
                'smtp',
                'log',
            ],
            'retry_after' => 60,
        ],

        'roundrobin' => [
            'transport' => 'roundrobin',
            'mailers' => [
                'ses',
                'postmark',
            ],
            'retry_after' => 60,
        ],

        /*
        | One mailer per purpose. Deliberately STATIC: they name a purpose and
        | nothing else, so building this config reads no database. Which
        | mailbox a purpose resolves to is decided by MailboxTransport at send
        | time — see App\Services\Secrets\SecretVault rule 3, which this
        | follows: an overlay at boot costs a query on every request and leaves
        | long-running queue workers holding whatever was true when they started.
        |
        | Still used by everything that has no key of its own in MailCatalogue
        | (ContactRequestMail, MailboxTester, the readiness checks). A mail type
        | that IS in the catalogue goes over its own mailer instead — see
        | $perMailType at the top of this file for why.
        */
        'cp_maintenance' => ['transport' => 'mailbox', 'purpose' => 'maintenance'],
        'cp_provisioning' => ['transport' => 'mailbox', 'purpose' => 'provisioning'],
        'cp_support' => ['transport' => 'mailbox', 'purpose' => 'support'],
        'cp_billing' => ['transport' => 'mailbox', 'purpose' => 'billing'],
        'cp_system' => ['transport' => 'mailbox', 'purpose' => 'system'],

        ...$perMailType,

    ],

    /*
    |--------------------------------------------------------------------------
    | Global "From" Address
    |--------------------------------------------------------------------------
    |
    | You may wish for all emails sent by your application to be sent from
    | the same address. Here you may specify a name and address that is
    | used globally for all emails that are sent by your application.
    |
    */

    'from' => [
        'address' => env('MAIL_FROM_ADDRESS', 'hello@example.com'),
        'name' => env('MAIL_FROM_NAME', env('APP_NAME', 'Laravel')),
    ],

];