Hello,
I had the mail server that worked normally, but yesterday I decided to change the domain for the site, so I changed the domain in the main.cf, also for the SSL certificates, then I restarted Postfix and its configuration that appears to be active and works with a telnet localhost 587, but if I try to connect from Outlook, Thunderbird or PHPmailer it no longer works.
Dovecot handles that, so changing thing in postfix has screwed your imap/pop logins.
Hopefully you have created a backup of your main.cf or can remember what you changed.
I have no problem restoring the old main.cf, but could you tell me how to fix the problem? Because the old domain no longer points to my IP, so Dovecot can’t handle it as the signal doesn’t reach my server.
Not sure in webmin, virtualmin it would do it easy. I haven’t used webmin do that for at least 10 years.
Doesn’t Mail Alais and Virtual Domains handle most of the domain stuff
When state domain do you mean hostname ? Most virtual servers should have an a record in dns so it resolves to your IP and of course the mx record should point to the correct ip. Check the dns records for your new domain and make sure they point to your ip, if not correct them in the webmin bind module, if your webmin instance is responsible for serving your dns if not use the interface that is responsible for managing your dns
I can’t understand you, I changed the domain of the main.cf from mail.xxx.tld to mail.zzz.tld, then I changed the paths of the SSL certificates.
Now I should be able to connect via mail.zzz.tld, but for some reason it doesn’t work.
I just realized we’re also doing this in the Virtualmin installer, too, and it’s not necessary.
$myhostname is automatically the system hostname, and it’s automatically the right thing for mydestination if everything else is in virtual.
But, that has nothing to do with Outlook or whatever, it’s just about deliverability, I just got distracted, and now I need to fix the installer to stop doing this (it’s been doing it for 15 years, so it’s obviously harmless, but it’s going to bug me).
Anyway, connections to 587 are configured in master.cf, so maybe show us that, if you’ve modified it.
But, we need to see the actual error (“it no longer works” is not useful for troubleshooting). And, we need to see what appears in the mail log or the journal for the postfix unit when you try to send a message with a mail client.
Postfix is set up to use a mail filter service, but the socket file for the milter is missing. If the milter is mandatory, this causes Postfix to fail to process messages.
The path looks like a chrooted Postfix. Is Postfix actually running in a chroot on this system, and does everything else know what? I mean is the milter configured to put its socket file inside the chroot?