I'm at my wits end trying to track down what is causing the error mentioned in the title. I have a server running Debian 11 (due for an upgrade to 13 soon.) and Postfix 3.25 which is run chrooted. Three domains are hosted, one canonical and two virtual.
This was all working until a few days ago when in order to overhaul my amavis-based antispam set up which was quite a memory hog, I moved to milters. I have opendkim, open-dmarc, spamassassin, and clamav milters set up and working for sending and receiving or so I thought. I did not think to check the virtual aliases and it was only a day or two later when a cron job that sent mail to [email protected] failed that I realized.
As the milters were the last thing I changed, I backed that out. Mail to virtual aliases still fails. In /etc/postfix/main.cf I have:
virtual_alias_domains = virtual1.domain, virtual2.domain virtual_alias_maps = hash:/etc/postfix/virtual /etc/postfix/virtual exists as does /etc/postfix/virtual.db
They haven't been touched for years but just in case I recreated the db with
postmap -v hash:/etc/postfix/virtual which gives the result:
postmap: name_mask: all postmap: inet_addr_local: configured 2 IPv4 addresses postmap: inet_addr_local: configured 2 IPv6 addresses postmap: open hash /etc/postfix/virtual postmap: Compiled against Berkeley DB: 5.3.28? postmap: Run-time linked against Berkeley DB: 5.3.28? The version of Berkeley DB on the system is indeed 5.3.28. However mail to virtual aliases still gives this error messages.
The aliases definitely exist. For example
postmap -q [email protected] /etc/postfix/virtual returns
root just as it should. Local aliases work fine. mail to system accounts fine. I have mailing lists that use GNU Mailman and users can send and receive to them without problems. Only virtual aliases bounce. Does anyone know why?
