[Mailman-Users] qfiles commands directory? Tried to delete outgoing message....

[NOW Website Coordinator]

I was trying to stop an outgoing message and wasn't quite sure where to do 
it.  I deleted two files in the qfiles/commands directory which seemed to 
be relevant, but it was too late, the message was on its way out.

I've accepted that fact, now my questions are:

1) What problems could I have caused by deleting something in the 
qfiles/commands directory?
2) How *do* you stop an outgoing mailman message?

Thanks.

Sarah Stapleton-Gray

Web Site Coordinator
National Organization for Women
http://www.now.org


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] 2.1 install glitches

[Phil Stracchino]

One more question, if people will bear with me 

My Postfix mailserver answers (for now) to both smtp.babcom.com and
smtp.caerllewys.net, and accepts mail for both.  Apache likewise serves
both www.babcom.com and www.caerllewys.net.  I want my lists to have mail
addresses such as [EMAIL PROTECTED], rather than smtp.caerllewys.net,
but I want the service page URLs to be http://www.caerllewys.net/...
rather than just http://caerllewys.net/...

I can get the first part of this equation, but I can't get Mailman to
consistently do the second.  I attach a sample for your perusal:

List-Id: 
List-Help: 
List-Post: 
List-Subscribe: ,

List-Archive: 
List-Unsubscribe: ,

Errors-To: [EMAIL PROTECTED]

On Sat, Feb 22, 2003 at 12:31:53AM -0500, Phil Stracchino wrote:
> Test
___
Moo-wizards mailing list
[EMAIL PROTECTED]
http://caerllewys.net/mailman/listinfo/moo-wizards


Note that List-Archive is http://www.caerllewys.net/pipermail/moo-wizards,
but every other URL is just http://caerllewys.net/mailman/...


What magic invocation do I need to use to fix this?  I've tried
everything I can think of, and I'm baffled.  What am I missing?


-- 
 .*  Fight Back!  It may not be just YOUR life at risk.  *.
 : phil stracchino : unix ronin : renaissance man : mystic zen biker geek :
 :  [EMAIL PROTECTED] : [EMAIL PROTECTED] : [EMAIL PROTECTED]  :
 :   2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold)   :
 :Linux Now!   ...Because friends don't let friends use Microsoft.:

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Shunting problem

[cary]

- I create a new list
- Subscribe my self to the list
- Send a test message
- Mass subscribe 50 email addresses to the new list
- Send a message

It never arrives and it shunted. I checked the error log and I get this.
This is a little frustrating as new lists work but fail the moment I add
new users. 

Any pointers? 

Thanks, 

Cary. 

---
ERROR
---

Feb 21 22:28:26 2003 (28586) Uncaught runner exception: iterable
argument required
Feb 21 22:28:26 2003 (28586) Traceback (most recent call last):
  File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop
self._onefile(msg, msgdata)
  File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File "/home/mailman/Mailman/Queue/IncomingRunner.py", line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
  File "/home/mailman/Mailman/Handlers/ToDigest.py", line 82, in process
send_digests(mlist, mboxfp)
  File "/home/mailman/Mailman/Handlers/ToDigest.py", line 123, in
send_digests
send_i18n_digests(mlist, mboxfp)
  File "/home/mailman/Mailman/Handlers/ToDigest.py", line 295, in
send_i18n_digests
msg = scrubber(mlist, msg)
  File "/home/mailman/Mailman/Handlers/Scrubber.py", line 257, in
process
url = save_attachment(mlist, part, dir)
  File "/home/mailman/Mailman/Handlers/Scrubber.py", line 349, in
save_attachment
ext = guess_extension(ctype, fnext)
  File "/home/mailman/Mailman/Handlers/Scrubber.py", line 80, in
guess_extension
if ext in all:
TypeError: iterable argument required


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] MemoryError in htmlformat.py

[Jon Carnes]

Hmmm Now that is a good question!

I assume you tried copying the heldmsg files back into the data
directory and then running the web-admindb (and that didn't work?)

If so then try sending a message to the list that would be held for
moderation and then replace the heldmsg-...pck file that is created with
one of the ones you copied off (just renaming it). Then approve the
moderated message and see if that does the job proper.

If that doesn't work, you can use the strings command to find who sent
the message and drop them a note asking them to resend the message.

Good Luck (and let us know what happens!)

On Fri, 2003-02-21 at 18:53, Stephan Spencer wrote:
> Thanks for that, Jon.
> 
> I am indeed running 2.1.
> 
> I tried deleting held messages but that didn't work. I'm still getting 
> a low-level error:
> 
> Feb 21 17:38:44 2003 admin(32190): 
> 
> admin(32190): [- Mailman Version: 2.1 -]
> admin(32190): [- Traceback --]
> admin(32190): Traceback (most recent call last):
> admin(32190):   File "/usr/local/mailman/scripts/driver", line 87, in 
> run_main
> 
> I deleted request.db and it works fine now. I've made backups of the 15 
> or so legitimate held messages (heldmsg-bnb-list-xxx.pck).
> 
> How do I get those back into request.db?
> 
> Thanks,
> Stephan
> 
> 
> On Saturday, February 22, 2003, at 04:54 AM, Jon Carnes wrote:
> 
> > What version of Mailman are you using?  (it looks like one of the 2.1.x
> > versions).
> >
> > Hope you have already fixed this by now, but just in case, here is
> > something you can try.  Look in the data directory for Mailman - this 
> > is
> > where the held messages are stored.  You can actually scan the heldmsg
> > files manually and delete ones that might be overly large.
> >
> > cd /usr/local/mailman/data
> > ls -l
> >
> > The default message format in version 2.1 is pickle (instead of text),
> > but you can still easily look at each held message by using the strings
> > command ("strings" is a utility that used to be loaded by default, if
> > you don't have it loaded it's very easy to find).
> >
> > strings heldmsg-b2b-list-1.pck
> >
> > Deleting the heldmsg's here does not delete them from your lists
> > "request.db" file, but when you run admindb for the list, that will
> > compare the heldmsg files to the ones in request.db and then update
> > request.db (the handling of the request.db file is a lot smarter in
> > version 2.1 of Mailman).
> >
> > In other words,once you launch the Web-admindb everything should sync 
> > up
> > and you will just see the messages you left that need approving.  It
> > *should* work at this point.  > you deleted the bad email>
> >
> > If not, I recommend removing that lists request.db file:
> > /usr/local/mailman/lists/b2b-list/request.db
> >
> > Just rename the file to something else and then try launching the
> > web-admindb again.
> >
> > Good Luck - Jon Carnes
> >
> > ==
> > On Wed, 2003-02-19 at 05:14, Stephan Spencer wrote:
> >> This one is out of my depth. The Tend to Pending Moderator Requests
> >> page has become inaccessible due to a MemoryError. The traceback
> >> follows below. Any guidance would be greatly appreciated. (The list in
> >> question is gated to the moderated Usenet newsgroup
> >> rec.travel.bed+breakfast, so it gets a lot of incoming spam. Not sure
> >> if that has anything to do with the problem at hand, however.). 
> >> Thanks!
> >>
> >>
> >> Traceback (most recent call last):
> >>File "/usr/local/mailman/scripts/driver", line 87, in run_main
> >>  main()
> >>File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 236, in main
> >>  print doc.Format()
> >>File "/usr/local/mailman/Mailman/htmlformat.py", line 331, in 
> >> Format
> >>  output.append(Container.Format(self, indent))
> >>File "/usr/local/mailman/Mailman/htmlformat.py", line 264, in 
> >> Format
> >>  output.append(HTMLFormatObject(item, indent))
> >>File "/usr/local/mailman/Mailman/htmlformat.py", line 50, in
> >> HTMLFormatObject
> >>  return item.Format(indent)
> >>File "/usr/local/mailman/Mailman/htmlformat.py", line 417, in 
> >> Format
> >>  output = output + Container.Format(self, indent+2)
> >>File "/usr/local/mailman/Mailman/htmlformat.py", line 264, in 
> >> Format
> >>  output.append(HTMLFormatObject(item, indent))
> >>File "/usr/local/mailman/Mailman/htmlformat.py", line 50, in
> >> HTMLFormatObject
> >>  return item.Format(indent)
> >>File "/usr/local/mailman/Mailman/htmlformat.py", line 200, in 
> >> Format
> >>  output = output + self.FormatRow(i, indent + 2)
> >> MemoryError
> >>
> >> Python information:
> >>
> >> Variable
> >> Value
> >>
> >> sys.version
> >> 2.2.2 (#1, Jan 14 2003, 02:49:11)  [GCC 2.96 2731 (Red Hat Linux
> >> 7.1 2.96-98)]
> >>
> >> sys.executable
> >> /usr/local/bin/python
> >>
> >> sys.prefix
> >> /usr/local
> >>
> >> sys.exec_prefix
> >> /usr/local
> >>
> >> sys.p

Re: [Mailman-Users] reject all...

[Spam Collector]

Right on!  I'll inquire to see if I can get this done.
C.


On 21 Feb 2003, Jon Carnes wrote:

> This is a feature of Mailman version 2.1.  Upgrade to version 2.1.1
>
> On Fri, 2003-02-21 at 02:57, Spam Collector wrote:
> >
> > Hello..
> >   Anyone know of a way to do a "reject all"?  My lists get a ton of spam,
> > and it gets old selected reject over and over..
> >
> > Thanks!
> >
> > C.
> >
>
>
>


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] reject all...

[Spam Collector]

Thanks, I am aware of the FAQ, and the process that you suggested,
however I am not the owner of the machine, IE I run the lists via the
gui, , but  do not have command line access.  Ideally I thought this forum
would be  the best place to ask, and sugest that in the "held messages"
area there  be radio buttons at the top or bottom for "delete all" or
"approve all" etc.

C.

On Fri, 21 Feb 2003, Matthew Davis wrote:

> * Spam Collector ([EMAIL PROTECTED]) wrote:
> >   Anyone know of a way to do a "reject all"?  My lists get a ton of spam,
> > and it gets old selected reject over and over..
>
> Check FAQ 1.12
>
> > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
>
> --
> Matthew Davis
> http://dogpound.vnet.net/
>
> Thesaurus: ancient reptile with an excellent vocabulary.
>


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] EFF Mailing List Query

[Barry A. Warsaw]

FYI,

>From the latest EFF mailer...
-Barry

 snip snip 
* Mailing List Headaches? Contact us.

EFF believes that delivery of legitimate e-mail needs to be carefully
protected as a fundamental part of any solution to the spam problem.
Unfortunately, we've lately learned that more and more opt-in mailing
lists are being mislabeled as spam and wrongly blocked.  EFF is
looking for people who administer opt-in e-mail mailing lists and have
had difficulty because their messages have been mislabeled as spam,
causing delivery to fail.  Our hope is to connect the folks facing
this problem so that they can work together to find a global solution
that both respects the Internet as a place of free speech (and e-mail
as a vital organizing tool) while protecting Internet users and
sysadmins from the problems that *real* spam causes.  Contact
[EMAIL PROTECTED]

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] 2.1 install glitches

[Phil Stracchino]

I finally got Mailman-2.1.1 doing what I want, but a certain amount of
trial and error in the data directory was involved.  It appears if you
have a umask set when you install it, you will end up with incorrect and
non-working permissions on data/aliases and data/aliases.db.


-- 
 .*  Fight Back!  It may not be just YOUR life at risk.  *.
 : phil stracchino : unix ronin : renaissance man : mystic zen biker geek :
 :  [EMAIL PROTECTED] : [EMAIL PROTECTED] : [EMAIL PROTECTED]  :
 :   2000 CBR929RR, 1991 VFR750F3 (foully murdered), 1986 VF500F (sold)   :
 :Linux Now!   ...Because friends don't let friends use Microsoft.:

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman 2.2.1 and Apache running on adifferent port

[Larry Rosenman]

--On Friday, February 21, 2003 21:42:50 -0300 Jorge Godoy <[EMAIL PROTECTED]> 
wrote:

Hi!

I have apache running on port 8080 and when I try using the
administrative interface for, e.g., creating a mailing list, it
redirects or try accessing port 80. Mailman isn't keeping the ":8080"
after the domain name.
Is it a bug of mine or from Mailman's code?
what mailman version, please?



TIA,
--
Godoy.   <[EMAIL PROTECTED]>
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/ler%40lerctr.org


--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: [EMAIL PROTECTED]
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman 2.2.1 and Apache running on a different port

[Jorge Godoy]

Hi!


I have apache running on port 8080 and when I try using the
administrative interface for, e.g., creating a mailing list, it
redirects or try accessing port 80. Mailman isn't keeping the ":8080"
after the domain name.

Is it a bug of mine or from Mailman's code?


TIA,
-- 
Godoy.   <[EMAIL PROTECTED]>

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Problem with bogus un-unsubscribable user

[Jay Sekora]

Hi.  One of the list-admins at my site was testing the bulk-subscription
box under Mailman 2.1, and tried to subscribe an address that looked 
like (as he described it to me)

[EMAIL PROTECTED] (Foo Bar)

but there must have been a tab in there because (according to 
mm_list_members) the address that actually got subscribed was

[EMAIL PROTECTED]   foo

(all lowercase, no parentheses, but with a tab in the middle).  Now 
he can't unsubscribe that address via the web interface, and I can't 
unsubscribe it with remove_members.  Here's what I get (with the actual 
bits of the address changed for privacy's sake) when I try:

%  /priv/daemons/packages/mailman-2.1/mailman/bin/remove_members -f - com3351
[EMAIL PROTECTED]  foo  [typed with a tab; I've also tried
sticking the address in a file and
providing that]
[Control-D]
Traceback (most recent call last):
  File "/priv/daemons/packages/mailman-2.1/mailman/bin/remove_members", line 179, in ?
main()
  File "/priv/daemons/packages/mailman-2.1/mailman/bin/remove_members", line 169, in 
main
userack)
  File "/priv/daemons/packages/mailman-2.1/mailman/Mailman/MailList.py", line 922, in 
ApprovedDeleteMember
self.removeMember(emailaddr)
  File "/priv/daemons/packages/mailman-2.1/mailman/Mailman/OldStyleMemberships.py", 
line 217, in removeMember
self.__assertIsMember(member)
  File "/priv/daemons/packages/mailman-2.1/mailman/Mailman/OldStyleMemberships.py", 
line 113, in __assertIsMember
raise Errors.NotAMemberError, member
Mailman.Errors.NotAMemberError: [EMAIL PROTECTED]


So evidently the tab is getting stripped out before remove_members 
tries to unsubscribe, but not getting stripped out before the CGI 
script adds the address (and it seems to have messed up parsing of 
the comment in parentheses).

So to make a long story short:

(1) I guess this is a bug report, and

(2) Can anybody tell me how I can remove this address by hand?  (I 
can mostly make sense of Python when I read it, but I don't know enough 
Python to pull the bad value out of the .pck file.)

Thanks!

Jay

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Problem with multiple subscription confirmation messages

[S. Krishnan]

Hi,

I just upgraded my mailman 2.0.13 install to 2.1.1 by downloading and
installing from source. The previous version worked fine.  However,
2.1.1 has a major issue with subscription messages.  Every time someone
subscribes to a list, mailman sends them a mailing list subscription
confirmation notice.  With mailman 2.1.1, replying to this notice does
not seem to work.  Instead of confirming the subscription, it sends
*another* mailing list subscription confirmation notice, with a
different number.  Replying to this results in yet another subscription
confirmation notice! 

However, subscription confirmation off the web page works OK.  It is
only the confirmation by reply to the notice that is broken.

Could someone please help?

TIA,

Krishnan



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] arch failure (MM2.1)

[Rupa Schomaker]

So, i wanted to re build my web archives...  Running:

bin/arch --wipe listname

did a bunch of work and then (python 2.1 from debian):

Pickling archive state into /var/lib/mailman/archives/private/kiwi/pipermail.pck
Traceback (most recent call last):
  File "bin/arch", line 187, in ?
main()
  File "bin/arch", line 175, in main
archiver.processUnixMailbox(fp, start, end)
  File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 544, in 
processUnixMailbox
m = mbox.next()
  File "/usr/lib/python2.1/mailbox.py", line 30, in next
return self.factory(_Subfile(self.fp, start, stop))
  File "/usr/lib/mailman/Mailman/Mailbox.py", line 79, in scrubber
return mailbox.scrub(msg)
  File "/usr/lib/mailman/Mailman/Mailbox.py", line 99, in scrub
return self._scrubber(self._mlist, msg)
  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 223, in process
url = save_attachment(mlist, part, dir)
  File "/usr/lib/mailman/Mailman/Handlers/Scrubber.py", line 302, in save_attachment
decodedpayload = msg.get_payload(decode=1)
  File 
"/home/rupa/src/mailman/mailman-2.1/debian/mailman/var/lib/mailman/pythonlib/email/Message.py",
 line 189, in get_payload
return Utils._bdecode(payload)
  File 
"/home/rupa/src/mailman/mailman-2.1/debian/mailman/var/lib/mailman/pythonlib/email/Utils.py",
 line 75, in _bdecode
value = base64.decodestring(s)
  File "/usr/lib/python2.1/base64.py", line 44, in decodestring
return binascii.a2b_base64(s)
binascii.Error: Incorrect padding

-- 
-rupa


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] upgrade

[_andreas]

hmm, no, USE_CRYPT=0 did not work.
I am using 2.1 full version.
Maybe there is a way to convert the user database to the current format?

_andreas.

- Original Message -
From: "Jon Carnes" <[EMAIL PROTECTED]>
To: "Andreas Moxnes" <[EMAIL PROTECTED]>
Cc: "Mailman users Mailing list" <[EMAIL PROTECTED]>
Sent: Friday, February 21, 2003 8:15 PM
Subject: Re: [Mailman-Users] upgrade


> Interesting... That is not supposed to happen in version 2.1 (are you
> running the full version or one of the betas?)
>
> >From the archives come wisdom in form of words from Barry:
> ===
> I'm guessing somewhere along the way Python got upgraded and the
> status of the crypt libraries changed (either they were there before
> and not now, or vice versa).  Try setting USE_CRYPT=0 in your
> mm_cfg.py file.
>
> A better solution would be to upgrade to MM2.1.  It uses sha1 hashing,
> which will always be available.
> ===
>
> I don't think that MM2.1 recognizes the "USE_CRYPT" variable, but since
> it is calling the older version of the Password handler, that may work.
>
> Hope that works (or it's not a problem any more...)

> On Wed, 2003-02-19 at 04:04, Andreas Moxnes wrote:
> > hello,
> > i've received a dump of different lists and archives
> > from an older mailman version (don't know which version).
> > i've installed mailman2.1, copied the lists to the mailman
> > dir and used the ./bin/fix_url.py.
> >
> > everything works fine exept for one thing: if an "old" user
> > (from the previous version) asks mailman to send a passord-reminder,
> > the following error occurs.
> >
> > any tips?
> >
> > thanks,
> > _andreas.
> >
> > Bug in Mailman version 2.1
> >
> > We're sorry, we hit a bug!
> > If you would like to help us identify the problem, please email a copy
of
> > this page to the webmaster for this site with a description of what
> > happened. Thanks!
> >
> > Traceback:
> >
> > Traceback (most recent call last):
> >   File "/usr/local/mailman/scripts/driver", line 87, in run_main
> > main()
> >   File "/usr/local/mailman/Mailman/Cgi/options.py", line 169, in main
> > mlist.MailUserPassword(user)
> >   File "/usr/local/mailman/Mailman/Deliverer.py", line 87, in
> > MailUserPassword
> > if not self.getMemberPassword(user):
> >   File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in
> > getMemberPassword
> > raise Errors.NotAMemberError, member
> > NotAMemberError: [EMAIL PROTECTED]
> >
> >
> >
> >
> >
>
> --
--
> >
> > Python information:
> > Variable Value
> > sys.version 2.2.2 (#3, Dec 30 2002, 15:34:51) [GCC 3.2 20020903 (Red Hat
> > Linux 8.0 3.2-7)]
> > sys.executable /usr/local/www/bin/python2.2
> > sys.prefix /usr/local/www
> > sys.exec_prefix /usr/local/www
> > sys.path /usr/local/www
> > sys.platform linux2
> >
> >
> >
> >
>
> --
--
> >
> > Environment variables:
> > Variable Value
> > PATH_INFO  /110
> > HTTP_ACCEPT  image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> > application/msword, application/vnd.ms-excel,
> > application/vnd.ms-powerpoint, */*
> > HTTP_PRAGMA  no-cache
> > CONTENT_TYPE  application/x-www-form-urlencoded
> > HTTP_REFERER  http://kunst.no/mailman/options/110
> > SERVER_SOFTWARE  Apache/1.3.27 (Unix) PHP/4.3.0
> > PYTHONPATH  /usr/local/mailman
> > SCRIPT_FILENAME  /usr/local/mailman/cgi-bin/options
> > SERVER_ADMIN  [EMAIL PROTECTED]
> > SCRIPT_NAME  /mailman/options
> > SCRIPT_URI  http://kunst.no/mailman/options/110
> > SERVER_SIGNATURE  Apache/1.3.27 Server at kunst.no Port 80
> > REQUEST_METHOD  POST
> > HTTP_HOST  kunst.no
> > SCRIPT_URL  /mailman/options/110
> > SERVER_PROTOCOL  HTTP/1.0
> > QUERY_STRING
> > REQUEST_URI  /mailman/options/110
> > CONTENT_LENGTH  69
> > HTTP_USER_AGENT  Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0)
> > HTTP_CONNECTION  Keep-Alive
> > HTTP_COOKIE
> >
110+admin=28020069a6ae533e732800353666376238383338303238666530346663
31393234323533346236353062323861633637633666;
> > PHPSESSID=46be25a32188f7c0d5ff4a7acdaa9cc9
> > SERVER_NAME  kunst.no
> > REMOTE_ADDR  129.240.157.171
> > REMOTE_PORT  3576
> > HTTP_ACCEPT_LANGUAGE  en-us
> > PATH_TRANSLATED  /usr/local/www/htdocs/kunst.no/110
> > SERVER_PORT  80
> > GATEWAY_INTERFACE  CGI/1.1
> > SERVER_ADDR  158.36.77.162
> > DOCUMENT_ROOT  /usr/local/www/htdocs/kunst.no
>


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] upgrade

[Jon Carnes]

Interesting... That is not supposed to happen in version 2.1 (are you
running the full version or one of the betas?)

>From the archives come wisdom in form of words from Barry:
===
I'm guessing somewhere along the way Python got upgraded and the
status of the crypt libraries changed (either they were there before
and not now, or vice versa).  Try setting USE_CRYPT=0 in your
mm_cfg.py file.

A better solution would be to upgrade to MM2.1.  It uses sha1 hashing,
which will always be available.
===

I don't think that MM2.1 recognizes the "USE_CRYPT" variable, but since
it is calling the older version of the Password handler, that may work.

Hope that works (or it's not a problem any more...)

On Wed, 2003-02-19 at 04:04, Andreas Moxnes wrote:
> hello,
> i've received a dump of different lists and archives
> from an older mailman version (don't know which version).
> i've installed mailman2.1, copied the lists to the mailman
> dir and used the ./bin/fix_url.py.
> 
> everything works fine exept for one thing: if an "old" user
> (from the previous version) asks mailman to send a passord-reminder,
> the following error occurs.
> 
> any tips?
> 
> thanks,
> _andreas.
> 
> Bug in Mailman version 2.1
> 
> We're sorry, we hit a bug!
> If you would like to help us identify the problem, please email a copy of
> this page to the webmaster for this site with a description of what
> happened. Thanks!
> 
> Traceback:
> 
> Traceback (most recent call last):
>   File "/usr/local/mailman/scripts/driver", line 87, in run_main
> main()
>   File "/usr/local/mailman/Mailman/Cgi/options.py", line 169, in main
> mlist.MailUserPassword(user)
>   File "/usr/local/mailman/Mailman/Deliverer.py", line 87, in
> MailUserPassword
> if not self.getMemberPassword(user):
>   File "/usr/local/mailman/Mailman/OldStyleMemberships.py", line 102, in
> getMemberPassword
> raise Errors.NotAMemberError, member
> NotAMemberError: [EMAIL PROTECTED]
> 
> 
> 
> 
> 
> 
> 
> Python information:
> Variable Value
> sys.version 2.2.2 (#3, Dec 30 2002, 15:34:51) [GCC 3.2 20020903 (Red Hat
> Linux 8.0 3.2-7)]
> sys.executable /usr/local/www/bin/python2.2
> sys.prefix /usr/local/www
> sys.exec_prefix /usr/local/www
> sys.path /usr/local/www
> sys.platform linux2
> 
> 
> 
> 
> 
> 
> Environment variables:
> Variable Value
> PATH_INFO  /110
> HTTP_ACCEPT  image/gif, image/x-xbitmap, image/jpeg, image/pjpeg,
> application/msword, application/vnd.ms-excel,
> application/vnd.ms-powerpoint, */*
> HTTP_PRAGMA  no-cache
> CONTENT_TYPE  application/x-www-form-urlencoded
> HTTP_REFERER  http://kunst.no/mailman/options/110
> SERVER_SOFTWARE  Apache/1.3.27 (Unix) PHP/4.3.0
> PYTHONPATH  /usr/local/mailman
> SCRIPT_FILENAME  /usr/local/mailman/cgi-bin/options
> SERVER_ADMIN  [EMAIL PROTECTED]
> SCRIPT_NAME  /mailman/options
> SCRIPT_URI  http://kunst.no/mailman/options/110
> SERVER_SIGNATURE  Apache/1.3.27 Server at kunst.no Port 80
> REQUEST_METHOD  POST
> HTTP_HOST  kunst.no
> SCRIPT_URL  /mailman/options/110
> SERVER_PROTOCOL  HTTP/1.0
> QUERY_STRING
> REQUEST_URI  /mailman/options/110
> CONTENT_LENGTH  69
> HTTP_USER_AGENT  Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 4.0)
> HTTP_CONNECTION  Keep-Alive
> HTTP_COOKIE
> 
>110+admin=28020069a6ae533e73280035366637623838333830323866653034666331393234323533346236353062323861633637633666;
> PHPSESSID=46be25a32188f7c0d5ff4a7acdaa9cc9
> SERVER_NAME  kunst.no
> REMOTE_ADDR  129.240.157.171
> REMOTE_PORT  3576
> HTTP_ACCEPT_LANGUAGE  en-us
> PATH_TRANSLATED  /usr/local/www/htdocs/kunst.no/110
> SERVER_PORT  80
> GATEWAY_INTERFACE  CGI/1.1
> SERVER_ADDR  158.36.77.162
> DOCUMENT_ROOT  /usr/local/www/htdocs/kunst.no
> 
> 
> 
> 
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] reject all...

[Jon Carnes]

This is a feature of Mailman version 2.1.  Upgrade to version 2.1.1

On Fri, 2003-02-21 at 02:57, Spam Collector wrote:
> 
> Hello..
>   Anyone know of a way to do a "reject all"?  My lists get a ton of spam,
> and it gets old selected reject over and over..
> 
> Thanks!
> 
> C.
> 



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Problems with Apache on different port

[Jon Carnes]

A couple of folks have done this and they needed to use
~mailman/bin/fix_url.py to modify the url's inside the configurations of
their existing lists in order for it work.  You may also need to modify
the default urls in ~mailman/Mailman/mm_cfg.py

Note: a redirect to the port will not work as the redirect loses all the
post information.

HtH, Jon Carnes

On Thu, 2003-02-20 at 13:25, Jorge Godoy wrote:
> 
> Hi!
> 
> 
> I have apache listening on port 8080 here, so I access the mailman
> interface as http://server.home.com:8080/mailman/ -- this works just
> fine but then my problems start. Every link I click links correctly to
> the page, except for the port number on the URL. It prevents me from
> using the webinterface to create or maintain lists.
> 
> I'm using mailman-2.1.1 on a FreeBSD 5.0
> 
> 
> TIA,
> -- 
> Godoy.<[EMAIL PROTECTED]>
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Authentication doesn't "stick" for virtual domain

[Rupa Schomaker]

I have mailman setup with two virtual domains.  Emails seem to work
fine, but authentication on one of the virtual domains does not work.

Primary: www.rupa.com/mailman/... works fine
virtual: list.gurukuli.com/mailman/... doens't.

The symptom is that I can "login" on the virtual, but any action after
that dumps me back into the login screen.

Not sure how to debug this one.  I searched the archives, but didn't
see anything obvious.

Version: 2.1 + htdig pages (and all the ones associated with it)

This used to work with v2.0

-- 
-rupa


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Multiple-domain Mailman question

[Jon Carnes]

On Thu, 2003-02-20 at 19:14, Phil Stracchino wrote:
> I think I may be trying to do something unsupported.

No. It is supported, and a common occurrence.  Feel free to read the
archives.
> 
> I just upgraded my Mailman installation from v2.0.6 to v2.1.1, and at
> the same time I'm preparing to switch my mail delivery domain over from
> babcom.com to caerllewys.net.  The webserver still advertises as
> www.babcom.com (although it answers to www.caerllewys.net as well).  Is
> there a defined way to migrate my existing Mailman lists from
> [EMAIL PROTECTED] to [EMAIL PROTECTED]?  

Yes. you will need to edit mm_cfg.py and modify the default host and url
values; then you will have to modify the existing host and url values in
your current lists - use the ~mailman/bin/fix_url.py utility (read that
file for examples, see the archives for other examples)

Note: Read ~mailman/Mailman/Defaults.py and copy any and all sections
that you want to modify over to mm_cfg.py

> I *also* want the lists to
> appear on the main Mailman listinfo page regardless of whether the
> listinfo page is invoked as http://www.babcom.com/mailman/listinfo or as
> http://www.caerllewys.net/mailman/listinfo.
> 
> Is this possible?

Yes.  You will need to change a setting in your mm_cfg.py file:

  # When set, the listinfo and admin overviews of lists
  # on the machine will be confined to only those lists
  # whose web_page_url configuration option host is
  # included within the URL by which the page is visited.
  # Only those "on the virtual host".  If unset, then all
  # advertised (i.e. public) lists are included in the
  # overview.
  # VIRTUAL_HOST_OVERVIEW = 1
  VIRTUAL_HOST_OVERVIEW = 0

> 
Good Luck - Jon Carnes


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Monthly password reminders

[Jon Carnes]

Apples and Oranges?

When I set the list to no monthly reminders (Web-Admin/general) then
that stays set - even after I add folks to the list.  Is it changing for
you?

When I add folks to the list (Web-Admin/members/add), there is the
option to send them a "welcome message", but there is no individual
monthly password notification for them.
Note: the welcome message does contain the users password.

Take care - Jon Carnes

On Thu, 2003-02-20 at 10:53, Paul Dekkers wrote:
> Hi,
> 
> In the mailinglist configuration I specified that users should not get 
> monthly password reminders by default: when I add a new users to the 
> mailinglist however, I see that the password reminder IS enabled!
> Is this OK?
> 
> I'm using mailman-2.1.1
> 
> Regards,
> Paul
> 
> 
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Upgrade to 2.1

[Andy Firman]

> >I am upgrading to 2.1 now from 2.0.13
> >a couple of questions
> >How safe is it to install into the previuos mailman directory
> > (/home/mailman)? If I do not install in the old directory how easy is it
> > to copy my lists across?
>
> I upgraded my production MM 2.0.13 to MM 2.1 (and later that to 2.1.1) by
> installing over the old installation without any problems. 

I would like to do the same but I am using Debian 3.0.

Any Debian users on this list?
How would I upgrade from 2.0.11?

When I installed the system I just did an apt-get install mailman.

Do I need to do a source install to upgrade?
Not sure if I can do that.

(same thing with Exim 3 to Exim 4...I have no clue how to upgrade but
that question is probably not appropriate here.)

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] reject all...

[Matthew Davis]

* Spam Collector ([EMAIL PROTECTED]) wrote:
>   Anyone know of a way to do a "reject all"?  My lists get a ton of spam,
> and it gets old selected reject over and over..

Check FAQ 1.12

> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

--
Matthew Davis
http://dogpound.vnet.net/

Thesaurus: ancient reptile with an excellent vocabulary.

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Re: Mailman-Users Digest, Vol 5, Issue 69

[Warren Hoffman]

We set the count to 90k and daily which results in one digest 99.9% of the 
time. I do appreciate that people on slow connections might prefer smaller 
digests, but then they could get individual messages or read the mail 
selectively via a web interface. I suspect most people on this list are on 
some sort of high speed connection. Anyway (and I have to confess my major 
profession concerns (people) group dynamics), it's a question of which 
norms suit the larger number of people or the people with the power. Maybe 
a vote is needed (for guidance).

--Warren
-
At 12:00 PM 2/21/2003 -0500, you wrote:
Content-Transfer-Encoding: 7bit
From: John DeCarlo <[EMAIL PROTECTED]>
Subject: Re: [Mailman-Users] Digests for this list
Cc: [EMAIL PROTECTED]
Date: Fri, 21 Feb 2003 09:41:29 -0500
To: Warren Hoffman <[EMAIL PROTECTED]>
Message: 3

Warren,

How do you set up digests on the lists you run?




_|_|_|  Warren Hoffman - Organization Improvement Consultant
_|_|_|  208 Jackson Blvd., Wilmington, DE 19803
_|_|_|  Phone/Fax: 302-658-7508
_|_|_|  [EMAIL PROTECTED]
_|_|_|   http://www.whoffman.com


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] MM 2.1 topics question...

[Jon Carnes]

In logic class we learned that the opposite of: A or B
was:  not(A) and not(B)

The "or" changes to "and"

HtH - Jon Carnes

On Thu, 2003-02-20 at 14:04, Jeff Hahn wrote:
> I'm playing with topics to see how they work.
> 
> I want to hold any message that doesn't match an existing topic.
> 
> (actually I'd also like to hold any message that has more than one topic, 
> but that can wait for step two)
> 
> let's say we have topics AAA and BBB and topics must be in subject.
> 
> if I use "subject: .*AAA.*|.*BBB.*" in the spam filters on the privacy 
> option page, it works backwords (as you would expect).  
> 
> how the heck do I "negate" that regular expression?
> 
> it would seem that"subject: [^.*AAA.*|.*BBB.*]" or 
>   "subject: [^[.*AAA.*|.*BBB.*]]"
> 
> but those don't seem to work as they should
> 
> I'm obviously missing something simple (greedy matching perhaps?), but I 
> can't seem to see it.
> 
> any helpful hints???
> 
> Thanks,
> 
> -Jeff
> 
> 
> 
> 
> 
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] MemoryError in htmlformat.py

[Jon Carnes]

What version of Mailman are you using?  (it looks like one of the 2.1.x
versions).

Hope you have already fixed this by now, but just in case, here is
something you can try.  Look in the data directory for Mailman - this is
where the held messages are stored.  You can actually scan the heldmsg
files manually and delete ones that might be overly large.  

cd /usr/local/mailman/data
ls -l

The default message format in version 2.1 is pickle (instead of text),
but you can still easily look at each held message by using the strings
command ("strings" is a utility that used to be loaded by default, if
you don't have it loaded it's very easy to find).

strings heldmsg-b2b-list-1.pck

Deleting the heldmsg's here does not delete them from your lists
"request.db" file, but when you run admindb for the list, that will
compare the heldmsg files to the ones in request.db and then update
request.db (the handling of the request.db file is a lot smarter in
version 2.1 of Mailman).

In other words,once you launch the Web-admindb everything should sync up
and you will just see the messages you left that need approving.  It
*should* work at this point. 

If not, I recommend removing that lists request.db file:
/usr/local/mailman/lists/b2b-list/request.db

Just rename the file to something else and then try launching the
web-admindb again.

Good Luck - Jon Carnes
 
==
On Wed, 2003-02-19 at 05:14, Stephan Spencer wrote:
> This one is out of my depth. The Tend to Pending Moderator Requests 
> page has become inaccessible due to a MemoryError. The traceback 
> follows below. Any guidance would be greatly appreciated. (The list in 
> question is gated to the moderated Usenet newsgroup 
> rec.travel.bed+breakfast, so it gets a lot of incoming spam. Not sure 
> if that has anything to do with the problem at hand, however.). Thanks!
> 
> 
> Traceback (most recent call last):
>File "/usr/local/mailman/scripts/driver", line 87, in run_main
>  main()
>File "/usr/local/mailman/Mailman/Cgi/admindb.py", line 236, in main
>  print doc.Format()
>File "/usr/local/mailman/Mailman/htmlformat.py", line 331, in Format
>  output.append(Container.Format(self, indent))
>File "/usr/local/mailman/Mailman/htmlformat.py", line 264, in Format
>  output.append(HTMLFormatObject(item, indent))
>File "/usr/local/mailman/Mailman/htmlformat.py", line 50, in 
> HTMLFormatObject
>  return item.Format(indent)
>File "/usr/local/mailman/Mailman/htmlformat.py", line 417, in Format
>  output = output + Container.Format(self, indent+2)
>File "/usr/local/mailman/Mailman/htmlformat.py", line 264, in Format
>  output.append(HTMLFormatObject(item, indent))
>File "/usr/local/mailman/Mailman/htmlformat.py", line 50, in 
> HTMLFormatObject
>  return item.Format(indent)
>File "/usr/local/mailman/Mailman/htmlformat.py", line 200, in Format
>  output = output + self.FormatRow(i, indent + 2)
> MemoryError
> 
> Python information:
> 
> Variable
> Value
> 
> sys.version
> 2.2.2 (#1, Jan 14 2003, 02:49:11)  [GCC 2.96 2731 (Red Hat Linux 
> 7.1 2.96-98)]
> 
> sys.executable
> /usr/local/bin/python
> 
> sys.prefix
> /usr/local
> 
> sys.exec_prefix
> /usr/local
> 
> sys.path
> /usr/local
> 
> sys.platform
> linux2
> 
> Environment variables:
> 
> Variable
> Value
> 
> PATH_INFO
> /bnb-list
> 
> HTTP_ACCEPT
> */*
> 
> CONTENT_TYPE
> application/x-www-form-urlencoded
> 
> HTTP_REFERER
> http://www.innsite.com/mailman/admindb/bnb-list
> 
> SERVER_SOFTWARE
> Apache/1.3.26 (Unix) PHP/4.2.3
> 
> PYTHONPATH
> /usr/local/mailman
> 
> SCRIPT_FILENAME
> /usr/local/mailman/cgi-bin/admindb
> 
> SERVER_ADMIN
> [EMAIL PROTECTED]
> 
> SCRIPT_NAME
> /mailman/admindb
> 
> SCRIPT_URI
> http://www.innsite.com/mailman/admindb/bnb-list
> 
> SERVER_SIGNATURE
> Apache/1.3.26 Server at www.innsite.com Port 80
> 
> REQUEST_METHOD
> POST
> 
> HTTP_HOST
> www.innsite.com
> 
> SCRIPT_URL
> /mailman/admindb/bnb-list
> 
> SERVER_PROTOCOL
> HTTP/1.0
> 
> QUERY_STRING
> 
> REQUEST_URI
> /mailman/admindb/bnb-list
> 
> CONTENT_LENGTH
> 35
> 
> PATH_TRANSLATED
> /www/data/innsite/bnb-list
> 
> HTTP_USER_AGENT
> Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-us) AppleWebKit/48 (like 
> Gecko) Safari/48
> 
> HTTP_CONNECTION
> close
> 
> HTTP_COOKIE
> Apache=219.88.207.149.5151045648465275
> 
> SERVER_NAME
> www.innsite.com
> 
> REMOTE_ADDR
> 219.88.207.149
> 
> REMOTE_PORT
> 49346
> 
> HTTP_ACCEPT_LANGUAGE
> en-us, ja;q=0.33, en;q=0.67
> 
> SERVER_ADDR
> 66.250.38.164
> 
> SERVER_PORT
> 80
> 
> GATEWAY_INTERFACE
> CGI/1.1
> 
> UNIQUE_ID
> PlNUVkL6JqQAAAICmwI
> 
> DOCUMENT_ROOT
> /www/data/innsite 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> 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/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsu

[Mailman-Users] Problems with Apache on different port

[Jorge Godoy]

Hi!


I have apache listening on port 8080 here, so I access the mailman
interface as http://server.home.com:8080/mailman/ -- this works just
fine but then my problems start. Every link I click links correctly to
the page, except for the port number on the URL. It prevents me from
using the webinterface to create or maintain lists.

I'm using mailman-2.1.1 on a FreeBSD 5.0


TIA,
-- 
Godoy.<[EMAIL PROTECTED]>

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Digests for this list

[John DeCarlo]

Warren,

How do you set up digests on the lists you run?

Because the related question is why the Mailman 2.1 defaults are to send 
a digest when it hits a certain size (30 K).

I can't speak for Barry, but in deference to people with slow email 
access, keeping the size of each digest down makes it easier to download 
them.  Though one can argue that there is little difference between one 
90 K digest in a day and 3 30 K digests in a day.

Thanks for your message, since I hadn't noticed I was sending out 
multiple digests every day, too.  So I went and changed the maximum size 
to 500 K, and checked to send a digest out every day whether you hit the 
size or not.

Warren Hoffman wrote:
Just out of curiosity, I get several digests a day from this list. The 
'norm' for digests (elsewhere) is to send digests daily (unless size is 
extraordinary). If that isn't fast enough, users can select regular 
delivery or regularly review the archives for responses to their 
messages. Was sending daily considered? Rejected? Worth reconsidering?

--

John DeCarlo, My Views Are My Own



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] User AKAs?

[John DeCarlo]

Alan,

This works, though it is not exactly what you are asking for.

Set up multiple accounts for each person, with every variation of email 
address you expect to receive.  Then set all but one of them to "nomail".

This allows them to be recognized as members while still only receiving 
one copy of each message.


APBulletins wrote:
Issue is that mail is held for approval for people not recognized as a
member.
But, they are members.
Our damn mailserver changes how it says who the mail is from.
 - One day it's our registered email address as in mailman
 - One day it's our full name, versus an email address
 - etc.

Is there a way to set up AKAs for each user so no matter what our IT group
changes about the mailserver, it sees members properly?


--

John DeCarlo, My Views Are My Own



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Digests for this list

[Warren Hoffman]

Just out of curiosity, I get several digests a day from this list. The 
'norm' for digests (elsewhere) is to send digests daily (unless size is 
extraordinary). If that isn't fast enough, users can select regular 
delivery or regularly review the archives for responses to their messages. 
Was sending daily considered? Rejected? Worth reconsidering?

--Warren


_|_|_|  Warren Hoffman - Organization Improvement Consultant
_|_|_|  208 Jackson Blvd., Wilmington, DE 19803
_|_|_|  Phone/Fax: 302-658-7508
_|_|_|  [EMAIL PROTECTED]
_|_|_|   http://www.whoffman.com


--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Upgrading to 2.1 - a couple of Qs

[Richard Barrett]

At 09:16 21/02/2003, david.gordon wrote:

I want to go from 2.0.13 to 2.1.1. I (think I) understand I need to
install 2.1 then move my current list archives etc over to the new
directory. Its all in the documents!


First, you can go directly from 2.0.13 to 2.1.1. There is no need to do the 
upgrade in two hops.

Second, you do not need to update lists one at a time. This is just a 
precautionary approach.

You can in fact upgrade a 2.0.13 installation to 2.1.1 by just installing 
2.1.1 over the 2.0.13 installation.

If you have a production server with a bunch of critical lists and you 
cannot take risks with your list service then you could try the 
precautionary approach.

I faced the problem of having a large number of lists, some of which 
function as primary channels of communication between customers and 
company, where problems with list service are simply unacceptable to 
management. See the following archived e-mail for how I approached the 
problem, and it wasn't doing the lists one at a time:

http://mail.python.org/pipermail/mailman-users/2003-February/026611.html

I don't understand this, what is the concept here? Don't I just rename
the new MM21 directory to the 'old' name and everything would work.
Perhaps I am missing some basic *nix theory?!


The precautionary upgrade approach discussed in the MM $build/INSTALL file 
is just a suggestion. It just outlines a way of having two different 
version of MM installed and coexistng on a server, with some lists being 
serviced by one version and others being serviced by the other version.

>RewriteRule ^/mailman/(.*)/(foo-list.*) \
>$MM21/cgi-bin/$1/$2 \
>[T=application/x-httpd-cgi]

and

>RewriteRule ^/pipermail/(foo-list.*) $MM21/archives/public/$1

Given my (test) lists are called "test" and "testtwo", can someone help
me fill in the gaps. Should I add two lines to my VirtualHost for
mydomain.tld thus...

RewriteRule ^/mailman/(.*)/(test.*) \
  mailman/cgi-bin/$1/$2 \
  [T=application/x-httpd-cgi]


No need as the single rule will match any list whose name begins with the 4 
characters 'test'.

But I don't know what these variables refer to " mailman/cgi-bin/$1/$2 \"


RewriteRules are based on regular expressions, which are used for pattern 
matching:

1. The first part of the rule - '^/mailman/(.*)/(test.*)' - specifies a 
pattern to match against. The brackets '(' and ')' are used to capture 
substrings during pattern matching.

2. If the match succeeds the second part of the rule - 
'mailman/cgi-bin/$1/$2' - says what the revised URL is to be. The $1 and $2 
refer to substrings of the pattern, matched by the first part of the rule.

3. The third part - '[T=application/x-httpd-cgi]' - tells Apache the 
MIME  type of the rewritten URL. In this case it lets the RewriteRule 
function as a ScriptAlias directive.

So for the rule above:

4. if, for example, the requested URL is: /mailman/admin/test-list1/general

5. then the match succeeds and:

$1 = 'admin'

$2 = 'test-list1/general'

6. the URL is written as: mailman/cgi-bin/admin/test-list1/general



One rewrite for each list?

Maybe some one could translate what the rewrite is doing. And explain
what "sharing the same URL-space" means.


"sharing the same URL-space" means that URLs providing web access to lists 
look the same regardless of which version of MM is servicing the list., The 
URLs are distinguished only by the listname in the URL. But depending on 
which list is being addressed, and hence which version of MM is handling 
the list, the appropriate version of the MM CGI script concerned has to be 
run. The purpose of the RewriteRules is to match against listnames and if 
the match succeeds, change the requested URI into one which calls the 
alternate CGI scripts of the alternate MM installation.

This means that, from a web browser user's standpoint, the web GUI to the 
lists is an homogenous URL space. The server RewriteRules sort out the problem.


Thank you.

--
david.gordon



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Upgrading to 2.1 - a couple of Qs

[david.gordon]

I want to go from 2.0.13 to 2.1.1. I (think I) understand I need to
install 2.1 then move my current list archives etc over to the new
directory. Its all in the documents!

I don't understand this, what is the concept here? Don't I just rename
the new MM21 directory to the 'old' name and everything would work.
Perhaps I am missing some basic *nix theory?!

>RewriteRule ^/mailman/(.*)/(foo-list.*) \
>$MM21/cgi-bin/$1/$2 \
>[T=application/x-httpd-cgi]

and

>RewriteRule ^/pipermail/(foo-list.*) $MM21/archives/public/$1

Given my (test) lists are called "test" and "testtwo", can someone help
me fill in the gaps. Should I add two lines to my VirtualHost for
mydomain.tld thus...

RewriteRule ^/mailman/(.*)/(test.*) \
  mailman/cgi-bin/$1/$2 \
  [T=application/x-httpd-cgi]

But I don't know what these variables refer to " mailman/cgi-bin/$1/$2 \"

One rewrite for each list?

Maybe some one could translate what the rewrite is doing. And explain
what "sharing the same URL-space" means.

Thank you.

-- 
david.gordon



--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users]

[Simon White]

20-Feb-03 at 23:27, Matthew Davis ([EMAIL PROTECTED]) wrote :
> * Pawan Singh ([EMAIL PROTECTED]) wrote:
> > Is there any way to hide the maling lists
> 
> To make it not publicly advertized on the web page, set 'advertised' to 'No'
> on the "Privacy" page.

Pawan,

Great to see you on the list.

Good to see you have questions.

However, it's probably a better idea to get stuff working, try all
sorts, and come back with a single well written post, instead of firing
just one question to the list, a single phrase, because you could read
the docs and experiment to answer all those you have answered so far.

Mailing lists are *not* a substitute for reading the docs. 

-- 
|-Simon White, Internet Services Manager, Certified Check Point CCSA.
|-MTDS  Internet, Security, Anti-Virus, Linux and Hosting Solutions.
|-MTDS  14, rue du 16 novembre, Agdal, Rabat, Morocco.
|-MTDS  tel +212.3.767.4861 - fax +212.3.767.4863

--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org