{% extends "baseTemplate/index.html" %}
{% load static %}
{% comment %}
Catch-all address, one per domain.

Stored as an ordinary virtual-alias row keyed "@domain" in email_forwardings,
which is the key Postfix probes after the full address misses. Nothing about
the installer's alias map had to change.

The spam warning on this page is not decoration. A catch-all accepts every
invented local part a dictionary attack tries, and most operators who ask for
one actually want two or three explicit aliases instead. Say so before they
switch it on, not in a tooltip afterwards.
{% endcomment %}

{% block title %}Catch-all address{% endblock %}

{% block content %}
<div ng-controller="catchAllController">

  <div class="mb-4">
    <h1 class="h4 mb-1">Catch-all address</h1>
    <p class="text-muted mb-0 small">
      Deliver mail sent to <em>any</em> address at a domain — including addresses
      that do not exist — to one mailbox.
    </p>
  </div>

  {% if not domains %}
    <div class="alert alert-info">
      <i class="fas fa-circle-info me-1"></i>
      There are no domains available to you yet.
    </div>
  {% else %}

  <div class="alert alert-warning" role="alert">
    <h2 class="h6 alert-heading">
      <i class="fas fa-triangle-exclamation me-1"></i>A catch-all attracts spam
    </h2>
    <p class="mb-2 small">
      Spammers guess addresses — <span class="font-monospace">info@</span>,
      <span class="font-monospace">sales@</span>, then thousands of invented
      names. Without a catch-all every guess bounces at the edge and costs you
      nothing. With one, every guess lands in a real mailbox, and that mailbox
      becomes the busiest source of spam on the domain. It also hides typos: a
      customer who writes to <span class="font-monospace">infor@</span> gets
      through, so nobody ever finds out the address was wrong.
    </p>
    <p class="mb-0 small">
      <strong>Most domains should not have one.</strong> Prefer explicit
      mailboxes, or a couple of
      <a href="/email/emailForwarding" class="alert-link">forwarders</a>, and
      keep a catch-all for the cases it is genuinely right for: a migration
      where the old address list is unknown, or a short-lived domain whose mail
      you intend to sort by hand.
    </p>
  </div>

  <div class="card mb-4">
    <div class="card-body">
      <div class="row g-3 align-items-end">
        <div class="col-md-4">
          <label class="form-label" for="cpDomain">Domain</label>
          <select class="form-select" id="cpDomain" ng-model="domain" ng-change="load()">
            {% for entry in domains %}
              <option value="{{ entry }}">{{ entry }}</option>
            {% endfor %}
          </select>
        </div>

        <div class="col-md-8">
          <div class="alert mb-0 py-2 px-3"
               ng-class="state.enabled ? 'alert-warning' : 'alert-secondary'" ng-cloak>
            <span ng-show="state.enabled">
              <i class="fas fa-inbox me-1"></i>
              <span class="font-monospace">{$ state.source $}</span> is delivering to
              <span class="font-monospace">{$ state.destination $}</span><span
                ng-show="state.created"> since {$ state.created $}</span>.
            </span>
            <span ng-hide="state.enabled">
              <i class="fas fa-shield-halved me-1"></i>
              No catch-all on this domain. Mail to an unknown address is rejected
              at the edge, which is the safe default.
            </span>
          </div>
        </div>
      </div>
    </div>
  </div>

  <div class="card mb-4">
    <div class="card-body">
      <h2 class="h6 mb-3">
        <span ng-show="state.enabled" ng-cloak>Change the destination</span>
        <span ng-hide="state.enabled" ng-cloak>Turn a catch-all on</span>
      </h2>

      <form novalidate ng-submit="save()">
        <div class="row g-3 align-items-end">
          <div class="col-md-8">
            <label class="form-label" for="cpDestination">Deliver caught mail to</label>
            <input type="email" class="form-control" id="cpDestination"
                   ng-model="destination" autocomplete="off" spellcheck="false"
                   list="cpMailboxes" placeholder="catchall@example.com" required>
            <datalist id="cpMailboxes">
              <option ng-repeat="address in mailboxes" value="{$ address $}"></option>
            </datalist>
            <div class="form-text">
              Pick a mailbox on this domain, or any address elsewhere. A mailbox on
              this domain must already exist — pointing the catch-all at one that
              does not makes Postfix loop the alias back into itself and defer
              every caught message.
            </div>
          </div>

          <div class="col-md-4 d-grid">
            <button type="submit" class="btn btn-primary" ng-disabled="busy || !domain">
              <i class="fas fa-inbox me-1"></i>
              <span ng-bind="busy ? 'Saving…' : (state.enabled ? 'Update catch-all' : 'Enable catch-all')"></span>
            </button>
          </div>
        </div>
      </form>
    </div>
  </div>

  <div class="card" ng-show="state.enabled" ng-cloak>
    <div class="card-body d-flex justify-content-between align-items-center flex-wrap gap-2">
      <div>
        <h2 class="h6 mb-1">Turn the catch-all off</h2>
        <p class="text-muted small mb-0">
          Mail to addresses that do not exist starts bouncing again, immediately.
          Mailboxes and forwarders on the domain are untouched.
        </p>
      </div>
      <button class="btn btn-outline-danger" type="button"
              ng-click="remove()" ng-disabled="busy">
        <i class="fas fa-trash me-1"></i>Remove catch-all
      </button>
    </div>
  </div>

  {% endif %}
</div>
{% endblock %}

{% block scripts %}
<script src="{% static 'mailServer/mailServer.js' %}"></script>
{% endblock %}