Mail

Tiger_Mail is a fluent wrapper over Zend_Mail. You compose a message; the transport is config-driven, so the same code sends via boring mail() in dev and authenticated SMTP in production.

Transport

Pick the transport per deploy:

  • mail() / sendmail — the default, zero config.
  • SMTP with TLS + auth — set mail.transport = smtp and mail.smtp.* / mail.from.*.

SMTP credentials live in local.ini (never committed), like every other secret.

Every message is multipart

Tiger auto-derives a plain-text alternative from your HTML, so every message goes out multipart — better deliverability, no extra work.

Where it's used

The auth flows use it out of the box — password-reset links and the "email me a code" passwordless login are Tiger_Mail + auth_challenge (no account enumeration).

See also