I set up mailcow 2023-02, and migrated emails from another very old postfix+dovecot installation. Now, to migrate in steps and not bother all users at once, I set up user specific transport:smtp rules in mailcow’s postfix, so people were able to continu to use the old server. ( I’ve been running postfix since 2001, so I know some tricks). I added my transport hash to the extra.cf file, adding to the existing transport_maps variable. All was well.
Now, everyone but one user was happily migrated. Then I made the mistake to upgrade the server to 2023-02a. And after that, migrate an old user.
Even though the user has a mailbox, and no aliases appear for that user or domain, all emails for that address are still send to the old server! As if the transport rule is still active, but not visible in the new web UI. MX records only point to new server (we’re 36 hours further from DNS change).
I see in the logs the mail is delivered from the new to the old server.
I looked in the postfix docker, but my transport.db file was gone (as expected), and the whole main.cf was almost empty. Inside were references to shlib directories, but everywhere I looked and with ‘find’, I could not find these files. Are they now also incorporated into the mysql database?
I am happy that transport is now included in the UI, but what has happened with the old transport setting?
I need to ‘dig into’ the postfix configs to see if anything is still lingering around, where can I start? And how can I enable ‘debug logging’ if not in the main.cf file?