I have a postfix mail server used in conjunction with Maia Mailguard, Amavis, and clamav for spam. I've upgraded the primary mail server and it has a new IP address. I change main.cf and transport to point to the new server in /etc/postfix, then reload postfix. When I look in /var/log/mail.log, "postfix/smtp * relay=[]:25 is still the old mail server (

postconf -n with our actual domain changed to mydomain.com

alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
content_filter = smtp-amavis:[]:10024
delay_warning_time = 4h
inet_interfaces = all
local_recipient_maps =
mailbox_size_limit = 0
message_size_limit = 20480000
mydestination = mydomain.com
myhostname = spam.mydomain.com
mynetworks =,,
myorigin = mydomain.com
recipient_delimiter = ;
relay_domains = mydomain, mydomain.net, mydomain.int,,
relay_recipient_maps = hash:/etc/postfix/relay_recipients
relayhost =
smtpd_banner = $myhostname ESMTP $mail_name
transport_maps = hash:/etc/postfix/transport

Transport file

mydoamin.com smtp:[]:25

I've checked resolve.conf and the hosts file to make sure there's nothing funny going on in there, all looks fine.

I've reviewed the maia config.php file and the maia.conf file, nothing there.

Where else could the old server IP be set for mail flow?


So it turns out I had everything changed that need to be changed:

  • /etc/postfix/main.cf
  • /etc/postfix/transport
  • /var/www/maia/config.php

You then need to run these commands to tell postfix to recreate the transport database and load the new config settings.

sudo postmap /etc/postfix/transport
sudo service postfix restart
| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.