see below On Tue, Jul 16, 2013 at 9:56 PM, Mark Sapiro <m...@msapiro.net> wrote:
> On 07/16/2013 06:39 PM, David wrote: > > > > Here's what the sysadmin ended up doing. > > > > First, he added our domain in postfix mydestination but it didn't help > > so he did these steps: > > > > 1) Added our domain in relay_domains > > > > 2) Added the following in in master.cf <http://master.cf> > > > > mailman unix - n n - - pipe > > flags=FR user=list argv=/usr/lib/mailman/bin/postfix-to-mailman.py > > ${nexthop} ${user} > > > I think this is the first mention of postfix-to-mailman.py in this > thread. My advice to ensure that the list domain was in mydestination > was based on my incorrect assumption that you were using aliases. > > You and your sysadmin may find the FAQ at <http://wiki.list.org/x/EYDt> > and the post at > <http://mail.python.org/pipermail/mailman-users/2012-September/074017.html > > > which is linked therefrom to be of interest. > > -- > Mark Sapiro <m...@msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > Yes, this is the first mention of postfix-to-mailman.py in this thread. I did not know what it was until I read your links. And your assumption was *not* incorrect. We *are* using aliases! >From the links you provided, I see this quote: "postfix_to_mailman.py is an alternative to and is incompatible with Mailman delivery via aliases." So we have a problem here... BTW, my sysadmin doesn't know Mailman. ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://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: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
