Re: [Mailman-Users] Problem enforcing text/plain posts only policy
On Wed, 2002-07-17 at 07:47, JC Dill wrote: On 10:57 AM 7/16/02, Tim Hutchinson wrote: Thank you for the suggestion. Unfortunately, although this sounds like a better solution, I'm just a list owner and don't have access to the mailman installation (and I'd be surprised if our ISP would be prepared to do this, either). I'd be more surprised if your ISP would refuse to do it. Stripping MIME off mailing list destined posts makes everyone's life easier. It helps ensure that the list can't be used to spread a virus, it helps ensure that unsubscribe requests are processed, etc. It's not that hard to install, and it's a huge value-add for the ISP. It would be a reason to immediately change ISP if my mailing list would break all signed e-mail. Also, there are many lists where file attachments are not that uncommon. While I do not like html mail, I doubt that generally stripping MIME is a good move. Any ISP should install that only on request for a specific list. cheers -- vbi -- secure email with gpg http://fortytwo.ch/gpg signature.asc Description: This is a digitally signed message part
[Mailman-Users] Perhaps an arb question but would really appreciate any help
Hi, I'm trying to found out where to set up the indentation formatting for messages in the archive , at the moment all the messages and their replies are not differentiated (one long list down the left hand side) so it is quite hard to tell where a thread starts. Any help would be greatly appreciated. TIA Geoff Robertson Myles Ahead Networking -- 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
[Mailman-Users] MAILMAN 2.0.12
Hi all,
I've upgraded from 2.0.8 to 2.0.12, but now I can't send email to the
list. The qrunner log this :
Jul 17 08:02:01 2002 qrunner(12122): Traceback (innermost last):
Jul 17 08:02:01 2002 qrunner(12122): File
/usr/local/apps/mailman/cron/qrunner, line 283, in ?
Jul 17 08:02:01 2002 qrunner(12122): kids = main(lock)
Jul 17 08:02:01 2002 qrunner(12122): File
/usr/local/apps/mailman/cron/qrunner, line 253, in main
Jul 17 08:02:01 2002 qrunner(12122): keepqueued =
dispose_message(mlist, msg, msgdata)
Jul 17 08:02:01 2002 qrunner(12122): File
/usr/local/apps/mailman/cron/qrunner, line 157, in dispose_message
Jul 17 08:02:01 2002 qrunner(12122): mlist.ParseMailCommands(msg)
Jul 17 08:02:01 2002 qrunner(12122): File
/usr/local/apps/mailman-2.0.12/Mailman/MailCommandHandler.py, line
123, in ParseMailCommands
Jul 17 08:02:01 2002 qrunner(12122): precedence =
msg.get('precedence', '').lower()
Jul 17 08:02:01 2002 qrunner(12122): AttributeError : 'string' object
has no attribute 'lower'
Any Idea ?
Thanks
--
Marco Induni
Universita` della Svizzera italiana
Servizi informatici / TI-EDU
Galleria 2
CH-6928 Manno (Switzerland)
E-mail: [EMAIL PROTECTED]
Tel./Fax: +41 91 610 94 01
--
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
[Mailman-Users] MAILMAN 2.0.12
Does anyone know if there's a RH 7.3 RPM out yet? I checked rpmfind.net but the latest version was 2.0.11. Thanks! :) Jim Hale --- http://hale.dyndns.org -- 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
Re: [Mailman-Users] Problem enforcing text/plain posts only policy
Please do not send attachments to the list. They are deleted, unopened. SD - Original Message - From: Adrian 'Dagurashibanipal' von Bidder [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 17, 2002 3:50 AM Subject: Re: [Mailman-Users] Problem enforcing text/plain posts only policy j)fju,z»j)b b²ÓYK ®Êr¶'¢¸!¶Úþf¢è®æj)fjåËbú?¨¥©î±êì1¨¥©Åm¶ÿà )ÊØhàýÈn)ÿ}ª°jr
Re: [Mailman-Users] Problem enforcing text/plain posts only policy
You replied without attachment, which leads to conclusion
that YOU have control of the option on your end.
Mailman FAQ Entry
3.10. How do I enforce a text/plain posts only policy?
In Privacy Options - Spam-specific posting filters
Hold posts with header value matching a specified regexp.
Content-Type: .*octet
Content-Type: .*oda
Content-Type: .*audio
Content-Type: .*image
Content-Type: .*alternative
Content-Type: .*digest
Content-Type: .*mixed
Content-Type: .*rich
Content-Type: .*html
Content-Type: .*video
Sample Rejection Message:
Content-Type: (from message header)
X-Mailer: (from message header)
Please configure your email client [1] to send text/plain messages to
this list. Instead of attachments, you should include any diagnostic
information as in-line text in the main message body.
[1] http://www.expita.com/nomime.html
Details:
Only messages with a Content-type: of text/plain and
multipart/signed are automatically posted to the list. All other
content-types are held for administrative action.
If you have any questions about this policy, please send them to
yourlist-admin@yourdomain.
An alternate solution is to use a mime stripping script. FAQ 1.8
explains how to do this.
SD
- Original Message -
From: Adrian 'Dagurashibanipal' von Bidder [EMAIL PROTECTED]
To: Support Desk [EMAIL PROTECTED]
Sent: Wednesday, July 17, 2002 8:08 AM
Subject: Re: [Mailman-Users] Problem enforcing text/plain posts only policy
| On Wed, 2002-07-17 at 14:03, Support Desk wrote:
| Please do not send attachments to the list.
| They are deleted, unopened.
| SD
|
| Please fix your mail system not to sent such message to mailing lists.
|
| And, btw, the attachment in question was a pgp signature. This is common
| on many lists, and I've not seen anybody complaining about it.
|
|
| cheers
| -- vbi
|
|
| - Original Message -
| From: Adrian 'Dagurashibanipal' von Bidder [EMAIL PROTECTED]
| To: [EMAIL PROTECTED]
| Sent: Wednesday, July 17, 2002 3:50 AM
| Subject: Re: [Mailman-Users] Problem enforcing text/plain posts only policy
| --
| secure email with gpg http://fortytwo.ch/gpg
|
|
| YK ®ÉX§X¬´Æ¢f§RÇ«²è®m¶ÿ¨¥§+a¢z+ùYùb²Ø§~æj)fj{¬z» j)fjq@Bm§ÿðÃ
r¶'¢¸?rßj¬
[Mailman-Users] Importing Archives From Listserv
Hello all, I've looked over the documentation on Mailman and can't find anything on this, so I have to ask: is there any way to import message archives from Listserv into Mailman? I'd like to move a list from Listserv into Mailman, but there are more than two years on archived messages from this list that I'd like to keep and possibly integrate into Mailman's own archives as well. Is this possible? If so, how? -- Victor Daniel a.k.a The MacNut [EMAIL PROTECTED][EMAIL PROTECTED] Listmom, ClarisWorks/AppleWorks email list: http://www.macnuthome.com/awlist And the Macintosh Personal Finance List: http://www.macnuthome.com/mailman/listinfo.cgi/macfinlist -- 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
Re: [Mailman-Users] Feedback?
This sounds a lot like what a weblog server does. A great example of this in action is http://www.slashdot.org. If you have access to a server that can run Zope, you should try a Zope product called Squishdot. I believe it does user feedback really well, though my experience with it is limited. Dennis On Tue, 16 Jul 2002, Nick Arnett wrote: Does anyone here know of any message feedback mechanism that can be added to Mailman? I'm looking to add a web-based rating mechanism. Initially, the idea is to let people give others negative feedback points, but the price of doing so is that you received a percentage of a point yourself, thus creating a disincentive for downgrading a lot of other people. I'm not interested in debating the ethics or efficacy of such a mechanism right now, but I'd be more than happy to hear suggestions about how to make it work properly. I expect it to be relatively simple -- addition of a code identifying the sender and recipient, which feed back via a CGI to Apache and then MySQL. I'm a bit concerned about the implicit slowdown in delivery, but I'm not looking at a high-volume list yet. That's the one-click approach. Otherwise, I could munge something into the archives, but that'll require login to identify who's voting. Any and all suggestions will be welcome. Pointers on the best place(s) to touch the code will be gratefully accepted. Nick -- 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
[Mailman-Users] Help for a Newbie!
Title: Message I am brand new at this and am setting up a mail list. I have run into a problem that may be my stupidity, but I can't figure it out. If someone posts something to a mail list that is off (rude, defamatory, illegal) I want to be able to delete the entry from the archive. I also want to delete all my "test messages" before I bring other people into the mail list. I have searched the FAQ's and although python.org FAQs includes an entry on removing a post (3.3), the solution depends on running a script or command. I have no idea how to do that or even how to find the archive (other than through the normal web browser interface). Can anyone give me some basic (noddy language) clues as to how to do this? Phil
[Mailman-Users] need advice on migrating existing Mailman to new hard drive
I sent this message to the list but received no response so thought I might try again. Thanks in advance to anyone who may be able to offer advice. I am installing a new hard drive in my server with a clean install of Redhat 7.3 and its updated Mailman RPM (version 2.0.11-1). I am looking for some advice on how to move all of the Mailman files (membership, archives, list configs, etc.) from the old drive to the new one safely. The old hard drive is running Redhat 7.1 with Mailman 2.0.5 using Sendmail. Randy Stoecker Professor of Sociology Moderator/Editor COMM-ORG: The On-Line Conference on Community Organizing and Development Department of Sociology and Anthropology University of Toledo Toledo, OH 43606 USA phone: 419-530-4975 fax: 419-530-8406 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
Re: [Mailman-Users] Problem enforcing text/plain posts only policy
On Tue, 16 Jul 2002, Chuq Von Rospach wrote: On 7/16/02 10:47 PM, JC Dill [EMAIL PROTECTED] wrote: I'd be more surprised if your ISP would refuse to do it. Stripping MIME off mailing list destined posts makes everyone's life easier. Except that's not where things are headed. Especially when you start dealing with non-english language stuff. Instead, we need to selectively strip UNSAFE content and stop going to LCD situations. But I know from previous discussions you won't agree with me on this, and I won't push the agenda right now... Mailman needs to have better support for MIME in digests and archives before not stripping all MIME makes sense. My users who were happiest when I started stripping all MIME were the digest recipients who previously had to wade through raw MIME. You can tell Mailman to send digests with each message as a MIME attachment, but that is harder for most people to browse using common MUAs. Two of the four stripping tools mentioned in the FAQ allow for selective stripping of content. I'll agree that my tool (stripmime) takes the most drastic approach of stripping everything. alex -- 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
RE: [Mailman-Users] Feedback?
Thanks for the suggestion, that that's not really what I'm after. I'm talking about adding that sort of functionality to the e-mail messages themselves, with links back to the server. I'm quite familiar with Slashdot, Zope, etc. Nick -Original Message- From: Dennis W Heltzel [mailto:[EMAIL PROTECTED]]On Behalf Of Dennis W Heltzel Sent: Wednesday, July 17, 2002 6:42 AM To: Nick Arnett Cc: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Feedback? This sounds a lot like what a weblog server does. A great example of this in action is http://www.slashdot.org. If you have access to a server that can run Zope, you should try a Zope product called Squishdot. I believe it does user feedback really well, though my experience with it is limited. -- 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
Re: [Mailman-Users] HowTo edit Archives by hand
I think this is already in the FAQ, but just in case, here is a brief run through for the 2.0.x series... The archives are found in: ~mailman/archives/private/ There are two subdirectories for each list: listname.mbox: This directory contains one file, a text based Mailbox with all the archived messages. This file is the *real* archive. listname : This directory contains all the manufactured Web/text files needed to display the archived messages. The files in this directory are all generated from the Mailbox found in the other directory. To edit out an email, - Take mailman off-line (stopping cron is effective for this). - Goto the Mailbox containing the archive - Edit this large file and remove the offending email Note: this is a large text based file containing many emails, each stacked on top of each other inside the file. Each email starts with a line like: From [EMAIL PROTECTED] Mon Mar 12 14:23 2002 There will be other lines in the email that look similar and start with From: (note the colon instead of a space) From: User Name user@domain These lines are header lines inside the email. - Once the offending emails are edited or removed, move the files in the current web files for the archive to a backup directory and run: ~mailman/bin/arch listname This will regenerate all the HTML files used by the archive. - Bring mailman back on-line (restart cron) Best of luck, Jon Carnes On Wednesday 17 July 2002 10:22 am, Phil Greenwood wrote: I am brand new at this and am setting up a mail list. I have run into a problem that may be my stupidity, but I can't figure it out. If someone posts something to a mail list that is off (rude, defamatory, illegal) I want to be able to delete the entry from the archive. I also want to delete all my test messages before I bring other people into the mail list. I have searched the FAQ's and although python.org FAQs includes an entry on removing a post (3.3), the solution depends on running a script or command. I have no idea how to do that or even how to find the archive (other than through the normal web browser interface). Can anyone give me some basic (noddy language) clues as to how to do this? Phil -- 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
[Mailman-Users] Extending mailman (adding config options)
Those of you following my previous emails (lamentably unanswered so far) will already know that I'm trying to extend mailman to add color-coded graphics to the archives to parse logwatch emails and such more efficiently. I'd like to have this configurable from the archive options page, so I was wondering what the standard structure for adding options is. Is there a premade set of mailman functions for extending this in a standard and non-kldugy way, and are they accessible as is from HyperArch.py? TIA, Laurence -- 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
[Mailman-Users] Re: Exim 4.05 Mailiman - Missing the Directors Configuration(update)
Hello Again,
| I'm assuming now that the Directors Config area in the runtime
| configuration file has been removed in 4.x
Correct. exim4 was revamped, and the router/director distinction was
removed.
Ok.. So when mailman's README.EXIM tells me to put files in the
Directors section, this should be the same as putting it in the ROUTERS
CONFIGURATION section as exim is no longer distinguishing between the
two.
| If so does anyone have any suggestions on the modifications required
| to a 4.05 setting to get mailman exim cooperating?
Convert the example director to a router.
I've tried to do this... I can't see how it would need any more
configuration.. However exim 4.05 seems to dislike the driver =
smartuser in the following (Now at the bottom of the Routers Config
section):
list_owner_director:
driver = smartuser
require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
suffix = -owner
new_address = ${lc:$local_part}-admin@${domain}
The error it gives me is as follows:
[root@learningpartnership exim.mike]# bin/exim -C configure -bV
Exim version 4.05 #3 built 13-Jul-2002 23:35:22
Copyright (c) University of Cambridge 2002
2002-07-16 10:31:21 Exim configuration error in line 438:
router list_owner_director: cannot find router driver smartuser
I've been searching for info on this error, but I can't seem to find
much of interest. Does exim 4.05 support a smartuser driver or has this
concept too been revised.
The Mailman 2.1 CVS tree has instructions on using exim4.
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/mailman/mailman/README.EXIM?rev=2.4content-type=text/vnd.viewcvs-markup
From this I'm guessing that
driver = smartuser
should be replaced by
driver = accept
But pretty much every line in the exim config looks like it would need
to be rewritten as
suffix = -request
new_address = ${lc:$local_part}-admin@${domain}
(and likely others)
prefix = owner-
all need to be rewritten for 4.0.5
I'm sure you can combine the data in the mailman instructions and
exim's spec to create the necessary transports and routers tailored to
your usage of mailman. If you have specific questions about certain
options or something, then by all means ask.
The are very different and I don't know enough about exim or mailman to
wade through the code and try to find something that 'may' work via
trial error. Could take years..
Is there a way to rewrite this easily for exim 4.05? What other
instructions are no longer useful in the new exim and can I just replace
them?
list_owner_director:
driver = smartuser
require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
suffix = -owner
new_address = ${lc:$local_part}-admin@${domain}
owner_list_director:
driver = smartuser
require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
prefix = owner-
new_address = ${lc:$local_part}-admin@${domain}
##
## Next 3 directors direct admin, request and list mail to the
appropriate
## transport. List existence is checked as above.
list_admin_director:
driver = smartuser
suffix = -admin
require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
transport = list_admin_transport
list_request_director:
driver = smartuser
suffix = -request
require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
transport = list_request_transport
list_director:
driver = smartuser
require_files = MAILMAN_HOME/lists/${lc:$local_part}/config.db
transport = list_transport
(I haven't personally
configured mailman so I can't really give any better info than that)
That makes it harder.. I didn't think I was doing anything too
groundbreaking here.. this isn't the alpha release of exim.. Had hoped
that others using mailman had upgraded to a more current version of exim
than 3.33 and would have experience (and config pointers) to share.
Mike
--
Mike Gifford, OpenConcept Consulting, http://www.openconcept.ca
Open Source Web Applications for Social Change.
Featured Client - NDP Leadership Candidate - http://www.billblaikie.org
An unjust law is no law at all. - Saint Augustine
--
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
RE: [Mailman-Users] need advice on migrating existing Mailman to new hard drive
1. Backup /lists and /archives directories and config.db for each list 2. Use newlist utility to create a list for each 3. Drop in /lists and /archives directories in appropriate locations (see original lists for pathing) 4. Replace config.db with backup copy for each If paths are same -- 5. Use move_list utility to update config.db for each If paths are different -- 5. Use withlist utility in script to update config.db for each Sample scripts available at http://mail.python.org/pipermail/mailman-users/1999-August/002009.html http://mail.python.org/pipermail/mailman-users/2002-April/018960.html http://mail.python.org/pipermail/mailman-users/2002-April/018998.html Hope this helps, Anna Anna Q. Fong, Webmaster California Data Exchange Center -Original Message- From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]] On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, July 17, 2002 7:34 AM To: [EMAIL PROTECTED] Subject: [Mailman-Users] need advice on migrating existing Mailman to new hard drive I sent this message to the list but received no response so thought I might try again. Thanks in advance to anyone who may be able to offer advice. I am installing a new hard drive in my server with a clean install of Redhat 7.3 and its updated Mailman RPM (version 2.0.11-1). I am looking for some advice on how to move all of the Mailman files (membership, archives, list configs, etc.) from the old drive to the new one safely. The old hard drive is running Redhat 7.1 with Mailman 2.0.5 using Sendmail. Randy Stoecker Professor of Sociology Moderator/Editor COMM-ORG: The On-Line Conference on Community Organizing and Development Department of Sociology and Anthropology University of Toledo Toledo, OH 43606 USA phone: 419-530-4975 fax: 419-530-8406 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
RE: [Mailman-Users] HowTo edit Archives by hand
A side effect of doing this is that the re-generated html files are not necessarily referenced as they used to be. Thus if there are other references to these files (such as this one: http://mail.python.org/pipermail/mailman-users/2002-July/021154.html) they will be incorrect/invalid after a re-arch. -Jim P. -Original Message- From: Jon Carnes I think this is already in the FAQ, but just in case, here is a brief run through for the 2.0.x series... The archives are found in: ~mailman/archives/private/ There are two subdirectories for each list: listname.mbox: This directory contains one file, a text based Mailbox with all the archived messages. This file is the *real* archive. listname : This directory contains all the manufactured Web/text files needed to display the archived messages. The files in this directory are all generated from the Mailbox found in the other directory. To edit out an email, - Take mailman off-line (stopping cron is effective for this). - Goto the Mailbox containing the archive - Edit this large file and remove the offending email Note: this is a large text based file containing many emails, each stacked on top of each other inside the file. Each email starts with a line like: From [EMAIL PROTECTED] Mon Mar 12 14:23 2002 There will be other lines in the email that look similar and start with From: (note the colon instead of a space) From: User Name user@domain These lines are header lines inside the email. - Once the offending emails are edited or removed, move the files in the current web files for the archive to a backup directory and run: ~mailman/bin/arch listname This will regenerate all the HTML files used by the archive. - Bring mailman back on-line (restart cron) Best of 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
[Mailman-Users] Setup problem w/email commands
Just installed Mailman v2.0.9 with Python v2.1.3 on FreeBSD, and I'm having difficulty enabling any active responses to email commands. For example: o posts to the list result in a copy being sent to the list owner only -- not to the subscribers o email subscribe requests result in a copy being sent to the list owner, but do not result in any server responses, i.e. subscriber does not receive a confirmation email, and is not shown on list of subscribers o email unsubscribe requests = same problem o email help requests = blank email response Suggestions?? 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
[Mailman-Users] Mailman Install Issues
Hello All, I have used Mailman in the past on other servers and really appreciated it. Now it is time to change servers and I am having some problems. First of all I have an issue that it appears from my searching that there is not currently a solution for. I am running Red Hat 7.x ... it is my understanding that there is no practical and safe way to upgrade these machines to the version of Python needed to operate the latest Mailman version. Is that correct? Now on to the more pressing problem. I am trying to install Mailman. Every time when I complete the ./configure command and then run make install I get an error saying that there is no target for install and make stops. Any ideas? What am I doing wrong? Christopher -- 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
[Mailman-Users] Re: [Mailman-Developers] Extending mailman (adding config options)
LB == Laurence Berland [EMAIL PROTECTED] writes: LB Those of you following my previous emails (lamentably LB unanswered so far) will already know that I'm trying to extend LB mailman to add color-coded graphics to the archives to parse LB logwatch emails and such more efficiently. LB I'd like to have this configurable from the archive options LB page, so I was wondering what the standard structure for LB adding options is. Is there a premade set of mailman LB functions for extending this in a standard and non-kldugy way, LB and are they accessible as is from HyperArch.py? I'm not totally sure what you're asking about, but there is definitely a recipe for adding new mailing list configuration options. Briefly outlined: - Decide on an attribute name (or names if there are more than one). Be sure they don't collide with existing names. - Decide what the data type will be (bool, int, strings) -- for simplicity try to stick to one of the 13 existing Enumeration for Mailman cgi widget types defined in Defaults.py.in - Add attribute init code for newly created lists. For archiver/pipermail options, these would go in Archiver.InitVars() in Mailman/Archiver/Archiver.py - Add support for schema updating for existing lists. If you're adding new config options, this probably means adding a few lines to NewVars() in Mailman/versions.py - Bump the DATA_FILE_VERSION so the schemas will auto-update on next MailList object load. - Add the gui goo (i.e. the widget descriptions). For the archiver admin page, you're talking about adding to the returned list in Archive.GetConfigInfo() in Mailman/Gui/Archive.py. HTH, -Barry -- 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
[Mailman-Users] newbie question --installation
Greetings all: I thought I just got mailman set up. I created a test mailing list test and try to subscribe to the list. I got confirmation number and reply as instructed. But I never got Welcome message. View subscribers of test or running bin/list_members test gave me a blank page. I would appreciate you kind help if you can point out what could be wrong with my setting. Thanks in advance! Hongbin __ Do You Yahoo!? Yahoo! Autos - Get free new car price quotes http://autos.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
