Re: [Mailman-Users] Follow-up Weird problem data format error.Commandoutput Mailbox does'nt exist

[carconni]

Hi Mark,

I decided to make a copy of the /var/mailman/data/aliases.db file  
yesterday.  I wanted to see if it changed after the server rebooted.   
Well the server rebooted a couple of minutes ago and I took a look at  
the directory:

-rw-r- 1 root mailman 41 Apr 12 11:39  
adm.pw
-rw-rw   1 root mailman228933 Aug  2 15:17 aliases
-rwxrwxr-x 1 mailman  mailman 81920 Aug  2 15:17 aliases.db
-rwxr-xr-x   1 mailman  mailman  344064 Aug  2 22:32 aliases.db.bak
-rwxrwsr-x  1 mailman  mailman 0 Aug  1  2006 bounce- 
events-00481.pck

(notice how the aliases, aliases.db and aliases.db.bak are all  
different sizes?)

It appears that the aliase.db does somehow get reverted to an earlier  
version of itself (very weird) - but it would explain why I loosing  
lists and users.  I took your advice and postalias aliases/postfix  
reload and that worked:

corp-admin2:/var/mailman/data root# ls -l
total 5376
-rw-r-   1 root mailman  41 Apr 12 11:39 adm.pw
-rw-rw   1 root mailman  228933 Aug  2 15:17 aliases
-rwxrwxr-x   1 mailman  mailman  344064 Aug  3 11:04 aliases.db
-rwxr-xr-x   1 mailman  mailman  344064 Aug  2 22:32 aliases.db.bak

Your absolutely right, postifx isn't doing what it should on boot  
up.  But where is that old db file coming from?

still looking


On Aug 3, 2007, at 8:07 AM, Mark Sapiro wrote:

> carconni wrote:
>>
>> The other thing that troubles me is that I can't figure out why lists
>> are loosing members.
>
>
> Check the lists' bounce processing settings and look at Mailman's
> 'bounce' and 'smtp-failure' logs.
>
> -- 
> Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
>
>

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

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

Re: [Mailman-Users] Follow-up Weird problem data format error. Commandoutput Mailbox does'nt exist

[carconni]

Hi Mark,

Thank you for your advice and I will certainly look into what postfix  
is doing.  In addition, I'll try your suggestion to run postalias to  
see if that corrects the problem.  I've now had 3 more lists become  
undeliverable.  They are all in the /var/mailman/data/alias file, so  
I'll keep digging.

The other thing that troubles me is that I can't figure out why lists  
are loosing members.  When the mailserver bounced tuesday, users  
added several days beforehand disappeared from the list.  The users  
were re-added, only for the problem to reoccur after a server  
restart.  I should point out this isn't occurring with the lists that  
became undeliverable, maybe it's a coincidence, and the 2 are unrelated.

I'll update the list with what I find - and thank you again for  
taking the time help me.

Carconni



On Aug 2, 2007, at 6:40 PM, Mark Sapiro wrote:

> carconni wrote:
>>
>> I've just been updated by more of the users/list admins.  It seems
>> that every-time the mail-server bounces/restarts, configurations are
>> lost.  Members fall off lists, lists stop running, or are no longer
>> recognized by the mail server.  Is there a central DB or something
>> that is rolling back to an earlier version?
>
>
> Could be, but it is pretty clear to me that the problem is with your
> MTA, not with mailman. Since your MTA is Postfix, and delivery is via
> aliases, this can't be a Mailman (other than aliases) issue because
> the mail is being bounced by Postfix because "Recipient address
> rejected: User unknown in local recipient table" which means that
> somehow the aliases for this list are being lost.
>
>
> When the problem occurs, are the aliases still in
> /var/mailman/data/aliases? What is the mod time on
> /var/mailman/data/aliases.db? Are all the list's (working and
> non-working) aliases in /var/mailman/data/aliases and nowhere else (eg
> /etc/postfix/lmail/company.aliases or /etc/aliases)?
>
>
>>> I have spent the better part of 6 hours looking for a reason.  I've
>>> checked permissions, not just with checkperms but manually, step by
>>> step, directory by directory comparing the broken list to a list  
>>> that
>>> is known to be working.
>
>
> Nothing in Mailman is causing this. It is postfix that 'forgets'  
> how to
> deliver to [EMAIL PROTECTED] Apparently deleting and
> recreating the list fixes the problem because it runs Postfix's
> /usr/sbin/postalias command abd rebuilds /var/mailman/data/aliases.db
> from /var/mailman/data/aliases. Probably just running postalias would
> fix it too without the pain of recreating the list.
>
>
> 
>
>>> I've checked the alias file in /var/mailman/data/aliases:
>>> (Everything looks ok)
>>>
>>> # STANZA START: qvc-requests
>>> # CREATED: Wed Aug  1 09:09:12 2007
>>> qvc-requests: "|/usr/share/mailman/mail/mailman post  
>>> qvc-
>>> requests"
>>> qvc-requests-admin:   "|/usr/share/mailman/mail/mailman admin  
>>> qvc-
>>> requests"
>>> qvc-requests-bounces: "|/usr/share/mailman/mail/mailman bounces
>>> qvc-requests"
>>> qvc-requests-confirm: "|/usr/share/mailman/mail/mailman confirm
>>> qvc-requests"
>>> qvc-requests-join:"|/usr/share/mailman/mail/mailman join  
>>> qvc-
>>> requests"
>>> qvc-requests-leave:   "|/usr/share/mailman/mail/mailman leave  
>>> qvc-
>>> requests"
>>> qvc-requests-owner:   "|/usr/share/mailman/mail/mailman owner  
>>> qvc-
>>> requests"
>>> qvc-requests-request: "|/usr/share/mailman/mail/mailman request
>>> qvc-requests"
>>> qvc-requests-subscribe:   "|/usr/share/mailman/mail/mailman  
>>> subscribe
>>> qvc-requests"
>>> qvc-requests-unsubscribe: "|/usr/share/mailman/mail/mailman
>>> unsubscribe qvc-requests"
>>> # STANZA END: qvc-requests
>>>
>>> I've checked locks: - nothing regarding this list there.
>
>
> Mailman locks aren't relevant to this.
>
>
>>> main.cf shows: alias_maps = hash:/etc/postfix/lmail/
>>> company.aliases,hash:/var/mailman/data/aliases
>
>
> Looks OK to me, but I'm not a postfix guy?
>
>
>>> Where else can I check?
>
> Something is happening when Postfix is restarted that is causing this,
> but I don't know what or why. I'm guessing the
> /var/mailman/data/aliases.db file gets modified somehow using data

[Mailman-Users] Follow-up Weird problem data format error. Command output Mailbox does'nt exist

[carconni]

Hi,

I've just been updated by more of the users/list admins.  It seems  
that every-time the mail-server bounces/restarts, configurations are  
lost.  Members fall off lists, lists stop running, or are no longer  
recognized by the mail server.  Is there a central DB or something  
that is rolling back to an earlier version?

I haven't made any changes to lists since they moved -  but then  
again - this could be a result of the move since our mail server  
really doesn't get restarted often.

Any ideas?


Begin forwarded message:

> From: carconni <[EMAIL PROTECTED]>
> Date: August 2, 2007 3:14:12 PM PDT
> To: mailman-users@python.org
> Subject: [Mailman-Users] Weird problem data format error. Command  
> output Mailbox does'nt exist
>
> HI,
>
> I have an odd problem.  I have over a hundred lists and all but one
> is working properly.  The initial support call was a complaint that
> the mail server was bouncing back the emails sent to the list
> claiming that there was no such user (list-name).
>
> I thought it was odd, so I rmlist -a and recreated it using newlist.
> I tested the list, mail went to the user and everyone was happy.
>
> Oddly, the mailserver bounced that night (we aren't sure why) but the
> next day I got another call about the same list.  I thought that it
> was a fluke, maybe some weird setting had been reverted when the
> server bounced, so again I removed the list (rmlist but without
> removing the archives) and recreated the list using newlist.  I
> tested the list by sending an email and everyone (except the
> administrator who now had to repopulate the list was happy)
>
> It is day 3.  I got phone call today.  The same list is broken
> again.  All the other lists work fine but this one seems to be
> unrecognized by the system:
>
> Aug  2 13:36:36 mail postfix/smtpd[5008]: NOQUEUE: reject: RCPT from
> sjc.mailserver.com[63.80.14.252]: 550  [EMAIL PROTECTED]>: Recipient address rejected: User
> unknown in local recipient table; from=<[EMAIL PROTECTED]>
> to=<[EMAIL PROTECTED]> proto=ESMTP helo=< 
> [172.16.246.5]>
> Aug  2 13:42:02 mail postfix/smtpd[5066]: NOQUEUE: reject: RCPT from
> sjc.mailserver.com[63.80.14.252]: 550  [EMAIL PROTECTED]>: Recipient address rejected: User
> unknown in local recipient table; from=<[EMAIL PROTECTED]>
> to=<[EMAIL PROTECTED]> proto=ESMTP helo=< 
> [172.16.246.5]>
> Aug  2 13:45:31 mail postfix/pipe[6401]: 9E219166485D: to= [EMAIL PROTECTED]>, relay=cyrus, delay=0, status=bounced (data
> format error. Command output: qvc-requests: Mailbox does not exist )
> Aug  2 13:57:17 corp-admin2 postfix/pipe[7594]: 222591665614: to= [EMAIL PROTECTED]>, relay=cyrus, delay=0, status=bounced (data
> format error. Command output: qvc-requests: Mailbox does not exist )
> Aug  2 14:05:45 mail postfix/pipe[7722]: 34A081666003: to= [EMAIL PROTECTED]>, relay=cyrus, delay=0, status=bounced (data
> format error. Command output: qvc-requests: Mailbox does not exist )
>
> I have spent the better part of 6 hours looking for a reason.  I've
> checked permissions, not just with checkperms but manually, step by
> step, directory by directory comparing the broken list to a list that
> is known to be working.
>
>
> /private/var/mailman/archives/private/qvc-requests/database "other"
> perms must be 000 (fixing)
>
> drwxrwsr-x3 root mailman   102 Jun 18 13:30 production
> drwxrwsr-x2 root mailman68 Jun 18 13:30 production.mbox
> drwxrwsr-x   10 root mailman   340 Aug  1 11:18 qvc-requests
> drwxrwsr-x3 root mailman   102 Jul 26 09:02 qvc-requests.mbox
>
>
> /var/mailman/lists root# ls -l qvc-requests
> total 56
> -rw-rw   1 mailman  mailman   3777 Aug  2 11:25 config.pck
> -rw-rw   1 mailman  mailman   3778 Aug  2 11:24 config.pck.last
> -rw-rw   1 mailman  mailman  11089 Aug  1 14:16 digest.mbox
> -rw-rw   1 mailman  mailman131 Aug  1 10:24 pending.pck
> -rw-rw-r--   1 www  mailman 24 Aug  1 11:18 request.pck
>
> /var/mailman/archives/private/qvc-requests root# ls -l
> total 160
> drwxrwsr-x   10 mailman  mailman340 Aug  1 14:16 2007-August
> -rw-rw-r--1 mailman  mailman   2476 Aug  1 14:16 2007-August.txt
> drwxrwsr-x   28 mailman  mailman952 Jul 31 15:08 2007-July
> -rw-rw-r--1 mailman  mailman  66954 Jul 31 15:08 2007-July.txt
> drwxrwsr-x7 root mailman238 Aug  1 11:59 attachments
> drwxrwx---   12 mailman  mailman408 Aug  1 14:16 database
> -rw-rw-r--1 root mailman   1465 Aug  1 14:16 index.html
> -rw-rw1 mailman  mailman892 Aug  1 14:16 pipermail.pck
>
>
>
> I've checked the alias file in /var/mailman/data/aliases:
> (E

[Mailman-Users] Weird problem data format error. Command output Mailbox does'nt exist

[carconni]

HI,

I have an odd problem.  I have over a hundred lists and all but one  
is working properly.  The initial support call was a complaint that  
the mail server was bouncing back the emails sent to the list  
claiming that there was no such user (list-name).

I thought it was odd, so I rmlist -a and recreated it using newlist.   
I tested the list, mail went to the user and everyone was happy.

Oddly, the mailserver bounced that night (we aren't sure why) but the  
next day I got another call about the same list.  I thought that it  
was a fluke, maybe some weird setting had been reverted when the  
server bounced, so again I removed the list (rmlist but without  
removing the archives) and recreated the list using newlist.  I  
tested the list by sending an email and everyone (except the  
administrator who now had to repopulate the list was happy)

It is day 3.  I got phone call today.  The same list is broken  
again.  All the other lists work fine but this one seems to be  
unrecognized by the system:

Aug  2 13:36:36 mail postfix/smtpd[5008]: NOQUEUE: reject: RCPT from  
sjc.mailserver.com[63.80.14.252]: 550 : Recipient address rejected: User  
unknown in local recipient table; from=<[EMAIL PROTECTED]>  
to=<[EMAIL PROTECTED]> proto=ESMTP helo=<[172.16.246.5]>
Aug  2 13:42:02 mail postfix/smtpd[5066]: NOQUEUE: reject: RCPT from  
sjc.mailserver.com[63.80.14.252]: 550 : Recipient address rejected: User  
unknown in local recipient table; from=<[EMAIL PROTECTED]>  
to=<[EMAIL PROTECTED]> proto=ESMTP helo=<[172.16.246.5]>
Aug  2 13:45:31 mail postfix/pipe[6401]: 9E219166485D: to=, relay=cyrus, delay=0, status=bounced (data  
format error. Command output: qvc-requests: Mailbox does not exist )
Aug  2 13:57:17 corp-admin2 postfix/pipe[7594]: 222591665614: to=, relay=cyrus, delay=0, status=bounced (data  
format error. Command output: qvc-requests: Mailbox does not exist )
Aug  2 14:05:45 mail postfix/pipe[7722]: 34A081666003: to=, relay=cyrus, delay=0, status=bounced (data  
format error. Command output: qvc-requests: Mailbox does not exist )

I have spent the better part of 6 hours looking for a reason.  I've  
checked permissions, not just with checkperms but manually, step by  
step, directory by directory comparing the broken list to a list that  
is known to be working.


/private/var/mailman/archives/private/qvc-requests/database "other"  
perms must be 000 (fixing)

drwxrwsr-x3 root mailman   102 Jun 18 13:30 production
drwxrwsr-x2 root mailman68 Jun 18 13:30 production.mbox
drwxrwsr-x   10 root mailman   340 Aug  1 11:18 qvc-requests
drwxrwsr-x3 root mailman   102 Jul 26 09:02 qvc-requests.mbox


/var/mailman/lists root# ls -l qvc-requests
total 56
-rw-rw   1 mailman  mailman   3777 Aug  2 11:25 config.pck
-rw-rw   1 mailman  mailman   3778 Aug  2 11:24 config.pck.last
-rw-rw   1 mailman  mailman  11089 Aug  1 14:16 digest.mbox
-rw-rw   1 mailman  mailman131 Aug  1 10:24 pending.pck
-rw-rw-r--   1 www  mailman 24 Aug  1 11:18 request.pck

/var/mailman/archives/private/qvc-requests root# ls -l
total 160
drwxrwsr-x   10 mailman  mailman340 Aug  1 14:16 2007-August
-rw-rw-r--1 mailman  mailman   2476 Aug  1 14:16 2007-August.txt
drwxrwsr-x   28 mailman  mailman952 Jul 31 15:08 2007-July
-rw-rw-r--1 mailman  mailman  66954 Jul 31 15:08 2007-July.txt
drwxrwsr-x7 root mailman238 Aug  1 11:59 attachments
drwxrwx---   12 mailman  mailman408 Aug  1 14:16 database
-rw-rw-r--1 root mailman   1465 Aug  1 14:16 index.html
-rw-rw1 mailman  mailman892 Aug  1 14:16 pipermail.pck



I've checked the alias file in /var/mailman/data/aliases:   
(Everything looks ok)

# STANZA START: qvc-requests
# CREATED: Wed Aug  1 09:09:12 2007
qvc-requests: "|/usr/share/mailman/mail/mailman post qvc- 
requests"
qvc-requests-admin:   "|/usr/share/mailman/mail/mailman admin qvc- 
requests"
qvc-requests-bounces: "|/usr/share/mailman/mail/mailman bounces  
qvc-requests"
qvc-requests-confirm: "|/usr/share/mailman/mail/mailman confirm  
qvc-requests"
qvc-requests-join:"|/usr/share/mailman/mail/mailman join qvc- 
requests"
qvc-requests-leave:   "|/usr/share/mailman/mail/mailman leave qvc- 
requests"
qvc-requests-owner:   "|/usr/share/mailman/mail/mailman owner qvc- 
requests"
qvc-requests-request: "|/usr/share/mailman/mail/mailman request  
qvc-requests"
qvc-requests-subscribe:   "|/usr/share/mailman/mail/mailman subscribe  
qvc-requests"
qvc-requests-unsubscribe: "|/usr/share/mailman/mail/mailman  
unsubscribe qvc-requests"
# STANZA END: qvc-requests

I've checked locks: - nothing regarding this list there.

main.cf shows: alias_maps = hash:/etc/postfix/lmail/ 
company.aliases,hash:/var/mailman/data/aliases

Where else can I check?

Thank you

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/lis

Re: [Mailman-Users] moved lists and now they don't work

[carconni]

Hi,

I know you guys aren't excited to hear this but it's running on an  
xserve.  I think there may have been an error in how I was told to  
move mailman...

does this look right?

corp-admin2:/private/var/mailman/archives/private root# ls -la ops.mbox/
total 80
drwxrwsr-x 3 root  mailman102 Jun 18 13:30 .
drw-rw   736 root  mailman  25024 Jun 26 19:55 ..
-rw-rw-r-- 1 root  mailman  37806 Jun 18 13:30 ops.mbox

corp-admin2:/private/var/mailman/archives/private root# ls -la ops
total 8
drwxrwsr-x 3 root  mailman102 Jun 26 19:56 .
drw-rw   736 root  mailman  25024 Jun 26 19:55 ..
-rw-rw-r-- 1 root  mailman   1040 Jun 26 19:55 index.html

On Jun 26, 2007, at 8:55 PM, Mark Sapiro wrote:

> carconni wrote:
>>
>> I'm still having trouble...
>>
>> I removed everything in /private/var/mailman/archives/public/ but
>> Mailman didn't replace the symlinks and when I tried to create the
>> symlinks, Mailman got really confused.  My lists are down and I don't
>> know how to recover them.
>>
>> corp-admin2:/private/var/mailman/archives/public root# ls -l
>> corp-admin2:/private/var/mailman/archives/public root#
>>
>>
>> I've run check permissions dozen's of times:
>>
>> corp-admin2:/private/var/mailman/archives/public root# /usr/share/
>> mailman/bin/check_perms -f
>> No problems found
>> corp-admin2:/private/var/mailman/archives/public root#
>>
>> yet my error logs show permission errors.  I've tried changing owners
>> from mailman:mailman to root:mailman and back again - I've made
>> directories world readable but I still get these errors...
>
>
> Are you running SeLinux or some other kind of security policy that is
> denying access?
>
>
>> Jun 26 19:13:08 2007 (10311) SHUNTING: 1182910388.3509221
>> +37c9f7ce90d565375941efb6b3a61c9ad826
>> Jun 26 19:13:28 2007 (10311) Archive file access failure:
>> /private/var/mailman/archives/private/customer-us.mbox/
>> customer-us.mbox [Errno 13] Permission denied: '/private/var/mailman/
>> archives/private/customer-us.mbox/customer-us.mbox'
>>
>>  corp-admin2:/private/var/mailman/archives/private root# cd  
>> customer-us
>
>
> And what if you
>
>cd customer-us.mbox
>ls -la
>
>
>>  corp-admin2:/private/var/mailman/archives/private/customer-us root#
>> ls -l
>>  total 5200
>>  drwxrwsr-x   8 root  mailman  272 Jun 26 14:33 2007-June
>>  -rw-rw-r--   1 root  mailman  2654504 Jun 26 14:33 2007-June.txt
>>  drw-rw   2 root  mailman   68 Jun 26 14:33 database
>>  -rw-rw-r--   1 root  mailman  479 Jun 18 13:30 index.html
>>
>> Jun 26 19:13:28 2007 (10311) Uncaught runner exception: [Errno 13]
>> Permission denied: '/private/var/mailman/archives/private/customer-
>> us.mbox/customer-us.mbox'
>> Jun 26 19:13:28 2007 (10311) Traceback (most recent call last):
>>   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in
>> _oneloop
>> self._onefile(msg, msgdata)
>>   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in
>> _onefile
>> keepqueued = self._dispose(mlist, msg, msgdata)
>>   File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in
>> _dispose
>> mlist.ArchiveMail(msg)
>>   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 199,
>> in ArchiveMail
>> self.__archive_to_mbox(msg)
>>   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 168,
>> in __archive_to_mbox
>> mbox = self.__archive_file(afn)
>>   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 156,
>> in __archive_file
>> return Mailbox.Mailbox(open(afn, 'a+'))
>> IOError: [Errno 13] Permission denied: '/private/var/mailman/ 
>> archives/
>> private/customer-us.mbox/customer-us.mbox'
>>
>>
>> Jun 26 19:23:03 2007 (10314) SHUNTING: 1182910982.1765511
>> +4636bcd0509b8d4fc66200d2a26b32dc929f0e06
>> Jun 26 19:23:13 2007 (10314) Uncaught runner exception: [Errno 13]
>> Permission denied: '/private/var/mailman/archives/private/ops'
>> Jun 26 19:23:13 2007 (10314) Traceback (most recent call last):
>>   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in
>> _oneloop
>> self._onefile(msg, msgdata)
>>   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in
>> _onefile
>> keepqueued = self._dispose(mlist, msg, msgdata)
>>   File "/usr/share/

Re: [Mailman-Users] moved lists and now they don't work

[carconni]

rrno 13] Permission denied: '/private/var/mailman/archives/ 
private/ops'

Jun 26 19:23:13 2007 (10314) SHUNTING: 1182910992.721427 
+d396922f361992f9d2b65e96d4763591331f5010


drwxrwsr-x9 root mailman  306 Jun 26 18:49 ops
drwxrwsr-x3 root mailman  102 Jun 18 13:30 ops.mbox

corp-admin2:/private/var/mailman/archives/private/ops root# ls -l
total 40
drwxrwxrwx   23 root mailman   782 Jun 18 13:30 2006-April
-rwxrwxrwx1 root mailman  6277 Jun 18 13:30 2006-April.txt
-rwxrwxrwx1 root mailman  1444 Jun 18 13:30 2006-April.txt.gz
drwxrwxrwx8 mailman  mailman   272 Jun 25 18:53 attachments
drwxrwxrwx7 root mailman   238 Jun 18 13:30 database
-rwxrwxrwx1 root mailman  1040 Jun 18 13:30 index.html
-rwxrwxrwx1 root mailman   864 Jun 18 13:30 pipermail.pck

Its funny, I was more worried about moving postfix and everyone's  
mailboxesI thought mailman would be a piece of cake.  If anyone  
understands what happening here - I'd really appreciate it.




On Jun 18, 2007, at 10:08 PM, Mark Sapiro wrote:


> carconni wrote:
>
>>
>> I had to move lists.  We had a hardware failure and they had to move
>> to our new mail server.  The mail server migration went fine and we
>> thought mailman moved okay as well but we were wrong.
>>
>> Earlier today I tried to create a new list and and got an error so my
>> boss said to check permissions.  I ran the /usr/share/mailman/bin/
>> check_perms -f in every mailman file I could find but Im still
>> getting permission errors.  I even gave global permissions to all the
>> archives but no luck.
>>
>
>
> It doesn't matter where your current directory is. You just run
>
> /usr/share/mailman/bin/check_perms -f
>
> as root until it reports no errors.
>
>
>
>> Right now, lists have stopped - they just aren't working and I just
>> can't figure out what the problem is.  The more we tried to fix it,
>> the worse it got.  Unfortunately my company heavily relies on them so
>> I figured before I set out to manually configure mail aliases, does
>> anyone know a way around this mess?
>>
>> from var/mailman/logs/error: (the permissions and ownership for the
>> client-list is -rw-r--r--   1 root  mailman  479 Jun 18 13:30 /
>> private/var/mailman/archives/private/client-list/index.html)
>>
>
>
> It should be group writable - i.e. -rw-rw-r--   1 root  mailman
>
>
>
>> Jun 18 19:24:34 2007 (10816) SHUNTING: 1182219873.5167899
>> +ceff885a98ff1c83a23f7e83b4d94678813ee808
>> Jun 18 19:25:36 2007 (10819) Uncaught runner exception: [Errno 1]
>> Operation not permitted: '/private/var/mailman/archives/public/ 
>> client-
>> list'
>> Jun 18 19:25:36 2007 (10819) Traceback (most recent call last):
>>   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in
>> _oneloop
>> self._onefile(msg, msgdata)
>>   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in
>> _onefile
>> keepqueued = self._dispose(mlist, msg, msgdata)
>>   File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line
>> 133, in _dispose
>> mlist.Save()
>>   File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save
>> self.CheckHTMLArchiveDir()
>>   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235,
>> in CheckHTMLArchiveDir
>> breaklink(pubdir)
>>   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55,
>> in breaklink
>> os.unlink(link)
>> OSError: [Errno 1] Operation not permitted: '/private/var/mailman/
>> archives/public/client-list'
>>
>
>
> I'm guessing when you backed up and moved from the old machines, you
> wound up with files in /private/var/mailman/archives/public/
>
> There should only be symlinks in that directory. Every
> /private/var/mailman/archives/public/ and
> /private/var/mailman/archives/public/ is a symlink to
> the corresponding /private/var/mailman/archives/private/ and
> /private/var/mailman/archives/private/ directory.
>
> Either fixing that or simply removing everything in the
> /private/var/mailman/archives/public/ will allow Mailman to recreate
> the proper symlinks.
>
>
>
>> Jun 18 19:25:36 2007 (10819) SHUNTING: 1182219935.3121431
>> +07ef8a32317dde697d0042ee151b8fd11d41b398
>> Jun 18 19:25:36 2007 (10816) Uncaught runner exception: [Errno 13]
>> Permission denied: '/private/var/mailman/archives/private/client- 
>> list/
>> index.html

[Mailman-Users] moved lists and now they don't work

[carconni]

Hi

I had to move lists.  We had a hardware failure and they had to move  
to our new mail server.  The mail server migration went fine and we  
thought mailman moved okay as well but we were wrong.

Earlier today I tried to create a new list and and got an error so my  
boss said to check permissions.  I ran the /usr/share/mailman/bin/ 
check_perms -f in every mailman file I could find but Im still  
getting permission errors.  I even gave global permissions to all the  
archives but no luck.

Right now, lists have stopped - they just aren't working and I just  
can't figure out what the problem is.  The more we tried to fix it,  
the worse it got.  Unfortunately my company heavily relies on them so  
I figured before I set out to manually configure mail aliases, does  
anyone know a way around this mess?

from var/mailman/logs/error: (the permissions and ownership for the  
client-list is -rw-r--r--   1 root  mailman  479 Jun 18 13:30 / 
private/var/mailman/archives/private/client-list/index.html)

Jun 18 19:24:34 2007 (10816) SHUNTING: 1182219873.5167899 
+ceff885a98ff1c83a23f7e83b4d94678813ee808
Jun 18 19:25:36 2007 (10819) Uncaught runner exception: [Errno 1]  
Operation not permitted: '/private/var/mailman/archives/public/client- 
list'
Jun 18 19:25:36 2007 (10819) Traceback (most recent call last):
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in  
_oneloop
 self._onefile(msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in  
_onefile
 keepqueued = self._dispose(mlist, msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line  
133, in _dispose
 mlist.Save()
   File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save
 self.CheckHTMLArchiveDir()
   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235,  
in CheckHTMLArchiveDir
 breaklink(pubdir)
   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55,  
in breaklink
 os.unlink(link)
OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ 
archives/public/client-list'

Jun 18 19:25:36 2007 (10819) SHUNTING: 1182219935.3121431 
+07ef8a32317dde697d0042ee151b8fd11d41b398
Jun 18 19:25:36 2007 (10816) Uncaught runner exception: [Errno 13]  
Permission denied: '/private/var/mailman/archives/private/client-list/ 
index.html'
Jun 18 19:25:36 2007 (10816) Traceback (most recent call last):
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in  
_oneloop
 self._onefile(msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in  
_onefile
 keepqueued = self._dispose(mlist, msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in  
_dispose
 mlist.ArchiveMail(msg)
   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 216,  
in ArchiveMail
 h.close()
   File "/usr/share/mailman/Mailman/Archiver/pipermail.py", line 313,  
in close
 self.write_TOC()
   File "/usr/share/mailman/Mailman/Archiver/HyperArch.py", line  
1048, in write_TOC
 toc = open(os.path.join(self.basedir, 'index.html'), 'w')
IOError: [Errno 13] Permission denied: '/private/var/mailman/archives/ 
private/client-list/index.html'

Jun 18 19:25:36 2007 (10816) SHUNTING: 1182219935.3121431 
+1f5997710b510ce2af03c4b18e68bca2a9a7cf5d
Jun 18 19:25:53 2007 (10819) Uncaught runner exception: [Errno 1]  
Operation not permitted: '/private/var/mailman/archives/public/client- 
list'
Jun 18 19:25:53 2007 (10819) Traceback (most recent call last):
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in  
_oneloop
 self._onefile(msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in  
_onefile
 keepqueued = self._dispose(mlist, msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line  
133, in _dispose
 mlist.Save()
   File "/usr/share/mailman/Mailman/MailList.py", line 529, in Save
 self.CheckHTMLArchiveDir()
   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 235,  
in CheckHTMLArchiveDir
 breaklink(pubdir)
   File "/usr/share/mailman/Mailman/Archiver/Archiver.py", line 55,  
in breaklink
 os.unlink(link)
OSError: [Errno 1] Operation not permitted: '/private/var/mailman/ 
archives/public/client-list'

Jun 18 19:25:53 2007 (10819) SHUNTING: 1182219952.298547 
+a97ef5907aa7d67744b62971add1b089b4336b32
Jun 18 19:25:53 2007 (10816) Uncaught runner exception: [Errno 13]  
Permission denied: '/private/var/mailman/archives/private/client-list/ 
index.html'
Jun 18 19:25:53 2007 (10816) Traceback (most recent call last):
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in  
_oneloop
 self._onefile(msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in  
_onefile
 keepqueued = self._dispose(mlist, msg, msgdata)
   File "/usr/share/mailman/Mailman/Queue/ArchRunner.py", line 73, in  
_dispose
 mlist.ArchiveMail(msg)
   File "/usr/share/mailman/Mailman/

Re: [Mailman-Users] Moving Lists

[carconni]

Brad,

Thank you!  It sounds like you've saved me a lot of heartache.  We  
have a Netapps that I was hoping to mount on the mail server  and was  
hoping I could avoid losing mail when the mail server ran into problems.

It's my understanding that the next version on Leopard will support  
mail clustering so the solution I was looking for was somewhat  
temporary.  I'll have to give this a lot more thought.


On May 24, 2007, at 9:46 PM, Brad Knowles wrote:

> On 5/24/07, Brad Knowles wrote:
>
>>  In short, I'd avoid this kind of solution like the plague, as far as
>>  postfix is concerned.  It may be okay to store certain types of user
>>  mailboxes out on NFS (or other shared filesystem type), but not the
>>  mail queues themselves.
>
> I should also say that most mailbox formats are not safe to store  
> on NFS, or any other kind of typical shared filesystem.  If you  
> spend the really big bucks and you get Veritas VxFS (plus all their  
> cluster-aware software) on big honking Sun Solaris servers, then  
> you may be able to store them on a shared filesystem (if you do it  
> right), but at that point I imagine you'd have enough money that  
> you wouldn't need to be coming to us with questions.
>
> There are some mailbox formats that are supposedly safe to store on  
> NFS, but even they have some issues and extra baggage that they  
> bring to the table, and which I imagine you are probably not aware of.
>
>
> Of course, most NFS implementations would still leave you with a  
> single-point-of-failure (SPOF), that being your NFS server.
>
> The only way to resolve that one is to go with a clustered NFS  
> server solution, such as sold by the folks at Network Appliance.   
> But those things are pretty damn bloody expensive, too.  Even so,  
> they're still a lot less expensive than solutions from the likes of  
> EMC or Hitachi Data Systems.
>
>
> Now, if you're talking about a shared filesystem type that is  
> anything but NFS, then you've got a whole 'nother Universe of  
> problems.
>
> Yes, I know about GFS from what used to be Sistina (since bought by  
> Red Hat), and I know one of their former senior architects -- he's  
> been my co-author on some of the invited talks I've done, and I've  
> been a technical reviewer of his book.  I also know about things  
> like Coda (or AFS), and a wide variety of other distributed  
> filesystem solutions.
>
> No, I'm not going to buy any sales pitch regarding how they're the  
> perfect solution for problems like this.  If you want a real  
> distributed cluster-aware filesystem for use with mail servers,  
> then you're going to have to pay some real money.  It's that simple.
>
> Veritas VxFS isn't necessarily the only solution here, but it is  
> one of the best known.  There are other alternatives in this space,  
> but they are equally expensive.  And no, Veritas VxFS on Linux is  
> not the same as Veritas VxFS on Solaris.
>
>
> Since you're using Mailman on Mac OS X, I should also point out FAQ  
> 1.21 and 1.29 at  req=show&file=faq01.021.htp> and  faqw-mm.py?req=show&file=faq01.029.htp>.
>
> -- 
> Brad Knowles <[EMAIL PROTECTED]>, Consultant & Author
> LinkedIn Profile: 
> Slides from Invited Talks: 
>
> 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
>

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

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

[Mailman-Users] Moving Lists

[carconni]

Hi,

I'm having some trouble with my mail server (xserve 10.4.9).  We  
discovered that there were some hardware issues and I'm in the  
process of building a new mail server to replace the old.  I  
understand that the current MAC OS doesn't support clustering so what  
we would like to do is move user data to a shared drive.  The service  
will remain on the server but we'd like to move the data to a shared  
file system.  Only one server will be processing mail but because of  
multiple failures, we'd like to find a way to safeguard our data.

I'm moving postfix's /var/spool to /mounted_file_share/mail/var/spool  
and I've changed the path in the main.cf file to point to it.  Is  
there anyway to do this with mailman?  Can I move /var/mailman to / 
mounted_file_share/var/mailman and is there a configuration file in / 
usr/share/mailman that I should modify?

Thank you


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

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

[Mailman-Users] additional Mailman Admin accounts

[Carconni]

Hi,

Is it possible to create an additional Mailman admin account.  I have a 
department director who want access over all his department's mailing lists.  
He wants to be able to use one username and password without changing the 
individual list passwords.  Is there a way to do this?  We can't give them the 
mailman account info so we need to find an alternative.

Thanks


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

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

[Mailman-Users] Mailman just stopped

[Carconni]

First, thank you Mr. Sapiro for all the help you provide us.  I couldn't have 
gotten as far as I have with my mailmain program without you.

Out of desperation, I backed up the inbox (/private/var/mailman/qfiles/in) and 
dumped it and the lists just started working again.  I've started moving mail 
back little by little and everything seems to be okay now.

I'm still not sure what happened.  Aside from the logs I've already posted, 
there was nothing else to indicate what went wrong.  I will however look into 
rebuilding my mailman install if you believe that the installation should 
recoginize gb2312.

Thanks again and until the next calamity,

Constance

Carconni wrote

Mailman has been working beautifully for awhile now but yesterday it just 
stopped.  I wound up repairing all of the databases but it happened again 
today.  I'm getting the following error:

Sep 21 06:11:17 2006 (15075) Uncaught runner exception: unknown encoding: gb2312
Sep 21 06:11:17 2006 (15075) Traceback (most recent call last):
 File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
   self._onefile(msg, msgdata)
 File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
   keepqueued = self._dispose(mlist, msg, msgdata)
 File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 130, in 
_dispose
   more = self._dopipeline(mlist, msg, msgdata, pipeline)
 File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 153, in 
_dopipeline
   sys.modules[modname].process(mlist, msg, msgdata)
 File "/usr/share/mailman/Mailman/Handlers/CookHeaders.py", line 74, in process
   prefix_subject(mlist, msg, msgdata)
 File "/usr/share/mailman/Mailman/Handlers/CookHeaders.py", line 262, in 
prefix_subject
   h.append(s, c)
 File 
"/BinaryCache/mailman/mailman-117.root~35/usr/share/mailman/pythonlib/email/Header.py",
 line 285, in append
LookupError: unknown encoding: gb2312


Sep 21 06:11:17 2006 (15075) SHUNTING: 
1158844276.9904189+1e2464070413bcc3355b914153a142061eb60c6f


Does anyone know what might be causing this and why it would happen suddenly 
like this.


There are several things going on here. A message (most likely spam) is
being posted to your list and accepted for delivery. This message has
it's Subject: header encoded in the 'gb2312' (chinese) character set.

Mailman is trying to decode the Subject: so it can add the
subject_prefix and your Mailman/Python installation does not
support/recognize the 'gb2312' character set.

The above error occurs and the message is moved to Mailman's shunt
queue where it will stay untouched until you manually remove it or
queue it for reprocessing using bin/unshunt.

You can use bin/show_qfiles or bin/dumpdb to look at the entries in
qfiles/shunt and then just remove those you don't want.

You can also adjust your list settings to be not so generous in what
you accept.

There is something wrong with your Mailman installation as it should
recognize 'gb2312'.

This specific error should not stop Mailman. It just shunts the message
and that should be the end of it.

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



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

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

[Mailman-Users] Mailman just stopped

[Carconni]

Hi,

Mailman has been working beautifully for awhile now but yesterday it just 
stopped.  I wound up repairing all of the databases but it happened again 
today.  I'm getting the following error:

Sep 21 06:11:17 2006 (15075) Uncaught runner exception: unknown encoding: gb2312
Sep 21 06:11:17 2006 (15075) Traceback (most recent call last):
  File "/usr/share/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop
self._onefile(msg, msgdata)
  File "/usr/share/mailman/Mailman/Queue/Runner.py", line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 130, in 
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
  File "/usr/share/mailman/Mailman/Queue/IncomingRunner.py", line 153, in 
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
  File "/usr/share/mailman/Mailman/Handlers/CookHeaders.py", line 74, in process
prefix_subject(mlist, msg, msgdata)
  File "/usr/share/mailman/Mailman/Handlers/CookHeaders.py", line 262, in 
prefix_subject
h.append(s, c)
  File 
"/BinaryCache/mailman/mailman-117.root~35/usr/share/mailman/pythonlib/email/Header.py",
 line 285, in append
LookupError: unknown encoding: gb2312


Sep 21 06:11:17 2006 (15075) SHUNTING: 
1158844276.9904189+1e2464070413bcc3355b914153a142061eb60c6f


Does anyone know what might be causing this and why it would happen suddenly 
like this.

Thank you in advance for your assistance

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

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

[Mailman-Users] isolating mailman attributes/variables

[Carconni]

Hi,

Hi

I have a few hundred lists.  During migration some of my reply to variables 
were over written with wrong reply to address.  This didn't happen to all of 
the lists but those that did have this overwrite need to be corrected.  (All my 
lists have explicit reply to).

For example:  List [EMAIL PROTECTED]  has an explicit reply to [EMAIL 
PROTECTED], List [EMAIL PROTECTED] has an explicit reply to [EMAIL PROTECTED]

Now [EMAIL PROTECTED] should have an explicit reply to [EMAIL PROTECTED] but 
somehow wound up with [EMAIL PROTECTED] as it's reply to address.
In addition, [EMAIL PROTECTED] was written to some other lists as well.

Is there a way to weed out which lists have a given reply to address?  I don't 
really want to walk through each list to find out which list contains the wrong 
variable.

We have ./find_member.  Is there something like  ./find_variable?  I tried to 
use config_list to print out all my lists into one file so I can grep the reply 
to info but unfortunately each time the script looped to the next list it 
overwrote the results of the last result.

Thanks







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

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

[Mailman-Users] odd little issues

[Carconni]

Hi,

We just migrated to mailman not to long ago and while I love it as the 
administrator my users are not pleased at this time.  I've got some strange 
issues that I haven't been able to work out and I'm hoping someone here can 
help.

I've done some googling and I've read quite a bit but for some reason I'm 
having trouble understanding what I need to do to resolve these issues.  I 
apologize in advance for asking what may seem to be "old" questions:

1.Most of my lists allow anyone to post with no explicit destination required

generic_nonmember_action = accept
require_explicit_destination = no
emergency moderation = no
default_member_moderation = no

yet I occasionally receive requests for an approval for posts by non-members.  
This is really bad since these are our customers.  What else could be causing 
this to happen?  What can I do to ensure that emails sent from certain domains 
(ie, that of my customers) are automatically accepted?

2. I've seen this around but I need to fix it:

I have Outlook users.  They are receiving empty attachments when receiving mail 
from mailman.  As they love to point out,  "this wasn't a problem with the old 
mail server" (to which I respond - "yeah - you didn't get any mail at all - but 
I guess we all forget the bad times")

Anyway - they do get the message in the body but they get this crazy empty 
attachment and it's driving them nuts.  Now removing HTML is not an option 
since a lot of our reports are sent this way.  (My VP of Engineering has 
already made this clear).  So I tried deleting the footer data thinking maybe 
this was the culprit but that didn't help.  Exactly what do I need to do to 
prevent this attachment from being sent out from our lists?  I don't know how 
to completely remove the footer but I don't know if that's actually causing the 
problem.

3.Is there any administrative interface that allows me to address all pending 
requests for all lists with out having to go through each and every list admin 
individually?  Lately my mailman server has been sending me approval requests 
but when I go to the individual list admin there are no posts waiting for 
approval.  I've noticed that many of "these requests" have a dash "-" 
proceeding the subject line.

for ex: From:   [EMAIL PROTECTED] Subject: -1 Expuk-reports moderator 
request(s) waiting

However, when I go to the admin interface to approve the request, there is none.

I get one for every list we have on this system.  We have well over a hundred 
lists on this server and a couple of hundred on the other.

I appreciate your assistance and patience




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

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

[Mailman-Users] config_list

[Carconni]

Hi,


Were migrating from dmail to mailman. 

I have a couple of quick questions - if I copy my /private/var/mailman 
directory to another location will I be able to use it to restore my listserv 
with it if something goes wrong with it?

I have over 300 lists and I need to modify 'generic_nonmember_action': 1, to 
'generic_nonmember_action': 0,.  I understand that config_list should be able 
to do that.  Will it change all the lists automatically?  What if I wanted to 
change only a group of lists?  Can I put 'generic_nonmember_action': 0, in a 
file and lets call that file (fix4), do I run ./config_list -i fix4?  What is 
the exact syntax. I've looked at mailman commands and I've also run 
./config_list -h and there just isn't enough information there.

Does config_list act on the *.pck files in /private/var/mailman/lists/listname 
directory?

Also can I set "List of non-member addresses whose postings should be 
automatically accepted. " under Privacy to *.emailaddress.com to accept all 
address from one client?


Thanks for any help you can provide with this.


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

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

Re: [Mailman-Users] create multiple lists resolved

[Carconni]

Dear Mr. Shapiro,

I just wanted to let you know how I resolved it.  Thanks again for your help.

#!/bin/sh

list=`cat $1`

for user in $list
do
echo $user
./newlist -q $user [EMAIL PROTECTED] password  
done



From: [EMAIL PROTECTED]
Subject:Re: [Mailman-Users] create multiple lists
Date:   March 29, 2006 5:22:54 PM PST
To:   [EMAIL PROTECTED], mailman-users@python.org

Carconni wrote:

Were moving to mailman and I need to create over 250 "lists".  All the lists 
will have the same owner and and the same password.  Is there anyway to 
automate this?  I can set up a script to loop through a test file but how can I 
set the owner_mail = args[1] and listpasswd = args[2] to a default value?

See

bin/newlist --help

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

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

[Mailman-Users] create multiple lists

[Carconni]

Hi,

Were moving to mailman and I need to create over 250 "lists".  All the lists 
will have the same owner and and the same password.  Is there anyway to 
automate this?  I can set up a script to loop through a test file but how can I 
set the owner_mail = args[1] and listpasswd = args[2] to a default value?

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

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