Re: [Mailman-Users] Mailman setup help....

[Mark Sapiro]

[EMAIL PROTECTED] wrote:
>
>  I'm running postfix with virtual host and mysql.
>I mainly followed the following guide:
>http://www.gentoo.org/doc/en/virt-mail-howto.xml
>
>
>I was wondering if there was any mailman documentation that is more
>detailed.  I ran through the setup instructions and as far as I can tell.
>it's just not doing anything... added the aliases etc.  The owner is not
>getting notified.. nor can I send/receive emails sent to that account.


It is not clear to me from your post whether your problem is in
delivery from postfix to Mailman, or if it is Mailman not processing
messages after receipt.

Are your qrunners running? (bin/mailmanctl start)

You may find the following helpful





-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Messages shunted and kept out of archives

[Tokio Kikuchi]

John Swartzentruber wrote:
> I recently upgraded to Mailman 2.1.7. A user (and co-moderator) on one 
> of the lists that I run reported that some of his messages were missing 
> from the archives and that one of them had been delivered to him without 
>   the normal Mailman footers and subject modification.
> 

>File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in 
> as_text
>  '\g<1>' + _(' at ') + '\g<2>', body)
>File "/usr/lib/python2.3/sre.py", line 143, in sub
>  return _compile(pattern, 0).sub(repl, string, count)
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 
> 5749: ordinal not in range(128)
> 
> Jan 15 19:39:13 2006 (7863) SHUNTING: 
> 1137283434.787801+8fcbe00f31f4008afd66221d0d9397ade1228077
> 

Please fetch this patch from SF tracker and apply it in mailman-2.1.7 
source.
http://sourceforge.net/tracker/index.php?func=detail&aid=1405790&group_id=103&atid=300103

-- 
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Messages shunted and kept out of archives

[John Swartzentruber]

I recently upgraded to Mailman 2.1.7. A user (and co-moderator) on one 
of the lists that I run reported that some of his messages were missing 
from the archives and that one of them had been delivered to him without 
  the normal Mailman footers and subject modification.

I looked into it today and saw that there were three messages in the 
shunt directory. At least one of these was the primary message that we 
had discovered was missing from the archives.

I tried bin/unshunt, but it had no affect. The information from the 
error log is as follows:

Jan 15 19:39:13 2006 (7863) Uncaught runner exception: 'ascii' codec 
can't decode byte 0xe4 in position 5749: ordinal not in range(128)
Jan 15 19:39:13 2006 (7863) Traceback (most recent call last):
   File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
 self._onefile(msg, msgdata)
   File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
 keepqueued = self._dispose(mlist, msg, msgdata)
   File "/usr/local/mailman/Mailman/Queue/ArchRunner.py", line 73, in 
_dispose
 mlist.ArchiveMail(msg)
   File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 216, in 
ArchiveMail
 h.processUnixMailbox(f)
   File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 585, in 
processUnixMailbox
 self.add_article(a)
   File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 626, in 
add_article
 filename))
   File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 1116, 
in write_article
 f.write(article.as_text())
   File "/usr/local/mailman/Mailman/Archiver/HyperArch.py", line 579, in 
as_text
 '\g<1>' + _(' at ') + '\g<2>', body)
   File "/usr/lib/python2.3/sre.py", line 143, in sub
 return _compile(pattern, 0).sub(repl, string, count)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 
5749: ordinal not in range(128)

Jan 15 19:39:13 2006 (7863) SHUNTING: 
1137283434.787801+8fcbe00f31f4008afd66221d0d9397ade1228077



Because this is a new problem, I decided to try downgrading back to 
2.1.6 (by running "make install" in the 2.1.6 source directory). After I 
did this and ran bin/unshunt, the shunt directory was empty. 
Unfortunately, I'm an idiot and I didn't look to see whether it was the 
downgrade or the unshunt that emptied the directory. I also then ran 
bin/arch to rebuild the archives, and the previously missing message now 
shows up.

So it is possible that there is a problem introduced in 2.1.7, or it is 
possible that I still have the problem, but have worked around it. In 
case it is the former, I'm reporting it here. It seems like this might 
be similar to the "Shunting msgs." thread from a couple weeks ago, but 
that person was running 2.1.6.

I'll be happy to attempt to provide additional information if I can. 
This is just a personal server that I also use to host two or three 
small mailing lists.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] [Mailman-Developers] Problems with uuencoded attachments

[Tokio Kikuchi]

Barry Warsaw wrote:
> On Mon, 2006-01-16 at 09:25 +0900, Tokio Kikuchi wrote:
> 
> 
>>In usual mailman qrunner execs, stderr is logged into logs/errors.  It 
>>is the additional tee_to_real_stderr in LogStdErr() setting which wants 
>>to print the error into real stderr.
>>
>>Isn't it safe to put the tee_to_real_stderr value 0 in bin/qrunner script ?
> 
> 
> Ideally, tee_to_real_stderr would be !AS_SUBPROC (i.e. tee when not
> running qrunner under mailmanctl).  That would have to be done in main()
> after processing the command line arguments.
> 
Yeah, I noticed that too and played around.  How about this patch.

I assumed running qrunner independently is for debugging purpose and
quit redirecting stderr into logs/error.

-- 
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: qrunner
===
RCS file: /cvsroot/mailman/mailman/bin/qrunner,v
retrieving revision 2.9.2.1
diff -u -r2.9.2.1 qrunner
--- qrunner 27 Aug 2005 01:40:16 -  2.9.2.1
+++ qrunner 16 Jan 2006 01:58:49 -
@@ -66,6 +66,9 @@
 
 runner is required unless -l or -h is given, and it must be one of the names
 displayed by the -l switch.
+
+Note also that this script should be started up from mailmanctl as a normal
+operation.  It is only useful for debugging if it is run separately.
 """
 
 import sys
@@ -84,8 +87,6 @@
 # Flag which says whether we're running under mailmanctl or not.
 AS_SUBPROC = 0
 
-LogStdErr('error', 'qrunner', manual_reprime=0)
-
 
 
 def usage(code, msg=''):
@@ -212,6 +213,10 @@
 if len(runners) == 0:
 usage(1, _('No runner name given.'))
 
+# Before we startup qrunners, we redirect the stderr to mailman syslog.
+if AS_SUBPROC:
+LogStdErr('error', 'qrunner', manual_reprime=0, tee_to_real_stderr=0)
+
 # Fast track for one infinite runner
 if len(runners) == 1 and not once:
 qrunner = make_qrunner(*runners[0])
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

[Mailman-Users] Mailman setup help....

[joe]

Hi all,

  I'm running postfix with virtual host and mysql.
I mainly followed the following guide:
http://www.gentoo.org/doc/en/virt-mail-howto.xml


I was wondering if there was any mailman documentation that is more
detailed.  I ran through the setup instructions and as far as I can tell.
it's just not doing anything... added the aliases etc.  The owner is not
getting notified.. nor can I send/receive emails sent to that account.

Any ideas suggestion would be appreciated.

Joe.




--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] [Mailman-Developers] Problems with uuencoded attachments

[Barry Warsaw]

On Mon, 2006-01-16 at 09:25 +0900, Tokio Kikuchi wrote:

> In usual mailman qrunner execs, stderr is logged into logs/errors.  It 
> is the additional tee_to_real_stderr in LogStdErr() setting which wants 
> to print the error into real stderr.
> 
> Isn't it safe to put the tee_to_real_stderr value 0 in bin/qrunner script ?

Ideally, tee_to_real_stderr would be !AS_SUBPROC (i.e. tee when not
running qrunner under mailmanctl).  That would have to be done in main()
after processing the command line arguments.

-Barry



signature.asc
Description: This is a digitally signed message part
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] SpamDetect loop?

[Tokio Kikuchi]

David Gibbs wrote:
> Tokio Kikuchi wrote:
> 
>>Can you test this patch?
> 
> 
> Seems to be working fine.
> 
> david
> 
> 
> 
Thank you David.  I changed the patch slightly and checked into the CVS. 
  See also this patch tracker entry:
http://sourceforge.net/tracker/index.php?func=detail&aid=1405790&group_id=103&atid=300103

Cheers,
-- 
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] [Mailman-Developers] Problems with uuencoded attachments

[Tokio Kikuchi]

Barry Warsaw wrote:
> On Jan 14, 2006, at 9:59 PM, Tokio Kikuchi wrote:
> 
> 
>>Mark Sapiro wrote:
>>
>>
>>
File "/usr/lib/python2.3/uu.py", line 139, in decode
  sys.stderr.write("Warning: %s\n" % str(v))
File "/usr/lib/mailman/Mailman/Logging/MultiLogger.py", line 45,  
in write
  _logexc(logger, msg)
File "/usr/lib/mailman/Mailman/Logging/Utils.py", line 22, in  
_logexc
  sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 32] Broken pipe
>>
>>>I think this could be fixed by changing
>>>"/usr/lib/mailman/pythonlib/email/Message.py", line 223 from
>>>uu.decode(StringIO(payload+'\n'), sfp)
>>>to
>>>uu.decode(StringIO(payload+'\n'), sfp,  
>>>quiet=True)
>>
>>
>>There should be other chances that Python builtin modules spew  
>>warnings to sys.stderr.  How about this patch for Logging/Utils.py  
>>to write these messages into syslog facility.
> 
> 
> The only problem is that currently Mailman does not use the syslog  
> module, and I'm uncomfortable with adding it for this one situation  
> (are there others?).  We should definitely be passing the quiet flag  
> to uu.decode(), but OTOH maybe we should also be testing whether  
> sys.__stderr__ is detached and then redirecting that to logs/errors?
> 
In usual mailman qrunner execs, stderr is logged into logs/errors.  It 
is the additional tee_to_real_stderr in LogStdErr() setting which wants 
to print the error into real stderr.

Isn't it safe to put the tee_to_real_stderr value 0 in bin/qrunner script ?


-- 
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] SpamDetect loop?

[David Gibbs]

Tokio Kikuchi wrote:
> Can you test this patch?

Seems to be working fine.

david
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Hello and newbie question(s)

[J. Horton]

Thank you to Mark and Bryan for the help.  Trying to figure out what  
this all this means (I'm still in the deep water.)  I've asked our  
network guy to take a look, though I know I'm driving him crazy.

I might perhaps need to come back and ask some for some further  
simplification, but here's hoping I can figure it out.

Thanks again!

Jeremy

On Jan 14, 2006, at 7:57 PM, Mark Sapiro wrote:

> J. Horton wrote:
>>
>> I'm very adept at configuring list via the web interface, but I now
>> have a bit of a problem.
>>
>> Recently, we decided to set up individual lists for each Kentucky
>> county represented in our organization's BIG LIST.  I created these
>> lists (120 in all) using the command lines, and they are now set up
>> and running (though empty).   Problem is, I'd like to set the same
>> bounce processing variables for each list, without having to go into
>> the web interface to each individually (a huge time killer).
>>
>> Is there anyway to do this kind of work globally via the command
>> line?  Here are the configurations I would like to try and do all at
>> one time, and I was wondering not only how to type the command, but
>> also how to enter the values (whether integer or Yes/No):
>
> You need a combination of things.
>
> bin/config_list -i file_name list_name
>
> will do the work of configuring one list. Run
>
> bin/config_list --help
>
> for details of the command. Run
>
> bin/config_list -o file_name some_list_name
>
> to get an example of what things need to look like in the input file.
> Keep in mind that the input file need have only those attributes you
> want to change.
>
> Then you need to wrap the above command in a shell script that will  
> run
> it for each list.
>
>
>> Also, I have yet to import email addresses into these 120 individual
>> lists.  I have, however, separated all the lists into individual text
>> files ("countyX.txt", "countyY.txt", etc.)  Is there a way (again) to
>> do this import via the command line (thus bypassing the web  
>> interface?)
>
>
> bin/add_members is what you want here. Again, run
>
> bin/add_members --help
>
> for details. and you'll need to wrap this in a shell script to run the
> command once for each list/input combination.
>
> I have no idea what the scripting commands look like in the Mac
> Terminal shell, but this kind of script is fairly simple.
>
> For example, suppose you have the listnames in a file named
> /path/to/listnames, and further suppose for simplicity that the list
> names are "countyX", "countyY", etc. as in the file names above.
>
> Then if this were a *nix sh compatible shell, the script might look  
> like
>
> for name in `cat /path/to/listnames`
> do bin/config_list -i /path/to/config/input ${name}
> bin/add_members -r /path/to/${name}.txt -w n -a n ${name}
> done
>
>
> -- 
> Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
>

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] [Mailman-Developers] Problems with uuencoded attachments

[Barry Warsaw]

On Jan 14, 2006, at 9:59 PM, Tokio Kikuchi wrote:

> Mark Sapiro wrote:
>
>
>>> File "/usr/lib/python2.3/uu.py", line 139, in decode
>>>   sys.stderr.write("Warning: %s\n" % str(v))
>>> File "/usr/lib/mailman/Mailman/Logging/MultiLogger.py", line 45,  
>>> in write
>>>   _logexc(logger, msg)
>>> File "/usr/lib/mailman/Mailman/Logging/Utils.py", line 22, in  
>>> _logexc
>>>   sys.__stderr__.write('Logging error: %s\n' % logger)
>>> IOError: [Errno 32] Broken pipe
>
>> I think this could be fixed by changing
>> "/usr/lib/mailman/pythonlib/email/Message.py", line 223 from
>> uu.decode(StringIO(payload+'\n'), sfp)
>> to
>> uu.decode(StringIO(payload+'\n'), sfp,  
>> quiet=True)
>
>
> There should be other chances that Python builtin modules spew  
> warnings to sys.stderr.  How about this patch for Logging/Utils.py  
> to write these messages into syslog facility.

The only problem is that currently Mailman does not use the syslog  
module, and I'm uncomfortable with adding it for this one situation  
(are there others?).  We should definitely be passing the quiet flag  
to uu.decode(), but OTOH maybe we should also be testing whether  
sys.__stderr__ is detached and then redirecting that to logs/errors?

-Barry

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Problems with uuencoded attachments

[Mark Sapiro]

Tokio Kikuchi wrote:
>
>There should be other chances that Python builtin modules spew warnings 
>to sys.stderr.  How about this patch for Logging/Utils.py to write these 
>messages into syslog facility.

The patch looks good to me, and I think is a good thing in general.
It's clearly better than supressing warnings one at a time.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] can't find smrsh wrapper in sendmail

[Mark Sapiro]

Myo Zaw Nyunt wrote:
>
>Thanks for your reply. But after I read this article at
>http://mail.python.org/pipermail/mailman-users/2004-June/037514.html, I do not
>understand very well about this section. I can't find /etc/sudoers fiels in my
>FreeBSD.


You probably have to create it. See 'man sudo'. BUT, you don't have to
follow the procedure in the above post. It is for automating Mailman
alias creation with sendmail.

I suggest you just create aliases manually until you get sendmail
properly delivering to your list(s). Then you can go back and do the
procedure outlined in the above post if you wish.

I.e., start with MTA='Manual' and manually add aliases for the
'mailman' list and your test list to /etc/aliases. Then, only after
everything is working, consider doing the above. If you are not going
to be adding and/or deleting lists frequently, you can probably just
stay with a manual process for aliases.



>And I still get userunkonw as bounced back mail.
>
>I created for mailman aliases file like this : for example I created list named
>"test" and members in this list are [EMAIL PROTECTED] and [EMAIL PROTECTED]
>
>So, I created as:
>
>test   test1 test2
>
>Is that right?


No. That would not use Mailman at all. You want sendmail to deliver
mail to 'test' to Mailman, and Mailman resends to 'test1 and test2'.
If sendmail is rerouting mail to 'test' to 'test1 and test2', you
aren't using Mailman at all.


See my prior response that you quote below for the form of these aliases
You need the folowing aliases for the 'mailman' site list which you
must have (quoted from my prior post).

>>
>> Here is a typical set for the site list named 'mailman'
>>
>> ## mailman mailing list
>> mailman:"|/usr/local/mailman/mail/mailman post mailman"
>> mailman-admin:  "|/usr/local/mailman/mail/mailman admin mailman"
>> mailman-bounces:"|/usr/local/mailman/mail/mailman bounces mailman"
>> mailman-confirm:"|/usr/local/mailman/mail/mailman confirm mailman"
>> mailman-join:   "|/usr/local/mailman/mail/mailman join mailman"
>> mailman-leave:  "|/usr/local/mailman/mail/mailman leave mailman"
>> mailman-owner:  "|/usr/local/mailman/mail/mailman owner mailman"
>> mailman-request:"|/usr/local/mailman/mail/mailman request mailman"
>> mailman-subscribe:  "|/usr/local/mailman/mail/mailman subscribe mailman"
>> mailman-unsubscribe:"|/usr/local/mailman/mail/mailman unsubscribe mailman"
>>

You also need a set for your 'test' list as follows, and similarly for
each additional list you create.

## test mailing list
test:"|/usr/local/mailman/mail/mailman post test"
test-admin:  "|/usr/local/mailman/mail/mailman admin test"
test-bounces:"|/usr/local/mailman/mail/mailman bounces test"
test-confirm:"|/usr/local/mailman/mail/mailman confirm test"
test-join:   "|/usr/local/mailman/mail/mailman join test"
test-leave:  "|/usr/local/mailman/mail/mailman leave test"
test-owner:  "|/usr/local/mailman/mail/mailman owner test"
test-request:"|/usr/local/mailman/mail/mailman request test"
test-subscribe:  "|/usr/local/mailman/mail/mailman subscribe test"
test-unsubscribe:"|/usr/local/mailman/mail/mailman unsubscribe test"

Also note from my prior post -
>> The '/usr/local/mailman' part of the path is the default, but may be
>> diferent if you specified different directories via the --prefix= or
>> --exec-prefix= options to configure. Also, some of the above lines may
>> be wrapped.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp