03-Feb-03 at 20:00, John Locke ([EMAIL PROTECTED]) wrote :
Nothing but silence... Let me simplify rephrase my questions:
1. Is there any support for storing member information in a SQL
database, with MM 2.1?
I do this via synchronisation. A script that calls
add_member/remove_member
Hi,
Last month there was a thread about a problem that I am now having.
Was a solution, or at least a cause, found?
The problem, as stated by the original poster, is It shows the pending
messages with the choices - but if I select to approve, reject, or
discard - nothing happens after I click
On a new list I created I'm getting incorrect url links
This is how it stands:
http://mysite.mycompany.com/listinfo/mysite.company.com/admin/listname
Obviously, no such link exists. I can see that in Defaults.py there are entries
DEFAULT_EMAIL_HOST = 'mysite.mycompany.com'
DEFAULT_URL_HOST =
At 00:08 04/02/2003, Tom Maddox wrote:
So, is it possible to disable the VERP functionality in some fashion? My
users would prefer to have regular From: and Reply-to: headers, not the
irritating VERP ones. I'm hesitant to make changes to the VERP_FORMAT and
VERP_REGEXP lines in mm_cfg.py
I just ran check_db --verbose --all
I got this during run (although all other output seemed to suggest the
dbs were OK)
Traceback (most recent call last):
File /home/mailman/bin/qrunner, line 270, in ?
main()
File /home/mailman/bin/qrunner, line 230, in main
qrunner.run()
File
Folks,
Please try my new patch to ToDigest.py,
http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id=41440aid=674401
You may also want fix some bug in Scrubber.py,
http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id=41438aid=670167
Both patches are for
Nope. Only the single member I manually added shows up anywhere at all.
-Original Message-
From: Jon Carnes [mailto:[EMAIL PROTECTED]]
Sent: 04 February 2003 00:37
To: [EMAIL PROTECTED]
Cc: Mailman users Mailing list
Subject: RE: [Mailman-Users] Initial Setup Issues
Not to be too
Although I am now having some thoughts...probably not relevant but you
never know!
Here is my installation history:
1. Installed Mailman 2.1, but had major problems
2. My ISP (I rent a virtual server) told me that they were only
supporting 2.0.x at this time, thus:
3. Installed 2.0.13 as it is
jam == John A Martin [EMAIL PROTECTED] writes:
jam ,[ Google ] | Your search - Warsaw's 4th Law - did not
jam match any documents. `
jam :-)
Try Warsaw's Fourth Law :)
-Barry
--
Mailman-Users mailing list
[EMAIL
Hello all,
I just noticed the following while looking at my list of mails, there is
no date in the header of a digest !
Have a look:
Return-Path: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Received: (qmail 19281 invoked from network); 4 Feb 2003 07:35:49 -
Received: from
Let me point you to a posting from the archives from Vivek Khera:
If you redirect a POST using mod_redirect, you lose
the data. The workaround is to capture the POST
data from the original request, convert it to a GET
and redirect to that. But then if you're sending
the first
Unfortunately you did not answer my question...
If the admin pages for your list are:
http://mysite.domain/mailman/admin/listname
Then what do you see when you go to:
http://mysite.domain/mailman/admindb/listname
On Tue, 2003-02-04 at 06:08, dino wrote:
Nope. Only the single member I
I don't have this problem at all, and my threading works fine as well.
What version of Mailman are you using and what is your
ARCHIVER_CLOBBER_DATE set to?
# This sets the default `clobber date' policy for the archiver.
# When a message is to be archived either by Pipermail or an
#
I have just recently tried to setup my list and am having some problems. For some
reason, I send an e-mail to the list and nothing happens. I am unable to find it on
the server and it does not get dispatched out to the members. Any ideas?
Tony
03-Feb-03 at 14:52, drmichaelmason ([EMAIL PROTECTED]) wrote :
I have just recently tried to setup my list and am having some
problems. For some reason, I send an e-mail to the list and nothing
happens. I am unable to find it on the server and it does not get
dispatched out to the members.
On Tue, 4 Feb 2003, Tokio Kikuchi wrote:
I think this bug is fixed. Please get a patch from
http://sourceforge.net/tracker/index.php?func=detailaid=670167group_id=103atid=300103
The patch seems to work. Thanks!
-David
+--+
David Eisner
On Tue, 2003-02-04 at 00:40, Simon White wrote:
03-Feb-03 at 20:00, John Locke ([EMAIL PROTECTED]) wrote :
1. Is there any support for storing member information in a SQL
database, with MM 2.1?
I do this via synchronisation. A script that calls
add_member/remove_member called from
I recently installed Mailman 2.1 on a machine running Apache 1.3.20.
Mailman is installed in a central location and made available to all virtual
sites via an Apache ScriptAlias directive. The lists function properly and
all are accessible, but are not listed on the listinfo page even though
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John Locke wrote:
On Tue, 2003-02-04 at 00:40, Simon White wrote:
I do this via synchronisation. A script that calls
add_member/remove_member called from the code that does the
INSERT/DELETE query in SQL. It's not particularly robust but it
Hello,
The current results of sending the who command via email is a list of
all the members of the list, divided into Digest and Non-digest.
However, I would like to break out the members who are disabled
separately from those receiving mail.
If anyone has looked at doing this or something
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
John DeCarlo wrote:
If anyone has looked at doing this or something similar, I would
appreciate any pointers. So far I haven't even found the script that
responds to the who command.
I haven't done anything like this, but I believe the place
At 00:08 04/02/2003, Tom Maddox wrote:
So, is it possible to disable the VERP functionality in some fashion? My
users would prefer to have regular From: and Reply-to: headers, not the
irritating VERP ones. I'm hesitant to make changes to the
VERP_FORMAT and
VERP_REGEXP lines in mm_cfg.py
Someone asked about the content of the qrunner log and another some other
questions about processes and such, as well as the status of the archives.
The archives are a bit behind. The last seven messages to the list have
yet to appear in the archive pages. In fact, I notice a huge time lag
On Tue, 2003-02-04 at 09:25, Todd wrote:
I haven't seen anyone announce a MySQLMemberAdaptor yet either, but
Martin
Whinnery made an announcement here a few weeks ago for an
LDAPMemberAdaptor.
If you know some python, perhaps you want to look at the LDAP version
and
try and convert it for
At 18:13 04/02/2003, Tom Maddox wrote:
At 00:08 04/02/2003, Tom Maddox wrote:
So, is it possible to disable the VERP functionality in some fashion? My
users would prefer to have regular From: and Reply-to: headers, not the
irritating VERP ones. I'm hesitant to make changes to the
SW == Steve Werby [EMAIL PROTECTED] writes:
SW I recently installed Mailman 2.1 on a machine running Apache 1.3.20.
SW Mailman is installed in a central location and made available to all virtual
SW sites via an Apache ScriptAlias directive. The lists function properly and
SW all are
Vivek Khera [EMAIL PROTECTED] wrote:
SW == Steve Werby [EMAIL PROTECTED] writes:
SW I recently installed Mailman 2.1 on a machine running Apache 1.3.20.
SW Mailman is installed in a central location and made available to all
virtual
SW sites via an Apache ScriptAlias directive. The lists
So, is it possible to disable the VERP functionality in some
fashion? My
users would prefer to have regular From: and Reply-to:
headers, not the
irritating VERP ones. I'm hesitant to make changes to the
VERP_FORMAT and
VERP_REGEXP lines in mm_cfg.py without knowing precisely
Tom Maddox said:
I tried twiddling the VERP_DELIVERY_INTERVAL setting, but it made no
difference.
Hey Tom... a couple of questions (forgive me if they sound silly, or if
they've already been asked):
1) Are you changing ~mailman/Mailman/mm_cfg.py--not
~mailman/Mailman/Defaults.py? (and if
I tried twiddling the VERP_DELIVERY_INTERVAL setting, but it made no
difference.
Hey Tom... a couple of questions (forgive me if they sound silly, or if
they've already been asked):
1) Are you changing ~mailman/Mailman/mm_cfg.py--not
~mailman/Mailman/Defaults.py? (and if you're changing
At 22:42 04/02/2003, Tom Maddox wrote:
I tried twiddling the VERP_DELIVERY_INTERVAL setting, but it made no
difference.
Hey Tom... a couple of questions (forgive me if they sound silly, or if
they've already been asked):
1) Are you changing ~mailman/Mailman/mm_cfg.py--not
At 22:02 04/02/2003, Tom Maddox wrote:
So, is it possible to disable the VERP functionality in some
fashion? My
users would prefer to have regular From: and Reply-to:
headers, not the
irritating VERP ones. I'm hesitant to make changes to the
VERP_FORMAT and
VERP_REGEXP lines in
In message [EMAIL PROTECTED]
on Tue, Feb 04, 2003 at 09:58:02AM -0500, Jon Carnes wrote:
If you redirect a POST using mod_redirect, you lose
Yes, that is what appears to be happening. It seems that the admindb web
forms (and e-mail to list admins) point to the (old) address. The other
admin
In message [EMAIL PROTECTED]
on Wed, Feb 05, 2003 at 08:46:52AM +0800, James Devenish wrote:
config_list, move_list, withlist scripts will
Hmm, http://mailman.sourceforge.net/site.html doesn't seem to
match my Mailman 2.1 installation. Nevertheless, the important
part for me was its
Look at ~mailman/bin/fix_url.py.
HtH - Jon Carnes
On Tue, 2003-02-04 at 19:46, James Devenish wrote:
In message [EMAIL PROTECTED]
on Tue, Feb 04, 2003 at 09:58:02AM -0500, Jon Carnes wrote:
If you redirect a POST using mod_redirect, you lose
Yes, that is what appears to be happening.
In message [EMAIL PROTECTED]
on Tue, Feb 04, 2003 at 10:09:25PM -0500, Jon Carnes wrote:
Look at ~mailman/bin/fix_url.py.
Yes, I was going to mention that but the notes at the top of the file
said This script is intended to be run as a bin/withlist script, i.e.
bin/withlist -l -r fix_url
In message [EMAIL PROTECTED]
on Wed, Feb 05, 2003 at 11:22:38AM +0800, James Devenish wrote:
In message [EMAIL PROTECTED]
on Tue, Feb 04, 2003 at 10:09:25PM -0500, Jon Carnes wrote:
Look at ~mailman/bin/fix_url.py.
[...]
I wasn't clear on when I would be prompted for an address.
Whoops, I
* Adam ([EMAIL PROTECTED]) wrote:
http://mysite.mycompany.com/listinfo/mysite.company.com/admin/listname
Obviously, no such link exists. I can see that in Defaults.py there are entries
DEFAULT_EMAIL_HOST = 'mysite.mycompany.com'
DEFAULT_URL_HOST = 'mysite.mycompany.com'
* Simon White ([EMAIL PROTECTED]) wrote:
I just ran check_db --verbose --all
I got this during run (although all other output seemed to suggest the
dbs were OK)
Traceback (most recent call last):
File /home/mailman/bin/qrunner, line 270, in ?
main()
File
I've looked through a couple of months of the mailman-users archive and the
FAQ. That said I feel safe asking this...
I added
Alias /pipermail/ /var/lib/mailman/archives/public/
to my Apache httpd.conf. After that I was getting things like this in my
/var/log/apache/error.log...
[Tue Feb 4
Location /pipermail
Options FollowSymLinks
/Location
http://httpd.apache.org/docs/mod/core.html#options
states that
Note: this option gets ignored if set inside a Location section.
Use
Directory /var/lib/mailman/archives/public
Options Indexes FollowSymLinks
/Directory
--
Tokio
41 matches
Mail list logo
