Mailman 3 June 2007 - Mailman-Users

Blank Characters Removed from "Subject:" Line
by Barry Finkel 28 Jun '07

28 Jun '07

I am running Mailman 2.1.9. I have a list where one posting has a "Subject:" line: Change in Procedure for Computers on list with possible Antivirus Problems The next posting in the thread has: Change in Procedure for Computers on list with possible AntivirusProblems A subsequent posting (not treated in the list archives as the same thread) has Change in Procedure for Computers on list with possibleAntivirusProblems The next posting in the thread has: Change in Procedure for Computers on list withpossibleAntivirusProblems The final posting in this thread has the same "Subject:" line as immediately above. I am not subscribed to this list and cannot post to it, so I do not know if a subsequent posting to this thread will remove another blank character in the "Subject:" line. What I see in the list mbox file are these lines (with line numbers): ------ 184232 Subject: Change in Procedure for Computers on list with possible Antivirus 184233 Problems ------ 184331 Subject: RE: Change in Procedure for Computers on list with possible 184332 AntivirusProblems ------ 184456 Subject: Re: Change in Procedure for Computers on list with 184457 possibleAntivirusProblems ------ 184566 Subject: RE: Change in Procedure for Computers on list 184567 withpossibleAntivirusProblems ------ 184735 Subject: RE: Change in Procedure for Computers on list 184736 withpossibleAntivirusProblems ------ Note that the original subject is split into two lines. What might be causing this? Is this a problem with Mailman, or is it a problem with the sender's Mail User Agent (probably Outlook), or a problem with the sender's mail system: X-MimeOLE: Produced By Microsoft Exchange V6.5 As the mbox file has the blanks removed, I have to believe that it is not Mailman that is removing the blanks. ---------------------------------------------------------------------- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone: +1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: BSFinkel(a)anl.gov Argonne, IL 60439-4828 IBMMAIL: I1004994

3 2

Re: [Mailman-Users] lurker behaving strangely
by Jenny Hopkins 28 Jun '07

28 Jun '07

On 21/06/07, Brad Knowles <brad(a)shub-internet.org> wrote: > Please do let us know how things turn out. We don't provide official > support for third-party add-ons, but it can be useful for us to > provide links to where people can get support, in case someone else > in the future follows the same logic that you did. > > -- As a follow-up to my problem with the lurker archives disappearing randomly: I found random mails were disappearing as they were being flagged as deleted in the lurker database, and each time I rebuilt the database from the mailman archives it would happen. I found a lurker-users list where it was suggested a web crawler could be triggering the delete action. I disabled the delete line in the lurker config and (touch wood) it has been stable for 3 days now. Many thanks for the suggestions. Jenny

1 0

Mail from GioMBG > hack this into /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf to alowed mod_security + mailman into fedora 7 moonshine with mod_security
by Gio MBG Canepa root 28 Jun '07

28 Jun '07

MANY Thanks Jeffrey! SINCERLY! I have resolved with this hack into my: /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf Simply I have commented: SecRule REQUEST_BASENAME as # SecRule REQUEST_BASENAME I think that is the minor hack to prevent this kind of apache+mod_security+mailman error and to alowed the .shtml file extension in my html... YES You have just resolved not one but the 2 unique most bad problem into my newest monshine (fedora7)! MANY THANKs! GioMBG ---| hack this into /etc/httpd/modsecurity.d/modsecurity_crs_30_http_policy.conf to alowed mod_security + mailman into fedora 7 moonshine with mod_security |--- # Restrict file extension # # TODO the list of file extensions below are virtually always considered unsafe # and not in use in any valid program. If your application uses one of # these extensions, please remove it from the list of blocked extensions. # You may need to use ModSecurity Core Rule Set Templates to do so, otherwise # comment the whole rule. # # SecRule REQUEST_BASENAME "\.(?:c(?:o(?:nf(?:ig)?|m)|s(?:proj|r)?|dx|er|fg|md)|p(?:rinter|ass|db|ol|wd)|v(?:b(?:proj|s)?|sdisco)|a(?:s(?:ax?|cx)|xd)|s(?:html?|ql|tm|ys)|d(?:bf?|at|ll|os)|i(?:d[acq]|n[ci])|ba(?:[kt]|ckup)|res(?:ources|x)|l(?:icx|nk|og)|\w{,5}~|webinfo|ht[rw]|xs[dx]|exe|key|mdb|old)$" \ "t:urlDecodeUni, t:lowercase, deny,log,auditlog,status:500,msg:'URL file extension is restricted by policy', severity:'2',id:'960035'" -- Giò "MBG" Canepa - E Mail: mbg a mbg.it Phone & Fax +39 0541 985 737 - Mobile +39 393 33 567 07 http://www.mbg.it | http://www.9Records.com Snail mail P.O. Box 59 / 47838 Riccione Italy

2 1

archive processing problem (mmarch w/ MIME)
by John Reddy 27 Jun '07

27 Jun '07

I've checked the FAQ and Googled this before coming here to ask for advice. Background: Running Debian 4.0, x86_64, MTA is Postfix, packaged Debian Mailman (version listed "2.1.9-7"), Python version 2.4.4. I'm having a problem where the archives are not ingesting MIME email for various mailing lists that I maintain. A message goes to the mailing list, is processed properly and gets reflected to the recipients. All email to the list winds up in /var/lib/mailman/archives/private/listname.mbox/listname.mbox. However, messages that have MIME encoding don't make it to /var/lib/mailman/archives/private/listname for inclusion in the web page. I tried running mmarch to rebuild the archive, and got the following output: > [root@mailserver] # mmarch --wipe testmaillist-l testmaillist-l.mbox.o > #00000 <200601010510.k015A1J17411(a)sample.email.bnl.gov> > figuring article archives > 2006-January > #00001 <200601020510.k025A0829608(a)sample.email.bnl.gov> > figuring article archives > 2006-January > #00002 <200601030510.k035A1w11781(a)sample.email.bnl.gov> > figuring article archives > 2006-January > Updating index files for archive [2006-January] > Date > Subject > Author > Thread > Computing threaded index > Updating HTML for article 0 > Updating HTML for article 1 > Updating HTML for article 2 > Pickling archive state into > /var/lib/mailman/archives/private/testmaillist-l/pipermail.pck > Traceback (most recent call last): > File "/usr/sbin/mmarch", line 200, in ? > main() > File "/usr/sbin/mmarch", line 188, in main > archiver.processUnixMailbox(fp, start, end) > File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 564, in > processUnixMailbox > m = mbox.next() > File "/usr/lib/python2.4/mailbox.py", line 35, in next > return self.factory(_Subfile(self.fp, start, stop)) > File "/var/lib/mailman/Mailman/Mailbox.py", line 89, in scrubber > return mailbox.scrub(msg) > File "/var/lib/mailman/Mailman/Mailbox.py", line 109, in scrub > return self._scrubber(self._mlist, msg) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 393, in > process > replace_payload_by_text(msg, sep.join(text), charset) > File "/var/lib/mailman/Mailman/Handlers/Scrubber.py", line 175, in > replace_payload_by_text > msg.set_payload(text, charset) > File "email/Message.py", line 218, in set_payload > File "email/Message.py", line 242, in set_charset > TypeError: us-ascii "mmarch" seems to be having trouble with the Content-Type header line. If I pull out that line for a given message, it is ingested, though it displays the full MIME text. Any direction on where to look would be appreciated. -John -- John Reddy jreddy(a)bnl.gov (631) 344-3284 Technology Architect ITD Unix Services Brookhaven National Labs

4 9

Re: [Mailman-Users] Member only list?
by Mark Sapiro 27 Jun '07

27 Jun '07

L. H. wrote: > >One minor thing. >This config: > ># Set misc settings >require_explicit_destination = 0 >default_member_moderation = 1 >member_moderation_action = 1 >member_moderation_notice = 'Sorry, subscribers cannot post to this list.' >generic_nonmember_action = 1 > >Should make it so that mod approval for posts is required, for both member >and non member posts... > >NON member posts works. It requires mod approval. >MEMBER posts just get rejected. That's because the correspondence between values and actions for member_moderation_action is different than that for generic_nonmember_action. member_moderation_action has no 'accept' action because it doesn't make sense. Therefore, the values for member_moderation_action are 0==Hold, 1==Reject and 2==Discard. -- Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

1 0

Re: [Mailman-Users] moved lists and now they don't work
by carconni 27 Jun '07

27 Jun '07

Hi, 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... Jun 26 19:13:08 2007 (10311) SHUNTING: 1182910388.3509221 +37c9faaaa7ce90d565375941efb6b3a61c9ad826 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 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/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/ToDigest.py", line 91, in process send_digests(mlist, mboxfp) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/share/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 227, in process url = save_attachment(mlist, part, dir, filter_html=False) File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 352, in save_attachment makedirs(fsdir) File "/usr/share/mailman/Mailman/Handlers/Scrubber.py", line 339, in makedirs os.makedirs(dir, 02775) File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 153, in makedirs File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 153, in makedirs File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 153, in makedirs File "/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ python2.3/os.py", line 154, in makedirs OSError: [Errno 13] Permission denied: '/private/var/mailman/archives/ private/ops' Jun 26 19:23:13 2007 (10314) SHUNTING: 1182910992.721427 +d396922f361992f9d2b65e96d4763591331f5010 drwxrwsr-x 9 root mailman 306 Jun 26 18:49 ops drwxrwsr-x 3 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 -rwxrwxrwx 1 root mailman 6277 Jun 18 13:30 2006-April.txt -rwxrwxrwx 1 root mailman 1444 Jun 18 13:30 2006-April.txt.gz drwxrwxrwx 8 mailman mailman 272 Jun 25 18:53 attachments drwxrwxrwx 7 root mailman 238 Jun 18 13:30 database -rwxrwxrwx 1 root mailman 1040 Jun 18 13:30 index.html -rwxrwxrwx 1 root mailman 864 Jun 18 13:30 pipermail.pck Its funny, I was more worried about moving postfix and everyone's mailboxes....I 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/<listname> and > /private/var/mailman/archives/public/<listname.mbox> is a symlink to > the corresponding /private/var/mailman/archives/private/<listname> and > /private/var/mailman/archives/private/<listname.mbox> 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' >> 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/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:53 2007 (10816) SHUNTING: 1182219952.298547 >> +542a885011bac44ed8f869a06f7c64ebe07acaf9 >> Jun 18 19:27:07 2007 (10819) Uncaught runner exception: [Errno 1] >> Operation not permitted: '/private/var/mailman/archives/public/ >> client- >> list' >> Jun 18 19:27:07 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:27:07 2007 (10819) SHUNTING: 1182220026.5520279 >> +b4a5f31a903a595b30aad7c8b13e6b37e44b3b25 >> Jun 18 19:27:07 2007 (10816) Uncaught runner exception: [Errno 13] >> Permission denied: '/private/var/mailman/archives/private/client- >> list/ >> index.html' >> Jun 18 19:27:07 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:27:07 2007 (10816) SHUNTING: 1182220026.5520279 >> +eddee6c8cd6b87769edeaa60fe9c23f1e3e19640 >> >> >> >> ------------------------------------------------------ >> Mailman-Users mailing list >> Mailman-Users(a)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/ >> msapiro%40value.net >> >> Security Policy: http://www.python.org/cgi-bin/faqw-mm.py? >> req=show&file=faq01.027.htp >> > > -- > Mark Sapiro <msapiro(a)value.net> The highway is for gamblers, > San Francisco Bay Area, California better use your sense - B. Dylan > > >

2 4

Re: [Mailman-Users] Member only list?
by L. H. 27 Jun '07

27 Jun '07

Hi Dan, > > The reason it is being held: > > > > Message has implicit destination > > Have you read http://www.python.org/cgi-bin/faqw-mm.py? > req=show&file=faq01.009.htp > regarding this message? Thanks for this link. It is not an umbrella list (or am I mistaking umbrella for something else here? Please elaborate), and the domain is fine... Do you think if I enfore "require_explicit_destination = 0", it will work?

2 3

Re: [Mailman-Users] Member only list?
by L. H. 27 Jun '07

27 Jun '07

Hi Mark / mailman user list, Hope you still remember me. Sorry, been VERY busy... Below is a brief summary of our previous exchange of mails. Beneath it are my finding whilst debugging some more... > >> What is the reason why the post is held? You will find the reason in > >> the admindb interface, in the notice to the admin and in Mailman's > >> vette log. > > > >It says, "dear moderator, the following message awaits your approval", or > >something like that... You know, the standard "moderator approval > request". > > And it also gives the subject of the post and the reason it was held > such as "post by non member", "implicit destination", "too big". or > some such. > > If you don't currently have the notice, you can find the held message > entries with reasons in Mailman's vette log. What are the reasons the > posts are held? 1) OPEN List Config settings: # Set misc settings generic_nonmember_action = 0 default_member_moderation = no subscribe_policy = 2 max_message_size = 50 reply_goes_to_list = 1 2) MEMBER posting only # Set misc settings default_member_moderation = no generic_nonmember_action = 2 subscribe_policy = 2 max_message_size = 50 reply_goes_to_list = 1 3) CLOSED (all posts req mod approval) # Set misc settings default_member_moderation = yes member_moderation_action = 1 member_moderation_notice = 'Sorry, subscribers cannot post to this list.' generic_nonmember_action = 1 subscribe_policy = 2 max_message_size = 50 reply_goes_to_list = 1 Now, in ALL cases, I end up with an email like this: ============ Subject: Your message to 53-debuglist awaits moderator approval Your mail to '53-debuglist' with the subject hiya Is being held until the list moderator can review it for approval. The reason it is being held: Message has implicit destination Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://www.test.com/mailman/confirm/53-debuglist/6a91ccdb4acaf7e5bd237e3059b 90d1439c8423d ============ (of course I did make member, etc. NO mail is sent to list admin! Only THIS mail is sent to the sender...) Furthermore, as you can see from the configs above, I am also trying to create 3 options for subscribing: Open (no approval of verification req, verification req, approval by mod required) However, in ALL cases, I get an email to confirm my address. NO mod approvals, no nothing. Also, in "open" mode (no verification), I DO get a verification request. I am working on the www.rackstar.net project. This used to have majordomo, which sucks. I am replacing it with mailman, which is a LOT better. However, I can NOT use the interface mailman offers for the above, because the rackstar interface has to do this. How I do it now is create a text file, and use config_list to generate the configuration. This must be possible... Right? Hope you have a solution for me. Thanks! Leslie

1 0

Is it possible to reply to listname@lists... and not to listname-bounces@lists...
by TRON478 27 Jun '07

27 Jun '07

Hello, when i get a mail from my mail i can reply to the list via the adress listname-bounces(a)lists.mailman.com but i want to reply via listname(a)lists.mailman.com is this possible? thanks yavuz

3 2

export list subscribers list
by TRON478 27 Jun '07

27 Jun '07

hi, is it possible to export the subscribers list of a list to a text, csv or another file format? thats very important for me, but i couldnt find a function in the list administration interface. thanks yavuz

5 5