User unknown in virtual alias table


I recently had several messages from users of my VMPro installation saying they could not get postings out on mailman lists. The error given in each case included, “User unknown in virtual alias table” I tracked this down to postfix and can get no further, when I read through /etc/postfix/ it looks pretty sane but I don’t know where to look for morre details. Suggestions?



Did those users go through and add mailman lists via the Virtualmin interface?

Doing that should generate aliases in /etc/aliases – do you see the mailman list names they were trying to send email to in there?


Hi Eric,

I think that in most cases I added the lists for the users. A recent list that gave rise to that error was tankerfreebc, it is the most recent list created on this server and here is the tail of /etc/aliases

Dave “|/usr/lib/mailman/mail/mailman post tankerfreebc_members” “|/usr/lib/mailman/mail/mailman admin tankerfreebc_members” “|/usr/lib/mailman/mail/mailman bounces tankerfreebc_members” “|/usr/lib/mailman/mail/mailman confirm tankerfreebc_members” “|/usr/lib/mailman/mail/mailman join tankerfreebc_members” “|/usr/lib/mailman/mail/mailman leave tankerfreebc_members” “|/usr/lib/mailman/mail/mailman owner tankerfreebc_members” “|/usr/lib/mailman/mail/mailman request tankerfreebc_members” “|/usr/lib/mailman/mail/mailman subscribe tankerfreebc_members” “|/usr/lib/mailman/mail/mailman unsubscribe tankerfreebc_members”

Hi Eric.

should I file a trouble ticket on this? It appears that not only mail lists but pop mail is also affected by the issue, whatever it is.


I’ve seen similar issues come up whenever there’s an issue with the hostname… if you run the command “hostname” on the command line, whatever shows up as being the hostname needs to also be listed in /etc/hosts, as well as on the mydestination line of /etc/postfix/


ok, I’ll check


hostname is cserver.davedomain, it is (now) listed in the mydestination line of /etc/postfix/ I’ve restarted postfix and dovecot but am still getting bounced with the same error message