Search Engine: Elastic

Article ID: 126524, created on Aug 12, 2015, last review on Jul 14, 2018

  • Applies to:
  • Plesk Automation 11.5


The IP address of the Postfix has been changed by using ppa.ip_address utility, but the Postfix transport map has not been updated.

The command

# postmap -s /var/spool/postfix/plesk/sdd_transport_maps

returns outdates IP address.

As a result, the mailflow disrupted and the following messages filled /usr/local/psa/var/log/maillog:

postfix/qmgr[3134]: warning: connect to transport private/OLDIP-: Connection refused
postfix/error[3219]: 2F24F240500: to=<>, relay=none, delay=0.2, delays=0.17/0/0/0.03, dsn=4.3.0, status=deferred (mail transport unavailable)


Such behaviour has been considered as a software issue #PPA-2268. The issue has been fixed in MU 19. Please install all the updates to fix the issue.


In order to fix postfix configuration please perform following steps:

  1. Create a backup copy of the /var/spool/postfix/plesk/sdd_transport_maps.db file:

    # cp /var/spool/postfix/plesk/sdd_transport_maps.db /home/sdd_transport_maps.db
  2. Save the content of the /var/spool/postfix/plesk/sdd_transport_maps.db as plain text replacing the old IP by new one:

    # postmap -s /var/spool/postfix/plesk/sdd_transport_maps | sed s/192\.168\.0\.1/172\.16\.0\.1/g > /tmp/sdd_transport_maps

    where is the old IP and is the new one.

  3. Generate new sdd_transport_maps.db:

    # postmap /tmp/sdd_transport_maps
  4. Check if the file content is correct (do not add .db at the end of the file name):

    # postmap -s /tmp/sdd_transport_maps
  5. Replace /var/spool/postfix/plesk/sdd_transport_maps.db with the new file:

    # cp /tmp/sdd_transport_maps.db /var/spool/postfix/plesk/sdd_transport_maps.db
    cp: overwrite `/var/spool/postfix/plesk/sdd_transport_maps.db'? y

33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065 e0aff7830fa22f92062ee4db78133079

Email subscription for changes to this article
Save as PDF