2 - Raspberry PI Community Projects

alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = mail.falcot.com, falcot.com, localhost, localhost.localdomain
relayhost =
mynetworks = 127.0.0.0/8 192.168.0.0/16
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
inet_protocols = all
Example 11.1
Initial /etc/postfix/main.cf file
SECURITY
Snake oil SSL certificates
The snake oil certificates, like the snake oil “medicine” sold by unscrupulous
quacks in old times, have absolutely no value, since they are generated similarly
on all Debian systems, with the same “private” part. They should only be
used for testing purposes, and normal service must use real certificates; these
can be generated with the procedure described in Section 10.2.1.1, “Public Key
Infrastructure: easy-rsa” (page 225).
11.1.2. Configuring Virtual Domains
The mail server can receive emails addressed to other domains besides the main domain; these
are then known as virtual domains. In most cases where this happens, the emails are not ultimately
destined to local users. Postfix provides two interesting features for handling virtual
domains.
CAUTION
Virtual domains and
canonical domains
None of the virtual domains must be referenced in the mydestination variable;
this variable only contains the names of the “canonical” domains directly
associated to the machine and its local users.
11.1.2.1. Virtual Alias Domains
A virtual alias domain only contains aliases, i.e. addresses that only forward emails to other
addresses.
Such a domain is enabled by adding its name to the virtual_alias_domains variable, and referencing
an address mapping file in the virtual_alias_maps variable.
Chapter 11 — Network Services: Postfix, Apache, NFS, Samba, Squid, LDAP
255