[Mailman-Users] Finding all unmoderated users in a list

2008-11-19 Thread D G Teed
Howdy,

We have some moderated lists with thousands of members
and a handful of people are appointed rights to post to it
(who are also members).

Periodically we don't know who has that posting
right, and someone asks for a list of those who can post.
How can this be queried?

--Donald
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Mailman Site Admin email Problem

2008-11-19 Thread Mark Sapiro
Sean Murphy wrote:

Mailman used to send me an email as the site admin that a new list has 
been created.  I use the web interface to create new lists.  This email 
had the aliases I needed to add to the /etc/mail/aliases file in the 
body of the email.   I have upgraded Mailman months ago but didn't 
notice that I had not been receiving this until now as the lists were 
already setup.

I know I can run the genaliases command to get the same output but I 
fear I am not seeing all of the mailman site admin email.

Is the email sent from a python script to an alias? is it specified in a 
config file?


This mail is only sent if MTA = 'Manual'. If you have MTA = 'Postfix'
or MTA = None in mm_cfg.py, no aliases mail will be sent.

When sent, the mail is sent to [EMAIL PROTECTED] (or whatever the name
of the site list is). You can test if this mail is deliverable by just
mailing anything to that address.

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Attachment URL in the archive is mangled.

2008-11-19 Thread Mark Sapiro
Mark Dale wrote:

In answer to your questions ...

I am using Mailman version: 2.1.5

Subscribers can choose digest if they want.

The link is broken in the digest messages, just like in the archive.

The broken link happens for every PDF file, even though the PDF arrives
with the email. (Doesn't arrive in the digest, just a broken link)

The link is almost okay, it's just the = sign that gets inserted that
messes things up.


There have been many changes in Scrubber.py (the module which does
this) since 2.1.5. I will look into it, but I don't know if I will be
able to duplicate the problem.


If it is a Word.doc that gets attached, no URL appears at all in the
archive, not is there even a scrubbed message. Also, Word.doc files
don't even arrive with the email.


Because these attachments are removed by content filtering before the
message is archived and delivered.

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Issues with sending messages to list

2008-11-19 Thread Mark Sapiro
Vikram Goyal wrote:

I manage three announcement only lists. I had some issues with the server
they were running on, because of which, I had to restart the server.
However, since starting the server, I can't seem to be able to send any
mails to any of the three lists.

 

I checked the mail logs (/var/log/maillog), and the following entry was
found for a test message send to the test list:

 

Nov 18 01:29:51 ip-X sendmail[13901]: mAI8ToHD013890:
to=|/usr/local/mailman/mail/mailman post test, ctladdr=[EMAIL PROTECTED]
(8/0), delay=00:00:01, xdelay=00:00:00, mailer=prog, pri=33119, dsn=2.0.0,
stat=Sent

 

To me, this means that the mail was sent to the mailman process. (I have
taken out the actual ip address and the domain for privacy reasons).


It means the mail was delivered to Mailman's mail wrapper which
presumably passed it to to Mailman's 'post' script which in turn would
place it in Mailman's in/ queue.


So, why would the users on the test list not get the messages? 


Ith most likely reason is you don't have an init script to start
mailman so mailman isn't running and all the messages are just sitting
in Mailman's in/ queue.

You could look at the FAQ at http://wiki.list.org/x/A4E9 for other
possibilities.


Also, which log messages should I look for and rely on? The var/log/maillog
or the log messages in the mailman directory?


Both, since the tell you about different steps in the process.

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


[Mailman-Users] One private archive not appearing online

2008-11-19 Thread jewel . brueggeman-makda
I am wanting to rebuild an archive but when I issue the following
command either as mailman or root:

bin/arch --wipe mylist
/usr/local/mailman/archives/private/mylist.mbox/mylist.mbox

I get the following error:

Traceback (most recent call last):
  File ./arch, line 200, in ?
main()
  File ./arch, line 177, in main
shutil.rmtree(mlist.archive_dir())
  File /usr/lib/python2.4/shutil.py, line 155, in rmtree
onerror(os.listdir, path, sys.exc_info())
  File /usr/lib/python2.4/shutil.py, line 153, in rmtree
names = os.listdir(path)
OSError: [Errno 2] No such file or directory:
'/usr/local/mailman/archives/private/mylist'

I believe this one archive has not been working for a very long time. 
The permissions are:
drwxrwsr-x   2 mailman mailman   4096 Nov 19 12:11 .
drwxrws--x 200 mailman mailman  12288 Nov 19 12:14 ..
-rw-rw-r--   1 mailman mailman 502357 Sep  1 04:00 mylist

When I run bin/check_perms -f it finds no problems.

Any other suggestions?

Jewel
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Finding all unmoderated users in a list

2008-11-19 Thread D G Teed
Here is a solution I received from Jerry Stratton using withlist command
from the command line...

Create a file to use with withlist.

==snip=
from Mailman import mm_cfg
def unmoderated(mlist):
   memberCount = 0
   for member in mlist.getMembers():
   if not mlist.getMemberOption(member, mm_cfg.Moderate):
   print member
   memberCount = memberCount + 1

   print Unmoderated members found:, memberCount
==snip=

If this is called queries.py, then you can use the following command to
list all unmoderated members of a mailing list:

withlist -r queries.unmoderated LISTNAME

Note that the file queries.py must be located in the home directory
of mailman (not in bin).

This is exactly what I needed.  Thanks to Jerry for this solution.

--Donald
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Attachment URL in the archive is mangled.

2008-11-19 Thread Mark Dale


 There have been many changes in Scrubber.py (the module which does
 this) since 2.1.5. I will look into it, but I don't know if I will be
 able to duplicate the problem.

For what it's worth Mark, I copied a Scrubber.py from a Version 2.19 on
the wild chance that it might do some good - but as was to be expected,
no magic occurred.

Here's hoping you do find a way to duplicate the problem. Upgrading this
installation would be like changing a flat tyre on a moving car.


 If it is a Word.doc that gets attached, no URL appears at all in the
 archive, not is there even a scrubbed message. Also, Word.doc files
 don't even arrive with the email.


 Because these attachments are removed by content filtering before the
 message is archived and delivered.

Understood. Thanks.



cheers
Mark Dale
-- 




--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


[Mailman-Users] Moving archives to a new list?

2008-11-19 Thread Johnny Stork


I have been running a mailing list which now requires a name change. I 
have created the new list and so was wondering if there is some way to 
move all the old archives to the new list? They are on the same 
server/domain, but have different names now?




--
Johnny Stork
Open Enterprise Solutions
Empowering Business With Open Solutions

http://www.openenterprise.ca

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


[Mailman-Users] Using an AUP with Mailman?

2008-11-19 Thread Johnny Stork
Other than placing a link on the mailing list signup page to an 
Acceptable Use Policy is there any way to force the use of such a 
policy before people can sign up for a mailing list in mailman? What I 
mean by force is something where they need to at least scroll down to 
the bottom of an AUP and check a box that they have read it before they 
can submit their signup request.



--
Johnny Stork
Open Enterprise Solutions
Empowering Business With Open Solutions

http://www.openenterprise.ca

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] The Mysterious Disappearing Disk Space (fwd)

2008-11-19 Thread J.A. Terranson

On Tue, 18 Nov 2008, Mark Sapiro wrote:

 J.A. Terranson wrote:
 
  I have looked through the archives for something similar to my 
 issue, and I noticed that by searching on disk full, I get similar 
 reports beginning in roughly July of 08.
 
  As with these other reports, I have noticed *tremendous* 
 disappearing space.  When I tried to find the actual files, I was 
 unsuccessful.  Interestingly, if I stop mailman and then restart it, the 
 missing space miraculously reappears! 
 
 
 Is this Solaris? If so, see the thread beginning at
 http://mail.python.org/pipermail/mailman-users/2008-July/062359.html
 which is about an alleged memory leak.

FreeBSD 6.3, and the issue in the above thread doesn't look like the same 
thing.

 If you're running out of disk, and restarting the processes solves it,
 it may be swap space that's eating up the disk.

I considered this, however swap is simply not being used at any time.  I 
put up a cron job to monitor, and swap use is literally zero all the way 
up to the crash for lack of space.  Honestly, it *feels* like some huge 
log file somewhere, but I can find no viable explanation for it.  This is 
a single partitioned box, with a single dedicated user (running 4 mailman 
lists and a few websites).  Using du I see space being eaten, but no 
indication as to where.   I see /usr and /var growing, but looking into 
them shows no file(s) that could account for the amount of missing space.

 
  So, now that the background is over with, here's where I find 
 myself (besides just looking stupid):
 
 (1) Yesterday I enabled VERP, and it appeared to be working well,  At the 
 time I turned on VERP, I had around 5gb of free space (which would take 
 about two weeks to disappear before VERP).
 
 
 5gb of free disk space doesn't seem like a lot these days.

Agreed.  But then, they arent doing much either.

 
 (2) Around 2pm today, the disk was full, and mailman died.
 
 
 Enabling VERP might cause the MTA to use a lot more queue space, but I
 don't see that it would affect Mailman much.

The only difference was in the rate at which the loss accrued.  Roughly 
a 6x increase.

 
 (3) My inkling of something being wrong was this on the web interface:
 
   Bug in Mailman version 2.1.11rc2
 
   We're sorry, we hit a bug!
 
   Please inform the webmaster for this site of this problem. Printing of 
   traceback and other system information has been explicitly inhibited, 
   but the webmaster can find this information in the Mailman error logs. 
 
 (4) Upon looking at the system in response to the above missive, I checked 
 and saw the system ws out of space again.  I did what I always do - shut 
 down mailman (which usually drops ~5gb of missing space, and then 
 restart it.  Everything before today has come up roses doing this.
 
 
 So are you saying that this time you didn't recover any disk space or
 just that the web error didn't go away. If the latter, it seems likely
 that the disk space error caused a config.pck file to be corrupted and
 that is the cause of the recurrent bug. What is the traceback from
 the most recent of these from the error log?

I apologize for the lack of clarity.  Im saying that the space did come 
back, as always, but this time was unique in throwing up this web message.  
All of the mailman core functionality appeared to be running normally 
(lots of traffic back and forth), but the web UI was dead.


 (5) There is nothing in any of the logs that indicate why this message is 
 continuing to poke fun at me.
 
 There almost certainly is something in Mailman's error log unless the
 logfile just can't be grown to accommodate the message.

No, there really isn't.  I have combed through all of them (bounce, error, 
mischeif, post qrunner, smtp  failure, subscribe and vette.  Did I miss 
anything?), with no sign of anything being wrong.  

I have several other mailman systems, and I have always seen a traceback 
or slew of messages when something went south, but nothing here.  Also, of 
note, this is the only mailman with the disappearing disk issue.  My other 
boxen are all running *really* old versions, and this new customer build 
is doubling as my canary:  so far, I see BIG improvements in throughput, 
but this disk thing has me crazy.  If I stop mailman when the drive hits 
99%, I instantly get my 5gb back.  It feels like Im writing a file that I 
cannot see, but I dont think this is physically possible (anyone know 
otherwise?).

I spent a few hours mucking around with the pickles trying to figure what 
broke, and finally gave up due to screaming users: I rebuilt.  The new 
build acts *just* like the last one (the reason for the delay in answering 
your kind reply was to see if the rebuild would get rid of this).  Ive 
lost about a gig over 24 hours, and I have NO idea where its going.  I 
stopped the job while writing this paragraph just to double check, and 
yes, I get it all back when the job is terminated.  Very odd indeed.

Im not 

[Mailman-Users] Patch available for review - SpamBayes support in gate_news

2008-11-19 Thread skip
I worked up a straightforward patch for gate_news which adds SpamBayes
support to that program.  This allows incoming Usenet news postings to be
checked for spam before foisting them off on unsuspecting mailing list
folks.

https://bugs.launchpad.net/mailman/+bug/300176

I've yet to figure out where gate_news is documented.  Once I have I'll
update that manual and upload a patch.

Feedback is appreciated.  After a couple extra sets of eyeballs have been
aimed at it I will work with the python.org postmasters to start testing it
there.

-- 
Skip Montanaro - [EMAIL PROTECTED] - http://smontanaro.dyndns.org/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] The Mysterious Disappearing Disk Space (fwd)

2008-11-19 Thread Stephen J. Turnbull
J.A. Terranson writes:

  It feels like Im writing a file that I cannot see, but I dont think
  this is physically possible (anyone know otherwise?).

Oh, indeed it is possible, and happens with log files all the time.
All you need to do is start a process that doesn't close its logfile
until it exits, then rm the logfile.  A variant of this technique is
also used to create secure scratch files (what other programs can't
see, they can't touch).

In Unix file system semantics, rm simply changes the entry in the
directory to make the file inaccessible, but the inode where all the
space allocation details are still exists, and the process with the
open file descriptor can continue writing to it.  However, when the
process exits, the file descriptor is close, the inode and the space
become garbage, and they get freed.

  Have I missed any log files?  Is there somewhere specific I should be 
  looking?  Is there some way to (easily) increase logging details to try 
  and track this down?

Unlikely.  A more direct approach is lsof (list open files).
Mailman has a bunch of processes, though, so make sure you've
identified the one you need to look at.  You want the -c (check
processes running certain command names) or -p (check processes for
certain PIDs) options.  Here's a look at my shell on Mac OS X:

chibi:SeminarSEA steve$ lsof -p 3771
COMMAND  PID  USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
bash3771 steve  cwd   VDIR   14,2  952 40850782 
/Users/steve/Work/Teaching/MBA/SeminarSEA
bash3771 steve  txt   VREG   14,2   581636 10221991 /bin/bash
bash3771 steve  txt   VREG   14,2  1797576 21766582 /usr/lib/dyld
bash3771 steve  txt   VREG   14,2  4402196 39746339 
/usr/lib/libSystem.B.dylib
bash3771 steve  txt   VREG   14,2   304580 39764872 
/usr/lib/libncurses.5.4.dylib
bash3771 steve0u  VCHR4,6  0t72917 42347780 /dev/ttyp6
bash3771 steve1u  VCHR4,6  0t72917 42347780 /dev/ttyp6
bash3771 steve2u  VCHR4,6  0t72917 42347780 /dev/ttyp6
bash3771 steve  255u  VCHR4,6  0t72917 42347780 /dev/ttyp6

In the FD column, cwd and txt are files that have been read into
the process space in some sense; they are not subject to IO.  The
numerical FDs are the ones of interest; here they are all just the
attached TTY (0, 1, and 2 are stdin, stdout, and stderr, of course).
bash apparently isn't writing or reading any regular files at the
moment.

Although Mac OS X uses the Mach microkernel, userland is based on
FreeBSD, so Your Mileage Should Not Vary (much).

I haven't actually looked at a file with no links in maybe a decade
(over precisely the issue I started with, I needed to free up space
fast so I nuked an unimportant log file ... but the process hadn't
closed it so I didn't get any space back :-P), so I'm not sure exactly
what you're looking for.  But I bet it sticks out like a sore
thumb. ;-)  I suppose there may be a way to look at its content
(perhaps in gdb?) which might help to identify what is going on.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] The Mysterious Disappearing Disk Space (fwd)

2008-11-19 Thread Gary Algier

J.A. Terranson wrote:

On Tue, 18 Nov 2008, Mark Sapiro wrote:


J.A. Terranson wrote:
	I have looked through the archives for something similar to my 
issue, and I noticed that by searching on disk full, I get similar 
reports beginning in roughly July of 08.


	As with these other reports, I have noticed *tremendous* 
disappearing space.  When I tried to find the actual files, I was 
unsuccessful.  Interestingly, if I stop mailman and then restart it, the 
missing space miraculously reappears! 


Is this Solaris? If so, see the thread beginning at
http://mail.python.org/pipermail/mailman-users/2008-July/062359.html
which is about an alleged memory leak.


FreeBSD 6.3, and the issue in the above thread doesn't look like the same 
thing.



If you're running out of disk, and restarting the processes solves it,
it may be swap space that's eating up the disk.


I considered this, however swap is simply not being used at any time.  I 
put up a cron job to monitor, and swap use is literally zero all the way 
up to the crash for lack of space.  Honestly, it *feels* like some huge 
log file somewhere, but I can find no viable explanation for it.  This is 
a single partitioned box, with a single dedicated user (running 4 mailman 
lists and a few websites).  Using du I see space being eaten, but no 
indication as to where.   I see /usr and /var growing, but looking into 
them shows no file(s) that could account for the amount of missing space.


 
	So, now that the background is over with, here's where I find 
myself (besides just looking stupid):


(1) Yesterday I enabled VERP, and it appeared to be working well,  At the 
time I turned on VERP, I had around 5gb of free space (which would take 
about two weeks to disappear before VERP).


5gb of free disk space doesn't seem like a lot these days.


Agreed.  But then, they arent doing much either.

 

(2) Around 2pm today, the disk was full, and mailman died.


Enabling VERP might cause the MTA to use a lot more queue space, but I
don't see that it would affect Mailman much.


The only difference was in the rate at which the loss accrued.  Roughly 
a 6x increase.


 

(3) My inkling of something being wrong was this on the web interface:

 Bug in Mailman version 2.1.11rc2

 We're sorry, we hit a bug!

 Please inform the webmaster for this site of this problem. Printing of 
 traceback and other system information has been explicitly inhibited, 
 but the webmaster can find this information in the Mailman error logs. 


(4) Upon looking at the system in response to the above missive, I checked 
and saw the system ws out of space again.  I did what I always do - shut 
down mailman (which usually drops ~5gb of missing space, and then 
restart it.  Everything before today has come up roses doing this.


So are you saying that this time you didn't recover any disk space or
just that the web error didn't go away. If the latter, it seems likely
that the disk space error caused a config.pck file to be corrupted and
that is the cause of the recurrent bug. What is the traceback from
the most recent of these from the error log?


I apologize for the lack of clarity.  Im saying that the space did come 
back, as always, but this time was unique in throwing up this web message.  
All of the mailman core functionality appeared to be running normally 
(lots of traffic back and forth), but the web UI was dead.



(5) There is nothing in any of the logs that indicate why this message is 
continuing to poke fun at me.

There almost certainly is something in Mailman's error log unless the
logfile just can't be grown to accommodate the message.


No, there really isn't.  I have combed through all of them (bounce, error, 
mischeif, post qrunner, smtp  failure, subscribe and vette.  Did I miss 
anything?), with no sign of anything being wrong.  

I have several other mailman systems, and I have always seen a traceback 
or slew of messages when something went south, but nothing here.  Also, of 
note, this is the only mailman with the disappearing disk issue.  My other 
boxen are all running *really* old versions, and this new customer build 
is doubling as my canary:  so far, I see BIG improvements in throughput, 
but this disk thing has me crazy.  If I stop mailman when the drive hits 
99%, I instantly get my 5gb back.  It feels like Im writing a file that I 
cannot see, but I dont think this is physically possible (anyone know 
otherwise?).


Yes, this is very possible:
1. open a file.
2. write data to it.
3. delete it
if the file is not closed, the space will still be in use, but there
won't be any entry in the parent directory for it.  You can test for
this by cd-ing to the base of the file system which is running out of
space.  Run du -dks ., then df -k ..  The two usage numbers should
be the same, within a few k.  If different, then the used space is not
reflected in any directory.

If this is the case, you may be able to find out which process has the
open, unlinked 

Re: [Mailman-Users] Finding all unmoderated users in a list

2008-11-19 Thread Mark Sapiro
D G Teed wrote:

If this is called queries.py, then you can use the following command to
list all unmoderated members of a mailing list:

withlist -r queries.unmoderated LISTNAME

Note that the file queries.py must be located in the home directory
of mailman (not in bin).


The above statement is not completely correct. It is true that if
queries.py is located in Mailman's home directory, it will work, but
it will also work if it is in the directory containing withlist
(normally Mailman's bin directory).

-- 
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://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] The Mysterious Disappearing Disk Space (fwd)

2008-11-19 Thread J.A. Terranson

A quick note to all three of you who responded with the lsof suggestion.

Thank you!  The first time I saw the lsof suggestion I wanted to kick 
myself in the back of the head!  It's been *so* long since I've had any 
need, that I had simply forgotten all about it.  It appears that it is no 
longer even part of the FreeBSD standard distribution anymore (I had to go 
fetch, although the last time I remember using lsof - ~20009ish or so - I 
am pretty sure it was already present and ready for service)...

I will be mucking with it tonight and I'll let everyone know what I find.

One last note, to everyone:  I always cringe when I have to break down and 
send out a help to a support list such as this, as so many of them will 
land you more RTFM and come back when you find it! than they civil 
replies.  This has been an inspiring experience - there is yet hope for 
the Intarwebs :-)

Thanks again, and I'll be back in a few days (or less).

//Alif

-- 
Yours,
J.A. Terranson
sysadmin_at_mfn.org
0xpgp_key_mgmt_is_broken-dont_bother
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] mail delivery not consistent and very slow

2008-11-19 Thread Grant Taylor

On 11/18/2008 12:14 PM, Jewel wrote:
*My smtp-failure and error logs are not helping me determine what's 
wrong. Whenever I post a test to any list so far it always gets 
delivered. But I have a few users who said they have tried several times 
and don't see anything.  I had one woman try again this morning and can 
see it on the archive but not in my email -but other postings have been 
successful!!


Please help me.  I have several members upset about the delay or lack of 
delivery and I can't find out what's going on.


Do your mail logs show messages leaving the mailing list going to the 
users that are claiming to have not received the message(s)?  If the 
messages do show up in your mail logs, then the problem is likely not 
with Mailman.  If the messages are not making it to your mail logs, then 
the problem probably is with Mailman.





Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] mail delivery not consistent and very slow

2008-11-19 Thread Grant Taylor

On 11/18/2008 02:09 PM, Jewel wrote:
I know it's not a gmail problem because it's happening with so many 
lists. I did notice that my CPU is almost always at 100% due to python - 
don't know why.  I know my machine is spitting out lots of mail but 
cannot figure out what there is such a delay.


With out knowing if messages are making it from Mailman to your MTA I 
can't say for sure, but it may be that your server's load average is too 
high and your MTA is refusing to accept new messages.




Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] spam gatewayed from Usenet to mail bypasses our spam filters

2008-11-19 Thread Grant Taylor

On 11/17/2008 11:20 PM, [EMAIL PROTECTED] wrote:
I still haven't figured out quite how to solve the problem.  In 
theory we could use some other tool to perform the gateway operation. 
Instead of passing Usenet postings directly to Mailman it would mail 
them to [EMAIL PROTECTED] where they would get the spam filter 
treatment before Mailman sees them.  I'm still thinking about the 
full ramifications of that.  It might be easier to get Mailman's 
news-to-mail gateway to mail incoming Usenet messages to the list 
address instead of directly distributing them to the subscribers 
though.  I don't believe Mailman does that out of the box (but I 
would love to be wrong here).  Has anyone tried implementing that? 
If so, got a patch or a recipe for how to configure Mailman to 
operate this way?


Few follow up questions:

1)  Will someone please provide the Path: header for a number (3 - 8) of 
the spam messages?  I suspect that the messages are originating from 
googlegroups.com which is /notorious/ for spam.


2)  Does gate_news have the ability to filter (gateway or not) messages 
based on the contents of the Path: header in the Usenet message?


3)  Is it possible to have gate_news call some of the other freely 
available Usenet spam filters that already exist?  Why re-invent the 
wheel if we can hook in to already existing filters on the Usenet side.




Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Attachment URL in the archive is mangled.

2008-11-19 Thread Grant Taylor

On 11/18/2008 06:52 PM, Mark Dale wrote:
Somehow an = gets inserted into the URL (see snippet below), and 
the links returns Private archive file not found.


*nod*

If I recall correctly when quoted=printable encoding is used, the = 
at the end of the line by its self is an indication to the receiving MUA 
that the line is suppose to be unwrapped.  I.e. remove the = from the 
end of the ...attachments/200 line and add the 81119... line to the end.


However if the quoted=printable MIME encoding is broken, things like 
this will happen.


Will you please forward me one of the problem messages (as an attachment 
because I need to see the message source) and I will verify this.



If I remove the = from the URL, all is well.


*nod*  This is as I would expect.

Actually I bet that you are removing the = and adding the subsequent 
line to the end of the URL, which is what quoted=printable is suppose to 
do for you.


Can anyone shed any light on this, and how I might correct things so 
the URL appears correctly (without the =) in the archive?


I think this is probably another small bug somewhere in Mailman in how 
it handles / folds lines of text.  Format=flowed (my preference) suffers 
equally in older versions of Mailman.



http://myDomain.com/cgi-bin/mailman/private/myListname/attachments/200=
81119/d1fa80ed/test.pdf



But this works:

http://myDomain.com/cgi-bin/mailman/private/myListname/attachments/20081119/d1fa80ed/test.pdf


*nod*



Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Using an AUP with Mailman?

2008-11-19 Thread Grant Taylor

On 11/19/2008 03:26 PM, Johnny Stork wrote:
Other than placing a link on the mailing list signup page to an 
Acceptable Use Policy is there any way to force the use of such a 
policy before people can sign up for a mailing list in mailman? What I 
mean by force is something where they need to at least scroll down to 
the bottom of an AUP and check a box that they have read it before they 
can submit their signup request.


You might be able to do some HTML / JavaScript trickery to pull this off 
on the sign up page.  At least in so far as hiding or disabling the 
button to sign up until people have checked the Accept the AUP check box.




Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] spam gatewayed from Usenet to mail bypasses our spam filters

2008-11-19 Thread Brad Knowles

on 11/20/08 12:54 AM, Grant Taylor said:

2)  Does gate_news have the ability to filter (gateway or not) messages 
based on the contents of the Path: header in the Usenet message?


Not inherently, no.  But that feature could be added.

3)  Is it possible to have gate_news call some of the other freely 
available Usenet spam filters that already exist?  Why re-invent the 
wheel if we can hook in to already existing filters on the Usenet side.


That's also a good idea, although not currently available in the 
existing code.


Call them before SpamBayes, I think.

--
Brad Knowles [EMAIL PROTECTED]
LinkedIn Profile: http://tinyurl.com/y8kpxu
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


[Mailman-Users] Duplicate posts to earthlink.com

2008-11-19 Thread BROOKS WILLIAMS
Hi,
We have subscribers on earthlink.com who receive multiple copies of
postings. Has anyone else had this problem? I saw a posting about it from
2003 but there was no solution given.

Thanks,

Brooks
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Duplicate posts to earthlink.com

2008-11-19 Thread Brad Knowles

on 11/19/08 11:16 PM, BROOKS WILLIAMS said:


We have subscribers on earthlink.com who receive multiple copies of
postings. Has anyone else had this problem? I saw a posting about it from
2003 but there was no solution given.


What is in your MTA logs?  What is in their MTA logs?

Have you seen several sample messages, so that you can do a comparison 
and contrast between the supposed duplicates?  In my experience, when 
you look closely at the Received: headers, you usually find that the two 
messages are literally identical with identical headers, queue-ids, 
etc... up to a point.  Beyond that point, they diverge.  And that's the 
place where your duplicate was created, so now you have a pretty good 
idea who to go whack.


--
Brad Knowles [EMAIL PROTECTED]
LinkedIn Profile: http://tinyurl.com/y8kpxu
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Duplicate posts to earthlink.com

2008-11-19 Thread Grant Taylor

On 11/20/2008 01:33 AM, Brad Knowles wrote:
Have you seen several sample messages, so that you can do a comparison 
and contrast between the supposed duplicates?  In my experience, when 
you look closely at the Received: headers, you usually find that the two 
messages are literally identical with identical headers, queue-ids, 
etc... up to a point.  Beyond that point, they diverge.  And that's the 
place where your duplicate was created, so now you have a pretty good 
idea who to go whack.


If my logic is correct, it should be the last server (Received: header 
closest to the top of the message) that received the message that was 
not duplicated.  If the two examples share one Received: header and then 
subsequent (closer to the top) are different, it is the server that 
generated last common Received header that is causing the duplication / 
sending the message multiple times.




Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] spam gatewayed from Usenet to mail bypasses our spam filters

2008-11-19 Thread Grant Taylor

On 11/20/2008 01:28 AM, Brad Knowles wrote:

Not inherently, no.  But that feature could be added.


*nod*

That's also a good idea, although not currently available in the 
existing code.


*nod*


Call them before SpamBayes, I think.


Agreed.

I don't know for sure, but I'm betting that SpamBayes is wanting to 
filter the message as if it is email, rather than news.  This means that 
it will inherently be later in the chain than other news filtering 
utilities.


Seeing as how there has been a fair amount of discussion about 
enhancing the Usenet support in Mailman, I as this question:


Is it appropriate to change Mailman such that it better supports Usenet 
or would we be better served by developing a gateway that will accept 
messages in on STDIN.


Doing things via STDIN would allow us to separate Mailman from the 
complexities of Usenet (or any thing else for that matter) and 
concentrate on mailing lists, what Mailman was designed to do.


Using the STDIN approach would dictate the need for a small standalone 
utility / gateway that could somehow get Usenet messages, be it a small 
NNTP server that receives a feed, some incarnation of suck, or something 
even more exotic retrieving messages and handing them out via STDOUT to 
Mailman's STDIN.


I believe this protocol independent interface between STDOUT and STDIN 
will make maintenance of things much simpler long term for both Mailman 
and what ever is used as the Usenet side of the gateway.


(Similar would be done to receive messages from Mailman and post them to 
Usenet.)




Grant. . . .
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9


Re: [Mailman-Users] Duplicate posts to earthlink.com

2008-11-19 Thread Brad Knowles

on 11/20/08 1:37 AM, Grant Taylor said:

If my logic is correct, it should be the last server (Received: header 
closest to the top of the message) that received the message that was 
not duplicated.  If the two examples share one Received: header and then 
subsequent (closer to the top) are different, it is the server that 
generated last common Received header that is causing the duplication / 
sending the message multiple times.


The problem is that you can't always be 100% certain which server is 
actually responsible.


I've seen cases where the receiving server generated a 4xx series error 
message after the end of the DATA section, or just plain timed out after 
the end of the DATA section, and the sending server thought it needed to 
retransmit the message.  But what really happened is that the receiving 
server actually accepted and delivered the message, and erroneously 
generated the error message, or didn't handle a timeout properly.


I've also seen cases where the sending server is at fault.


So, you at least know that there is a breakdown somewhere between the 
two machines in question, and you should be able to figure out who the 
respective administrators are, and work from there.  Once you actually 
confirm which machine is at fault, you know who you need to whack with 
the cluebat.


--
Brad Knowles [EMAIL PROTECTED]
LinkedIn Profile: http://tinyurl.com/y8kpxu
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9