[Mailman-Users] why txt files ??

2005-06-20 Thread Jean-Philippe GIOLA
Hi all!

I want to know why mailman developpers have choosen to store mails in 
txt files and not in a database like a forum ??

reguards

-- 
Jean-Philippe Giola - 6577


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

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


Re: [Mailman-Users] QRUNNER processes running high on CPU rates

2005-06-20 Thread Carl Zwanzig
In a flurry of recycled electrons, Chance Eppinette wrote:

 The CPU rate is hovering around 45% for the qrunner bounce process.
 The list has purged out about 1100 disabled subscribers over this weekend,
 but for some reason is still churning away about nothing - it seems.

Clearing the member list won't affect what's already queued up for delivery.
You either have to live with it for a few days or manually clear the queue.
(IIRC, this is as simple as deleting the files in the queue directory. See the 
FAQ.)

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

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


[Mailman-Users] Cleanup From: and CC:

2005-06-20 Thread Pantejo, Barbara FTL
I just set up a new mailing list and sent a test email (see below). I was
wondering how to change From: information...I would like the entry in the
CC: field ([EMAIL PROTECTED]) placed in the From: field and have
CC: field empty. How do I configure this?

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Monday, June 20, 2005 11:55 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Test # 3

Thanks you for your help, 
Barbara 

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

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


Re: [Mailman-Users] Still installation woes

2005-06-20 Thread Rob Shepherd

John Dennis wrote:

On Sun, 2005-06-19 at 21:54 +0100, Rob Shepherd wrote:


I can't believe this is giving me so much trouble.


fixed and working now Although I can't work out what I actually did 
different just plodding through the install script once more...


/usr/local/mailman is now owned root:mailman instead of mailman:mailman but I 
can't see that making a difference if the perms are coreect.



thanks to those that lended a helping hand.

One further thing though,

I ran genalias and then added the hash:/usr/local/mailman/data/aliases to 
postfix,

the next stage informed me to add hash:/usr/local/mailman/data/mailman-virtual 
in the case where I am running virtual domain lists. which I amwith the 
domains in postfix already running and configured


but this db did not yet exist so postfix/smtpd flipped out

After the sucessful installation with proper perms on the right files I then 
tried to add a virtual list via web, however the perms had come up wrong on


/usr/local/mailman/data/aliases.db as -rw-r--r-- mailman:mailman so apache 
flipped out too as it couldn't write the db with group mailman...


to work round this I

bin/rmlist mylist
touch data/aliases data/aliases.db data/virtual-mailman data/virtual-mailman.db
chmod 660 data/aliases*
chmod 660 data/virtual-mailman*

Then postfix and apache2 were happy.

So can genaliases or the install script not make an empty virtual-mailman file 
and assoc' db in addition to the standard aliases files


I suspect it boils down to umask for the associated users, but it will always be 
mailman doing the genaliases to begin with. It's not much wasted space for 
people not using virtual stuff and it makes the initialisation happier for those 
that do...


shall I submit an RFE or bug for this

Cheers

Rob

--
/**
 *  Rob Shepherd,
 *  University Of Wales, Bangor,
 *  +44 (0) 1248 38 27
 */
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

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

[Mailman-Users] Sendmail smrsh + multiple mailman

2005-06-20 Thread Ashley M. Kirchner

I have a bit of an odd one here.  I have multiple mailman 
installations on one machine (for reasons we won't detail here) as follows:

~mailman/host1_list/mailman install for one specific hostname
~mailman/host2_list/mailman install for another specific hostname
etc.

When e-mail for [EMAIL PROTECTED] arrives, it goes into the 
appropriate folder and does what Mailman does best.  The same for 
[EMAIL PROTECTED], etc., etc.  (this setup allows me to have the same list 
name across multiple domains, behaving as individual lists)

The problem I'm running into now is sendmail's smrsh.  I can copy 
the wrapper from one of those hosts into sendmail smrsh's folder, 
however it will only work for that one host installation.  It won't work 
for the next.  And since all the wrappers are called 'mailman', 
obviously I can't copy all of them in the same (smrsh) folder.

So, my question, or questions:
   a) Is there an easy solution to this where smrsh will work?
   b) If not, can the 'mailman' wrapper be renamed?
  (this of course means aliases also get adjusted accordingly)

-- 
H | I haven't lost my mind; it's backed up on tape somewhere.
  +
  Ashley M. Kirchner mailto:[EMAIL PROTECTED]   .   303.442.6410 x130
  IT Director / SysAdmin / WebSmith . 800.441.3873 x130
  Photo Craft Imaging   . 3550 Arapahoe Ave. #6
  http://www.pcraft.com . .  ..   Boulder, CO 80303, U.S.A. 



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

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


Re: [Mailman-Users] Restrict Posting to individual users

2005-06-20 Thread Brad Knowles
At 11:42 AM -0400 2005-06-20, Eric Howell wrote:

  I have several lists available on a Mac OS X Server (Mailman 2.1.4) I can't
  figure out how to set the software (using the GUI) to ensure that only a
  single user is permitted to post a message for delivery.

So, you haven't gone to the FAQ Wizard page at 
http://www.python.org/cgi-bin/faqw-mm.py and you haven't read FAQ 
3.11?

-- 
Brad Knowles, [EMAIL PROTECTED]

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See http://www.sage.org/ for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

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


Re: [Mailman-Users] Exim + Mailman + Secondary MX

2005-06-20 Thread Brad Knowles
At 10:43 AM +0200 2005-06-20, GamCo - Gawie Marais wrote:

  If we take out the entries on the domainlist relay_to_domains ,, then
  everything works great except that anyone can then relay to any domain
  making the server a potential open relay.

  Has anyone got some idea to run this configuration correctly ??

This sounds like an Exim problem, and you would need to use their 
mailing lists, newsgroups, FAQs, etc... to help you resolve this 
issue.

-- 
Brad Knowles, [EMAIL PROTECTED]

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.

 -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
 Assembly to the Governor, November 11, 1755

   SAGE member since 1995.  See http://www.sage.org/ for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

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