Reassigning to the postfix maintainer in the Fedora Core component.  Postfix
documentation comes from upstream with the rest of the source, so it is not
anything Fedora Documentation has control over.

I don't know anything about the technical feasibility of this proposal, but I do
know that a patch accompanying the suggestion should help acceptance from the
Postfix team.

Seems that reassigning to the component didn't reassign to that component owner;
fixed by assigning to twoerner@redhat.com.

Hello,

Are there any news about this ?

Răzvan

Changing severity to 'medium', because this issue doesn't full-fill the 'high' definition, that is defined as:
> Problem due to crashes, loss of data, severe memory, leak, etc.

Cloning to RHEL-6.

RHEL-6 clone: Bug 734176

This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

For postfix any directory under /var/mail works even with selinux in enforcing mode. Also there are more complex configurations possible - e.g. mapping of virtual users to more than one system user (in this case the preset user wouldn't help).

I would like to follow upstream and I wouldn't like to enforce anything in default configuration (especially during the RHEL-5 lifecycle). Probably better to only provide example configuration in RH documentation, e.g. for postfix:

General config:
# groupadd -g 5000 vmail
# useradd -u 5000 -g vmail -M vmail
# mkdir -p /var/mail/virtual/example.com
# chown -R vmail:vmail /var/mail/virtual

Postfix config:
# postconf -e virtual_mailbox_domains=example.com
# postconf -e virtual_mailbox_base=/var/spool/mail/virtual
# postconf -e virtual_mailbox_maps=hash:/etc/postfix/virtual_mailbox
# postconf -e virtual_minimum_uid=100
# postconf -e virtual_uid_maps=static:5000
# postconf -e virtual_gid_maps=static:5000
# postconf -e virtual_alias_maps=hash:/etc/postfix/virtual
# echo 'postmaster@example.com postmaster' > /etc/postfix/virtual
# postmap hash:/etc/postfix/virtual

Addition of users user1, user2:
# echo 'user1@example.com  example.com/user1' > /etc/postfix/virtual_mailbox
# echo 'user2@example.com  example.com/user2' >> /etc/postfix/virtual_mailbox
# postmap hash:/etc/postfix/virtual_mailbox

# service postfix reload


For dovecot compatible example should be added.

According to review of current RHEL-5 deployment guide I would prefer documenting in Knowledge base.

Adding SMTP SASL config example (using Dovecot SASL) to have complete example.

SMTP SASL config:
# postconf -e smtpd_sasl_type=dovecot
# postconf -e smtpd_sasl_path=private/auth
# postconf -e smtpd_sasl_auth_enable=yes
# postconf -e broken_sasl_auth_clients=yes  # Enable broken clients
# postconf -e smtpd_sasl_security_options=noanonymous  # Disable anonymous
# postcond -e smtpd_recipient_restrictions="permit_mynetworks, reject_sender_login_mismatch, permit_sasl_authenticated, reject_unauth_destination"  # Enable relay for SASL authenticated

TLS config (optional):
# postconf -e smtpd_tls_security_level=may
# postcond -e smtpd_tls_key_file=/etc/pki/tls/private/mail.example.com.key
# postconf -e smtpd_tls_cert_file=/etc/pki/tls/certs/mail.example.com.crt
# postconf -e smtpd_tls_CAfile=/etc/pki/tls/certs/ca-bundle.crt

# postconf -e smtpd_tls_auth_only=yes  # Enable SASL only over TLS (more secure)

(In reply to comment #14)
s/postcond/postconf/

Dovecot's simple configuration for virtual users:

# environment
mkdir /home/virtual
chown vmail:vmail /home/virtual

# in /etc/dovecot.conf, set:

mail_location = mbox:~/mail:INBOX=/var/mail/virtual/%d/%n
auth_realms = "example.com"
auth_default_realm = "example.com"

# and change whole auth default { ... } section to:
auth default {
  mechanisms = plain login
  passdb passwd-file {
    args = /etc/dovecot.passdb
  }
  userdb static {
   args = uid=vmail gid=vmail home=/home/virtual/%d/%n
  }
  user = root
  socket listen {
    client {
      path = /var/spool/postfix/private/auth
      mode = 0660
      user = postfix
      group = postfix
    }
  }
}

# create user database
touch /etc/dovecot.passdb
chmod 0600 /etc/dovecot.passdb

# Addition of users user1, user2:
USR=user1@example.com; echo "${USR}:$(dovecotpw -u $USR )" >>/etc/dovecot.passdb

USR=user2@example.com; echo "${USR}:$(dovecotpw -u $USR )" >>/etc/dovecot.passdb

# restart dovecot
service dovecot restart

As requested, a Knowledgebase page, on how to configure a system to manage multiple virtual mailboxes using Postfix and Dovecot, has been created.

Page location: https://access.redhat.com/knowledge/articles/209683

Since this is no longer about the Deployment Guide, I am closing this bug as WONTFIX.