Article ID: 113343, created on Feb 21, 2012, last review on Apr 20, 2017

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4

This article describes how to manage allowed IP addresses of SpamAssassin services.

To manage allowed IP adresses of SpamAssassin services, follow these steps:

  1. Prepare SPAMASSASSIN_SERVICE_IDs of the SpamAssassin services. These identifiers can be obtained at Provider Control Panel > Infrastructure > Services Nodes > SpamAssassin service node > Packages tab > Applications subtab.

  2. Log in to the Odin Automation Management Node.

  3. Go to the /usr/local/pem/bin/ directory.

  4. Perform necessary operations:

    • Viewing a list of allowed IP addresses of a SpamAssassin service

      SpamAssassin_ctl service listips SPAMASSASSIN_SERVICE_ID
      
    • Adding allowed IP addresses for a SpamAssassin service:

      SpamAssassin_ctl service addips SPAMASSASSIN_SERVICE_ID ALLOWED_IP_01 ALLOWED_IP_02 ...
      
    • Adding allowed IP addresses to all SpamAssassin services:

      SpamAssassin_ctl addips ALLOWED_IP_01 ALLOWED_IP_02 ...
      
    • Removing allowed IP addresses of a SpamAssassin service:

      SpamAssassin_ctl service removeips SPAMASSASSIN_SERVICE_ID ALLOWED_IP_01 ALLOWED_IP_02 ...
      
  5. Wait until all SpamAssassin configuration tasks complete.

  6. Restart all affected SpamAssassin services by using the following command on the corresponding SpamAssassin service nodes:

    service spamassassin restart
    
  7. If necessary, reconfigure your firewall for each affected SpamAssassin service:

    • If an IP address was added to the list of allowed IP addresses of a SpamAssassin service, allow connections from the added IP address to the SpamAssassin service node's BackNet IP address (TCP ports 783, 784).
    • If an IP address was removed from the list of allowed IP addresses of a SpamAssassin service, prohibit connections from the removed IP address to the SpamAssassin service node's BackNet IP address (TCP ports 783, 784);

Search Words

none

spamassassin does not detect spam messages

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 ac82ce33439a9c1feec4ff4f2f638899 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37

Email subscription for changes to this article
Save as PDF