Configure the list manager (Sympa).

1 files changed, 2 insertions, 2 deletions

diff --git a/roles/MX/templates/etc/postfix/virtual/transport.j2 b/roles/MX/templates/etc/postfix/virtual/transport.j2
index 57a0349..69a8c83 100644
--- a/roles/MX/templates/etc/postfix/virtual/transport.j2
+++ b/roles/MX/templates/etc/postfix/virtual/transport.j2
@@ -6,24 +6,24 @@
 # transport_maps.  Hence high latency maps such as LDAP or SQL would
 # congestion the queue manager.  On the other hand, virtual aliasing is
 # performed by cleanup(8), multiples instances of which can run in
 # parallel. See http://www.postfix.org/ADDRESS_REWRITING_README.html .
 #
 # /!\ WARNING: xxx.fripost.org should NOT be in the list of valid
 # domains ($virtual_alias_domains)!  Otherwise at the next iteration of
 # the alias resolution loop the domain will be validated but not the
 # address, and the MTA will reply with "Recipient address rejected: User
 # unknown in virtual alias table".
 
 reserved.fripost.org    reserved-alias:
 
 {% if 'LDA' in group_names %}
 mda.fripost.org smtpl:[127.0.0.1]:{{ postfix_instance.IMAP.port }}
 {% else %}
 mda.fripost.org smtp:[mda.fripost.org]:{{ postfix_instance.IMAP.port }}
 {% endif %}
 
 {% if 'lists' in group_names %}
-mailman.fripost.org smtpl:[127.0.0.1]:{{ postfix_instance.lists.port }}
+sympa.fripost.org smtpl:[127.0.0.1]:{{ postfix_instance.lists.port }}
 {% else %}
-mailman.fripost.org smtp:[lists.fripost.org]:{{ postfix_instance.lists.port }}
+sympa.fripost.org smtp:[lists.fripost.org]:{{ postfix_instance.lists.port }}
 {% endif %}