| Re: MAILMAN: using maillist.php as PRIVATE_EXTERNAL_ARCHIVER [message #11092 is a reply to message #11091] |
Tue, 17 June 2003 18:18   |
Tobias Eigen
Messages: 85
Registered: June 2003
Location: Seattle, WA USA
Karma:
|
Member |
|
|
 I'll keep plowing away at it.
Basically Mailman is piping the message to maillist.php in the same way that a .qmail file would. Mailman provides the list name via a variable, which I use to generate the listname(at)lists(dot)kabissa(dot)org on the command line. This works fine for lists configured in FUD, and when it's the only program configured as the external archiver.
If the listname(at)lists(dot)kabissa(dot)org rule isn't specified in FUD someplace, then it chokes on the message and saves it in the .mlist error directory. My preference would be for it to be posted to a default holding forum where I can then deal with it by deleting it or creating the appropriate forum and moving the message there.
I've had no luck getting Mailman to pipe the message to two external archivers at the same time - this is a disappointment since it hampers my testing and transition efforts. I must be missing something about how shell commands work. There must be a way to it, ie.
cat blah.txt | (program1 >> log1 ; program 2 >> log2)
Cheers,
Tobias
Kabissa - Space for change in Africa
[Updated on: Tue, 17 June 2003 18:18] Report message to a moderator |
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]