Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
(no subject)

From: Len Conrad (lconradGo2France.com)
Date: Tue Aug 18 2009 - 11:08:59 CDT

mail_version = 2.3.3

postconf | egrep virtual_alias_maps

proxy_read_maps = $local_recipient_maps, $mydestination,
$virtual_alias_maps, $virtual_alias_domains, $virtual_mailbox_maps, $virtual_mailbox_domains, $relay_recipient_maps, $relay_domains, $canonical_maps, $sender_canonical_maps, $recipient_canonical_maps, $relocated_maps, $transport_maps, $mynetworks

virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-

virtual_forwardings.cf, mysql:/etc/postfix/mysql-virtual_email2email.cf

On the mailbox server, the mysql table answers correctly:

postmap -q "exstoryxxx.com" mysql:/etc/postfix/mysql-virtual_forwardings.cf

... so the virtual_forwardings.cf is correct, the table is correct, returing the right answer.


Aug 18 10:56:54 ms1.zzz.net/ms1.zzz.net postfix/virtual[5386]: 854544E4066: to=<exstoryxxx.com>, relay=virtual, delay=0.05, delays=0.04/0/0/0.01, dsn=5.1.1, status=bounced (unknown user: "exstoryxxx.com")

When we do "virtual -vv", we see virtual resolving recipients only with virtual_mailbox_maps, and apparently not looking at virtual_alias_maps

virtual_alias_maps worked fine for months until yesterday. We can't find what changed.