Good afternoon, After I updated my ISPConfig to 3.2.11p2 when I create a new e-mail I get the error below: Recipient address rejected: unverified address This happens when I send an e-mail to the mailbox I created Existing emails before the update work normally Only the new ones give this error. I don't know what to do, all my servers have this error. Debian buster postfix, amavis, spamassassin, clamav IPSCONFIG 3.2.11p2 Feb 10 15:22:25 servidor1 postfix/submission/smtpd[25867]: NOQUEUE: reject: RCPT from unknown[177.220.172.94]: 450 4.1.1 <[email protected]>: Recipient address rejected: unverified address: host 127.0.0.1[127.0.0.1] said: 554 5.7.1 <[email protected]>: Recipient address rejected: Access denied (in reply to RCPT TO command); from=<[email protected]> to=<[email protected]> proto=ESMTP helo=<[192.168.100.11]> Thanks for any help
Seems as if you might missed to enable smtp authentication in your mail client when configuring the mail client for the new address.
My servers are many years old I've been updating ISPconfig since the initial version of 3.0 Yesterday when I updated it, this started and I didn't change anything in the configuration. Please, where can I check what you've told me? I'm using gmail webmail, yahoo, to send to the new email, etc. They all give an error. No matter where I send it from, the new mailboxes don't receive any email
Please try whats described in the last post here: https://forum.howtoforge.com/thread...cipient-address-rejected-access-denied.90127/
And nefore you change postfix main.cf file. Please make a backup and send it to me by email to dev at ispconfig dot org. and you can find a copy of the /etc folder from before the update in a subfolder in /var/backup/ please extract that etc backup tar.gz and send me a copy of the old main.cf file you have in there as well. So I can compare what exactly has changed as there seem to be several people affected by this same issue but it never occurred on any system managed by us or by any of our support clients, so its interesting what might cause this.
In my main.cf I had smtp_bind_address configured with my main public ip. When I removed this setting it started working again and new emails started receiving emails. What I don't understand is that it worked for years. After the 3.2.11p2 update, it stopped working if I left the smtp_bind_address active.
The ISPConfig update did not contain any changes in Postfix configuration, it just fixed some UI issues and a issue wich unexpectedly removed a rspamd config file for mailboxes.
I understand. There are things that only God can explain when they happen. I'll continue my research on the subject. I consider the topic resolved. Anyway, thank you very much for getting back to me so quickly.
OK. Then my suspicion is this: between the previous time ISPConfig was upgraded and the latest time it was upgraded, Postfix must have been updated to a newer version. Some config that's only added when you're only at a specific Postfix version or above must have been added now, but wasn't added before as the Postfix version was too old.
It's a hypothesis. But looking at the apt log, I didn't see any postix updates. Not even in the debian security list: https://www.debian.org/security/
It can just be that your installed Postfix version was out of date and your system upgraded to the latest available version somewhere in the last few months.
my sources.list doesn't allow this: root@servidor1:/etc/apt# cat sources.list deb http://deb.debian.org/debian/ buster main contrib non-free deb-src http://deb.debian.org/debian/ buster main contrib non-free deb http://security.debian.org/debian-security buster/updates main contrib non-free deb-src http://security.debian.org/debian-security buster/updates main contrib non-free # buster-updates, previously known as 'volatile' deb http://deb.debian.org/debian/ buster-updates main contrib non-free deb-src http://deb.debian.org/debian/ buster-updates main contrib non-free it is fixed in the buster
Please reread my posts as I think you don't understand what I mean. In short, it comes down to a package upgrade that probably ran between the previous ISPConfig update and the 3.2.11p2 update you did.
