On 02/25/2015 08:53 AM, Kevin Nowaczyk wrote: > Postconf Output ... > alias_maps = hash:/etc/aliases ... > mailman_destination_recipient_limit = 1 ... > relay_domains = lists.domain3.com > relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman ... > transport_maps = hash:/etc/postfix/transport > virtual_alias_domains = list.domain3.com
I'm confused about list.domain3.com vs. lists.domain3.com in relay_domains. > virtual_alias_maps = hash:/etc/postfix/virtual, > hash:/var/www/domain3.com/domain3-virtual, > hash:/var/lib/mailman/data/virtual-mailman ... > Feb 25 16:48:48 bunsen postfix/virtual[3850]: 65F271C37A: > to=<mailingl...@domain3.com>, relay=virtual, delay=0.22, > delays=0.2/0.02/0/0.01, dsn=5.1.1, status=bounced (unknown user: > "mailingl...@domain3.com") It appears your mail is being mapped to mailingl...@domain3.com via the mapping in /var/lib/mailman/data/virtual-mailman, and there is probably an alias for this address in /var/lib/mailman/data/aliases, but there is no hash:/var/lib/mailman/data/aliases in alias_maps. It is not completely clear to me what's going on, but it looks like you have a Debian/Ubuntu package and are using postfix_to_mailman.py as a transport. I'd know more if I saw /etc/postfix/transport and /etc/postfix/master.cf. If my thought above is correct, the issue is all lists should be in the same domain. See the FAQ at <http://wiki.list.org/x/15564817> for more. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/archive%40jab.org
