Difference between revisions of "SAC:Message Transport Agent"

From OSGeo
Jump to navigation Jump to search
 
Line 17: Line 17:
 
   ansible-playbook deployment/deploy-mail-servers.yml \
 
   ansible-playbook deployment/deploy-mail-servers.yml \
 
     --tags mail-aliases --check --diff
 
     --tags mail-aliases --check --diff
 +
 +
== Blacklisting senders or recipient addresses ==
 +
 +
Blacklists can be configured from ansible:
 +
 +
1. Edit deployment/roles/mail-server/files/etc/postfix/blacklisted_senders (for senders) and deployment/roles/mail-server/files/etc/postfix/blacklisted_recipients (for recipients)
 +
2. Deploy ( for example: ansible-playbook deployment/deploy-mail-servers.yml --diff --tags postfix-blacklist )
 +
 +
  
  

Latest revision as of 01:33, 16 September 2025

Message Transport Agent

With this [Message_transport_agent Message Transport Agent] (MTA) service, OSGeo provides the ability to receive emails to osgeo.org and some subdomain addresses for services and community members. Note that this is not a full email service with an inbox to manage and store messages.

It is the central OSGeo MX, running Postfix

It is managed via AnsibleDeployment using the mail-server role

Setting up mail alias

Setting up aliases can be done via ansible, editing deployment/roles/mail-server/files/etc/aliases and running the deployment/deploy-mail-servers.yml playbook with the mail-aliases tag, for example:

 ANSIBLE_CONFIG=ansible.osgeo.prod.cfg \
 ansible-playbook deployment/deploy-mail-servers.yml \
   --tags mail-aliases --check --diff

Blacklisting senders or recipient addresses

Blacklists can be configured from ansible:

1. Edit deployment/roles/mail-server/files/etc/postfix/blacklisted_senders (for senders) and deployment/roles/mail-server/files/etc/postfix/blacklisted_recipients (for recipients)
2. Deploy ( for example: ansible-playbook deployment/deploy-mail-servers.yml --diff --tags postfix-blacklist )



See Also

SAC:Message Submission Agent