[Mailman-Users] I was thinking.doc
I was thinking... Could it be possible to edit the file '/etc/sysconfig/mailman' put in another parameter to get it reflected into the resulting mm_cfg.py when I change it in YaST2 and then run SuSEconfig ? Or are all parameters in the /etc/sysconfig files hardcoded? If it's possible, and anyone know how to manage it, can you please tell me how to put in a line for OWNERS_CAN_ENABLE_PERSONALIZATION ? Thanks! Anders Norrbring Norrbring Consulting -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Information !!!
I´m using mailman in my server and I have a litle problem. My list (1 list only) have 1.400 mails on it... And I´m having bounce problem How many mails can be recorded to a list ??? Kirk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Access problem..
On Wednesday, August 13, 2003, at 10:13 am, Anders Norrbring wrote: Here's one of the mails I get every 5 minutes from my server: Traceback (most recent call last): File /usr/lib/mailman/cron/gate_news, line 274, in ? main() File /usr/lib/mailman/cron/gate_news, line 249, in main lock.lock(timeout=0.5) File /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, line 238, in lock File /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, line 415, in __write IOError: [Errno 13] Permission denied: '/var/lib/mailman/locks/gate_news.lock.berit.6176.0' You could try running Mailman's check_perms program. Looks from the paths in the traceback above as though it could be in /usr/lib/mailman/bin/check_perms. Run it with the -h option to get it to print its usage. And when I look in '/var/mailman/locks' that dir is empty! Also, in '/var/tmp' there's only one entry, a subdir named 'vi.recover' There's something wrong, but I don't know where to start looking. It's installed on a SuSE system based on United Linux 1.0 and the mailman package is a SuSE distributed one. Anders Norrbring Norrbring Consulting -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman with sendmail
Hello, I Have problems getting mailman to work with sendmail. I followed the Readme.sendmail instructions, but always i send a mail to [EMAIL PROTECTED] i get an error that the user 'somelist' doesnt exist. Thx --- Georges ENGELMANN (www.xliners.org) Webmaster Server Admin E-Mail: [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Replaced sendmail with qmail - kaaputz
In mm_cfg.py you may find that the delivery defaults need to be changed. In particular, DELIVERY_MODULE = 'SMTPDirect' should be used. Make this change after the form Defaults import * line. On Thursday, August 7, 2003, at 01:16 PM, Jaswinder S. Hayre wrote: Peter, It's a FreeBSD 4.8-RELEASE box. All the necessary five processes are running for qmail: qmail-send, splogger, qmail-lspawn, qmail-rspawn, qmail-clean. The aliases are setup correctly, as follows: |preline /home/mailman/mail/wrapper post test in .qmail-test Yeha, I always see the mail in the admin page, but after I approve it, it doesn't go anywhere. And for some reason log/bounces notes all the members as bouncing, don't know why. I don't ever see any attempts to actually deliver the message in maillog. It has this kind of message Aug 07 11:57:20 2003 (16657) Test: [EMAIL PROTECTED] - 3 more allowed over 431385 secs for all the members of the test list. And the log/post always has Aug 07 11:57:20 2003 (16657) post to test from [EMAIL PROTECTED], size=141, 3 failures, notice the failures at the end. It always fails. I have not a single clue about whats going on. I tried about 10 reinstalls. I disabled sendmail totally. What changes do I need to make to Mailman when I change an MTA? I didn't make any changes to mailman. Maillog shows messages coming into the list server, but never shows any messages going out after I have approved them from the admin interface. Jas This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/ ptatters%40zerobyzero.ca -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Message Sizes
I'm sure this question has been asked before, but I couldn't find it in the FAQ. I kind of need to find an answer quickly, as we are setting up our list to take over for a previous one. I put in a help ticket to my web host, but they directed me here. If it's a bug. I'll be sure and pass the info along. Version 2.1.2 We are running a moderated list, so every message is set to be held for review. I set the Maximum length for a messge at 8KB (we tried varying it, all with eth same results). Normally, I'd expect (and it has worked in an earlier software version) it to flag the message for approval, and have a message too big rejection note waiting for me. Instead, the message is sitting in the approval queue with the standard unappropriate content note. We thought that it may be like the HTML notes - if a note with HTML (such as from AOL) gets approved, it goes to the list nice and pretty with no secondary HTML-markup-gobbledygook. So, we tried approving it. Nope, the oversize message gets pushed out. Is it because we have the list set to hold every message (meaning that the Moderators will now have to be sure to review message size, as well as content), or is there a problem? Can it be fixed, or do I need to delete then re-install my list? Thanks for any insight you can offer, Tex -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] mailman not sending [remote host address is thelocal host]
I am trying to set up mailman on through a virtual domain. I have the everything working except that no mail is going out. I set masquerading with: MASQUERADE_AS(`neighborsunited.org')dnl FEATURE(masquerade_envelope)dnl in sendmail. I have looked through the faq and all of the obvious stuff is working (alaises, qrunner, etc...) I am getting a repeated error message in /var/log/exim/mainlog that reads: 2003-08-06 10:48:31 H=localhost.forestry.umn.edu (lorax.forestry.umn.edu) [::1] sender verify defer for [EMAIL PROTECTED]: remote host address is the local host Does anyone recognize this error Thanks Kirk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] qrunner with over 90% CPU
Paul, I have never seen this on a sendmail install. Maybe your problem is a different one. what version of python are your running, and what is the OS? From a command line type: python look at the first line printed: Python 2.2.2 Type a cntl-d to get out of python Jon Carnes On Sun, 2003-08-10 at 18:13, Paul H Byerly wrote: Richard Barrett wrote: Take a look at: http://www.mail-archive.com/[EMAIL PROTECTED]/msg17786.html Of course it's not just postfix, it bites me about once a week with sendmail. I watch it and kill the PID when it happens, but it's a PITA. Any chance of a patch? I know it's in the CVS, but I'm in over my head with that. Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] roster verification error
Hello! When I'm trying to access the user listing via the listinfo page, I enter the creator's (admin's) name and password, still it won't let me in? Should there be special access configs for that one? Mailman is v2.1.1 Anders Norrbring Norrbring Consulting -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] new to mailman
Hi, im new to this mail list and have a few questionsim currently working with a client who owns a night club, my host provides mailman...here is my question my client has a weekly mail that he sends to all the user who subscribe to the viplist (users email to [EMAIL PROTECTED] they get subscribed)this list has grown to 1000+, he is currently using yahoo mail to send the weekly email to all (using an adress book)yahoo only lets you send 100 each hour...and it always times out so this is what i need...and was wondering if with mailman i can achieve this need to be able to send a mail to 1000+ persons. i tried using mailman...and i c that if u send a mail to my list all the members get it, but also if a member writes to the list all the members also receive the message... i only wanna be the one that can send the messages...how do i go about doing this?? thanks! -Juan Luis Gonzalez -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Archive dating problem - mailman 2.1.2,regenerating archives from mbox
Hello, I'm having trouble getting the archives to show the correct dates in mailman version 2.1.2 (running on Red Hat Linux 7.3). I have some lists that I copied to my current server from a previous mail host (which was running 2.0.x, but that should be irrelevant). I copied the archives and concatonated the mbox files of the new and old archives. I made sure to include a blank line between messages in the mbox files, as suggested in the FAQ, and the mbox file appears correct when viewed with mailx (the mail comamnd in Linux) and pine. However, when I regenerate the archives from the mbox file, by removing the old archive directory and running mailman/bin/arch , many of the messages are dated incorrectly. Some of the messages archive fine, but others are given the _current_ date and time, instead of the date on the message. This is very annoying as it means I have a huge number of messages in August 2003 which do not belong there, and the original date/time information is lost! When I look at the messages in question in the mbox file, they appear to be properly formatted with correct Date: and From headers. In previous versions of mailman, there was a configuration flag on whether to follow the date/time of the message Date: header, or the one from the mbox format From line. However, I can't seem to find this option in mailman 2.1.2. Has it been removed, and if so, why? Thanks for any ideas! --Jeremy -- /-\ | Jeremy Portzer [EMAIL PROTECTED] trilug.org/~jeremy | | GPG Fingerprint: 712D 77C7 AB2D 2130 989F E135 6F9F F7BC CC1A 7B92 | \-/ signature.asc Description: This is a digitally signed message part -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] using the web interface to confirm subscription
yours is the thread i saw :] the list name is rochester, so i'm not sure how that could be the problem... --david - Original Message - From: Sylvain Langlade [EMAIL PROTECTED] To: 'david l goodrich' [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Wednesday, August 13, 2003 10:38 AM Subject: RE: [Mailman-Users] using the web interface to confirm subscription I once had such problem with a list. You can search this list for more infos about this one (thread name was Mailman 2.1.1 crashing when approving a new member). It looks like a deep bug somewhere between Python and Mailman. In my case, I noticed that it happened only when the list name contains hyphens (-). Check if this is your case. Not using hyphens works great for me but it surely is somewhat annoying. HTH when users try the web interface to confirm their subscription to a mailman list (running mailman 2.1.1 on openbsd 3.3/i386-stable) they're presented with this error message. i've seen this error on the list before, but never a solution. help? -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Whoooi... :)
Make all members moderated and the uncheck the moderated flags on the members you want to be able to post. Brent. D. Brent Herring Computer Services University of Central Arkansas Anders Norrbring [EMAIL PROTECTED] 8/13/2003 10:21:50 AM So many obstacles.. But now I'm up and running! But.. Now to another thing, if I want a list to be 'read-only', that is so users can't post, just receive mail from the list? Only admin and moderators should be able to post to it. (It an info list). How do I set that up? It doesn't seem to be all logical to me and I can't find it in the doc files I have. Anders Norrbring Norrbring Consulting -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/brenth%40uca.edu -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] 'empty module name' error and shunting
I've seen a number of posts (courtesy of Google) about this topic, yet not a single one noted a solution. All either were resolved with, 1. upgrade and it will go away (I have the latest of everything) 2. this only happens on spam (bad header), don't worry about it. 3. you are using a RH RPM install that is broken. Well, in my case I'm on a debian system (code via apt-get) running mailman-2.1.2-6. I have about 12 mailing-lists all seem to function without an issue except for one. Anytime anyone mails to it, the message gets Shunned and I see this error in the log/error file (mind you the message is obsoletely fine - its as though there is lock someone that is forcing all legit messages to be shunned). Aug 13 16:40:05 2003 (13248) Uncaught runner exception: Empty module name Aug 13 16:40:05 2003 (13248) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 105, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipel ine sys.modules[modname].process(mlist, msg, msgdata) File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 89, in process send_digests(mlist, mboxfp) File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 130, in send_digest s send_i18n_digests(mlist, mboxfp) File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 303, in send_i18n_d igests msg = scrubber(mlist, msg) File /var/lib/mailman/Mailman/Handlers/Scrubber.py, line 308, in process t = t.encode(charset, 'replace') File /usr/lib/python2.2/encodings/__init__.py, line 51, in search_function mod = __import__(modname,globals(),locals(),'*') ValueError: Empty module name Aug 13 16:40:05 2003 (13248) SHUNTING: 1060794892.466989+1b026fcd575182e5c957eae f9f3caac319c9a8e3 If I try to 'unshunt' the message - nothing happens and it simply pops back into the qfiles/shunt dir. I have hoards of people waiting for this to get resolved and I've tried asking anyone who would listen on IRC (irc.freenode.net #mailman and/or #debian) to no avail. The website was no help at all (there is no mention of 'shunting' even and alot of the info is rather dated). Could someone please lend a helping hand _ASAP_ ? I'm not on the list, so please CC your replies. Regards, - Nadim __ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Whoooi... :)
On Wed, 2003-08-13 at 11:21, Anders Norrbring wrote: So many obstacles.. But now I'm up and running! But.. Now to another thing, if I want a list to be 'read-only', that is so users can't post, just receive mail from the list? Only admin and moderators should be able to post to it. (It an info list). How do I set that up? It doesn't seem to be all logical to me and I can't find it in the doc files I have. Anders Norrbring Norrbring Consulting Take a look at the FAQ. There is one written about just how to setup an announce only list. Basically you go to the membership section of the Web-admin and set all the users Modify bit to on, then you go to selected users (like your admins) and turn their modify bit off - or leave them all on and force the admins to approve any and all messages (so that the messages can't be spoofed by someone). Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py HtH - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] using the web interface to confirm subscription
when users try the web interface to confirm their subscription to a mailman list (running mailman 2.1.1 on openbsd 3.3/i386-stable) they're presented with this error message. i've seen this error on the list before, but never a solution. help? --david - Original Message - From: Joe Trebinde To: david l goodrich Sent: Wednesday, August 13, 2003 9:38 AM Subject: Error Bug in Mailman version 2.1.1 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File /usr/local/lib/mailman/scripts/driver, line 222, in ? run_main() File /usr/local/lib/mailman/scripts/driver, line 96, in run_main print_traceback(logger) File /usr/local/lib/mailman/scripts/driver, line 119, in print_traceback print logfp, '' File /usr/ports/mail/mailman/w-mailman-2.1.1/fake-i386/usr/local/lib/mailman/Mai lman/Logging/StampedLogger.py, line 73, in write File /usr/ports/mail/mailman/w-mailman-2.1.1/fake-i386/usr/local/lib/mailman/Mai lman/Logging/Logger.py, line 88, in write SystemError: can't resize shared unicode objects Python information: VariableValue sys.version2.2.1 (#1, Mar 19 2003, 15:02:42) [GCC 2.95.3 20010125 (prerelease, propolice)] sys.executable/usr/local/bin/python2.2 sys.prefix/usr/local sys.exec_prefix/usr/local sys.path/usr/local sys.platformopenbsd3 Environment variables: VariableValue HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, application/vnd.ms-excel, application/msword, application/vnd.ms-powerpoint, */* CONTENT_TYPE application/x-www-form-urlencoded HTTP_REFERER http://mail.dorkzilla.org/mailman/confirm/rochester/09ddf19d2dc7e409f704a061c110c7cc8bbf6a46 SERVER_SOFTWARE Apache/1.3.27 (Unix) PHP/4.2.3 mod_ssl/2.8.12 OpenSSL/0.9.7-beta3 PYTHONPATH /usr/local/lib/mailman SCRIPT_FILENAME /usr/local/lib/mailman/cgi-bin/confirm SERVER_ADMIN [EMAIL PROTECTED] SCRIPT_NAME /mailman/confirm SERVER_SIGNATURE Apache/1.3.27 Server at mail.dorkzilla.org Port 80 REQUEST_METHOD POST HTTP_HOST mail.dorkzilla.org PATH_INFO /rochester SERVER_PROTOCOL HTTP/1.0 QUERY_STRING HTTP_CACHE_CONTROL no-cache, max-stale=0 REQUEST_URI /mailman/confirm/rochester CONTENT_LENGTH 133 HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) SERVER_NAME mail.dorkzilla.org REMOTE_ADDR 129.176.151.121 REMOTE_PORT 17651 HTTP_ACCEPT_LANGUAGE en-us HTTP_X_BLUECOAT_VIA 7DC4662F44BCF3E8 PATH_TRANSLATED /var/www/htdocs/rochester SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip, deflate SERVER_ADDR 209.234.76.77 DOCUMENT_ROOT /var/www/htdocs -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] using the web interface to confirm subscription
I once had such problem with a list. You can search this list for more infos about this one (thread name was Mailman 2.1.1 crashing when approving a new member). It looks like a deep bug somewhere between Python and Mailman. In my case, I noticed that it happened only when the list name contains hyphens (-). Check if this is your case. Not using hyphens works great for me but it surely is somewhat annoying. HTH when users try the web interface to confirm their subscription to a mailman list (running mailman 2.1.1 on openbsd 3.3/i386-stable) they're presented with this error message. i've seen this error on the list before, but never a solution. help? -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Removing list archives
Hello, I have decided to stop archiving the mails in one of my mailman lists, is there any problem removing using rm -r -f * in linux or there is a cleanner method to execute this task? Thanks in advance. -- Bruno António, Administração de Sistemas do Dep. de Informática da Fac. de Ciências da Universidade de Lisboa, Campo Grande Bloco C5 piso 1 sala 5.1.25B 1749-016 Lisboa - Portugal Tel: +351 217500513 Fax: +351 217500084 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Charset conversion
Hiho! Thanks for the patch, now everything works as I want it. Ciao, Schoeppi On Son, Aug 03, 2003 at 08:42:23 +0900, Tokio Kikuchi wrote: Hi, This patch should help. http://sourceforge.net/tracker/?func=detailaid=664209group_id=103atid=300103 Cheers, Tokio Christian Schoepplein wrote: Hello! I'm using mailman 2.1.2 that uses AFAIK email 2.5.1 for messageprocessing. However, I have a problem with some emails in mailmanlists :-(. If the listlanguage is set to German (iso-8859-1) and a message is posted with this characterset to a list, everything works fine. If the posters use another characterset I get multiparted messages..., messages with attachments. For example a poster uses 7bit us-ascii in its mailer, in my lists appears a message with tow parts: The text from the poster in us-ascii and the listsignature in iso-8859-1. Such a meeeage looks like this: - From [EMAIL PROTECTED] Sat Aug 2 15:49:00 2003 Return-Path: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: from toshiba.schoeppi (localhost [127.0.0.1]) by toshiba.schoeppi (Postfix) with ESMTP id 621DC1047B; Sat, 2 Aug 2003 15:48:58 +0200 (CEST) X-Original-To: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] Received: by toshiba.schoeppi (Postfix, from userid 503) id F247F109C0; Sat, 2 Aug 2003 15:48:56 +0200 (CEST) Date: Sat, 2 Aug 2003 15:48:56 +0200 From: Christian Schoepplein [EMAIL PROTECTED] To: [EMAIL PROTECTED] Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 User-Agent: Mutt/1.4i Subject: [Lh2] test X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.2 Precedence: list Reply-To: [EMAIL PROTECTED] List-Id: lh2.test.dom List-Unsubscribe: http://localhost/mailman/listinfo/lh2, mailto:[EMAIL PROTECTED] List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://localhost/mailman/listinfo/lh2, mailto:[EMAIL PROTECTED] Content-Type: multipart/mixed; boundary64836026195830321== Sender: [EMAIL PROTECTED] Errors-To: [EMAIL PROTECTED] [-- Anhang #1 --] [-- Typ: text/plain, Kodierung: 7bit, Größe: 0,1K --] Content-Type: text/plain; charset=us-ascii Content-Disposition: inline messagetext [-- Anhang #2 --] [-- Typ: text/plain, Kodierung: quoted-printable, Größe: 0,1K --] Content-Type: text/plain; charset=iso-8859-1 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline -- listfooter - -- Christian Schoepplein | Beste Rockband der Welt: http://www.lily-rockt.de [EMAIL PROTECTED] | Linux fuer Blinde: http://www.blinux.suse.de -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Length limit of list names
Begin forwarded message: From: Richard Barrett [EMAIL PROTECTED] Date: Thu Aug 7, 2003 5:45:27 pm Europe/London To: Chinn, Hindy [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Length limit of list names On Thursday, August 7, 2003, at 05:18 pm, Chinn, Hindy wrote: Thanx for your reply.. So why wouldn't these listnames work? Alumni-hbispring03 Alumnihbispr03 There is no reason why, with a standard MM installation, that these two mailing list names will not work. To try and confirm this I have just created and sent messages through two lists with these names on my test system. This server is running Suse Linux 7.3, Sendmail 8.11.6 and MM 2.1.2 When you say the list names did not work what do you mean. How does the 'not working-ness' manifest itself. The problem is probably not inherently a Mailman one but maybe your MTA is imposing restrictions of some sort. What type and version of OS. MTA and Mailman are your running? But this did... Alumhbis03 hindy -Original Message- From: Richard Barrett [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 12:15 PM To: Chinn, Hindy Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Length limit of list names On Thursday, August 7, 2003, at 04:33 pm, Chinn, Hindy wrote: What are the do's and don'ts of list names? Limit number of characters? Can there be spaces, dashes, underscores in name? I am not aware of any explicit length limits but I wouldn't write an essay in a list. Long list names can be inconvenient for users to type when posting etc Mail list names have to function as valid mail aliases, as a directory name and as part of file names in the server's file system so you have several constraints to consider. To complicate life, there is a set of mail aliases associated with any given list; for instance for the list called 'testlist' the menagerie is. testlist testlist-admin testlist-bounces testlist-confirm testlist-join testlist-leave testlist-owner testlist-request testlist-subscribe testlist-unsubscribe owner-testlist You want to avoid like the plague having a list whose base list name ends/begins with any of the suffices/prefixes. This will cause problems for instance if one list's -admin alias is another list's base name! Although mail aliases are notionally case sensitive, that way lies insanity, and few MTAs will distinguish mail aliases that are differentiated by case alone. Mailman treats all list names as case insensitive and the directory/file names associated with a list in the file system and in MM's web GUI interface URI's exclusively use the lower-case version version of the list name. Various characters other than a-zA-Z0-9 are entirely legal in mail aliases but will cause grief when used in file names. In some case they may also break code that decomposes mail aliases in a simple-minded, maybe even incompetent, way. There is little point in exploring the outer-reaches of such code's capability unless you are a masochist. I would suggest you stick to a-zA-Z0-9 and hyphen as characters in list names. Thanx hindy H I N D Y C H I N N Asst. Director of Information Technology Hillel: The Foundation for Jewish Campus Life phone: 202-449-6542 fax: 202-449-6442 -- - Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mm_cfg.py
On Tue, 2003-08-05 at 08:18, david.gordon wrote: I've just updated to MM 2.1.2. All now working as expected - thanks to those who helped! I'd like to add personalisation to the mail footer (as this list does). As I understand it I have to edit the mm_cfg.py file. Looking at it, it appears to be an old version from my MM 2.0.x perhaps. Anyway there's no lines about VERP_PERSONALIZED_DELIVERIES = 1 which I expected. I think the mm.cfg.py is not updated - correct? Whatever, do I have a correct version to replace the old one with? What should I be doing? I assume when I find these lines and enable them I'll see a change in the web interface? Thanks You'll find examples of all those settings in Defaults.py (which gets updated when you upgrade). Feel free to copy any sections from that file into your mm_cfg.py file. For a painless, step-by-step, approach to adding VERP to your lists, look in the FAQ. There are a couple of nice write-ups there. http://www.python.org/cgi-bin/faqw-mm.py Good luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Too many HOPS update
It appears to be doing this on ALL e-mail's where I have sent an invitation to someone to join. They get the invitation and it is the reply that has problems.. it keeps repeating until it gets the too many hops message.. Thanks, Daniel A. Creed -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman + htDig
Assuming you are using en as the list language and standard templates, can you take a look at the file $prefix/templates/en/archtoc.html line 16 should read: %(htsearch)s Yup.. it is there.. This is where the results of the quick_maketext() on TOC_htsearch.html, that is the search form, get inserted into the list TOC page. This line should have been inserted into archtoc.html by the htdig-2.1.2-0.4.patch One possibility is that you may be using site, host or list specific templates and you generated these from the standard installed templates before applying the mailman-htdig and kindred patches. If so then these will not have been/could not be patched by the htdig-2.1.2-0.4.patch. In this case you will have to take a look at the htdig-2.1.2-0.4.patch file for the template changes made by the patch and apply these by hand to your local variants of the templates. The patch file is a unified diff format and quite human legible. Wait a sec... if I am reading that correctly, then existing lists would have been created using the standard templates which did not, obviously, have the htdig patch. Newly created lists would be created against the now-patched htdig templates, and they should work properly. Existing lists would have to have their templates patched accordingly. Is that right? If so, then it is likely that my installation IS working as expected. I will have to delete my test list and recreate it, then run some tests and observe the results. I'll let you know if I have any troubles there. Thanks for your help!! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] changed domains, need to change list url
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kirk R. Wythers wrote: Here is my mm_cfg (do I have to add the virtual host line?): Yes. Here's the comments from Defaults.py: # Mailman needs to know about (at least) two fully-qualified domain # names (fqdn); 1) the hostname used in your urls, and 2) the hostname # used in email addresses for your domain. For example, if people visit # your Mailman system with http://www.dom.ain/mailman; then your url # fqdn is www.dom.ain, and if people send mail to your system via # [EMAIL PROTECTED] then your email fqdn is dom.ain. # DEFAULT_URL_HOST controls the former, and DEFAULT_EMAIL_HOST controls # the latter. Mailman also needs to know how to map from one to the # other (this is especially important if you're running with virtual # domains). You use add_virtualhost(urlfqdn, emailfqdn) to add new # mappings. # # If you don't need to change DEFAULT_EMAIL_HOST and DEFAULT_URL_HOST in # your mm_cfg.py, then you're done; the default mapping is added # automatically. If however you change either variable in your # mm_cfg.py, then be sure to also include the following: # # add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) # # because otherwise the default mappings won't be correct. DEFAULT_EMAIL_HOST = 'localhost.localdomain' DEFAULT_URL_HOST = 'localhost.localdomain' DEFAULT_URL_PATTERN = 'http://%s/mailman/' - -- Todd OpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp So live that you can look any man in the eye and tell him to go to hell. -- Anonymous -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3rc2 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE/L+dCuv+09NZUB1oRAnjJAJ0Zil3sXvBPqNR/qBgvlopNFTfB2ACgjP8R smiEJ2C0xMI0iSZaiIHClMM= =C3cL -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] IP's instead of FQDN
Actually I did look those over, but someone on another list (before joining this one) told me I didn't need to do all that. Obviously they were mistaken. I looked it over again and not being a sendmail expert I'm uncomfortable with the changes since this is my main mail server running MailScanner, etc. So I'm going to try putting it on another machine. Let me ask you this, more of a sendmail question. If I install Mailman on another machine, could I have it use the same domain, and have my main Sendmail server forward email for specific addresses, like lists, to this other mailman server? Would that work? The mailman server would be able to deliver directly. Also, if I do it on another machine, should I use something other than Sendmail? Are any of the others easier to integrate? From the files it looks like postfix. Thanks for your time. James On Thu, 2003-08-07 at 09:58, Richard Barrett wrote: I can only assume that you haven't read all of the notes in the INSTALL and README.SENDMAIL documentation files in the Mailman build directory. If that is because you did not install from source then I suggest you download the MM source distribution from: http://sourceforge.net/project/showfiles.php?group_id=103 and unpack it to get at those two files. On Thursday, August 7, 2003, at 02:05 pm, James Pifer wrote: No I hadn't started that. Is that something I should add to rc.local so it starts every time the box is restarted? Covered in the INSTALL file Something is still screwed up in my Sendmail config. I tried to post a message to my new list and got the following: - The following addresses had permanent fatal errors - |/usr/local/mailman/mail/mailman post stoneware-users (reason: Service unavailable) (expanded from: [EMAIL PROTECTED]) - Transcript of session follows - smrsh: mailman not available for sendmail programs (stat failed) 554 5.0.0 Service unavailable Covered in the README.SENDMAIL file Thanks, James On Thu, 2003-08-07 at 02:45, Richard Barrett wrote: On Thursday, August 7, 2003, at 01:50 am, James Pifer wrote: Thanks, worked like a champ. Now my next problem after fixing that one. Looks like the messages are getting stuck in the virgin directory? Have you started Mailman's qrunner daemons by executing $prefix/bin/mailmanctl start? I'm using Sendmail and not sure I've done everything I need to do. I do have the aliases set up assuming I did it correctly. I have not search the archives on this one yet, but I will. Thanks for the help. James On Wed, 2003-08-06 at 14:56, Richard Barrett wrote: See: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp and in particular the comment under the heading 'Existing versus new lists' On Wednesday, August 6, 2003, at 07:42 pm, James Pifer wrote: I'm new to mailman and have everything setup except for one problem. I've tried searching the archives but didn't find my resolution. I have it installed (version 2.1.2) and created a list. It seems fine except that some of the links in the forms are not using my domain settings, rather that have an IP address in the URL like, 192.168.1.99. For example, when you try to subscribe the Subscribe button tries to post to the IP address rather than the domain. I've tried setting the defaults for HOST and URL in defaults.py, but still can't get it fixed. Can anyone tell me what I might be missing? Thanks, James -- - Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/ r.barrett%40openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] changed domains, need to change list url
On Tue, 2003-08-05 at 16:40, Richard Barrett wrote: See the FAQ entry: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp Run fix_url after you have changed mm_cfg.py and do not foget to mailmanctl restart. I'm restarting mailmanctl and I it keeps setting the url to the uname of the machine. Here is the output form fix_url lorax[/usr/local/mailman/bin]$ ./withlist -l -r fix_url neighborsunited -v Importing fix_url... Running fix_url.fix_url()... Loading list neighborsunited (locked) Setting web_page_url to: http://lorax.forestry.umn.edu/mailman/ Setting host_name to: lorax.forestry.umn.edu Saving list Finalizing lorax[/usr/local/mailman/bin]$ Here is my mm_cfg (do I have to add the virtual host line?): ### # Here's where we get the distributed defaults. from Defaults import * ## # Put YOUR site-specific settings below this line. DEFAULT_HOST_NAME = 'neighborsunited.net' DEFAULT_URL = 'http://www.neighborsunited.net' MAILMAN_OWNER = '[EMAIL PROTECTED]' % DEFAULT_HOST_NAME On Tuesday, August 5, 2003, at 05:15 pm, Kirk R. Wythers wrote: -- Kirk R. Wythers Department of Forest Resources Tel: 612.625.2261 University of Minnesota Fax: 612.625.5211530 Cleveland Ave. N Email: [EMAIL PROTECTED]Saint Paul, MN 55108 USA -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Simple question about Protected groups
Hello, In Mialman 2.1.X there is an unsubscribe_policy setting on the Privacy Options page that might work: unsubscribe_policy (privacy): Is the list moderator's approval required for unsubscription requests? (No is recommended) When members want to leave a list, they will make an unsubscription request, either via the web or via email. Normally it is best for you to allow open unsubscriptions so that users can easily remove themselves from mailing lists (they get really upset if they can't get off lists!). For some lists though, you may want to impose moderator approval before an unsubscription request is processed. Examples of such lists include a corporate mailing list that all employees are required to be members of. n. On Thu, Aug 07, 2003 at 01:18:01PM +0200, Laureijs, Quinten wrote: Hi all, One of our customer's requirements is that the application is able to contain protected groups: groups (or lists) that contain users' mailaddresses from which they cannot unsubscribe. I have gone through the admin pages on a test-machine and the online FAQ's but so far I haven't seen anything that could comply to my customer's requirement. Did I miss something or is it just not possible? Thanks in advance, Quinten --- Unix Administrator NCR Nederland N.V. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/nate%40plsweb.com -- Nate Perry-Thistle Director of Technology Performance Learning Systemshttp://www.plsweb.com/ 530.265.9066 800.255.8412 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] how can I get a list of all members of my maillist
Folks, I using mailman 2.1.2. How can I get a list of all members of my maillist? I wnat to be able to cut and paste the list and put it in an email or another document. But I can only see it a few members at a time. Thanks, Ed Franckowiak [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] qrunner with over 90% CPU
On Saturday 09 August 2003 20:29, Jens Gutzeit wrote: Now I've seen that qrunner has a high CPU usage, I had restartet mailman but that doens't change anything. Hmm, sorry I hate answering my own mails ;) Richard Barret had pointed me at http://www.mail-archive.com/[EMAIL PROTECTED]/msg17786.html in private mail, that wasn't the problem, but after I had stopped mailman, restartet postfix and then started mailman again all is well. Seems like a problem with my system, sorry for bothering you with this. Jens -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users]HandlerAPE error: WAS :Listserv wide announcements?
Richard--- You're right, thanks. I have a number of files from the old install: Apr 16 2002 /usr/local/mailman/Mailman/Handlers/HandlerAPI.py Dec 20 2002 /usr/local/mailman/ bin/digest_arch Dec 20 2002 /usr/local/mailman/ bin/move_list a bunch of cgi's, Apr 16 2002 ../cron/qrunner I removed HandlerAPI.py, renamed cron/qrunnerBU (with current date) to qrunner. Gave it 755 perms. This has not seemed to have calmed things down. If I wanted to do a clean install --start from scratch-- what directories in /usr/local/mailman/ should I keep? Thanks a lot for your help. Bruce On Tuesday, August 12, 2003, at 07:23 pm, Bruce Mitzit wrote: At 3:33 PM +0100 8/12/03, Richard Barrett wrote: On Tuesday, August 12, 2003, at 03:10 pm, Bruce Mitzit wrote: Hello, MM users--- After upgrading from mailman 2.0.9 to mailman-2.1.2, and tweaking all the things I could find to tweak, I still get this error emailed to me at the rate of about three a minute: Your cron job on urserver.uchicago.edu /usr/local/bin/python -S /usr/local/mailman/cron/qrunner produced the following output: Traceback (most recent call last): File /usr/local/mailman/cron/qrunner, line 89, in ? from Mailman.Handlers import HandlerAPI File /usr/local/mailman/Mailman/Handlers/HandlerAPI.py, line 26, in ? from Mailman.pythonlib.StringIO import StringIO ImportError: No module named pythonlib.StringIO Well some of your old MM installation is executing to generate these warnings. The traceback is from MM 2.0.x code as the Mailman/Handlers/HandlerAPI.py file is not in the MM 2.1.2 distribution; well its in MM 2.0.13 but not in MM 2.1.2 on my test system. With Mailman 2.1.2 the qrunner is no longer run as a cron job. The 2.1.2 qrunners are run as daemons started by the $prefix/bin/mailmanctl script. Looks like, maybe, you did not remove the mailman user's crontab before doing the update and the old 2.0.9 crontab is still trying to do stuff. Did you take a look at the section 'UPGRADING FROM 2.0.x to 2.1' in the UPGRADING file in your MM 2.1.2 build director as part of your tweakingy? Richard et. al.-- Well, yeah, I did read that thing. I did not remove (in Solaris 7) /var/spool/cron/cronjobs/mailman prior to the install. So, I've rm'd that cronjob. We'd been running that cron from root anyway, so I commented all out from there as well. I did a configure, make install all over again. I still am getting the same error message by email. Any suggestions? The original install of MM made me feel pretty smart. This one makes me feel dumb. If messages reporting the same error are still turning up then either the mail system has a backlog it is drip feeding you or there is still another crontab which executes the old MM qrunner script in place and enough old MM code extant to generate the error. Bruce --- Richard Barrett http://www.openinfo.co.uk -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mm_cfg.py
On Tuesday, August 5, 2003, at 01:18 pm, david.gordon wrote: I've just updated to MM 2.1.2. All now working as expected - thanks to those who helped! I'd like to add personalisation to the mail footer (as this list does). As I understand it I have to edit the mm_cfg.py file. Looking at it, it appears to be an old version from my MM 2.0.x perhaps. That is to be exepected as the site specific changes you make to Mailman's configuration in mm_cfg.py are not changed by upgrades; be thankful for that. Anyway there's no lines about VERP_PERSONALIZED_DELIVERIES = 1 which I expected. MM has always defined the default configuration in Defaults.py. You change the defaults to suit your site requirements by by copying the definitions you want to change from Defaults.py and inserting them into mm_cfg.py and editing them there. Those (the majority?) defaults that are OK do not need to be added to mm_cfg.py I think the mm.cfg.py is not updated - correct? Whatever, do I have a correct version to replace the old one with? What should I be doing? I assume when I find these lines and enable them I'll see a change in the web interface? And you should also run mailmanctl restart to get the daemons to recognise the changes. btw: If you had an operational MM 2.0.13 configuration and you had defined DEFAULT_HOST_NAME and DEFAULT_URL in mm_cfg.py you might want to read the comments about them in Defaults.py Thanks -- david.gordon -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Howto on front ending exchange ?
On Mon, 2003-08-11 at 15:10, Michael H Moran wrote: Anyone written or know of a HowTo on frontending exchange servers ? Thanks in advance Mike I've done it plenty of times with mailman (and spamassassin, and even clam). This is not a big deal but is easier if your Exchange server is internal and your using a Unix-like server for the external mail exchange. If you look at the SpamAssassin site, there used to be a nice article that talks about three different configurations for using SA with Exchange. The setup would be very similar to using mailman. If you want more specific advice, then please provide more specific information regarding your setup. Good luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] v2.1.1 and Archive download problem
We are using version 2.1.1 and when someone clicks on the download the full raw archive on the archives page, the archive is not downloaded under IE. It downloads okay using Netscape or Opera. I've tried downloading this list's archives and it works fine. Therefore I'm thinking this is either a configuration problem or an upgrade problem. Has anyone experienced this? Got a fix? Ken -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Edit rejection notice text
Todd, As far as I can tell, it is hard coded into mailman-dir/Mailman/Handlers/Moderate.py So you would have to edit that file directly. Todd Felmly wrote: Is there a way to edit the text contained in _non-member_ rejection notices? I.e., if a non-member posts to a list and the Action to take for postings from non-members for which no explicit action is defined setting is set for reject, this is what the user gets: You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at [EMAIL PROTECTED] Where is this template at? I've searched through the archives/en directory and can't find it. -- John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Public/private archives problem.
On Monday, August 11, 2003, at 10:31 am, Tony wrote:
Hi Tokio,
I checked out Rob's bug report and he says that he tried fix_url, but
it only
worked for private archives, not for the public ones :(
Rob's bug report, as with yours, lack precision in specifying exactly
which Mailman generated pages have links on them which contain (in the
HTML text), absolute URLs referring to the wrong hostname. See my
comments below on the broadfer questions that need to be answered in
order to attack the perceived problem.
Thanks for the suggestion though.
Tony
Quoting Tokio Kikuchi [EMAIL PROTECTED]:
Hi,
You should state your urlhost/emailhost pairs in mm_cfg.py like;
add_virtualhost('www.virtual.dom', 'mail.virtual.dom')
then use fix_url.py.
Rob Brandt wrote:
I recently submitted a bug report on that:
https://sourceforge.net/tracker/?
func=detailaid=784888group_id=103atid=100103
No response yet.
Rob
Quoting [EMAIL PROTECTED]:
Hi,
I hope someone can help me with this:
I am a web space reseller on a shared server.
One of the features we get is mailman, which we offer to our
clients.
One thing I have noticed about it is that if a mailing list has a
has a
private archive, the address is
http://clientdomain.com/mailman/private/listname, which is fine,
but if
the archive is public, then the address is
http://myhostingprovidersservername.com/pipermail/listname - which
is
not fine :(
The cause of this is likely to be in the configuration of the Apache
server servicing the virtual hosts concerned rather than it being a
Mailman problem per se.
I'm assuming that named virtual hosting is being used by the Apache
server concerned so that clientdomain.com and
myhostingprovidersservername.com resolve to the same IP number.
Unless the Apache server has some special provisions made in its
configuration/operation the pipermail archives, which are served as
regular web pages by Apache without the intervention of Mailman
specific CGI programs, will be equally visible through any of the
hostnames that resolve to the same IP that
myhostingprovidersservername.com resolves to. If this is the case then
any of the public lists is potentially visible through any of the named
virtual hosts supported by Apache on the same IP number.
I do not work with it myself, but I believe that the CPanel virtual
hosting support software, which your hosting provider may be using,
does perform some trickery to help avoid conflicts between list names
on different virtual hosts. If your hosting provider is using that and
something related to it is misconfigured then this may be contributing
to the problem.
When you say if the archive is public, then the address is
http://myhostingprovidersservername.com/pipermail/listname; what
precisely do you mean?
Do the links to list archives for a given virtual host on the
/mailman/listinfo and /mailman/admin and other /mailman/somtehing CGI
generated pages for that host have URL's that refer to the
myhostingprovidersservername.com rather than clientdomain.com host?
Or are there links on other pages on the server that have the
'defective' domain in their URLs?
If you look at the source of MM's pipermail archive pages you will find
that for the most part the generated links on those pages are server
relative, the main exception being (with MM2.1.2) to extracted
attachment files. So once started on a link specifying the 'wrong'
hostname, links on pages then reached also appear to be 'wrong'.
To get much further with diagnosing the problem will need a bit more
input from you.
This means that my clients can see the domain name of the underlying
provider I am buying space off, and potentially they might jump
ship.
Is this something that can be fixed by me/the hosting provider, and
if
so, how?
Many thanks,
Tony
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/tony-mm%
40arielbusiness.com
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
r.barrett%40openinfo.co.uk
--
Mailman-Users mailing list
[EMAIL PROTECTED]
Re: [Mailman-Users] Public/private archives problem.
Hi Richard, Quoting Richard Barrett [EMAIL PROTECTED]: Rob's bug report, as with yours, lack precision in specifying exactly which Mailman generated pages have links on them which contain (in the HTML text), absolute URLs referring to the wrong hostname. See my comments below on the broadfer questions that need to be answered in order to attack the perceived problem. Sorry, I thought it was clear enough. I will elaborate. I do not work with it myself, but I believe that the CPanel virtual hosting support software, which your hosting provider may be using, does perform some trickery to help avoid conflicts between list names on different virtual hosts. If your hosting provider is using that and something related to it is misconfigured then this may be contributing to the problem. Correct. The list directory gets names listname_domain to avoid conflicts with any other similarly named lists. CPanel is what is being used in this case. This means that any other virtual host on the server can access the mail archives by providing the correct path name to the list. When you say if the archive is public, then the address is http://myhostingprovidersservername.com/pipermail/listname; what precisely do you mean? What I mean is that the link to the archives, and only this link, from what I can see, shows the hosting provider's server name and not the virtual domain for the client. Example: I have a list called test on clientdomain1. The path to the list and all the admin pages etc is http://clientdomain1/mailman/whatever/test_clientdomain1/ This list could also be accessed by another virtual domain on the same server as: http://clientdomain2/mailman/whatever/test_clientdomain1/ When the archives are set to public, the archive address is: http://clientdomain1/mailman/private/test_clientdomain1/ When the list archives are set to public, then the archive address is: http://hostingproviderservername/pipermail/test_clientdomain1/ I would expect this to read: http://clientdomain1/pipermail/test_clientdomain1/ or similar. This appears the same on both the main page for the list and in the admin interface. Or are there links on other pages on the server that have the 'defective' domain in their URLs? No. To get much further with diagnosing the problem will need a bit more input from you. I hope I have provided enough info for you - if not, please tell me what else you need to know. many thanks, Tony -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] IP's instead of FQDN
On Thursday, August 7, 2003, at 01:50 am, James Pifer wrote: Thanks, worked like a champ. Now my next problem after fixing that one. Looks like the messages are getting stuck in the virgin directory? Have you started Mailman's qrunner daemons by executing $prefix/bin/mailmanctl start? I'm using Sendmail and not sure I've done everything I need to do. I do have the aliases set up assuming I did it correctly. I have not search the archives on this one yet, but I will. Thanks for the help. James On Wed, 2003-08-06 at 14:56, Richard Barrett wrote: See: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp and in particular the comment under the heading 'Existing versus new lists' On Wednesday, August 6, 2003, at 07:42 pm, James Pifer wrote: I'm new to mailman and have everything setup except for one problem. I've tried searching the archives but didn't find my resolution. I have it installed (version 2.1.2) and created a list. It seems fine except that some of the links in the forms are not using my domain settings, rather that have an IP address in the URL like, 192.168.1.99. For example, when you try to subscribe the Subscribe button tries to post to the IP address rather than the domain. I've tried setting the defaults for HOST and URL in defaults.py, but still can't get it fixed. Can anyone tell me what I might be missing? Thanks, James --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] SPAM getting through on moderated lists
Hi, SPAM email where the from address appears as the list itself is bypassing the list rules for posting and is automatically accepted. Is this a mailman feature? Does it always approve mail coming from itself? Should it? How can I stop it without turning emergency moderation on (not sure if this will stop them or not)? Thanks, Nuno -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] running nimda test
i didnt know if there was a way to test mailman to detect the nimda virus...since there was a tests folder... ive been trying to google for information but i havent come across anything really about testing... ...so if there isnt anyway to test it... what do you mean by excercising the email parser package's MIME handling code.is there anything to worry about and nothing to test reallyand are the tests for developing purposes only? -chris Ben Gertzfield wrote: chris weisiger wrote: i noticed the nimda test virus in the Mailman tar.gz file how do i test Mailman using the nimda test file? That file is actually only in the Mailman source code as a way to exercise the email parser package's MIME handling code; Nimda virus emails have particularly bad MIME parts, so we wanted to make sure Mailman's email parser didn't choke on them. There's no way to test Mailman using that file -- it doesn't even contain the whole virus, just part of an infected message. What exactly did you want to test? Ben -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Prevent bounce back messages to moderators?
We have an administrative type list with all employees as members. Only a small subset of members should be able to post messages. I created the list and made those members moderators. Now these moderators are not list admins, just the ones who can post. Whenever there is a bounce back message the moderators receive these notices as well as me. I would like for this to not happen but cannot figure out how to prevent the moderators from receiving the notices and still be the only ones who can post to the list. Any advise? D. Brent Herring Computer Services University of Central Arkansas -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] FW: I can't get my mail list to work
I forgot to mention in my previous message, I get the error message below when I try to send mail to the mailing list. [EMAIL PROTECTED] unknown local-part test_hcmcnurses.org in domain synedyne.appliednetworkservices.net -Original Message- From: Rick Cheney [mailto:[EMAIL PROTECTED] Sent: Sunday, August 10, 2003 9:36 AM To: [EMAIL PROTECTED] Subject: I can't get my mail list to work Hello, I have a mailing list at www.hcmcnurses.org we are a non-profit association and our web host, webmanix.com, is not very helpful. We cannot the mailing list to work. The mailing list [EMAIL PROTECTED] does not work. When I create a mailing list I get the text below. I didn't find an option on the Control Panel for editing the etc/aliases or running 'newalises'. I tried making folders named etc/aliases and adding a text file named text.txt to that folder with the information below, but it did not work. --- Account Created The mailing list test on hcmcnurses.org with password test was sucessfully created. To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## test_hcmcnurses.org mailing list test_hcmcnurses.org: |/usr/local/cpanel/3rdparty/mailman/mail/mailman post test_hcmcnurses.org test_hcmcnurses.org-admin: |/usr/local/cpanel/3rdparty/mailman/mail/mailman admin test_hcmcnurses.org test_hcmcnurses.org-bounces: |/usr/local/cpanel/3rdparty/mailman/mail/mailman bounces test_hcmcnurses.org test_hcmcnurses.org-confirm: |/usr/local/cpanel/3rdparty/mailman/mail/mailman confirm test_hcmcnurses.org test_hcmcnurses.org-join: |/usr/local/cpanel/3rdparty/mailman/mail/mailman join test_hcmcnurses.org test_hcmcnurses.org-leave: |/usr/local/cpanel/3rdparty/mailman/mail/mailman leave test_hcmcnurses.org test_hcmcnurses.org-owner: |/usr/local/cpanel/3rdparty/mailman/mail/mailman owner test_hcmcnurses.org test_hcmcnurses.org-request: |/usr/local/cpanel/3rdparty/mailman/mail/mailman request test_hcmcnurses.org test_hcmcnurses.org-subscribe: |/usr/local/cpanel/3rdparty/mailman/mail/mailman subscribe test_hcmcnurses.org test_hcmcnurses.org-unsubscribe: |/usr/local/cpanel/3rdparty/mailman/mail/mailman unsubscribe test_hcmcnurses.org Hit enter to notify test_hcmcnurses.org owner... Updated List test hcmcnurses.org Thanks for your help, Rick Cheney 651-227-9166 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Length limit of list names
On Thursday, August 7, 2003, at 04:33 pm, Chinn, Hindy wrote: What are the do's and don'ts of list names? Limit number of characters? Can there be spaces, dashes, underscores in name? I am not aware of any explicit length limits but I wouldn't write an essay in a list. Long list names can be inconvenient for users to type when posting etc Mail list names have to function as valid mail aliases, as a directory name and as part of file names in the server's file system so you have several constraints to consider. To complicate life, there is a set of mail aliases associated with any given list; for instance for the list called 'testlist' the menagerie is. testlist testlist-admin testlist-bounces testlist-confirm testlist-join testlist-leave testlist-owner testlist-request testlist-subscribe testlist-unsubscribe owner-testlist You want to avoid like the plague having a list whose base list name ends/begins with any of the suffices/prefixes. This will cause problems for instance if one list's -admin alias is another list's base name! Although mail aliases are notionally case sensitive, that way lies insanity, and few MTAs will distinguish mail aliases that are differentiated by case alone. Mailman treats all list names as case insensitive and the directory/file names associated with a list in the file system and in MM's web GUI interface URI's exclusively use the lower-case version version of the list name. Various characters other than a-zA-Z0-9 are entirely legal in mail aliases but will cause grief when used in file names. In some case they may also break code that decomposes mail aliases in a simple-minded, maybe even incompetent, way. There is little point in exploring the outer-reaches of such code's capability unless you are a masochist. I would suggest you stick to a-zA-Z0-9 and hyphen as characters in list names. Thanx hindy H I N D Y C H I N N Asst. Director of Information Technology Hillel: The Foundation for Jewish Campus Life phone: 202-449-6542 fax: 202-449-6442 --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Keeping process count low
On Wednesday, August 6, 2003, at 04:54 am, Amardeo Sarma wrote: In the meanwhile, I am getting around 200 error messages a day complaining about cannot fork. I have tried various settings of SMTP_MAX_SESSIONS_PER_CONNECTION and MAX_DELIVERY_THREADS, but that does not seem to help. Does anyone know what the problem could be? This is not a problem I have had to deal with but I suspect that, as the problem arises when the MTA delivering to MM is trying to spawn a process to perform the delivery, that changing SMTP_MAX_SESSIONS_PER_CONNECTION and MAX_DELIVERY_THREADS will not help much. These MM config variables are concerned with limiting MM's use of resource when trying to pass outgoing messages to the outbound MTA (which may or may not be the same as the inbound MTA). Only indirectly will they impact on delivery to Mailman by the MTA. Mailman's delivery function is low cost and concerns itself solely with taking the message from the MTA and getting into the qfiles directory on disc. Once that is done, the heavy lifting of the mail list processing is done by the qrunner daemons. I suspect you need to provide some idea of what type of machine (CPU, clock rate, memory, disc etc) you are running, what OS and its version, what MTA and such to get some more intelligent feedback from the list than I can provide. Amardeo. --On Dienstag, 5. August 2003 19:52 +0200 Amardeo Sarma [EMAIL PROTECTED] wrote: Hi, since a larger number of lists are hosted on our server, I am running into a problem with the number of processes on the server, which is limited. Is it a way out to set some limit on: SMTP_MAX_SESSIONS_PER_CONNECTION or MAX_DELIVERY_THREADS Any other suggestions to keep the number of concurrent processes down, even if delivery takes a bit longer? Typical errors I get are: - The following addresses had permanent fatal errors - |/usr/local/mailman/mail/mailman bounces abc (reason: 2) (expanded from: [EMAIL PROTECTED]) - Transcript of session follows - Cannot fork: Resource temporarily unavailable 554 5.3.0 unknown mailer error 2 It seems to me that this indicates that the maximum number of allowed processes has been exceeded. Amardeo. -- Amardeo Sarma [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/ r.barrett%40openinfo.co.uk --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Importing subscribers
Hindy, You certainly can. Either via the web or via the command line. Mailman will accept various formats, too. I just use the format: Joe Smith [EMAIL PROTECTED] Which works fine via the web or the command line. Chinn, Hindy wrote: Can one subscribe a list of email addresses with their corresponding names (one email + name per line)? -- John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Too many hops
Ok folks, I am finally getting around to this. With certain addresses like this bounces one I consistently get too many hops messages in my error log and messages that never make it to certain people. especially AOL users.Any ideas what might be causing this? Thanks, Daniel A. Creed Aug 3 08:00:12 vader sendmail[18462]: h73C0ACD018462: from=[EMAIL PROTECTED], size=998, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=vader [127.0.0.1] Aug 3 08:00:14 vader sendmail[18464]: h73C0ACD018462: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:01, mailer=relay, pri=138585, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h73Bep88016479 Message accepted for delivery) Aug 3 08:00:12 vader sendmail[18462]: h73C0ACD018462: from=[EMAIL PROTECTED], size=998, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=vader [127.0.0.1] Aug 3 08:00:14 vader sendmail[18464]: h73C0ACD018462: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:01, mailer=relay, pri=138585, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h73Bep88016479 Message accepted for delivery) Aug 3 08:00:15 vader sendmail[18465]: h73C0ECD018465: from=[EMAIL PROTECTED], size=1434, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.southeast.rr.com [24.93.67.82] Aug 3 08:00:17 vader sendmail[18468]: h73C0HCD018468: from=[EMAIL PROTECTED], size=1896, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 3 08:00:16 vader sendmail[18467]: h73C0ECD018465: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=139021, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h73Bi7mn015408 Message accepted for delivery) Aug 3 08:00:18 vader sendmail[18470]: h73C0HCD018468: to=[EMAIL PROTECTED], delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=139483, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h73Beu88016493 Message accepted for delivery) Aug 3 08:00:19 vader sendmail[18471]: h73C0JCD018471: from=[EMAIL PROTECTED], size=2358, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.southeast.rr.com [24.93.67.82] Aug 3 08:00:21 vader sendmail[18473]: h73C0JCD018471: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:01, mailer=relay, pri=139945, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h73BiCmn015433 Message accepted for delivery) Aug 3 08:00:21 vader sendmail[18474]: h73C0LCD018474: from=[EMAIL PROTECTED], size=2820, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 3 08:00:23 vader sendmail[18477]: h73C0NCD018477: from=[EMAIL PROTECTED], size=3282, class=-60, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 3 08:20:54 vader sendmail[18611]: h73CKsCD018611: from=, size=13396, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.southeast.rr.com [24.93.67.82] Aug 3 08:20:56 vader sendmail[18613]: h73CKsCD018611: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:01, mailer=relay, pri=35739, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h73C4lmn026095 Message accepted for delivery) Aug 3 08:20:56 vader sendmail[18614]: h73CKuCD018614: from=, size=13862, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 3 08:20:58 vader sendmail[18614]: h73CKuCD018614: SYSERR(root): Too many hops 26 (25 max): from via ms-smtp-02.southeast.rr.com, to [EMAIL PROTECTED]ug 3 08:20:58 vader sendmail[18614]: h73CKuCD018614: SYSERR(root): Too many hops 26 (25 max): from via ms-smtp-02.southeast.rr.com, to [EMAIL PROTECTED] Aug 3 08:31:56 vader sendmail[18619]: h73CKuCD018614: SYSERR(root): Too many hops 26 (25 max): from via localhost, to [EMAIL PROTECTED] Aug 3 08:31:56 vader sendmail[18619]: h73CKuCD018614: h73CVtCE018619: postmaster notify: Too many hops 26 (25 max): from via localhost, to [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] too many hops specific example...
Aug 6 13:55:49 vader sendmail[28771]: h76HtlCD028769: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:01, mailer=relay, pri=138581, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76Ha888021010 Message accepted for delivery) Aug 6 13:56:33 vader sendmail[28773]: h76HuWCD028773: from=[EMAIL PROTECTED], size=1953, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.tampabay.rr.com [65.32.1.43] Aug 6 13:56:35 vader sendmail[28776]: h76HuYCD028776: from=[EMAIL PROTECTED], size=2416, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.southeast.rr.com [24.93.67.82] Aug 6 13:56:34 vader sendmail[28775]: h76HuWCD028773: to=[EMAIL PROTECTED], delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=30820, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76Har88021487 Message accepted for delivery) Aug 6 13:56:36 vader ipop3d[28779]: pop3 service init from 65.32.219.231 Aug 6 13:56:36 vader sendmail[28778]: h76HuYCD028776: to=[EMAIL PROTECTED], delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=31283, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76HeAmn027638 Message accepted for delivery) Aug 6 13:56:37 vader sendmail[28780]: h76HubCD028780: from=[EMAIL PROTECTED], size=2882, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 6 13:56:39 vader sendmail[28782]: h76HubCD028780: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=31749, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76HeDmn027669 Message accepted for delivery) Aug 6 13:56:40 vader sendmail[28783]: h76HudCD028783: from=[EMAIL PROTECTED], size=3348, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 6 13:56:42 vader sendmail[28786]: h76HufCD028786: from=[EMAIL PROTECTED], size=3814, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-03.southeast.rr.com [24.93.67.84] Aug 6 13:56:41 vader sendmail[28785]: h76HudCD028783: to=[EMAIL PROTECTED], delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=32215, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76Hfb3M019082 Message accepted for delivery) Aug 6 13:56:44 vader sendmail[28789]: h76HuhCD028789: from=[EMAIL PROTECTED], size=4280, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 6 13:56:43 vader sendmail[28788]: h76HufCD028786: to=[EMAIL PROTECTED], delay=00:00:01, xdelay=00:00:00, mailer=relay, pri=32681, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76HeHmn027741 Message accepted for delivery) Aug 6 13:56:46 vader sendmail[28792]: h76HujCD028792: from=[EMAIL PROTECTED], size=4746, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.southeast.rr.com [24.93.67.82] Aug 6 13:56:45 vader sendmail[28791]: h76HuhCD028789: to=[EMAIL PROTECTED], delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=33147, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76Hb488021612 Message accepted for delivery) Aug 6 13:56:47 vader sendmail[28795]: h76HulCD028795: from=[EMAIL PROTECTED], size=5212, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.southeast.rr.com [24.93.67.82] Aug 6 13:56:47 vader sendmail[28794]: h76HujCD028792: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:01, mailer=relay, pri=33613, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76Hb688021631 Message accepted for delivery) Aug 6 13:56:50 vader sendmail[28798]: h76HunCD028798: from=[EMAIL PROTECTED], size=5678, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-01.southeast.rr.com [24.93.67.82] Aug 6 13:56:49 vader sendmail[28797]: h76HulCD028795: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:01, mailer=relay, pri=34079, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76Hb888021676 Message accepted for delivery) Aug 6 13:56:51 vader sendmail[28800]: h76HunCD028798: to=[EMAIL PROTECTED], delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=34545, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76HePmn027828 Message accepted for delivery) Aug 6 13:56:52 vader sendmail[28801]: h76HupCD028801: from=[EMAIL PROTECTED], size=6144, class=0, nrcpts=1, msgid=[EMAIL PROTECTED], proto=ESMTP, daemon=MTA, relay=ms-smtp-02.southeast.rr.com [24.93.67.83] Aug 6 13:56:53 vader sendmail[28803]: h76HupCD028801: to=[EMAIL PROTECTED], delay=00:00:02, xdelay=00:00:00, mailer=relay, pri=35011, relay=smtp-server.carolina.rr.com. [24.93.67.141], dsn=2.0.0, stat=Sent (h76HeRmn027861 Message accepted for delivery) Aug 6 13:56:54 vader sendmail[28804]: h76HurCD028804:
Re: [Mailman-Users] Mailman + htDig
Can you confirm you mean that the per-list htdig directories of the
following form are being created:
$prefix/archives/private/listname/htdig are being created
and that inside each of them there is a file named listname.conf
Is there also a file called rundig_last_run and a bunch of ,db files
in any of these per list directories?
Yes, all of that did get created.
and if I manually perform a search (htsearch -c blah)
While htsearch is used for index searching, it is not called directly
from the form on the list TOC page with the integration but via the
$prefix/Mailman/Cgi/mmsearch.py script.
When you run htsearch -c are you specifying the configuration file
path as:
$prefix/archives/private/listname/htdig/listname.conf
Yes.
, I do get output and results.
How have the search indexes being used by htsearch when you run it by
hand been built? Did you run nightly_htdig by hand?
Yes.
What form do the URLs of search hits in the response returned by
htsearch take?
Well, they look like:
htsearch -c htdig/test.conf
Enter value for words: test
Content-type: text/html
Enter value for format:
!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.0 Transitional//EN
htmlheadtitleSearch results for 'test'/title/head
body bgcolor=#eef7ff
snip
hr noshade size=1
img src=/htdig/star.gif alt=*img src=/htdig/star.gif
alt=*img src=/htdig/star.gif alt=*img src=/htdig/star.gif
alt=* stronga
href=http://lists.wesmo.com/mailman/htdig/test/2003-August/29.html;[Test]
test /a/strongbr
snip
However, I am not getting the search form at the top of the
index.html page as is supposed to happen. So, as expected, I cannot
search via the web interface. :(
The trigger for this form to be added to a list's archive TOC page is
a new message being sent to that particular list. And until
nightly_htidg has been run (which can be done from the command lien
as well as by cron) no per-list search indexes will be in existence.
Are these criteria being met and yet still the form does not appear
on a list's archive TOC page?
Yes. I first added the following to my mm_cfg.py:
USE_HTDIG = 0# 0 - don't use integrated htdig, 1 - use it
HTDIG_FILES_URL = '/htdig/'
HTDIG_CONF_LINK_DIR = os.path.join(VAR_PREFIX, 'archives', 'htdig')
HTDIG_HTSEARCH_PATH = '/usr/bin/htsearch'
HTDIG_RUNDIG_PATH = '/usr/bin/rundig'
Then I changed USE_HTDIG to 1 and restarted the qrunner (just for the
sake of sanity. :). I then sent a message to the test list. At once I
got the message that was sent to the test list, I checked out the
archives/private/test directory and saw that the timestamp on index.html
was updated, that a directory called htdig was created, and there were a
bunch of files (db.*, rundig_last_run, and test.conf) in that htdig
directory.
Does line 757 (or thereabouts) of
$prefix/Mailman/Archiver/HyperArch.py contain the following text:
d[htsearch] = quick_maketext('TOC_htsearch.html', dict=h,
This is the code that generates the form that is added to the html of
the list's TOC page a few lines further on. If this line is missing
then the patching has failed somehow.
I just checked, and it is there. Is the TOC_htsearch.html file supposed
to be in a particular location? It is in templates/en/ right now...
I *believe* I followed the htdig docs to the letter,
Do you mean the INSTALL.htdig-mm document in the Mailman build
directory?
Yup.. that, and the docs on the website.
I swear it seems like I missed something simple (and stupid) here.. I
even confirmed that the permissions on the directory and all files were
set correctly (owner group, too!).
Thanks!
-Rich
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Archive Problem.
I recently edited my archives to remove an email, but when I re-arched them I got a bunch of screwy entries. ( http://www.bhsims.com/pipermail/caledonia/2003-July/date.html ) When I tried to edit the archives again there were a bunch of messages that were fragments of messages that existe in other month's archives looking something like .. From: bogus at does.not.exist.com () Date: Mon Apr 30 11:55:01 2001 Subject: No subject present and she suddenly became aware of a muffled rucus just beyond the transport's walls. If thats what she'd landed in. *Battle to end all battles..from those sounds and the way these troops look..* Her mind struggling to determine just where *here* was. Where ever it was, it certainly wasn't her family's villiage in Japan or their homestead. Removed all of those and re-arched. They didn't go away. So I ask.. Does anyone know what's causing this problem and more importantly how I fix it? It's only affecting my July archives, but it's still irritating! -Lorna Appleby --- Queen of the Insane Stuffies http://www.tuxandbunny.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Managing archives
-Original Message- From: Jon Carnes Sent: Tuesday, 12 August, 2003 10:55 Once the mbox is put back in place, you will need to run the ~mailman/bin/arch command to rebuild the archives using the new mbox file. Doing this will cause all or most of your archives to have new URLs, thus causing problems for any users who search/locate your archives via public search engines. What would be really nice is a way to delete messages (yes, even via Evolution) but not mess up the archive URLs. -Jim P. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] no mail... looks like an exim config problem
I need to configure exim for a virtual domain. The uname of my machine in lorax.forestry.umn.edu, the virtual domain that I want to run mailman to/from is neighborsunited.net. Here is the exim log error: 2003-08-06 12:14:53 remote host address is the local host: neighborsunited.net (while verifying [EMAIL PROTECTED] from host localhost.forestry.umn.edu (lorax.forestry.umn.edu) [::1]) If I add the domain neighborsunited.net as the primary hostname, will that take care of it? # primary_hostname = primary_hostname = neighborsunited.net or do I also need something here? domainlist local_domains = @ domainlist relay_to_domains = hostlist relay_from_hosts = localhost Lastly, how does one HUP exim? Thanks -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] changed domains, need to change list url
On Tuesday, August 5, 2003, at 06:06 pm, Kirk R. Wythers wrote: On Tue, 2003-08-05 at 16:40, Richard Barrett wrote: See the FAQ entry: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp Run fix_url after you have changed mm_cfg.py and do not foget to mailmanctl restart. I'm restarting mailmanctl and I it keeps setting the url to the uname of the machine. Here is the output form fix_url lorax[/usr/local/mailman/bin]$ ./withlist -l -r fix_url neighborsunited -v Importing fix_url... Running fix_url.fix_url()... Loading list neighborsunited (locked) Setting web_page_url to: http://lorax.forestry.umn.edu/mailman/ Setting host_name to: lorax.forestry.umn.edu Saving list Finalizing lorax[/usr/local/mailman/bin]$ Here is my mm_cfg (do I have to add the virtual host line?): ### # Here's where we get the distributed defaults. from Defaults import * ## # Put YOUR site-specific settings below this line. DEFAULT_HOST_NAME = 'neighborsunited.net' DEFAULT_URL = 'http://www.neighborsunited.net' MAILMAN_OWNER = '[EMAIL PROTECTED]' % DEFAULT_HOST_NAME I cited the FAQ entry in my initial response because it says the following at the top: quote Changing hostnames -- These changes should be made $prefix/Mailman/mm_cfg.py. The applicable MM config variables are described in $prefix/Mailman/Defaults.py. Typically something like what follows, at the end of your mm_cfg.py, will do the trick: DEFAULT_EMAIL_HOST = 'your.mailhostname.tld' DEFAULT_URL_HOST = 'your.webhostname.tld' VIRTUAL_HOSTS.clear() add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) and some more add_virtualhost(URL_FQDN, EMAIL_FQDN) if you are using virtual hosts. /quote I am at a loss to find any simpler way of expressing what needs to be done. If you do this then fix_url.py will probably work as planned! On Tuesday, August 5, 2003, at 05:15 pm, Kirk R. Wythers wrote: -- Kirk R. Wythers Department of Forest Resources Tel: 612.625.2261 University of Minnesota Fax: 612.625.5211530 Cleveland Ave. N Email: [EMAIL PROTECTED]Saint Paul, MN 55108 USA -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Python error message...
RB == Richard Barrett [EMAIL PROTECTED] writes: RB You may have jumped the gun here. On mailman-developers Barry Warsaw RB posted a response to the 2.3 upgrade question. See: RB http://mail.python.org/pipermail/mailman-developers/2003-July/ RB 015462.html I did the upgrade the other day. broke mailman all over the place since for some reason it had /usr/local/bin/python2.2 hard-coded into it. i just re-instaled mailman (actually took the opportunity to update from 2.1.1 to 2.1.2) and it works fine. MM caused python 2.3 to issue some feature going away and depricated warnings, but it still appears to work. -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D.Khera Communications, Inc. Internet: [EMAIL PROTECTED] Rockville, MD +1-240-453-8497 AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] IP's instead of FQDN
See: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp and in particular the comment under the heading 'Existing versus new lists' On Wednesday, August 6, 2003, at 07:42 pm, James Pifer wrote: I'm new to mailman and have everything setup except for one problem. I've tried searching the archives but didn't find my resolution. I have it installed (version 2.1.2) and created a list. It seems fine except that some of the links in the forms are not using my domain settings, rather that have an IP address in the URL like, 192.168.1.99. For example, when you try to subscribe the Subscribe button tries to post to the IP address rather than the domain. I've tried setting the defaults for HOST and URL in defaults.py, but still can't get it fixed. Can anyone tell me what I might be missing? Thanks, James --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman + htDig
On Saturday, August 9, 2003, at 04:06 pm, Rich West wrote: Ok.. I think I know what I did.. I didn't restart the qrunner. As I wrote the previous email to you, I realized that I had _thought_ about restarting the qrunner, but didn't. I went through the whole process again: o Edit mm_cfg.py to set USE_HTDIR=1 o python -c 'from compileall import *; compile_dir(prefix/Mailman,10,prefix/Mailman)' o /etc/init.d/mailmanctrl restart o bin/rmlist test o bin/newlist test o bin/arch test o Entered additional recipients via the web interface. o Sent a test message to the test list o /usr/bin/python -S prefix/cron/nightly_htdig -v test (it complained about not having the centralized db files, but that seemed ok) I think you can resolve this by reference to the section under the heading htdig Permissions Considerations in INSTALL.htdig-mm When rundig is being run by 'mailman' cron as the 'mailman' uid it probably does not have permissions to create the 'shared' htdig db's. My hack is to give the 'mailman' group group ownership and write permission over the the common and db subdirectories of the htdig install (/opt/www/htdig/ or wherever yout htdig is installed), and the files there contained. o Pointed my browser at the test archives, and viola! The search ability was there! And searching worked! I'm not sure if it was the fact that I recompiled the mm_cfg.py file or restarting the qrunner which started things working, though. Now, I just have to go through and migrate the existing lists. :) Hopefully, that won't be too difficult. :) Best of luck. Thanks for all of your help! No problem. Pleased you are up and running. -Rich Rich West wrote: Ok.. I blew away my test list, set USE_HTDIG=1, restarted the qrunner, created the list with newlist, ran blow_away_htdig test, ran arch test, and sent a message to the list. It seems likeit does everything BUT create update the index.html file with the search info.. Perhaps I should start over from scratch... -Rich Wait a sec... if I am reading that correctly, then existing lists would have been created using the standard templates which did not, obviously, have the htdig patch. Newly created lists would be created against the now-patched htdig templates, and they should work properly. Existing lists would have to have their templates patched accordingly. Is that right? If so, then it is likely that my installation IS working as expected. I will have to delete my test list and recreate it, then run some tests and observe the results. I'll let you know if I have any troubles there. Thanks for your help!! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Public/private archives problem.
Tony
The questions I am asking are to elicit information that will
distinguish between and identify whether there is a problem with (a)
Mailman or (b) misconfiguration of Mailman or (c) third party
modifications made to Mailman or (d) other aspects of the host system
configuration such as the Apache server.
You are complaining about links but I can interpret that in several
ways:
1. whether the URL of concern is accepted and served by the Apache
server when you think/prefer it should or should not be.
2. whether the URL of concern is found embedded in the HTML text of a
web page generated by Mailman as either a static page or by a Mailman
CGI script.
3. whether the URL of concern is found embedded in the HTML text of a
web page generated by something other than Mailman as either a static
page or as one delivered by a CGI script.
I must have been having a stupid day as I was not entirely clear from
either the referenced bug report or your initial post about which of
these interpretations I should adopt.
Now see further comments below.
Richard
On Monday, August 11, 2003, at 01:14 pm, Tony wrote:
Hi Richard,
Quoting Richard Barrett [EMAIL PROTECTED]:
Rob's bug report, as with yours, lack precision in specifying exactly
which Mailman generated pages have links on them which contain (in the
HTML text), absolute URLs referring to the wrong hostname. See my
comments below on the broadfer questions that need to be answered in
order to attack the perceived problem.
Sorry, I thought it was clear enough. I will elaborate.
I do not work with it myself, but I believe that the CPanel virtual
hosting support software, which your hosting provider may be using,
does perform some trickery to help avoid conflicts between list names
on different virtual hosts. If your hosting provider is using that and
something related to it is misconfigured then this may be contributing
to the problem.
Correct. The list directory gets names listname_domain to avoid
conflicts
with any other similarly named lists. CPanel is what is being used in
this
case.
This means that any other virtual host on the server can access the
mail
archives by providing the correct path name to the list.
When you say if the archive is public, then the address is
http://myhostingprovidersservername.com/pipermail/listname; what
precisely do you mean?
What I mean is that the link to the archives, and only this link, from
what I
can see, shows the hosting provider's server name and not the virtual
domain
for the client.
Example:
I have a list called test on clientdomain1.
The path to the list and all the admin pages etc is
http://clientdomain1/mailman/whatever/test_clientdomain1/
This list could also be accessed by another virtual domain on the same
server
as:
http://clientdomain2/mailman/whatever/test_clientdomain1/
When the archives are set to public, the archive address is:
http://clientdomain1/mailman/private/test_clientdomain1/
Did you mean the statement immediately above or are you just reflecting
on the fact that a public list is still available through its private
list URL?
When the list archives are set to public, then the archive address is:
http://hostingproviderservername/pipermail/test_clientdomain1/
I would expect this to read:
http://clientdomain1/pipermail/test_clientdomain1/
or similar.
This appears the same on both the main page for the list and in the
admin
interface.
Just to confirm; do you mean the web pages returned by the URLs
http://clientdomain1/mailman/listinfo/test_clientdomain1 and
http://clientdomain1/mailman/admin/test_clientdomain1?
I am now talking about plain vanilla, unmodified, MM 2.1.2 code. The
GetBaseArchiveURL() function used to generate the links to both public
and private list archives. Its operation is subtly different in two
cases although both depend upon the values in the VIRTUAL_HOSTS
dictionary which is conventionally constructed by calls to the
add_virtualhosts() function in the MM configuration file mm_cfg.py.
In the case of a public archive, the function does a lookup for the
list's host_name attribute (visible/editable on the General Options
page of the list) in an inversion of the VIRTUAL_HOSTS dictionary. The
actual statement that forms the URL is:
url = mm_cfg.PUBLIC_ARCHIVE_URL % {
'listname': self.internal_name(),
'hostname': inv.get(self.host_name, mm_cfg.DEFAULT_URL_HOST),
}
This works reliably on vanilla MM installation with a correctly set up
VIRTUAL_HOSTS dictionary, so long as each URL_FQDN key in the
dictionary is associated with a unique EMAIL_FQDN value.
If the list's host_name is not found then the DEFAULT_URL_HOST value,
which is likely to be that of your myhostingprovidersservername.com,
will be used.
I have no idea as to how CPanel integrates with Mailman or how the
mm_cfg.py Mailman configuration file is maintained as new domains are
hosted by a server on the system you are depending on.
My best guess
Re: [Mailman-Users]HandlerAPE error: WAS :Listserv wide announcements?
On Tuesday, August 12, 2003, at 10:35 pm, Bruce Mitzit wrote: Richard--- You're right, thanks. I have a number of files from the old install: Apr 16 2002 /usr/local/mailman/Mailman/Handlers/HandlerAPI.py Dec 20 2002 /usr/local/mailman/ bin/digest_arch Dec 20 2002 /usr/local/mailman/ bin/move_list a bunch of cgi's, Apr 16 2002 ../cron/qrunner I removed HandlerAPI.py, renamed cron/qrunnerBU (with current date) to qrunner. Gave it 755 perms. This has not seemed to have calmed things down. I know it is a bit obvious but you have used the crontab command to double check that the old Mailman crontab is still not extant and being executed on behalf of some user or another. If I wanted to do a clean install --start from scratch-- what directories in /usr/local/mailman/ should I keep? If it were me trying to do what you suggest, I would; 1. rename the current /usr/local/mailman and take a backup of it 2. mkdir /usr/local/mailman 3. use mv to put /usr/local/mailman.old/lists and /usr/local/mailman.old/archives to /usr/local/mailman 4. ./configure and make install MM 2.1.2 into /usr/local/mailman 5. crank up the new MM install per the INSTALL file Best of luck Thanks a lot for your help. Bruce On Tuesday, August 12, 2003, at 07:23 pm, Bruce Mitzit wrote: At 3:33 PM +0100 8/12/03, Richard Barrett wrote: On Tuesday, August 12, 2003, at 03:10 pm, Bruce Mitzit wrote: Hello, MM users--- After upgrading from mailman 2.0.9 to mailman-2.1.2, and tweaking all the things I could find to tweak, I still get this error emailed to me at the rate of about three a minute: Your cron job on urserver.uchicago.edu /usr/local/bin/python -S /usr/local/mailman/cron/qrunner produced the following output: Traceback (most recent call last): File /usr/local/mailman/cron/qrunner, line 89, in ? from Mailman.Handlers import HandlerAPI File /usr/local/mailman/Mailman/Handlers/HandlerAPI.py, line 26, in ? from Mailman.pythonlib.StringIO import StringIO ImportError: No module named pythonlib.StringIO Well some of your old MM installation is executing to generate these warnings. The traceback is from MM 2.0.x code as the Mailman/Handlers/HandlerAPI.py file is not in the MM 2.1.2 distribution; well its in MM 2.0.13 but not in MM 2.1.2 on my test system. With Mailman 2.1.2 the qrunner is no longer run as a cron job. The 2.1.2 qrunners are run as daemons started by the $prefix/bin/mailmanctl script. Looks like, maybe, you did not remove the mailman user's crontab before doing the update and the old 2.0.9 crontab is still trying to do stuff. Did you take a look at the section 'UPGRADING FROM 2.0.x to 2.1' in the UPGRADING file in your MM 2.1.2 build director as part of your tweakingy? Richard et. al.-- Well, yeah, I did read that thing. I did not remove (in Solaris 7) /var/spool/cron/cronjobs/mailman prior to the install. So, I've rm'd that cronjob. We'd been running that cron from root anyway, so I commented all out from there as well. I did a configure, make install all over again. I still am getting the same error message by email. Any suggestions? The original install of MM made me feel pretty smart. This one makes me feel dumb. If messages reporting the same error are still turning up then either the mail system has a backlog it is drip feeding you or there is still another crontab which executes the old MM qrunner script in place and enough old MM code extant to generate the error. Bruce --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] There are humans at excite.com!!
Hi all, It took four rounds of auto responders requesting headers to get a real person, but I now have word from excite.com that they no longer use the filter that identifies as spam mail with long words in the subject line. Excite Email Help wrote: We regret you have not received an adequate response to your previous emails. The filter you are speaking about is no longer in use by our company. You should not have any difficulty sending emails that you have described below. If you experience any difficulty, please send an email to [EMAIL PROTECTED] Regards, Excite Abuse Department Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] IP's instead of FQDN
I can only assume that you haven't read all of the notes in the INSTALL and README.SENDMAIL documentation files in the Mailman build directory. If that is because you did not install from source then I suggest you download the MM source distribution from: http://sourceforge.net/project/showfiles.php?group_id=103 and unpack it to get at those two files. On Thursday, August 7, 2003, at 02:05 pm, James Pifer wrote: No I hadn't started that. Is that something I should add to rc.local so it starts every time the box is restarted? Covered in the INSTALL file Something is still screwed up in my Sendmail config. I tried to post a message to my new list and got the following: - The following addresses had permanent fatal errors - |/usr/local/mailman/mail/mailman post stoneware-users (reason: Service unavailable) (expanded from: [EMAIL PROTECTED]) - Transcript of session follows - smrsh: mailman not available for sendmail programs (stat failed) 554 5.0.0 Service unavailable Covered in the README.SENDMAIL file Thanks, James On Thu, 2003-08-07 at 02:45, Richard Barrett wrote: On Thursday, August 7, 2003, at 01:50 am, James Pifer wrote: Thanks, worked like a champ. Now my next problem after fixing that one. Looks like the messages are getting stuck in the virgin directory? Have you started Mailman's qrunner daemons by executing $prefix/bin/mailmanctl start? I'm using Sendmail and not sure I've done everything I need to do. I do have the aliases set up assuming I did it correctly. I have not search the archives on this one yet, but I will. Thanks for the help. James On Wed, 2003-08-06 at 14:56, Richard Barrett wrote: See: http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.029.htp and in particular the comment under the heading 'Existing versus new lists' On Wednesday, August 6, 2003, at 07:42 pm, James Pifer wrote: I'm new to mailman and have everything setup except for one problem. I've tried searching the archives but didn't find my resolution. I have it installed (version 2.1.2) and created a list. It seems fine except that some of the links in the forms are not using my domain settings, rather that have an IP address in the URL like, 192.168.1.99. For example, when you try to subscribe the Subscribe button tries to post to the IP address rather than the domain. I've tried setting the defaults for HOST and URL in defaults.py, but still can't get it fixed. Can anyone tell me what I might be missing? Thanks, James -- - Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/ r.barrett%40openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] deleting a list.
Hello to All How can I delete a mailing list and how can I change the name of an exesting list? With Best Regards, Subhasis Mahapatra -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Simple question about Protected groups
Hi, After upgrading from 2.0.13 to 2.1.2, the unsubscribe_policy becomes available and the customer requirement was satisfied. Thanks for your reply. best regards, Q. --- Unix Administrator NCR Nederland N.V. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, August 07, 2003 21:57 To: Laureijs, Quinten Cc: '[EMAIL PROTECTED]' Subject: Re: [Mailman-Users] Simple question about Protected groups Hello, In Mialman 2.1.X there is an unsubscribe_policy setting on the Privacy Options page that might work: unsubscribe_policy (privacy): Is the list moderator's approval required for unsubscription requests? (No is recommended) When members want to leave a list, they will make an unsubscription request, either via the web or via email. Normally it is best for you to allow open unsubscriptions so that users can easily remove themselves from mailing lists (they get really upset if they can't get off lists!). For some lists though, you may want to impose moderator approval before an unsubscription request is processed. Examples of such lists include a corporate mailing list that all employees are required to be members of. n. On Thu, Aug 07, 2003 at 01:18:01PM +0200, Laureijs, Quinten wrote: Hi all, One of our customer's requirements is that the application is able to contain protected groups: groups (or lists) that contain users' mailaddresses from which they cannot unsubscribe. I have gone through the admin pages on a test-machine and the online FAQ's but so far I haven't seen anything that could comply to my customer's requirement. Did I miss something or is it just not possible? Thanks in advance, Quinten --- Unix Administrator NCR Nederland N.V. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users% 40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman -users/nate%40plsweb.com -- Nate Perry-Thistle Director of Technology Performance Learning Systemshttp://www.plsweb.com/ 530.265.9066 800.255.8412 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users% 40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/quinten.l aureijs%40ncr.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman for fan club
Amy, I seem to have forgotten what the menu options are in 2.0.X. First you have to concentrate on making every subscriber set to moderated - I know there is a flag for this in 2.0.X, but I forget what it is called. This is the most important part. You can then make yourself able to post in various ways - subscribe and turn off the moderation flag, or add yourself to the list of people who can post unmoderated (I seem to remember this was also in 2.0.X). The rest is to make it nicer and cleaner - but it probably depends on what your hosting company will do for you. My guess is you can't edit system files. Anyone else out there who has maybe an archive copy of the old FAQ answer for 2.0.X? Amy Rynne wrote: John, Thanks, I have already looked at that and I am using version 2.0.6 which comes with my hosting company. most of the setup in this article is in version 2.1. Will this work in 2.0.6? Is this the only reference? I'm having a tough time figuring this one out. -- John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] SPAM getting through on moderated lists
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Nuno == Nuno Serra
[Mailman-Users] SPAM getting through on moderated lists
Wed, 13 Aug 2003 22:16:20 +0200
Nuno Hi, SPAM email where the from address appears as the list
Nuno itself is bypassing the list rules for posting and is
Nuno automatically accepted.
Hmm That makes for IMHO an interesting question. Since many, if
not most MTAs can be configured to reject mail from specific envelope
senders, usually specified as regular expressions, the question is
what if any envelope senders related to mailman lists (and not
from our local {host,net}) can be rejected by an MTA that is
dedicated to handling incoming mail for only the lists.
It is advantageous to reject unwanted mail during the SMTP
conversation rather than later.
It should be pretty easy to cause a MTA reject all incoming mail from
non-local relays with any envelope sender address appearing among the
Mailman aliases.
Will this do no harm?
Nuno How can I stop it without turning emergency moderation on
Nuno (not sure if this will stop them or not)?
If the list shows up as a header sender, have you looked at Hold
posts with header value matching a specified regexp among the Privacy
Options?
jam
-BEGIN PGP SIGNATURE-
iD8DBQE/O5THUEvv1b/iXy8RAovtAJsE5lIDD2JUzv0B74+wcIHB+ycvzgCfSFGQ
NyUrZBRPx9VaBvKBHK2o3gg=
=QSMB
-END PGP SIGNATURE-
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] SPAM getting through on moderated lists
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ed == Ed Wilts Re: [Mailman-Users] SPAM getting through on moderated lists Thu, 14 Aug 2003 10:09:46 -0500 Ed What would one look like to allow, for example, a mail message Ed to [EMAIL PROTECTED] to only come from an MTA in the foo.com Ed domain? I don't do Sendmail anymore. One way to do this with a recent Postfix would be something like the following which is untested but should work for a dedicated MTA on the same host as Mailman. 1. Check that 'postconf mynetworks' gives 127.0.0.0/8 plus whatever IPs from which you do _not_ want to block SMTP 'mail from: [EMAIL PROTECTED]'. NB. If 'mynetworks' includes MX backup hosts mail arriving therefrom will not be blocked by what follows. 2. Cause something like the following to be run as root either whenever the Mailman aliases are modified or, less well, periodically by cron. This converts the Mailman aliases file, excluding the loop detection alias, into a Postfix access table. egrep -v '^$|^#|^mailman-loop'/var/lib/mailman/data/aliases| sed 's/^\([^:]*\):.*$/\1 550 Bogus Mail From/' /etc/postfix/check-list-bmf postmap /etc/postfix/check-list-bmf The above bash script assumes Mailman and Postfix installed from recent Debian packages. 3. In /etc/postfix/main.cf smtpd_recipient_restrictions = ... permit_mynetworks ... check_sender_access hash:/etc/postfix/check-list-bmf ... permit Something similar should be easy with Sendmail, right? :) It still needs to be determined whether the above will do no harm. HTH jam -BEGIN PGP SIGNATURE- iD8DBQE/O7oJUEvv1b/iXy8RAsAxAJ9hjo902Pqpq2d58gmmQuBswKMVfQCfWDG4 /xVkiW9Iifs1jaSjzE2nC7Y= =Z3mN -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] yet another undocumented, undiscussed bug
Let's see how this one works...the last time I had a problem I got no response to two separate posts. We had a server crash yesterday, and I brought the server back online. Since then, I have this problem when viewing the mailman web interface or trying to run check_dbs: Bug in Mailman version 2.1.2 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File /usr/local/mailman/scripts/driver, line 87, in run_main main() File /usr/local/mailman/Mailman/Cgi/listinfo.py, line 42, in main listinfo_overview() File /usr/local/mailman/Mailman/Cgi/listinfo.py, line 87, in listinfo_overview mlist = MailList.MailList(name, lock=0) File /usr/local/mailman/Mailman/MailList.py, line 124, in __init__ self.Load() File /usr/local/mailman/Mailman/MailList.py, line 583, in Load dict, e = self.__load(file) File /usr/local/mailman/Mailman/MailList.py, line 556, in __load dict = loadfunc(fp) AttributeError: 'dict' object has no attribute 'append' Python information: VariableValue sys.version 2.2.2 (#1, Apr 6 2003, 18:09:02) [GCC 3.2] sys.executable /usr/local/bin/python sys.prefix /usr/local sys.exec_prefix /usr/local sys.path/usr/local sys.platformsunos5 Environment variables: Variable Value HTTP_PRAGMA no-cache PYTHONPATH /usr/local/mailman SERVER_SOFTWARE Apache/1.3.27 (Unix) SCRIPT_FILENAME /usr/local/mailman/cgi-bin/listinfo SERVER_ADMIN [EMAIL PROTECTED] SCRIPT_NAME /mailman/listinfo SERVER_SIGNATURE Apache/1.3.27 Server at lists.IN.gov Port 80 REQUEST_METHOD GET HTTP_HOST lists.in.gov HTTP_KEEP_ALIVE 300 SERVER_PROTOCOL HTTP/1.1 QUERY_STRING HTTP_CONNECTION keep-alive HTTP_CACHE_CONTROL no-cache REQUEST_URI /mailman/listinfo HTTP_ACCEPT text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1 HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7 HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030425 TZ US/East-Indiana SERVER_NAME lists.IN.gov REMOTE_ADDR 10.8.49.214 REMOTE_PORT 32807 HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5 SERVER_PORT 80 GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_ENCODING gzip,deflate,compress;q=0.9 SERVER_ADDR 10.8.51.75 DOCUMENT_ROOT /usr/local/apache/share/htdocs Any ideas, or should I start thinking about ditching mailman? -- I still think the odds are good that you can make a bet on what will be the odds -- Tub Ring +--+--+--+---+ | Greg Swallow | CCNA | System Administrator | accessIndiana | +--(http://www.IN.gov/)--(888.4IN.EGOV)--+ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Evolution, GPG,and mailman 2.1.2 - blank message bodies
Hello. I feel like this must be an F.A.Q. but I could find no mention of it in the searchable archives or the FAQ-O-Matic. Anyway, it seems that evolution has a bug in message display that affects GPG-signed email sent to mailman 2.1.x lists (when the GPG signature uses PGP/MIME). Mailman adds the list's signature as a MIME attachment, and for some reason evolution shows ONLY the list signature, and not the body of the message at all! This is apparently fixed in Evolution 1.4.3, but unfortunately a large number of our users are using prior versions of evolution, like 1.2.2 that's included in Red Hat Linux 9. I suspect this is true of many users around the community. Though this is an evolution bug, most of our users are seeing it as a mailman problem, because suddenly they cannot view their messages after we upgraded to mailman 2.1.x. Does anyone have any ideas or workarounds? Is there any way to make mailman 2.1.2 go back to the old behavior that doesn't use MIME to add the signature (or just skips it for MIME messages) ? Note: I've also heard that Outlook Express has a similar problem reading GPG-signed emails with evolution's MIME-added signature, so this isn't really uniquely an evolution problem. But Outlook Express handles GPG pretty pitifully anyway, so I'm not worrying about that. Thanks for any advice, Jeremy -- /-\ | Jeremy Portzer [EMAIL PROTECTED] trilug.org/~jeremy | | GPG Fingerprint: 712D 77C7 AB2D 2130 989F E135 6F9F F7BC CC1A 7B92 | \-/ signature.asc Description: This is a digitally signed message part -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Access problem..
This may be applicable: http://sourceforge.net/tracker/ index.php?func=detailaid=747470group_id=103atid=300103 On Wednesday, August 13, 2003, at 08:53 pm, Brian Burdette wrote: I do not know what version of Python you have installed. Python 2.2.3 would be good. I've not seen final confirmation about using Python 2.3 with MM 2.1.2 I'm running Python 2.3, MM 2.1.2, RH 8.3 3.2-7 I'm having issues with a few lists. most lists work properly. one list is generating the error below, and shunting ALL email. deletion and re-creation of the list will cause it to work again, for a while. It's just started this again. A hunt thru the tracker doesn't turn up anything about iterable arguements. Do I need to downgrade python to 2.2.3 to make this work? Thanks. Brian Aug 13 15:02:13 2003 (21139) SHUNTING: 1060804921.628845+2ecaa45b294ccc7106476c70caedaec27b32f635 Aug 13 15:02:14 2003 (21139) Uncaught runner exception: iterable argument required Aug 13 15:02:14 2003 (21139) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 105, in _oneloop self._onefile(msg, msgdata) File /usr/local/mailman/Mailman/Queue/Runner.py, line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/local/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 89, in process send_digests(mlist, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 130, in send_digests send_i18n_digests(mlist, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 303, in send_i18n_digests msg = scrubber(mlist, msg) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 257, in process url = save_attachment(mlist, part, dir) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 349, in save_attachment ext = guess_extension(ctype, fnext) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 80, in guess_extension if ext in all: TypeError: iterable argument required Aug 13 15:02:14 2003 (21139) SHUNTING: 1060804932.8378969+243bf64bd6fd2e2d56992162d98ba518c7ff22e2 --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman + htDig
I realize this has come up often in the list, but hit a snag and was not sure where else to turn. I couldn't find much in the archives that addressed this, but if it is a duplicate, please accept my apologies. I've applied the htDig patches : http://www.openinfo.co.uk/mailman/patches/728836/templates-2.1.2-0.1.patch http://www.openinfo.co.uk/mailman/patches/732366/tz-2.1.2-0.2.patch http://www.openinfo.co.uk/mailman/patches/730769/tcache-2.1.2-0.3.patch http://www.openinfo.co.uk/mailman/patches/444879/indexing-2.1.2-0.1.patch http://www.openinfo.co.uk/mailman/patches/444884/htdig-2.1.2-0.4.patch And all were applied happily. The indexing appears to be happening correctly on the filesystem level since the htdig directory is being created, the conf file is being created, and if I manually perform a search (htsearch -c blah), I do get output and results. However, I am not getting the search form at the top of the index.html page as is supposed to happen. So, as expected, I cannot search via the web interface. :( The index.html file *IS* being updated, but nothing is getting added to it (no search form)... I *believe* I followed the htdig docs to the letter, but it seems as if I am still missing something. Any help would be much appreciated! Thanks! -Rich -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Modifying held posts feature
I'm using mailman 2.1.2 As I recall in the archives of last year there was a post about a patch that could be installed in 2.0 that would allow moderators and admins to modify held posts. I'm wondering if this feature or patch has become a permanent addition to 2.1.2 or if there are plans to include it in the next upgrade? Also, I am new to Python so excuse the ignorant question, but how does one install a patch? Is there a document somewhere that explains it in layman's terms? And, if I install this patch, will I need to kill and then recreate my mailing list or regenerate it? Finally, I see by reading the archives that one can modify the held posts directly by modifying the file in /mailman/data . I tried this once using BBEdit and FTP and got an error when I tried to approve the post. Any suggestions on the best way to modify a file on the server and what parts of it I should stay away from or what file type it needs to be saved as? - Sorry for so many newbie questions. Thanks in advance for any insight. The modify held posts is a really critical feature for me, so I'd like to get it working. AB -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Modifying held posts feature
On Tue, 2003-08-12 at 12:26, Adam Boettiger wrote: I'm using mailman 2.1.2 As I recall in the archives of last year there was a post about a patch that could be installed in 2.0 that would allow moderators and admins to modify held posts. I'm wondering if this feature or patch has become a permanent addition to 2.1.2 or if there are plans to include it in the next upgrade? Also, I am new to Python so excuse the ignorant question, but how does one install a patch? Is there a document somewhere that explains it in layman's terms? And, if I install this patch, will I need to kill and then recreate my mailing list or regenerate it? Finally, I see by reading the archives that one can modify the held posts directly by modifying the file in /mailman/data . I tried this once using BBEdit and FTP and got an error when I tried to approve the post. Any suggestions on the best way to modify a file on the server and what parts of it I should stay away from or what file type it needs to be saved as? - Sorry for so many newbie questions. Thanks in advance for any insight. The modify held posts is a really critical feature for me, so I'd like to get it working. AB Look in the FAQ's. There is a specific procedure for editing the message directly using version 2.0. This also works in version 2.1, but only if you modify the default value for one of the settings in mm_cfg.py. The setting determines whether held messages will be stored in text format or in a pickle format. If you scan Defaults.py you should be able to find it. You of course want them stored in a text format if you are going to edit held messages directly. Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py There is a great patch that allow you to edit the message while in the approval web-browser. I *think* this patch was ported to 2.1 as well. This makes modifying messages a real snap! There is also an FAQ on applying patches to mailman. Be prepared to install from the source code! Good Luck - Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Access problem..
On Wednesday, August 13, 2003, at 01:24 pm, Anders Norrbring wrote: Richard, Thanks.. :) A -f fixed quite some errors, but still I get this in e-mail from the server: Traceback (most recent call last): File /usr/lib/mailman/cron/gate_news, line 274, in ? main() File /usr/lib/mailman/cron/gate_news, line 249, in main lock.lock(timeout=0.5) File /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, line 238, in lock File /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, line 415, in __write IOError: [Errno 13] Permission denied: '/var/lib/mailman/locks/gate_news.lock.berit.20898.0' Then I guess you will have to check what uid/gid has write permissions over the /var/lib/mailman/locks/ directory and compare this for compatibilty with the uid that the Mailman crontab has been installed under. I would expect then both to be the 'mailman' uid (as decided by the installer when Mailman was configured) but plainly they cannot be compatible or you would not have a permissions failure when the cron job is (presumably) trying to create a lock file in the directory. Still there's no directory in /var/tmp Anders Norrbring - -Original Message- - From: Richard Barrett [mailto:[EMAIL PROTECTED] - Sent: den 13 augusti 2003 12:44 - To: Anders Norrbring - Cc: Mailman users - Subject: Re: [Mailman-Users] Access problem.. - - - On Wednesday, August 13, 2003, at 10:13 am, Anders Norrbring wrote: - - Here's one of the mails I get every 5 minutes from my server: - - Traceback (most recent call last): -File /usr/lib/mailman/cron/gate_news, line 274, in ? - main() -File /usr/lib/mailman/cron/gate_news, line 249, in main - lock.lock(timeout=0.5) -File - /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, - line 238, in lock -File - /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, - line 415, in __write - IOError: [Errno 13] Permission denied: - '/var/lib/mailman/locks/gate_news.lock.berit.6176.0' - - - You could try running Mailman's check_perms program. Looks from the - paths in the traceback above as though it could be in - /usr/lib/mailman/bin/check_perms. Run it with the -h option to get it - to print its usage. - - And when I look in '/var/mailman/locks' that dir is empty! - Also, in '/var/tmp' there's only one entry, a subdir named 'vi.recover' - - There's something wrong, but I don't know where to start looking. It's - installed on a SuSE system based on United Linux 1.0 and the mailman - package - is a SuSE distributed one. - - Anders Norrbring - Norrbring Consulting --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Listserv wide announcements?
John (also), I decided to go with this plan and it's worked out fairly well I believe. I only had to moderate on the parent list (by choice, per recommendation) and and the site-lits mailman which I mistakenly added in the batch. Thanks a ton for the idea. -John John, It is probably about the same amount of work, but you could also create an umbrella list to which all the other lists are subscribed. The tedious part would be making sure that the sender is allowed to post to all 50 lists, but you have to do that one way or another. Then the infrastructure would be in place should you need to make any other huge announcements. Of course you would have to be extra careful about spam or other stray messages. Probably would want to require moderation of every message sent to the umbrella list, even by you. John Wofford wrote: On Tue, 2003-08-12 at 07:55, John Wofford wrote: [snip] Is there a nice, clean, and preferably easy way to send out an announcement to the *entire* listserve? Any other suggestions? -- John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Lines don't wrap in archive?
I notice that in the archives, email text lines don't wrap. Is this a configuration issue? and if so, where can I configure it so it will wrap them? Thanks! -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Managing archives
Alright, it worked great! I have a list on one of my servers called test, it has a lot of messages in it, but nothing I care anything about. I used it to test with... I created an empty mbox on one of my imap accounts and called it test then moved all the mbox information from the archives into the new imap mbox: cat /var/mailman/archives/private/test.mbox/test.mbox test This copied all the emails from the archive and left the imap header information intact. The imap header is an email at the top of the file. The IMAP header is created by Evolution (my email client) inside every IMAP mailbox that it reads. The header is exactly 13 lines long. This seems to be fairly standard for most IMAP clients. All the messages in my test archive showed up as email messages in the test mailbox. I pruned out some messages and then copied the test mbox back into the archive file. Next I edited the test.mbox file and removed the imap header (which looks like the first email in the mbox - very easy to recognize). Next I deleted the old archives: rm -rf /var/mailman/archives/private/test/* and generated the new archives: /var/mailman/bin/arch test Viola! It worked great. My newly pruned archives looked fantastic, and it was fast and easy. It would be quite easy to automate this as two scripts, one that creates the imap mbox and copies the mbox from the archive: #! /bin/bash # # Used to move an archive into position for editing # by anyone who can use an email client # # Assumptions: # - mailman install is in /var/mailman # - imap mailbox root is /home/user/mail/listname # This means that you already created the mbox # using your email program. # listname == $1 # # Input: a valid mailman list name (with archives) # PATH2ARC=/var/mailman/archives/private # Check that the list name is valid and the archives exist if [ ! -f $PATH2ARC/$1.mbox/$1.mbox ]; then echo ERROR: $1 is not a valid mailman list with archives echo (be sure to use all lower case) echo or path to archive files is incorrect: echo $PATH2ARC echo exit 0 fi # PATH2MB=/home/user/mail # # Check that mbox has been created... if [ ! -f $PATH2MB/$1 ]; then echo ERROR: Please check that the path to your IMAP Mailbox echo is: $PATH2MB echo and that you have created a Mailbox called:$1 echo exit 0 fi # cat $PATH2ARC/$1.mbox/$1.mbox $PATH2MB/$1 === Now someone simply edits the mailbox using their email client. This doesn't take anyone technically minded... When they are done, we put back the archives: #! /bin/bash # # Used to move an edited mbox from an imap folder # and put it back into the Mailman archive from # which it was grabbed. # # Assumptions: # - mailman install is in /var/mailman, # with archives being in /var/mailman/archives/private/.. # - imap mailbox root is /home/user/mail/listname # and the imap header for the file is 13 lines long # including the blank line at the end of the message. # # Input: a valid mailman list name (with archives) # PATH2ARC=/var/mailman/archives/private # # Check that the list name is valid and the archives exist if [ ! -f $PATH2ARC/$1.mbox/$1.mbox ]; then echo ERROR: $1 is not a valid mailman list with archives echo (be sure to use all lower case) echo exit 0 fi # PATH2MB=/home/user/mail # # Check that mbox has been created... if [ ! -f $PATH2MB/$1 ]; then echo ERROR: could not find mailbox $1 in path: echo $PATH2MB echo Please check that root path to mailbox is correct. echo exit 0 fi # # Number of lines in IMAP header IHEAD=13 # mv $PATH2ARC/$1.mbox/$1.mbox $PATH2ARC/$1.mbox/$1.mbox.bak # j=`cat $PATH2MB/$1 |wc -l` k=$(( j - IHEAD )) tail -$k $PATH2MB/$1 $PATH2ARC/$1.mbox/$1.mbox # # now lets remove the old archive files and regen # the archives with the new mbox! rm -rf $PATH2ARC/$1/* /var/mailman/bin/arch $1 === The scripts aren't tested, but should be good for a quick start! Take care. Hope that helps someone. Jon Carnes On Tue, 2003-08-12 at 12:09, Jon Carnes wrote: I'll give it a shot on one of my boxes (create a soft link to the mbox into my mailbox) and let you know... It *should* work. On Tue, 2003-08-12 at 11:18, Victor Tsaran wrote: Hi, John! Do you think the access to the mbox can also be done through IMAP? I am not an administrator on this machine, just a list admin, but I need to know what to tell the root. Regards, Victor -Original Message- From: Jon Carnes [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 10:55 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Managing archives On Tue, 2003-08-12 at 09:26, Victor Tsaran wrote: Hello, listers! Here is my situation. I am managing several lists for an international
[Mailman-Users] Subscriber tracking
To anyone who can offer advice, I admin a couple lists, and I have just come to realize that my ISP requires me to keep perfect history of every subscriber: date they signed up and originating ip address, all available with 1 day of any complaint. It is very important to me to conform to these requirements. It seems that a user subscribing via mailman's webform thing gets all this info logged in $MAILMANROOT/logs/subscribe. However the vast majority of my subscribers subscribe via a custom webform (integrated with a catalog request page). This custom webform just sends an email to the [EMAIL PROTECTED] with the necessary arguments. I looked in the subscribe log and it shows the users email address in place of the ip address. Ideally I need it to show the appropriate ip address. You can start to see some complications here, as if it were to simply use the ip address of the originating mail, it would get my webserver (it originates the mail on behalf of the user). So, ideally, I'd like to pass the originating ip address as an argument in the subscription request email, or have it log the ip address of the confirmation reply. I guess that in most cases I could line up logs and I might be able to figure it out (the clocks are always perfectly synced on these servers though). Does anybody else deal with this kind of issue? How do y'all handle this? Any advice of where to find docs on this? PS- Running mailman-2.0.13. I google'd, searched archives of this list, read the FAQ, and looked through the mailman docs. I couldn't find any document dealing with this type of issue. Thanks! Todd Morrey -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Mailman not starting correctly.
Hello all, I seem to have made a bad decision on changing my dedicated server to someplace that can't keep a machine with power for very long. I haven't had a problem with mailman 2.1.2 like this for some time. It seems that my ISP rebooted my machine or had a power failure. Now my machine is back up and mailman is only half working it seems. I can get to the web interface and all. And my list only has 3 people sending to the list occassionally. This morning a post was sent to the list and it was never sent out. I thought maybe it was a fluke when it was reported to me so I resent it from my account. Same deal, nothing in pending tasks and nothing going out. I know this is probably something very simple that didn't start on bootup. Just kinda odd that it didn't this time and me being new to freebsd (4.7) makes it a little harder to figure out. Any help would be greatly appreciated. jsmith -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: Hotmail and Yahoo sending mail straight to junkfolders
Angel Gabriel wrote: It seems that hotmail and yahoo are sending mail from mailman straight to junk folders, this is REAL bad, especially because it's possible to delete junk folders without actually looking in them. Why is this, is this because there is a bulk mail setting in the mail header? If so, how can I stop this being written into the mail? In my tests this only happens with HotMail when Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields) on the General Options list administration page is set to yes. Yahoo uses a bulk mail folder for this, and the first time a bulk mail is received a message about the folder is sent to the in box. Removing the bulk mail header would be false advertising of what the mail is, and that is a good way to get labeled as spam and end up on some blacklist. I hate spam more than the next guy, but we are starting to see an over the top, shoot first ask questions later mentality that is making it hard for anyone running any list. Usually the ISP could care less about a list owner, so you have to get the folks who use the service to complain. At some point I want to write a why I'm not getting my list mail page with info on the most common problems. When I get it done I'll let folks here know. Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Re: qrunner with over 90% CPU
Jon Carnes wrote: Both of which are well less than what I have. What would this do? For *you* it would make things worse! So don't change what you have. That's what I thought. Not yet, but it will be in time as I move more lists. I am way over due for some upgrades and the box no longer covers what I need, so I'm looking to move to a new server. I'm thinking a two HD box running C-panel, and I'm looking to run a better MTA than sendmail. Hmmm, well you could experiment with Postfix now. You might have to mess with the GID's from the Mailman install, but other than that (which is a PITA) Postfix is pretty much a drop and insert replacement for Sendmail. I have learned that with a chrooted environment nothing is a drop in ANYTHING. I plan to have a good long overlap on the two servers, so I can play with the new one and get it right without upsetting any of the paying customers! Unless Postfix could be installed alone side of Sendmail and used just for MM. I've not looked into that, but I have a bad feeling about it. I've googled for the problem and at least two other folks changed MTA's and the problem went away... No other solutions though. Well that is my long term fix. Thanks. Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List Admin sent to wrong domain--solved
On Wednesday 13 August 2003 21:47, John Locke wrote: Hello, I'm surprised nobody had an answer for this. Anyway, I just figured it This is a known problem, check the archives or just my thread qrunner with over 90% cpu, you should configure your postfix to give permanent errors instead of temporary ones. Jens -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] qrunner with over 90% CPU
Jon Carnes wrote: Paul, I have never seen this on a sendmail install. Maybe your problem is a different one. Perhaps I miss read the issue. Give that my runaway is Python I suspect this is the case. Sorry. I posted about my problem a while back, see http://www.mail-archive.com/[EMAIL PROTECTED]/msg18201.html. It seems MM is a little over eager about retrying messages when sendmail (or any MTA) reports a temporary failure. Richard said a change had been made in the CVS, and wondered if a patch was available. what version of python are your running, and what is the OS? Mailman 2.1.2 Redhat 7.1 Python 2.2.2 Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Uncaught runner exception: iterable argumentrequired
This is mailman 2.1.2 on RedHat linux 8.0 I get the following error entry when sending to certain lists. mail is shunted. Rebuilding those lists resolves the problem, temporarily. Anyone able to shed a bit of light on this, or should I move it to mailman developers? Is more data needed, is this a known bug, etc? The searchable archives appear to be unavailable, or I would have started this quest there. Thanks in advance. -- Brian Burdette, brian at whatever2k dot com Aug 12 15:55:06 2003 (21139) SHUNTING: 1060721704.746578+16653187a5b1707307a1b8ec45d1f32f25c338f1 Aug 12 16:56:52 2003 (21139) Uncaught runner exception: iterable argument required Aug 12 16:56:52 2003 (21139) Traceback (most recent call last): File /usr/local/mailman/Mailman/Queue/Runner.py, line 105, in _oneloop self._onefile(msg, msgdata) File /usr/local/mailman/Mailman/Queue/Runner.py, line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/local/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 89, in process send_digests(mlist, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 130, in send_digests send_i18n_digests(mlist, mboxfp) File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 303, in send_i18n_digests msg = scrubber(mlist, msg) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 257, in process url = save_attachment(mlist, part, dir) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 349, in save_attachment ext = guess_extension(ctype, fnext) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 80, in guess_extension if ext in all: TypeError: iterable argument required Aug 12 16:56:52 2003 (21139) SHUNTING: 1060725410.830851+0fccb1b8c3453d14bc83088fc33b08adc20b1f7b -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Managing archives
Hi, John! Do you think the access to the mbox can also be done through IMAP? I am not an administrator on this machine, just a list admin, but I need to know what to tell the root. Regards, Victor -Original Message- From: Jon Carnes [mailto:[EMAIL PROTECTED] Sent: Tuesday, August 12, 2003 10:55 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Managing archives On Tue, 2003-08-12 at 09:26, Victor Tsaran wrote: Hello, listers! Here is my situation. I am managing several lists for an international organization. Over the last couple of years our archives have grown quite large and, I am sure, that many of the messages are no longer necessary to keep. What is the easiest way for me to pull down the whole archive, convert it to something that can be reviewed/edited by the organization's secretary, pull it back together and reupload back to the server. Is there a tool that will allow me to do this? I myself don't have the time to carry out this task, however, I cannot expect the secretary to fool around with Unix mail boxes etc. Also, I have seen some web sites that zip their messages while archiving. How is this done? Thanks much for any response I can get on this. Regards, Vic -- You should be able to set it up so that the secretary can simply browse the archive emails via an email program and then delete the messages he thinks are not necessary. Mailman archives are stored in an mbox file on the server If you copy the mbox file to a computer running evolution (that's what I currently use for my email - and its great!) then he can read the messages as though they are simply local messages in the INBOX (or some other folder that you create). Once he deletes the extraneous messages, he does an expunge or rebuild on the mailbox! Now you have a new mbox that is ready to be copied back up to the Mailman archives. Once the mbox is put back in place, you will need to run the ~mailman/bin/arch command to rebuild the archives using the new mbox file. Aside: I wonder how hard it would be to build a web interface for editing the archives? We could use formail to break-out each of the old messages and move them into a holding directory, then scan the holding directory to get the subject/date from each message. Display those with a link to pull up the whole message, and a checkbox for deleting the message. Once you click done, the back-end cgi would reassembles the mbox by just cat-ing the remaining files back together - then it would back up the old mbox file and put this one in place. After that, it would run the Mailman arch program for the list. OR it would probably be easier to use the existing pipermail setup but add a delete field for use by an admin (running pipermail from a specified ip or from localhost), then use the built-in python libraries for handling mbox - after all, you are just deleting a message from an mbox file and that is a fairly boring/mundane task. Jon Carnes -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] 'recipient list too long'? -- [dr-fun-changes]http://www.ibiblio.org/Dave/ has changed. (fwd)
Hi The message below got bunged onto me as moderator even though I have an explicit non-member approve for this sender, [EMAIL PROTECTED] Mailman said the recipient list was too long, and to shorten it. However, of course, as moderator I approved it. This is a big 'um' for me, as I run another mailing list on this server, internet-news, where the moderator there crossposts to about five mailing lists! The real name 'Doctor Fun website changes list' I suspect may be at fault, but I don't see how that *should* make the recipient list too long. Ideas, people? I'd rather not approve messages every time unless I have to (though changing the real name might be a good idea, but again, I'd rather not if I don't have to). Thanks Jonathan -- Jonathan Ah Kit - Lower Hutt - New Zealand [EMAIL PROTECTED] - http://www.ah-kit.dropbear.id.au/ [EMAIL PROTECTED] - ICQ#9747234 - http://www.electric.gen.nz/ Away message: Looking for adhesive tape, not Alibrandi. -- Forwarded message -- Date: Tue, 12 Aug 2003 08:01:03 +1200 From: Jonathan Ah Kit [EMAIL PROTECTED] To: Doctor Fun website changes list [EMAIL PROTECTED] Subject: [dr-fun-changes] http://www.ibiblio.org/Dave/ has changed. Latest changes to http://www.ibiblio.org/Dave/ ___ 8,11c8 See below for an announcement about file locations, especially if you are running a mirror site, or want to run a mirror site, or are getting the cartoons via ftp from ibiblio. Thanks. --- File locations have been moved from /ftp the /html on ibiblio. 44a42,43 August 11, 2003 - All the stuff described below has been done. ___ dr-fun-changes mailing list http://greta.electric.gen.nz/mailman/listinfo/dr-fun-changes http://www.ibiblio.org/Dave/ http://www.ibiblio.org/Dave/books.htm http://www.ibiblio.org/Dave/faq.html http://www.ibiblio.org/Dave/book-faq.html Note: URLs aren't in this diff. :( -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Help with weird setup
I'm having a heck of a time getting my mailman configuration finalized and I know it's because of my setup. I'll ask my question now and list all the technical details below. QUESTION: What can I do to modify my current lists so that they send out their subscription confirmation links as http://host2.domain.com:8080/ instead of http://host.domain.com/? TECHNICAL DETAILS: I have two boxen behind a NATting firewall that looks like this: +-+ Port 80 +--| IIS | host.domain.com | +-+ host2.domain.com +--+ |redirects to + [Outside IP]--| Firewall |--+ | +--+ | | | +-+| Port 8080--- +--| Apache | host2.domain.com:8080 ---+ | Mailman | +-+ Apache is listening on Port 80 - IPTables DNAT is translating Port 8080 on the outside to Port 80 internally 1. When I access http://host2.domain.com/mailman/listinfo/listname I get redirected by the IIS server to http://host2.domain.com:8080/mailman/listinfo/listname. This is on purpose to get around people that will simply type in http://host2.domain.com and wonder why things don't work. When I get to the requested page, I can then fill out the HTML form to subscribe. When I submit the form, because it's ACTION is http://host2.domain.com/mailman/subscribe/listname/ and not host2:8080, the POST variables seem to get stripped and I get an error saying that You must supply a valid email address. I cannot subscribe to lists through the HTML pages. 2. If I send an email to [EMAIL PROTECTED] I get a confirmation e-mail back which looks like this: http://host.domain.com/mailman/confirm/listname/0618bc95ac6b9f595dafc3f6 c2b08fe34eb1b412 I click on the URL and am forwarded to: http://host2.domain.com:8080/mailman/confirm/listname/0618bc95ac6b9f595d afc3f6c2b08fe34eb1b412 When I click on the Subscribe to Listname button I'm presented with another form asking for the confirmation code. I then copy the confirmation code out of the e-mail (0618bc95ac6b9f595dafc3f6c2b08fe34eb1b412) and paste it to the form. The form is submitted and then I'm presented with the same form asking for the confirmation code. Again, I suspect this is happening because the FORM's ACTION is http://host2/ and not http://host2:8080/ resulting in the POST variables being stripped. 3. If I simply reply to the list confirmation request I can subscribe successfully and send and read email's sent to the list. 4. All of my lists were created internally with DNS pointing to the internal (192.168.0.x) address of the server. They worked great. Now I've changed the DNS to the outside IP of the firewall and now these problems are cropping up. Also, if I go directly to http://host2.domain.com:8080/mailman/admin I'm told that there are no lists available. If I attempt to create a list with this interface and then subscribe to it, I'm successful (even using the web interfaces). Thanks for any help, Mike Fetherston -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] v2.1.1 and Archive download problem
I have the precis same problem, seems like the URL is not converted right, in my IE6 it comes up with: mhtml:http://www.the-server.net/pipermail/fetishclub_info.mbox/fetishclub_in fo.mbox Which of course is totally wrong.. Anders Norrbring - We are using version 2.1.1 and when someone clicks on the download the - full - raw archive on the archives page, the archive is not downloaded under - IE. - It downloads okay using Netscape or Opera. - - I've tried downloading this list's archives and it works fine. Therefore - I'm thinking this is either a configuration problem or an upgrade - problem. - Has anyone experienced this? Got a fix? - - Ken -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Define stuff per list or language?
Hiya all! I've found the really nice feature in 2.1 to have custom templates for each list and/or language available. But, there's one important (to me, anyway) variable I can't seem to find any possibility to customize per language, so if anyone knows how, please help! The variable is 'member_moderation_notice'. Since we run a couple of dual language lists it kinda important to set. We have both English and Swedish languages on those lists, and as many of you know, we Scandinavians (and others) use extended ASCII in our texts, so if I use any of those, they show up correctly when a user have set his/her language to Swedish, but if the language option is set to English, then it's a mess in the mail sent out as moderation/reject e-mail. Due to the fact that I haven't found any customization function for that specific parameter, I have to include both Swedish and English explanatory text in the response e-mail, and it really sucks when a user gets a mail full of aring; and alikes just because I can't set one string per language. Please point out to me how it can be done! Thank you! Anders Norrbring Norrbring Consulting -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] changed domains, need to change list url
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Kirk,
Reply to the list. That way more folks can take a stab at offereing help
and then others can benefit from the answers if they search the archives.
Kirk R. Wythers wrote:
Sorry to be such a ditz... I tried changing mm_cfg.py to this:
DEFAULT_HOST_NAME = 'neighborsunited.net'
DEFAULT_URL = 'http://www.neighborsunited.net'
MAILMAN_OWNER = '[EMAIL PROTECTED]' % DEFAULT_HOST_NAME
add_virtualhost(neighborsunited.net, neighborsunited.net)
must be right... when I run mailmanctl restart I get:
lorax[/usr/local/mailman/bin]$ ./mailmanctl restart
Traceback (most recent call last):
File ./mailmanctl, line 105, in ?
from Mailman import mm_cfg
File /usr/local/mailman/Mailman/mm_cfg.py, line 49, in ?
add_virtualhost(neighborsunited.net, neighborsunited.net)
NameError: name 'neighborsunited' is not defined
lorax[/usr/local/mailman/bin]$
You want to literally use:
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
I think (and someone more knowledgeable will correct me if I'm wrong here, I
hope), that you could use neighborsunited.net in the add_virtualhost
function if you quoted it. So this *should* work as well:
add_virtualhost('neighborsunited.net', 'neighborsunited.net')
- --
Todd OpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
Some people are like Slinkies... not really good for anything, but you still
can't help but smile when you see one tumble down the stairs.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3rc2 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
iD8DBQE/L/Pluv+09NZUB1oRAmuaAKDBZ3WW0jnmDjTMfaxFI7yBxT3uXACgiwa6
GYD3xnq12mE28KSEBu6InU0=
=zOI8
-END PGP SIGNATURE-
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Importing subscribers
Can one subscribe a list of email addresses with their corresponding names (one email + name per line)? H I N D Y C H I N N Asst. Director of Information Technology Hillel: The Foundation for Jewish Campus Life phone: 202-449-6542 fax: 202-449-6442 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] command list
On Wednesday, August 13, 2003, at 12:07 pm, Anders N. Thingholm wrote: We are 2 guys' that are making API for mailman to a project in our education. So I need a complete list of commands to mailman. Anyone have a link for this ? Try http://mailman.sourceforge.net/docs.html Anders --- Richard Barrett http://www.openinfo.co.uk -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] There are humans at excite.com!!
I went round and round with them but I never seemed to get anywhere with them. They also have not sent me any response to my latest complaint of it. Who knows. But them removing it is a good thing. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul H Byerly Sent: Wednesday, August 06, 2003 11:51 AM To: [EMAIL PROTECTED] Subject: [Mailman-Users] There are humans at excite.com!! Hi all, It took four rounds of auto responders requesting headers to get a real person, but I now have word from excite.com that they no longer use the filter that identifies as spam mail with long words in the subject line. Excite Email Help wrote: We regret you have not received an adequate response to your previous emails. The filter you are speaking about is no longer in use by our company. You should not have any difficulty sending emails that you have described below. If you experience any difficulty, please send an email to [EMAIL PROTECTED] Regards, Excite Abuse Department Paul -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jsmith%40smittybuil t.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Hotmail and Yahoo sending mail straight tojunkfolders.
Yahoo! does that for a LOT of email, not necessarily because it comes from Mailman. For the record, all my Mailman delivered (note: Mailman doesn't deliver mail, your MTA does) email, sent to my personal Yahoo! address, is arriving in the intended destination not the bulk/junk email folder. More than likely you have an MTA configuration error or your MTA is not designed/setup (rDNS, clean IP/Network, etc) appropriately enough to satisfy Yahoo! polices. -Jim P. -Original Message- From: Angel Gabriel Sent: Monday, 11 August, 2003 11:14 It seems that hotmail and yahoo are sending mail from mailman straight to junk folders, this is REAL bad, especially because it's possible to delete junk folders without actually looking in them. Why is this, is this because there is a bulk mail setting in the mail header? If so, how can I stop this being written into the mail? -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Prevent bounce back messages to moderators?
Brent, The moderator role is to approve or disapprove messages. You don't have to make them moderators to let them post. Just make sure their mod flag is off and that the mod flag for everyone else is turned on. Brent Herring wrote: We have an administrative type list with all employees as members. Only a small subset of members should be able to post messages. I created the list and made those members moderators. Now these moderators are not list admins, just the ones who can post. Whenever there is a bounce back message the moderators receive these notices as well as me. I would like for this to not happen but cannot figure out how to prevent the moderators from receiving the notices and still be the only ones who can post to the list. -- John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Access problem..
Here's one of the mails I get every 5 minutes from my server: Traceback (most recent call last): File /usr/lib/mailman/cron/gate_news, line 274, in ? main() File /usr/lib/mailman/cron/gate_news, line 249, in main lock.lock(timeout=0.5) File /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, line 238, in lock File /var/tmp/mailman-2.1.1-build/usr/lib/mailman/Mailman/LockFile.py, line 415, in __write IOError: [Errno 13] Permission denied: '/var/lib/mailman/locks/gate_news.lock.berit.6176.0' And when I look in '/var/mailman/locks' that dir is empty! Also, in '/var/tmp' there's only one entry, a subdir named 'vi.recover' There's something wrong, but I don't know where to start looking. It's installed on a SuSE system based on United Linux 1.0 and the mailman package is a SuSE distributed one. Anders Norrbring Norrbring Consulting -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailman for fan club
John, Thanks, I have already looked at that and I am using version 2.0.6 which comes with my hosting company. most of the setup in this article is in version 2.1. Will this work in 2.0.6? Is this the only reference? I'm having a tough time figuring this one out. Thanks for your help, Amy - Original Message - From: John DeCarlo [EMAIL PROTECTED] To: Amy Rynne [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Thursday, August 07, 2003 7:20 AM Subject: Re: [Mailman-Users] mailman for fan club Amy, I suggest you peruse the Mailman FAQ. Read some of the Introduction sections, then look at 3.11 for the type of list you want. Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Amy Rynne wrote: Hello, I am interested in using Mailman for a fan club email list. I don't want a discussion list, just a monthly update for fans. Do you have any suggestions or can you point me to a webpage that will tell me more about what I need? -- John DeCarlo, My Views Are My Own -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Difference between PiperMail 0.5 and PiperMail 0.9
Hello, listers! Are there any huge differences between Pipermail 0.5 and Pipermail 0.9? Is it worth to ask our site administrator to update to the latest Pipermail? Regards and thanks, Victor -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Wish - Admin
I'm using 2.1.2. I wish for the next upgrade in the admin moderator area for approving held posts, there was a box that I could check that would remove the poster from the subscription list at the same time their message is discarded. I'm seeing some bounces and some autoresponses and occasionally wish to remove the address from the list at the same time I discard the held post. Right now it is a two-step process - discard the post, then go to another screen and perform an address search and remove the address. Would be really nice if I could just check a box on the held posts section that would remove that address from the list along with approving other messages in the queue. AB -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] List Admin sent to wrong domain--solved
Hello, I'm surprised nobody had an answer for this. Anyway, I just figured it out. While checking top on the server, I noticed that a Python process owned by mailman was taking up all the extra CPU, at a low priority, with some 52 hours of processing time. I used mailmanctl to stop and restart, but the process came right back up to the top of the list. So I tried doing an strace on the process, and it was quite active... it kept adding, renaming, and deleting a file in qfiles/out. On Sat, 2003-08-09 at 13:11, John Locke wrote: I checked in the qfiles/ directories, couldn't find it there. I tried stopping and starting mailmanctl. I checked all of the Postfix queues, and it's nowhere to be found. Where do I find this message, and how do I get rid of it? So I rechecked this directory, and found that mailman kept creating and deleting two files, a .db and a .pck in this directory, each time with a new name, a few times a second! I stopped mailmanctl, and this time the files were there. I deleted them, restarted mailmanctl, and both problems are solved--no more attempts to mail to the bad domain every hour, and mailman is no longer hogging all the cpu time. Cheers, John Locke Owner, Freelock, LLC Small Business Computing with Open Source http://www.freelock.com -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Public/private archives problem.
The problem is resolved, with great help from Richard. For the sake of posterity, let the mailing list archives show: * Be sure you have proper virtual host mapping (add_virtualhost()) in mm_cfg.py; * Be sure that the list setting for Host name this list prefers for email is in fact your mail exchange address, not a base URL for browsing (which was my problem); * Run fix_url.py Thanks Rob Quoting Rob Brandt [EMAIL PROTECTED]: Richard; Thanks for your help in this. I am going to email you a link to my testlist, which you can log into as an administrator and see for yourself what the problem is. My server does not run CPanel, so I don't think that's an issue here. My server is sitting here next to my desk, so I have full control if you need any information. Best Regards Rob Quoting Richard Barrett [EMAIL PROTECTED]: Tony The questions I am asking are to elicit information that will distinguish between and identify whether there is a problem with (a) Mailman or (b) misconfiguration of Mailman or (c) third party modifications made to Mailman or (d) other aspects of the host system configuration such as the Apache server. You are complaining about links but I can interpret that in several ways: 1. whether the URL of concern is accepted and served by the Apache server when you think/prefer it should or should not be. 2. whether the URL of concern is found embedded in the HTML text of a web page generated by Mailman as either a static page or by a Mailman CGI script. 3. whether the URL of concern is found embedded in the HTML text of a web page generated by something other than Mailman as either a static page or as one delivered by a CGI script. I must have been having a stupid day as I was not entirely clear from either the referenced bug report or your initial post about which of these interpretations I should adopt. Now see further comments below. Richard On Monday, August 11, 2003, at 01:14 pm, Tony wrote: Hi Richard, Quoting Richard Barrett [EMAIL PROTECTED]: Rob's bug report, as with yours, lack precision in specifying exactly which Mailman generated pages have links on them which contain (in the HTML text), absolute URLs referring to the wrong hostname. See my comments below on the broadfer questions that need to be answered in order to attack the perceived problem. Sorry, I thought it was clear enough. I will elaborate. I do not work with it myself, but I believe that the CPanel virtual hosting support software, which your hosting provider may be using, does perform some trickery to help avoid conflicts between list names on different virtual hosts. If your hosting provider is using that and something related to it is misconfigured then this may be contributing to the problem. Correct. The list directory gets names listname_domain to avoid conflicts with any other similarly named lists. CPanel is what is being used in this case. This means that any other virtual host on the server can access the mail archives by providing the correct path name to the list. When you say if the archive is public, then the address is http://myhostingprovidersservername.com/pipermail/listname; what precisely do you mean? What I mean is that the link to the archives, and only this link, from what I can see, shows the hosting provider's server name and not the virtual domain for the client. Example: I have a list called test on clientdomain1. The path to the list and all the admin pages etc is http://clientdomain1/mailman/whatever/test_clientdomain1/ This list could also be accessed by another virtual domain on the same server as: http://clientdomain2/mailman/whatever/test_clientdomain1/ When the archives are set to public, the archive address is: http://clientdomain1/mailman/private/test_clientdomain1/ Did you mean the statement immediately above or are you just reflecting on the fact that a public list is still available through its private list URL? When the list archives are set to public, then the archive address is: http://hostingproviderservername/pipermail/test_clientdomain1/ I would expect this to read: http://clientdomain1/pipermail/test_clientdomain1/ or similar. This appears the same on both the main page for the list and in the admin interface. Just to confirm; do you mean the web pages returned by the URLs http://clientdomain1/mailman/listinfo/test_clientdomain1 and http://clientdomain1/mailman/admin/test_clientdomain1? I am now talking about plain vanilla, unmodified, MM 2.1.2 code. The GetBaseArchiveURL() function used to generate the links to both public and private list archives. Its operation is subtly different in two cases although both depend upon the values in the VIRTUAL_HOSTS dictionary which
Re: [Mailman-Users]HandlerAPE error: WAS :Listserv wide announcements?
At 3:33 PM +0100 8/12/03, Richard Barrett wrote: On Tuesday, August 12, 2003, at 03:10 pm, Bruce Mitzit wrote: Hello, MM users--- After upgrading from mailman 2.0.9 to mailman-2.1.2, and tweaking all the things I could find to tweak, I still get this error emailed to me at the rate of about three a minute: Your cron job on urserver.uchicago.edu /usr/local/bin/python -S /usr/local/mailman/cron/qrunner produced the following output: Traceback (most recent call last): File /usr/local/mailman/cron/qrunner, line 89, in ? from Mailman.Handlers import HandlerAPI File /usr/local/mailman/Mailman/Handlers/HandlerAPI.py, line 26, in ? from Mailman.pythonlib.StringIO import StringIO ImportError: No module named pythonlib.StringIO With Mailman 2.1.2 the qrunner is no longer run as a cron job. The 2.1.2 qrunners are run as daemons started by the $prefix/bin/mailmanctl script. Looks like, maybe, you did not remove the mailman user's crontab before doing the update and the old 2.0.9 crontab is still trying to do stuff. Did you take a look at the section 'UPGRADING FROM 2.0.x to 2.1' in the UPGRADING file in your MM 2.1.2 build director as part of your tweakingy? Richard et. al.-- Well, yeah, I did read that thing. I did not remove (in Solaris 7) /var/spool/cron/cronjobs/mailman prior to the install. So, I've rm'd that cronjob. We'd been running that cron from root anyway, so I commented all out from there as well. I did a configure, make install all over again. I still am getting the same error message by email. Any suggestions? The original install of MM made me feel pretty smart. This one makes me feel dumb. Bruce -- -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Suscribers number
Hello I'm looking for a way to put the subscribers number of my lists on a web page that is not generated by MailMan. Is it possible ? Thank you -- Matthieu HUTIN Ceux qui ne luttent pas contre le mal, finissent par le servir -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] I was thinking.doc
On Wed, 2003-08-13 at 14:22, Anders Norrbring wrote: I was thinking... Could it be possible to edit the file '/etc/sysconfig/mailman' put in another parameter to get it reflected into the resulting mm_cfg.py when I change it in YaST2 and then run SuSEconfig ? Or are all parameters in the /etc/sysconfig files hardcoded? If it's possible, and anyone know how to manage it, can you please tell me how to put in a line for OWNERS_CAN_ENABLE_PERSONALIZATION ? Well that change rightfully should just go into mm_cfg.py and be left unchanged by whatever upgrade tool you use! Files in /etc/sysconfig are normally reserved for items that go on the command line for starting up a daemon. Just my .02 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
