Re: [Mailman-Users] Font customization in Pipermail archives
On 28/01/2005, at 10:35 AM, Jim Tittsler wrote: On Jan 27, 2005, at 00:36, Glen Low wrote: I can add things like Google Adsense code to the templates/en/article.html template, but as soon as I try to use FONT tags or STYLE tags, the archiver refuses to subsitute anything -- so my articles all end up with the % variables in them. Am I doing something wrong or is this a known problem? Without more details, it is hard to say, but I suspect you are doing something wrong. I use the STYLE tag and CSS to mark up my pipermail templates (including article.html) and it works as expected. I think if the dictionary interpolation fails, HyperArch simply gives up. You might check your template again to make sure you've not accidentally changed one of the dictionary keys. It turns out I was using STYLE=font-size:80% or FONT SIZE=80% and the % was tripping it up. Cheers, Glen Low --- pixelglow software | simply brilliant stuff www.pixelglow.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] sequence number patch
Hi I was trying to get the patch that adds sequence numbers to the subject prefix with mailman2.1.5 Do you have a version/patch for this realsease. (*Also in english is possible*) http://mm.tkikuchi.net/ from: http://mm.tkikuchi.net/ Cheers Sean _ Seán Reilly IT Systems Support Australia SoC Technology Centre Freescale Semiconductor Australia Pty Ltd. 2 Second Ave, Mawson Lakes, Adelaide 5095, Australia. [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] Phone: +61-8-8168-3637 Fax: +61-8-8168-3501 This e-mail, and any associated attachments have been classified as: General Business Information Freescale Internal Use Only Freescale Confidential Proprietary _ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] 'anonymous list ' setting
I'm running ver 2.1.1 in my general settings i have this option set to no, however when a poster sends a message, its not displaying senders name. its displaying the list name. its acting as if i had this option set to yes Hide the sender of a message, replacing it with the list address (Removes From, Sender and Reply-To fields) (Edit anonymous_list) is their another setting that i'm overlooking ? is this a bug that got fix in a later edition? Help!!! Grisel Montes Information Systems Mgr NYS Trial Lawyers Association 132 Nassau Street 2nd Fl New York, NY 10038 p 212.349.5890 f 212.608.2310 [EMAIL PROTECTED] www.nystla.org -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Strange bounce messages - why is it allowed throughand how do I find out?
On Tue, 2005-01-25 at 17:24, Mark Sapiro wrote: In the mailman/logs/post log file it just says that [EMAIL PROTECTED] posted to the list at this or that time. I'm both bewildered and estranged - what is this? And how do I find out why it is allowed to post to the list? Here's a possible scenario: A digest is sent to a subscribed address that is no longer valid. The receiving MTA is broken and sends a bounce message to the Reply-To: address of the digest (instead of the envelope sender, Sender: or Errors-To: address) which is the list. A related question: what are the requirements to such bounce messages so that Mailmans automatic (switched on in this case) bounce processing will take them as bounces and flag the user, etc? -- Mvh. Lars Bungum[EMAIL PROTECTED] OpenPGP: E2C5C0A2 Copyleft Software AS Telefon: +47 4000 3775 Telefaks : +47 21 93 33 71 Mobiltelefon : +47 92 04 61 35 Organisasjonsnummer: 982 116 252 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Mailman 2.1.5 VERP / Sendmail
Greetings. I'm evaluating Mailman (2.1.5) on some test lists, and seem to be having a problem getting VERP enabled. I've set what seem like reasonable values in mm_cfg.py (please see below). However, envelope From addresses are still un-VERPed (e.g. [EMAIL PROTECTED]) [testing on non-digest immediate delivery messages of course]. Two other questions: I assume that with sendmail it's necessary to build an alias file to handle the returning VERP bounces, since no intrinsic mechanism for this exists within sendmail itself? Also, I was surprised to discover that my mm_cfg.py file gets overwritten with the empty distribution version if make install is re-run. I had been under the impression that mm_cfg.py wouldn't be overwritten in such a case. Any suggestions on these issues would be appreciated. Thanks very much. --Lauren-- # These variables control the format and frequency of VERP-like delivery for # better bounce detection. VERP is Variable Envelope Return Path, defined # However, we're technically only VERP-like because we're doing the envelope # The first variable describes how to encode VERP envelopes. It must contain VERP_FORMAT = '%(bounces)s+%(mailbox)s=%(host)s' VERP_REGEXP = r'^(?Pbounces[^+]+?)\+(?Pmailbox[^=]+)=(?Phost[EMAIL PROTECTED])@.*$' # VERP format and regexp for probe messages VERP_PROBE_FORMAT = '%(bounces)s+%(token)s' VERP_PROBE_REGEXP = r'^(?Pbounces[^+]+?)\+(?Ptoken[EMAIL PROTECTED])@.*$' # A perfect opportunity for doing VERP is the password reminders, which are # VERPs on all password reminders. VERP_PASSWORD_REMINDERS = No # individual recipient. Set this to Yes to enable VERPs on all personalized VERP_PERSONALIZED_DELIVERIES = Yes # And finally, we can VERP normal, non-personalized deliveries. However, # often to VERP regular deliveries. This is the interval, in number of # messages, to do a VERP recipient address. The same variable controls both # regular and digest deliveries. Set to 0 to disable occasional VERPs, set to # 1 to VERP every delivery, or to some number 1 for only occasional VERPs. VERP_DELIVERY_INTERVAL = 1 # For nicer confirmation emails, use a VERP-like format which encodes the # Format is like VERP_FORMAT above, but with the following substitutions: VERP_CONFIRM_FORMAT = '%(addr)s+%(cookie)s' # This is analogous to VERP_REGEXP, but for splitting apart the # VERP_CONFIRM_FORMAT. VERP_CONFIRM_REGEXP = r'^(?Paddr[^+]+?)\+(?Pcookie[EMAIL PROTECTED])@.*$' # Set this to Yes to enable VERP-like (more user friendly) confirmations VERP_CONFIRMATIONS = Yes -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Interference from Cpanel mailman?
On 28/01/2005, at 12:39 PM, Mark Sapiro wrote: It's all very puzzling since the thelist-request obviously got through the system! It puzzles me too, but it looks like the MTA that generated it is at ESC13.midphase.com and is Exim 4.43. I don't know if this is coming into play here, but Exim can be configured to automatically recognize Mailman addresses and do the piping without explicit aliases. If this is the cPanel web host (also running Mailman) that you refer to, that's likely what's happening here. There is an Exim configuration document at http://www.exim.org/howto/mailman21.html which you might look at to see if there might be a way to let Exim do its Mailman thing in general and not do it for your lists. Sorry for the noise -- it seems I had tried to configure a mailing list of the same name with cpanel, but didn't succeed and it left forwarders in those names to the Cpanel mailman. I've rectified it with the web host and everything's hunky-dory now. Cheers, Glen Low --- pixelglow software | simply brilliant stuff www.pixelglow.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] sequence number patch
Reilly Sean-A6500C wrote: Hi Hi, I was trying to get the patch that adds sequence numbers to the subject prefix with mailman2.1.5 Do you have a version/patch for this realsease. (*Also in english is possible*) The numbering subject feature was integreated in mailman-2.1.6 (beta 2). Although the release is still in beta, it also includes bug fixes of 2.1.5 and in a stable state. http://mm.tkikuchi.net/ from: http://mm.tkikuchi.net/ Grab it from http://mm.tkikuchi.net/mailman-2.1.6b2.tgz Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] mailmanlistinfo without slash
- Original Message - From: Mark Sapiro [EMAIL PROTECTED] To: John Fleming [EMAIL PROTECTED]; mailman-users@python.org Sent: Thursday, January 27, 2005 11:08 PM Subject: Re: [Mailman-Users] mailmanlistinfo without slash John Fleming wrote: Well, it doesn't like bin/arch as above because the archive is empty: Luke:/var/lib/mailman/bin# ./arch --wipe sked snip Cannot open mbox file /var/lib/mailman/archives/private/sked.mbox/sked.mbox: [Errno 2] No such file or directory: '/var/lib/mailman/archives/private/sked.mbox/sked.mbox' Luke:/var/lib/mailman/bin# I also tried just ./arch without the --wipe and got the same error. *** I did create a brand new test list, and the link is CORRECT for that list, so fix_url after adding the trailing slash did fix the problem. Now to get the existing lists fixed - maybe. I intend for these lists to NOT have archives, so it's academic for existing lists. I just would like fix it so that the incorrect link doesn't appear if someone goes there out of curiosity and then hits the listinfo link to get back. I guess I might have to save the config and recreate the lists if I really want the link fixed that badly. Thanks Mark and Tokio for your help - Future lists won't have this problem! - John Tokio's suggestion to move (or copy) lists/listname/config.pck aside and then remove and recreate the list and then move the config.pck back is a good one, but a simpler idea is if there is no archives/private/listname.mbox/listname.mbox file, just do bin/arch --wipe sked /dev/null or whatever your other list names might be. I tested that this time and it works :-) The above seemed to work. I restarted Mailman, and then when clicking the Archives link on the Listinfo page, I was taken to Forbidden You don't have permission to access /pipermail/sked/ on this server. I thought maybe I just needed to rebuild the archive, so I did that, but same error. I looked at the permissions of /var/lib/mailman/archives/private/sked.mbox and it is the same as my other lists that don't give the FORBIDDEN error - group-list, owner www-data, 2775 (set GID). Which page exactly has incorrect permissions? Here's the bin/arch run: Luke:/var/lib/mailman/bin# ./arch --wipe sked /dev/null Traceback (most recent call last): File ./arch, line 187, in ? main() File ./arch, line 166, in main shutil.rmtree(mlist.archive_dir()) File /usr/lib/python2.3/shutil.py, line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing /var/lib/mailman/archives/private/sked Luke:/var/lib/mailman/bin# -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.1 - Release Date: 1/27/2005 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Customizing listinfo
Hi All, I've successfully customized listinfo.html but that seems to only take for the individual lists and not the overview page, e.g. http://www.pixelglow.com/lists/listinfo/ is not custom but http://www.pixelglow.com/lists/listinfo/macstl-dev/ is customized The listinfo.html I used was in templates/en, and I'm using English (US) throughout. What gives? Cheers, Glen Low --- pixelglow software | simply brilliant stuff www.pixelglow.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] cron for which user?
Hi All, I had followed the Mac OS X install instructions at http://mail.python.org/pipermail/mailman-users/2004-September/ 039600.html which say to install the crontab under su -- is that correct? should not the crontab be under the mailman user instead? Cheers, Glen Low --- pixelglow software | simply brilliant stuff www.pixelglow.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] failure to post to list
This may not be strictly a Mailman problem, but a problem posting to a Mailman list nonetheless. A specific list owner posts a message to a list. The maillog (I use Postfix) shows: maillog.1:Jan 27 16:31:27 webhost postfix/local[25275]: EBD2A4E5DF: to=[EMAIL PROTECTED], relay=local, delay=1, status=sent (|/l ists/mail/mailman post mylist) The mailman post log should show something like: post:Jan 28 07:31:05 2005 (3196) post to mylist from [EMAIL PROTECTED], size=3512, message-id=372EFF9FE4E42E419C978E7A305DC5FE082C8C09@ exsalem5.wherever.org, success However, there is no entry in the post log and the message is never delivered. This is a consistent problem for this particular person. There are no error messages sent back to her or messages to me as the mailman-owner. I am just sitting here scratching my head, wondering what to do next. Does anyone have any ideas what might be happening? -- Christopher Adams -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] cron for which user?
On Fri, 2005-01-28 at 23:57 +0800, Glen Low wrote: I had followed the Mac OS X install instructions at http://mail.python.org/pipermail/mailman-users/2004-September/ 039600.html which say to install the crontab under su -- is that correct? should not the crontab be under the mailman user instead? FWIW, different versions of cron and different UNIX's have different rules on who can install cron jobs. So this is really specific to the particular cron implementation, I'm not a Mac OS X user, but I think what is being suggested is that you need to be root to install the crontab, but execute the job under the mailman user (e.g. -u mailman). In other words I think you need to be root to add this set of cron jobs, or at least that would be my interpretation. HTH, -- John Dennis [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] cron for which user?
On Fri, 28 Jan 2005, Glen Low wrote: Hi All, I had followed the Mac OS X install instructions at http://mail.python.org/pipermail/mailman-users/2004-September/ 039600.html which say to install the crontab under su -- is that correct? should not the crontab be under the mailman user instead? Well, as the author of those instructions, all I can say is it works as written and that those instructions are part of the original instructions that I did not write but incorporated into my updated procedure. So if you think there's a more correct way to do it, try it and let us know if it works. -- Larry Stone [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Customizing listinfo
Glen Low wrote: I've successfully customized listinfo.html but that seems to only take for the individual lists and not the overview page, e.g. http://www.pixelglow.com/lists/listinfo/ is not custom but http://www.pixelglow.com/lists/listinfo/macstl-dev/ is customized The former page is not based on a template. It is built on the fly by Mailman/Cgi/listinfo.py -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] 'anonymous list ' setting
Grisel Montes wrote: I'm running ver 2.1.1 in my general settings i have this option set to no, however when a poster sends a message, its not displaying senders name. its displaying the list name. its acting as if i had this option set to yes Have you seen http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq02.003.htp -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] cpoying lists into mailman via commandline
Hi all I am currently in the process of moving all my university's mailing lists from majordomo to Mailman. I think I got most things figured out, I wrote a few scripts that generate the new lists and add all the members, no problem there. But there's one thing I am still unsure about. It seems that per default new members in a list are moderated for their first few posts. I also know there is an option somewhere in the webinterface to switch that off. However, it's quite a lot of mailing lists, so I'd rather not switch them all to unmoderated by hand but rather include it in my script or change the Default alltogether. Is there anything I could do to solve that? Thanks very much in advance, Meike -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] We're sorry, we hit a bug!
Hi all, I am running mailman 2.1.5 and when i try to enter the listinfo site i get this message in my browser: =START== Bug in Mailman version 2.1.5 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: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. STOP= When i look in the apache errorlog i find the following error-message: =START== Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] [- Mailman Version: 2.1.5 -] [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] [- Traceback --] [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] Traceback (most recent call last): [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] File /usr/lib/mailman/scripts/driver, line 241, in ? [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] run_main() [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] File /usr/lib/mailman/scripts/driver, line 69, in run_main [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] import xml.sax.saxutils [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] ImportError: No module named xml.sax.saxutils [Fri Jan 28 20:07:11 2005] [error] [client 62.251.80.209] [Mailman: low level unrecoverable exception] STOP= It seems that there is something wron with python module xml.sax.saxutils. Anyone any clues? -- Kind Regards / Met vriendelijke groet, Johan Barelds -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] We're sorry, we hit a bug!
Hi Dan, Thanks for the quick reply. Just found out that the Python module xml wasn't installed. After i installed it the bug was gone. Strange that this isn't checked in the update indeed! (running SuSE 9.2) Thanks anyway. Grz. Johan Op vrijdag 28 januari 2005 20:22, schreef u: On Jan 28, 2005, at 1:13 PM, Johan Barelds wrote: It seems that there is something wrong with python module xml.sax.saxutils. Anyone any clues? I don't remember the exact answer, but this has been discussed and a fix given on this list just within the last few days, so a quick search of the archives should find the answer. This is on SuSE? I believe the RPM you used to update mailman doesn't check for dependencies. Dan -- Kind Regards / Met vriendelijke groet, Johan Barelds Good-IT! Tel.+31(0)70-3965230Strijplaan 320 Mob.+31(0)6-542537502285 HZ Rijswijk(ZH) [EMAIL PROTECTED] http://www.good-it.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] mailmanlistinfo without slash
John Fleming wrote: - Original Message - From: Mark Sapiro [EMAIL PROTECTED] snip bin/arch --wipe sked /dev/null or whatever your other list names might be. I tested that this time and it works :-) The above seemed to work. I restarted Mailman, and then when clicking the Archives link on the Listinfo page, I was taken to Forbidden You don't have permission to access /pipermail/sked/ on this server. I thought maybe I just needed to rebuild the archive, so I did that, but same error. I looked at the permissions of /var/lib/mailman/archives/private/sked.mbox and it is the same as my other lists that don't give the FORBIDDEN error - group-list, owner www-data, 2775 (set GID). Which page exactly has incorrect permissions? /var/lib/mailman/archives/private/sked/index.html The web accessable archive is in the sked/ directory. The sked.mbox/ directory only contains the sked.mbox file which is the archive in mbox format. Here's the bin/arch run: Luke:/var/lib/mailman/bin# ./arch --wipe sked /dev/null Traceback (most recent call last): File ./arch, line 187, in ? main() File ./arch, line 166, in main shutil.rmtree(mlist.archive_dir()) File /usr/lib/python2.3/shutil.py, line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing /var/lib/mailman/archives/private/sked Luke:/var/lib/mailman/bin# It looks like there was no existing archive when you ran bin/arch --wipe sked /dev/null so the command failed and didn't build a new archive. The archive is gone because the previous bin/arch --wipe sked which failed on the lack of the sked.mbox file had removed the archive before failing. So now try bin/arch sked /dev/null i.e. without the --wipe. This should build a new, empty archive. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] vette log/discarded messages
I am following up a previous message about failure to post to a list. As I said, the Postfix/maillog shows that it was sent. However, the mailman/post log shows nothing. The mailman/vette log shows: Jan 28 11:32:23 2005 (20467) Message discarded, msgid: [EMAIL PROTECTED] I am sending as a non-moderated member and have tried changing various options for sending from non-members, moderated members, etc. It is set to discard automatically from a non-member. However, it looks like it is just discarding everything from everyone. I have many other lists and have never seen this behavior. The only thing significantly different about this list is that there are 38,000 members and the list is updated monthly by a script. It is possible that file permissions were changed, but I checked that and it doesn't seem to be anything that would affect this. Any ideas? Christopher Adams -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] ValueError: unpack list of wrong size
I'm having problems which I have solved but in doing so I've identified a problem in both Apple Mail and Mailman. I found this post which pointed me in the right direction: http://mail.python.org/pipermail/mailman-users/2004-October/040337.html After going through all my shunted files, I've isolated it to one message send with Apple Mail with a PDF attachment. The message contains these surprising MIME headers ( quoted for safety): --Apple-Mail-1--377637739 Content-Transfer-Encoding: base64 Content-Type: application/pdf; x-unix-mode=0644; name=Software Application Enhancement For Metro's Urban Growth Simulation Model.pdf Content-Disposition: inline; filename*0=Software Application Enhancement For Metro's Urban Growth Simula; filename*1=tion Model.pdf This, I suspect, is the cause of the problem. If Tokio or other MM developers would like access to the .pck, I can provide it (but I'd rather not publish it to the entire world). Wil -- Wil Cooley [EMAIL PROTECTED] Naked Ape Consultinghttp://nakedape.cc * * * * Linux, UNIX, Networking and Security Solutions * * * * -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] vette log/discarded messages
Christopher Adams wrote: I am following up a previous message about failure to post to a list. As I said, the Postfix/maillog shows that it was sent. However, the mailman/post log shows nothing. The mailman/vette log shows: Jan 28 11:32:23 2005 (20467) Message discarded, msgid: [EMAIL PROTECTED] I am sending as a non-moderated member and have tried changing various options for sending from non-members, moderated members, etc. It is set to discard automatically from a non-member. However, it looks like it is just discarding everything from everyone. I have many other lists and have never seen this behavior. The only thing significantly different about this list is that there are 38,000 members and the list is updated monthly by a script. It is possible that file permissions were changed, but I checked that and it doesn't seem to be anything that would affect this. And previously However, there is no entry in the post log and the message is never delivered. This is a consistent problem for this particular person. There are no error messages sent back to her or messages to me as the mailman-owner. I'm confused as to whether this affects all users, just one user or maybe a few? My thought is that you may have USE_ENVELOPE_SENDER = Yes in mm_cfg.py and this person's e-mail arrives with a different envelpe sender than her subscribed address. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Two questions
Mark Sapiro wrote:
Erin Dalzell wrote:
If you're changing things rather than just adding, try putting
VIRTUAL_HOSTS.clear() ahead of your mm_cfg.py entries.
That was the first thing I tried. Just to make sure this isn't something
weird. I am seeing this on the site wide mailing list mailman. I haven't
tried other mailing lists yet.
It's hard to say what might be happening without knowing what exactly
you're doing in mm_cfg.py, but some things which are set in
Defaults.py are also used in Defaults.py. Thus simply changing the
setting in mm_cfg.py isn't enough, you also have to redo (maybe after
undoing) the usage.
The most obvious example is DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST.
These are set in Defaults.py and then used in Defaults.py in
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
Thus if either or both is changed in mm_cfg.py, the
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
must be repeated after the change, or to be completely sure, clear the
existing entries and then re-add as in
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
If you're still having problems, please provide the contents of your
mm_cfg.py and a description of the actual problem behavior.
MTA = Postfix
IMAGE_LOGOS = '/icons/'
VIRTUAL_HOSTS.clear()
add_virtualhost('www.thedalzells.org')
My process is:
* change the file
* Run fix_url
* restart mailman
The problem is that the links on the site-wide Mailman list aren't
changed to whatever I have the the add_virtualhost call.
So I have made the changes in Defaults.py, which you are not supposed to do.
Thanks
emd
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] cron for which user?
On 1/28/2005 8:43, Larry Stone [EMAIL PROTECTED] wrote: On Fri, 28 Jan 2005, Glen Low wrote: Hi All, I had followed the Mac OS X install instructions at http://mail.python.org/pipermail/mailman-users/2004-September/ 039600.html which say to install the crontab under su -- is that correct? should not the crontab be under the mailman user instead? Well, as the author of those instructions, all I can say is it works as written and that those instructions are part of the original instructions that I did not write but incorporated into my updated procedure. So if you think there's a more correct way to do it, try it and let us know if it works. In Mac OS X (and fairly commonly elsewhere, but I don't claim everywhere), a non-privileged user can execute the crontab command fine but can't use the -u username option. So if you can become the mailman user you could run the command that way...or run it as root using -u, or run sudo crontab -u mailman blah blah (I have had no need to enable the root account, and my Mac OS X time goes back to day 1 of 10.0). I have not installed Mailman on Mac OS X, nor used the Mailman which Apple mangles and installs in Server. ---John -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Solved - Re: [Mailman-Users] mailmanlistinfo without slash
- Original Message - From: Mark Sapiro [EMAIL PROTECTED] To: John Fleming [EMAIL PROTECTED]; Mark Sapiro [EMAIL PROTECTED]; mailman-users@python.org Sent: Friday, January 28, 2005 3:00 PM Subject: Re: [Mailman-Users] mailmanlistinfo without slash John Fleming wrote: - Original Message - From: Mark Sapiro [EMAIL PROTECTED] snip bin/arch --wipe sked /dev/null or whatever your other list names might be. I tested that this time and it works :-) The above seemed to work. I restarted Mailman, and then when clicking the Archives link on the Listinfo page, I was taken to Forbidden You don't have permission to access /pipermail/sked/ on this server. I thought maybe I just needed to rebuild the archive, so I did that, but same error. I looked at the permissions of /var/lib/mailman/archives/private/sked.mbox and it is the same as my other lists that don't give the FORBIDDEN error - group-list, owner www-data, 2775 (set GID). Which page exactly has incorrect permissions? /var/lib/mailman/archives/private/sked/index.html The web accessable archive is in the sked/ directory. The sked.mbox/ directory only contains the sked.mbox file which is the archive in mbox format. Here's the bin/arch run: Luke:/var/lib/mailman/bin# ./arch --wipe sked /dev/null Traceback (most recent call last): File ./arch, line 187, in ? main() File ./arch, line 166, in main shutil.rmtree(mlist.archive_dir()) File /usr/lib/python2.3/shutil.py, line 142, in rmtree raise exc[0], (exc[1][0], exc[1][1] + ' removing '+arg) OSError: [Errno 2] No such file or directory removing /var/lib/mailman/archives/private/sked Luke:/var/lib/mailman/bin# It looks like there was no existing archive when you ran bin/arch --wipe sked /dev/null so the command failed and didn't build a new archive. The archive is gone because the previous bin/arch --wipe sked which failed on the lack of the sked.mbox file had removed the archive before failing. So now try bin/arch sked /dev/null i.e. without the --wipe. This should build a new, empty archive. I think that's right. I've done several things since my last post, and now everything's working great and life is good! I'd like to summarize for my own record and in case there's anyone as inept as me lurking here: 1. The original problem was that on a list's archive page, there was an incorrect link to More Information. That link was missing a slash, i.e. /mailmanlistinfo/listname. Several ways to handle that were mentioned, but I ended up saving the lists' .pck files and then deleting the lists and recreating and substituting the old .pck files. That fixed the original problem, and the missing slash appeared. However, there were now some virtual domain/weird link problems. When I went to list A's archive page, the More Information link was to another domain, the main domain of the site. If I clicked this link, I actually went to the correct page for list A, even with the correct domain (although technically incorrect in the link). When I started looking around and messing with other lists, things got really confusing! First I was told I should use fix_url.py. Then we decided I would also need to rebuild the archive after running fix_url.py to get the link corrected on the Archives page. 3. After some learning of how to use withlist, fix_url, and arch, I methodically went through each of my lists (I only have 4), running first fix_url and then rebuilding the archive. This got confusing to this newbie because when I rebuilt the archive, the ownership of the archive directory changed to the user I was running as rather than www-data. The owner of the archive has to be www-data or apache wouldn't let me surf that page later. 4. So for each list, I ran: bin/withlist -r -l fix_url listname --urlhost=desireddomain bin/arch --wipe listname /dev/null Then I changed the ownership of /archives/listname (and maybe /archives/listname.mbox) to www-data. These were both group list and didn't need to be changed. Then I restarted mailman (unnecessary?) Now when I click on the Archives link on a listinfo page, the link contains the proper slashes, and I am taken to a page that says there are no archives. The link for More Information on that archive page uses the correct domain! YAY! Life is good! I'm sure most of you knew all of this, but I've learned a lot. FAQ or no, when someone tells a newbie to run fix_url.py, you'd be surprised how difficult it can turn out to be. ;-) Thanks especially to Mark and Tokio and to everyone for your patience and bandwidth. - John -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.8.1 - Release Date: 1/27/2005 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives:
[Mailman-Users] Virus Just Got Through on TOTALLY MODERATED list.
Guys, I just had a small problem. A virus was just sent to all the list members which had spoofed the moderator's email address. No requires approval message was sent, despite the fact that everyone (even the moderator) has the mod bit set to on. http://securityresponse.symantec.com/avcenter/venc/data/[EMAIL PROTECTED] Are there any known and open bugs in 2.1.5 that would allow this behavior? Is there any way of telling in the headers (or archives, or logs?) how a message was approved? Here's the headers: Return-Path: [EMAIL PROTECTED] Received: from prime.gushi.org (localhost [IPv6:::1]) by prime.gushi.org (8.13.1/8.13.1) with ESMTP id j0S2GH5b080701 for [EMAIL PROTECTED]; Thu, 27 Jan 2005 22:50:56 -0500 (EST) Received: from ROBERTA.net (pcp08579508pcs.alxndr01.va.comcast.net [68.83.208.54]) by prime.gushi.org (8.13.1/8.13.1) with SMTP id j0S2FV8o080233 for [EMAIL PROTECTED]; Thu, 27 Jan 2005 21:15:35 -0500 (EST) Date: Thu, 27 Jan 2005 21:05:09 -0500 Any ideas? -Dan Mahoney -- Ca. Tas. Tro. Phy. -John Smedley, March 28th 1998, 3AM Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Two questions
Erin Dalzell wrote:
MTA = Postfix
IMAGE_LOGOS = '/icons/'
VIRTUAL_HOSTS.clear()
add_virtualhost('www.thedalzells.org')
My process is:
* change the file
* Run fix_url
* restart mailman
The problem is that the links on the site-wide Mailman list aren't
changed to whatever I have the the add_virtualhost call.
So I have made the changes in Defaults.py, which you are not supposed to do.
I would do the following:
Put Defaults.py back to it's original state.
Put the following in mm_cfg.py
MTA = Postfix
IMAGE_LOGOS = '/icons/'
DEFAULT_URL_HOST = 'www.thedalzells.org'
DEFAULT_EMAIL_HOST = 'thedalzells.org'
VIRTUAL_HOSTS.clear()
add_virtualhost('www.thedalzells.org')
The last could equally well be add_virtualhost(DEFAULT_URL_HOST) or
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) as all three are
equivalent in this case.
Then do
bin/withlist -l -a -r fix_url
and finally restart mailman.
If this doesn't work, then I don't know what's going on.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virus Just Got Through on TOTALLY MODERATED list.
Maybe you should install a virus scanning feature to your mailer? I use mimedefang which has a hook to many different virus scanning products. I use f-prot. My platform: Fedora Core 2 Sendmail 8.13.1 mimedefang 2.48 f-prot linux ws 4.4.2 this configuration discards infected email messages. Jeff g. Dan Mahoney, System Admin wrote: Guys, I just had a small problem. A virus was just sent to all the list members which had spoofed the moderator's email address. No requires approval message was sent, despite the fact that everyone (even the moderator) has the mod bit set to on. http://securityresponse.symantec.com/avcenter/venc/data/[EMAIL PROTECTED] Are there any known and open bugs in 2.1.5 that would allow this behavior? Is there any way of telling in the headers (or archives, or logs?) how a message was approved? Here's the headers: Return-Path: [EMAIL PROTECTED] Received: from prime.gushi.org (localhost [IPv6:::1]) by prime.gushi.org (8.13.1/8.13.1) with ESMTP id j0S2GH5b080701 for [EMAIL PROTECTED]; Thu, 27 Jan 2005 22:50:56 -0500 (EST) Received: from ROBERTA.net (pcp08579508pcs.alxndr01.va.comcast.net [68.83.208.54]) by prime.gushi.org (8.13.1/8.13.1) with SMTP id j0S2FV8o080233 for [EMAIL PROTECTED]; Thu, 27 Jan 2005 21:15:35 -0500 (EST) Date: Thu, 27 Jan 2005 21:05:09 -0500 Any ideas? -Dan Mahoney -- Ca. Tas. Tro. Phy. -John Smedley, March 28th 1998, 3AM Dan Mahoney Techie, Sysadmin, WebGeek Gushi on efnet/undernet IRC ICQ: 13735144 AIM: LarpGM Site: http://www.gushi.org --- -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ -- Law of Procrastination: Procrastination avoids boredom; one never has the feeling that there is nothing important to do. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virus Just Got Through on TOTALLY MODERATED list.
Agreed: I run Fedora Core 2 with Mailman on one of my mail servers, using MIMEDefang with SpamAssassin and Clam Antivirus, along with having my lists fully moderated. I've never had even one spam or virus get through (lists have been up for several years; started with RedHat 6.2 or 7.1 and Mailman 2.0.7, as I recall). Bob On Fri, 28 Jan 2005, Jeff Groves wrote: Maybe you should install a virus scanning feature to your mailer? I use mimedefang which has a hook to many different virus scanning products. I use f-prot. My platform: Fedora Core 2 Sendmail 8.13.1 mimedefang 2.48 f-prot linux ws 4.4.2 this configuration discards infected email messages. Jeff g. Bob Sully - Simi Valley, California, USA http://www.malibyte.net http://www.malibyte.com There will be no white flag above my door. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virus Just Got Through on TOTALLY MODERATED list.
Dan Mahoney wrote: I just had a small problem. A virus was just sent to all the list members which had spoofed the moderator's email address. No requires approval message was sent, despite the fact that everyone (even the moderator) has the mod bit set to on. http://securityresponse.symantec.com/avcenter/venc/data/[EMAIL PROTECTED] Are there any known and open bugs in 2.1.5 that would allow this behavior? I don't think so. If as you say, all member's mod bit is on, and no one is in accept_these_nonmembers, and generic_nonmember_action is other than Accept, then the only way I know for a message to get through without explicit moderator action is for the message to contain an Approved: header (or first line of body) with the list password. I'd guess that any message generated by a windows e-mail worm would not have this. Thus, I don't know how it got through. Is there any way of telling in the headers (or archives, or logs?) how a message was approved? If it was actually approved, there should be an entry in Mailman's vette log. If it just went through, I don't think there is any way to know why at this point. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] cpoying lists into mailman via commandline
Meike Reichle wrote: I am currently in the process of moving all my university's mailing lists from majordomo to Mailman. I think I got most things figured out, I wrote a few scripts that generate the new lists and add all the members, no problem there. But there's one thing I am still unsure about. It seems that per default new members in a list are moderated for their first few posts. I also know there is an option somewhere in the webinterface to switch that off. However, it's quite a lot of mailing lists, so I'd rather not switch them all to unmoderated by hand but rather include it in my script or change the Default alltogether. Is there anything I could do to solve that? Well, I don't know what exactly your scripts do, but what you want is after creating the list and before adding any members set the list's default_member_moderation variable to No. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] Virus Just Got Through on TOTALLY MODERATED list.
Dan Mahoney, System Admin wrote: Guys, I just had a small problem. A virus was just sent to all the list members which had spoofed the moderator's email address. No requires approval message was sent, despite the fact that everyone (even the moderator) has the mod bit set to on. http://securityresponse.symantec.com/avcenter/venc/data/[EMAIL PROTECTED] OK, I'm just speculating here... what if there's a virus/trojan out that is able to take email that a user had already sent (email in the sent folder), and resend it with a virus payload (in this case, the beagle.ba virus above)? If it grabbed an email that the moderator had sent to the list with the Approved: password included, and just appended the virus payload, it would result in what you saw, right? What was the subject of the virus-laden email, was it a subject that had been previously posted to your list. soapbox This is why my lists don't allow any attachments at all. IMHO, the benefits of making it easy for people to send files to a mailing list are outweighed by the costs (when a virus gets thru). I tell posters to put the file on a server and then email a post with a link to the file. /soapbox jc -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
