On 6/3/03 4:55 PM, "Jason R. Mastaler" <[EMAIL PROTECTED]> wrote:
> Marty Lyons <[EMAIL PROTECTED]> writes: > >> File "./TMDA/FilterParser.py", line 972, in firstmatch >> ImportError: No module named Mailman.Bouncer > > [...] > >> # Mailman mailing lists -- see /usr/local/bin/tmda-mailman-copy >> # simply specify directory that the Mailman pickle files reside in >> # This behavior has changed from TMDA v0.76 which required a full >> path/filename >> from-mailman -attr=members ~/.tmda/lists/mailman/adventure >> deliver=~/Maildir/ > > Can you try commenting out all the 'from-mailman' entries just to > narrow the problem down to those? That did it. I'm not sure why that would cause the failure, so I'm naturally interested. > These entries look odd to me. Why would your mailman list data > directories be located in "~/.tmda/lists"? Well, this is a Mailman issue. Mailman config files (*.pck) are mode 660, and owned by mailman.mailman. If you reset permissions on the .pck files to 664, mailman sweeps through during one of its routines and sets them back to 660. So the downside of that effect is normal users (me, in my non-sysadm role) can't read them. I tried for a day to figure out why Mailman wants to reset permissions, and finally gave up. So as a quick hack, I just set up a cron job to copy the configs (.pck) files into my home directory. That seemed logically until TMDA erred. If anyone knows how to solve the Mailman permission issue, that would be the right answer. But I don't want to have to end up listing all our users in group mailman. In the interim, I'll just check headers looking for local mailman lists in the TMDA filters. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
