On 09/14/2015 11:47 AM, DT wrote: > Here's a final update now that this is finally sorted out. It was just > as Mark said, HostRocket was catching the immediate notifications in > some spam filter. After submitting a trouble ticket, they adjusted > their filter and it hasn't been a problem since. > >> You may find the FAQ article at <http://wiki.list.org/x/10715238> helpful. > > Thanks again Mark. All the examples appear to be for doing a transport > of an entire domain, but I did find this > - > http://www.docunext.com/blog/2011/01/using-postfix-transport-maps-for-email-address-specific-aliasing.html > - which I think will allow me to internally route just the mailman > specific addresses for the wort.org <http://wort.org> domain locally.
Actually, the FAQ article at <http://wiki.list.org/x/10715238> tells you how to modify Mailman's existing postfix integration facility to create transport maps to route list addresses only to Postfix's local transport. I don't know what you saw in that article, but the third paragraph specifically says "Some people find these features insufficient as they want to use some specific transport or other mapping for Mailman list addresses that is *not* applied to all addresses in the list domain(s). The following is a way to automate the generation of some Postfix map via editing the Mailman generated virtual-mailman file." (emphasis mine) -- 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
