Re: [Mailman-Users] Creating lists based on a template
On Tue, 2004-03-02 at 11:03, Bowen, Robert wrote: I have searched the list archives for an answer, but haven't had much luck finding anything. I have multiple lists - one for each grade in our elementary schools, one for each grade in our high schools and some other lists that have for the most part the same attributes (Moderation on, don't send password monthly, etc.) Is there a way to setup one list and copy the attributes to my other lists? We don't have too many that I can't login to each one via the web and make the settings, I just think I could save a lot of time doing it the other way. Thanks, Robert Bowen Baldwin UFSD In the past I've found the config_list command helpful here. You can also modify most of the default settings used for list creation. You'll find them in ~mailman/Mailman/Defaults.py. To change them, copy the settings over to mm_cfg.py and then modify them in there. As an example, I *always* modify: DEFAULT_ADMIN_MEMBER_CHUNKSIZE = 30 and set it to at least 100 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/
Re: [Mailman-Users] Newbie question
Ok, thanks, i will go for it and ask again if i'll have a blocking point. On Wed, 2004-03-03 at 14:14, Jon Carnes wrote: The aliases from Mailman point to an application. So all mail going to a list is handed to Mailman's posting application and the application will either hold the post or pass it out to the list (depending on the rules you have setup for the list). HtH - Jon Carnes On Wed, 2004-03-03 at 03:19, Key Dof wrote: Ok, but using the alias file, how will it stop the delivery to a list from an unsubscribed user? On Tue, 2004-03-02 at 17:53, Jon Carnes wrote: On Tue, 2004-03-02 at 09:12, Key Dof wrote: Thanks a lot for you reply, in fact my question wasn't about the possibility of being installed (as servers) but it's about the fact of interacting, ie: when an email arrives to the server, if it knows where to deliver it (a user or mailman). If you confirm that it can be done, i will install it and go reading the docs, but if it is impossible because it's either a user delivery or a mailing list delivery, than i will have to start installing another machine. Thanks again Mailman uses the aliases file. Each mailing list adds several aliases to the aliases file. The only real user you need to add to the machine is one that is specifically setup to run the applications. The name of that user is normally mailman. -- 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/
[Mailman-Users] Attachment header mangling
I put the mangling in quotes because I don't know whether it's considered legal or not... This is Mailman 2.1.4, by the way... Say I send a message to a list that I'm on, with a copy directly to myself. To that message, I attach a document with a really long name, like: Response to Technical Issues - ETC - 2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.d oc In the copy of the message that comes directly to me, the headers in the attachment look like this (line numbers inserted so you can tell where the line breaks really were): 1. Content-Type: application/msword; 2. name=Response to Technical Issues - ETC - 2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.d oc 3. Content-Transfer-Encoding: base64 4. Content-Disposition: attachment; 5. filename=Response to Technical Issues - ETC - 2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.d oc; 6. size=19742 Note that the 'name=...' and 'filename=...' elements were each one long line. In the copy of the message that comes to me via the list, the corresponding headers in the attachment look something like: 1. Content-Type: application/msword; name=Response to Technical Issues 2. tab- ETC -2004-02-28-v3- LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.doc 3. Content-Transfer-Encoding: base64 4. Content-Disposition: attachment; filename=Response to Technical Issues 5. tab- ETC -2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle. doc; 6. tabsize=19742 I've slightly changed the place that the long lines were broken, in hopes that this message will make it through with its formatting mostly intact, but you get the idea. What Mailman seems to be doing is reflowing the header -- has moved the 'name=...' and 'filename=...' elements up onto the end of the previous line, then decided that the resulting line was too long and broken it in the middle of a string. This seems wrong to me (and to our director :-). But maybe it's legal, and it's the client's fault for not properly re-assembling the header? -- Steve Burlingmailto:[EMAIL PROTECTED] University of Michigan, ICPSRVoice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 -- 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/
Re: [Mailman-Users] Mailman on one server, archives on another
Thanks Dan and Joshua for your responses. I will be going with http://www.mail-archive.com/ which produces searchable mail archives and is a wonderful free service that has been around since 1998. Peace, Dan At 4:57 PM -0600 3/3/04, Dan Phillips wrote: On Mar 3, 2004, at 2:41 PM, Daniel Melnechuk wrote: I would like to have mailman run on one server but have the archives (ie. the mailman/archives folder) deposited another server on the internet. Does anyone done this successfully and how? The reason is that the server that will run the list does not have a lot of disk space to allocate to archives. A simple way would be to tell mailman not to archive, but subscribe an account on another machine to the list which feeds posts to mhonarc or another archiver. You could also use an existing archive service such as http://www.mail-archive.com/ to do this. Dan Dan Phillips Professor of Horn, University of Memphis site administrator: music.memphis.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/
[Mailman-Users] Mailman migration/reinstall?
We've just had a crash and burn of our server and are migrating everything to a new machine. Mailman was previously installed by a consultant and Im unable to reach him. Any resources/tips for help/consultants out there to help with either migrating from our current machine or reinstalling? Obviously it's pretty urgent :/ Please respond to [EMAIL PROTECTED] and not this email address. Anne -- 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/
Re: [Mailman-Users] Tieing Mailman to Spamassassin
I've continued working on this and made changes as I thought carefully about what is actually going on here. Assuming that the email is being routed to mailman before the maildrop filter is processed, I had the idea of piping the email to mailman *throuogh* the maildrop filter, instead of with the alias. That way, the maildrop filter can pass it to spamassassin first using xfilter, then pipe it to mailman. It doesn't work. When I send a message to the list, postfix bounces it back with the following message: [EMAIL PROTECTED]: Command died with status 2: /usr/local/bin/maildrop. Command output: Failed to create default user preference file /var/spool/postfix/virtual/.spamassassin/user_prefs Group mismatch error. Mailman expected the mail wrapper script to be executed as group mailman, but the system's mail server executed the mail script as group csdbes. Try tweaking the mail server to run the script as group mailman, or re-run configure, providing the command line option `--with-mail-gid=csdbes'. I understand what it's saying here, but I don't understand why. I recognize it's saying that the mailman process must be as the mailman group, but I don't see why the pipe works from postfix alias (the non-virtual kind) but not piping from maildrop. Is there an argument to use that will set run as group mailman for piping the message to mailman? Rob Quoting Rob Brandt [EMAIL PROTECTED]: I have a new mailing list that will likely attract spammers. I need to tie this in to my spamassassin installation and am not quite sure how to go about doing it. Here's my situation: My mail server configuration is postfix-courier-imap with mysql authentication. I use virtual domains in postfix, and to enable spam filtering I have maildrop installed and use a maildrop filter to pass email to spamassassin for analysis. This allows me to do spam control on a per-domain basis. If I want spam control on a particular domain, I set the postfix transport to maildrop; if not I set it to local. It works well, but have never used it for mailing lists. I was hoping that I would be able to use the same method with this new mailman list. The domain is in fact dedicated to the mailing list, and no other email will be routed through it. To try it, I assigned the transport for that domain to maildrop and created mail filter files for each of the mailman aliases. In the filter file for the actual mailing list, I put in the command to pass the mail through to spamassassin. It doesn't seem to work. The email gets processed through the list as if it hadn't been processed through spamassassin. I'm guess that this is exactly the case; that since the mailman aliases are not real email accounts, the mailfilter files aren't even being looked at. Am I wrong? Or is there a better way to do this? Thanks Rob -- 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/ -- 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/
Re: [Mailman-Users] Bumped from the list
I have been off this list for a long time... and on the 1st, I started recieving list messages again... strange.. Barry Smoke Jeff D wrote: I too realized today that the list had been awfully quiet for a few days. Unusually quiet. When I tried to log into the list's web interface for my account at python.org, it told me there was no such address subscribed to the list ! Again, my lack of receiving messages started on or about March 1. So, what the heck happened? Jeff D -- 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/ -- 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/
[Mailman-Users] Attachment header mangling
I put the mangling in quotes because I don't know whether it's considered legal or not... This is Mailman 2.1.4, by the way... Say I send a message to a list that I'm on, with a copy directly to myself. To that message, I attach a document with a really long name, like: Response to Technical Issues - ETC - 2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.d oc In the copy of the message that comes directly to me, the headers in the attachment look like this (line numbers inserted so you can tell where the line breaks really were): 1. Content-Type: application/msword; 2. name=Response to Technical Issues - ETC - 2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.d oc 3. Content-Transfer-Encoding: base64 4. Content-Disposition: attachment; 5. filename=Response to Technical Issues - ETC - 2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.d oc; 6. size=19742 Note that the 'name=...' and 'filename=...' elements were each one long line. In the copy of the message that comes to me via the list, the corresponding headers in the attachment look something like: 1. Content-Type: application/msword; name=Response to Technical Issues 2. tab- ETC -2004-02-28-v3- LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle.doc 3. Content-Transfer-Encoding: base64 4. Content-Disposition: attachment; filename=Response to Technical Issues 5. tab- ETC -2004-02-28-v3-LetsMakeThisReallyReallyLongByAddingManyMoreWordsToTheTitle. doc; 6. tabsize=19742 I've slightly changed the place that the long lines were broken, in hopes that this message will make it through with its formatting mostly intact, but you get the idea. What Mailman seems to be doing is reflowing the header -- has moved the 'name=...' and 'filename=...' elements up onto the end of the previous line, then decided that the resulting line was too long and broken it in the middle of a string. This seems wrong to me (and to our director :-). But maybe it's legal, and it's the client's fault for not properly re-assembling the header? -- Steve Burlingmailto:[EMAIL PROTECTED] University of Michigan, ICPSRVoice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 -- 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/
[Mailman-Users] Re: Attachment header mangling
Ack! My apologies for the double posting about this -- I read too hurriedly a rejection notice that claimed I wasn't allowed to post to the list, and didn't notice that it was from some other machine. -- Steve Burlingmailto:[EMAIL PROTECTED] University of Michigan, ICPSRVoice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 -- 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/
[Mailman-Users] Different machines?
I'm thinking about a thing.. Is it possible to split Mailman's functions across machines? What I want to accomplish is to run the web-part on the machine that runs only apache and the mail part on the second machine which acts as the mail server for our domain? A different approach would be to have mailman answer on a different port than 80 for the web interface and redirect the calls to the second machine, but it doesn't feel right. Anders Norrbring -- 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/
Re: [Mailman-Users] Different machines?
* Anders Norrbring [EMAIL PROTECTED] [040304 11:32]: Is it possible to split Mailman's functions across machines? What I want to accomplish is to run the web-part on the machine that runs only apache and the mail part on the second machine which acts as the mail server for our domain? Is this for performance reasons? What we did in my installation is to run mailman on a dedicated machine, which in turn hands off all the mail to a pair of servers running nothing but MTA's (postfix in my case). Very good performance. -jav -- 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/
[Mailman-Users] Fwd: We're sorry, we hit a bug! -- Please Help!
Hi, I sent this message out yesterday, but haven't received any replies... Can someone help me out with this? Original Message Subject: [Mailman-Users] We're sorry, we hit a bug! -- Please Help. From: ricardo [EMAIL PROTECTED] Date:Wed, March 3, 2004 12:00 pm To: [EMAIL PROTECTED] -- Hi, I'm getting this problem when attempting to enter the private list archives via private.cgi and log in with a subscriber's email and password. The login page comes up fine, but once I input the email and password, I get the error below. Traceback: Traceback (most recent call last): File /usr/local/mailman/scripts/driver, line 87, in run_main main() File /usr/local/mailman/Mailman/Cgi/private.py, line 120, in main password, username): File /usr/local/mailman/Mailman/SecurityManager.py, line 226, in WebAuthenticate print self.MakeCookie(ac, user) File /usr/local/mailman/Mailman/SecurityManager.py, line 233, in MakeCookie raise ValueError ValueError Python information: Variable Value sys.version 2.3+ (#1, Oct 2 2003, 23:03:59) [GCC 3.3.1 (SuSE Linux)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -- 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/ -- 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/
SV: [Mailman-Users] Different machines?
* Anders Norrbring [EMAIL PROTECTED] [040304 11:32]: Is it possible to split Mailman's functions across machines? What I want to accomplish is to run the web-part on the machine that runs only apache and the mail part on the second machine which acts as the mail server for our domain? Is this for performance reasons? What we did in my installation is to run mailman on a dedicated machine, which in turn hands off all the mail to a pair of servers running nothing but MTA's (postfix in my case). Very good performance. It's both performance and security reasons... Anyway, you write that your mailman server hands off all the mail to another machine running postfix, that's exactly what I want to achieve. No mail processing whatsoever on the web server (with mailman) and all the mail processing on the dedicated mail server. So, kind of gating over all the mail from mailman (box 1) to the mailserver (box 2). How do I set it up? I'm not very experienced with mailman, and I really don't find any relevant info anywhere. It seems like all docs are written for running mailman and the postfix service on the same box. Anders. -- 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/
[Mailman-Users] Extra newline inserted into subject line
To quote from a manager of one of the mailing lists on a site I manage: - For some reason there has been a feature--stable through multiple releases of Mailman--that is quite irritating. Under some condition(s) message arrive with a newline character inserted into the subject line. It may be as simple as a line of greater than a certain length. An example: The original message subject was fine, viz Subject: [Mailman-Announce] Terri Oda's List Member Manual now available When you forwarded it, it became Subject: [UUA-List-owners] [Fwd: [Mailman-Announce] Terri Oda's List Member\nManual now available] (The \n shows the newline in a standard unix escapement.) As far as I can determine, this does come from Mailman, as opposed to being passed through or generated on my receipt. It's a minor nit, but if there's an easy fix, I'd sure appreciate it. - There are some message archive hits related to this, including one (http://www.mail-archive.com/[EMAIL PROTECTED]/msg20343.html) hinting that the fix is simple. I searched the sources (2.1.4), though, and I could not find the relevant bits where this is modifiable. Any ideas? -- Dwight A. Ernest, dwight at significant dot comGPG key A6999567 Cell: +1-508-523-1416FAX: +1-978-405-2504YIM: dwight_ernest RHCE #803004293310030http://significant.com/~dwight/ KA2CNN Papa, partner, pilot, net geek, sysadmin, consultant, cohouser. -- 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/
SV: [Mailman-Users] Different machines?
* Anders Norrbring [EMAIL PROTECTED] [040304 11:32]: Is it possible to split Mailman's functions across machines? What I want to accomplish is to run the web-part on the machine that runs only apache and the mail part on the second machine which acts as the mail server for our domain? Is this for performance reasons? What we did in my installation is to run mailman on a dedicated machine, which in turn hands off all the mail to a pair of servers running nothing but MTA's (postfix in my case). Very good performance. So far, I've only found the parameter SMTPHOST, which of course could be set as any smtp host, but that would only be effective for outgoing mails, right? How should I go about to make incoming mails, both list mails and administrative mails to go from that external mail host into the mailman system? Anders. -- 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/
Re: [Mailman-Users] Bumped from the list
On 4 Mar 2004, at 16:55, Barry Smoke wrote: I have been off this list for a long time... and on the 1st, I started recieving list messages again... strange.. Barry Smoke You are not alone in finding your mailman-users list membership status mysteriously changed. Maybe it is something to do with the fact the list is now running MM 2.1.5b1. Maybe that upgraded was done for 1st Mar and something went awry (maybe it should have been planned for 1st Apr :-) Jeff D wrote: I too realized today that the list had been awfully quiet for a few days. Unusually quiet. When I tried to log into the list's web interface for my account at python.org, it told me there was no such address subscribed to the list ! Again, my lack of receiving messages started on or about March 1. So, what the heck happened? Jeff D -- 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/ -- 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/ -- 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/
Re: [Mailman-Users] Fwd: We're sorry, we hit a bug! -- Please Help!
Thank you for your feedback, Richard. I'm not sure why you say the traceback doesn't match MM 2.1.4. I'm running MM 2.1.4, I installed from mailman-2.1.4.tgz some time ago. The install is pretty much stock, I only made some modifications to the MailList.py module, but I have not changed any of the modules mentioned in the traceback. My set of python RPMs (in a SUSE system) are: python-mysql-0.9.2-52 python-devel-2.3-49 mod_python-2.7.8-427 python-2.3-49 python-curses-2.3-49 python-tk-2.3-49 What other information can I provide to help? Ricardo On 4 Mar 2004, at 19:36, Ricardo Kleemann wrote: Hi, I sent this message out yesterday, but haven't received any replies... Can someone help me out with this? At a minimum you need to say what versions of Mailman and Python you are running. The line numbers in the traceback do not match MM 2.1.4, the latest stable release, and the versions of software may well affect the interpretation of your problem. It would also help if you indicate if any modifications have been made to the standard MM distribution or patches applied. Looking at the current stable MM code it is difficult to see how this error could arise with unmodified code but an older version of MM may have an inherent problem which might lead to it. Original Message Subject: [Mailman-Users] We're sorry, we hit a bug! -- Please Help. From: ricardo [EMAIL PROTECTED] Date:Wed, March 3, 2004 12:00 pm To: [EMAIL PROTECTED] --- --- Hi, I'm getting this problem when attempting to enter the private list archives via private.cgi and log in with a subscriber's email and password. The login page comes up fine, but once I input the email and password, I get the error below. Traceback: Traceback (most recent call last): File /usr/local/mailman/scripts/driver, line 87, in run_main main() File /usr/local/mailman/Mailman/Cgi/private.py, line 120, in main password, username): File /usr/local/mailman/Mailman/SecurityManager.py, line 226, in WebAuthenticate print self.MakeCookie(ac, user) File /usr/local/mailman/Mailman/SecurityManager.py, line 233, in MakeCookie raise ValueError ValueError --- - Python information: Variable Value sys.version 2.3+ (#1, Oct 2 2003, 23:03:59) [GCC 3.3.1 (SuSE Linux)] sys.executable /usr/bin/python sys.prefix /usr sys.exec_prefix /usr sys.path /usr sys.platform linux2 -- 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/ -- 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/ -- 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/
[Mailman-Users] htmls back to txt.gz
Hi, I have list that does not have the txt.gz file available for a year. Is there a way to create it? Is there a way to convert the already generated html pages into a txt.gz file that is missing? Daniel -- 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/
[Mailman-Users] form-action tag and http-redirects - a solution?
Dear Mailman-users,
the following has already been discussed on this list but the
suggested solutions don't satisfy my needs which are to provide
mailinglist services to two kind of customers:
* users on out internal network
* users somewhere on the internet
The first group of people have to be able to use the mailman
webinterface via HTTP, the later are forced to connect with HTTPS
(company policy, not negotiable)
We're kind of forced to realize this by setting up the mailman server
on our internal network and to provide the webinterface though an
existing reverse-proxy (squid with https in reverse-proxy mode) to the
outside world.
In addition to the squid running on the reverse-proxy machine, an
apache-server listens on the same (outside) address. All it does is to
redirect http-requests to the corresponding https-url using
mod_rewrite.
And that's where the story begins:
Customers who connect to the mailman interface from the internet
through our reverse-proxy aren't able to submit their changes. This
is because http://ourserver/somecgi; is hardcoded in each
form action=... -tag, so the submit-request is sent to the
reverse-proxys' apache which does the redirection to the squid. The
post-data gets lost on the way and the request ends up doing nothing.
To make a long story short: I really don't understand why the
form-action has to have the whole protocol and servername in its
target. Is there any reason for not using the relative uri and to
let the browser do its job of forming the complete url? This way, the
interface would be independent of servername and protocol as seen
by the browser. Maybe I don't see the whole picture here, but this
is what gives us a bad headache in our setup.
Actually, I did some code digging (probably because I'm just too blind
to find the right configuration value to solve my problem easily). I'm
not much of a python-hacker (not much of a programmer at all in fact),
but the attached patch does seem to fit our needs by removing
http://; and the servers' name from DEFAULT_URL_PATTERN before
forming the form-action tag in htmlformat.py.
What do you think? Does it break anything I don't see right now?
Is there a chance to get this feature as an optional function into the
official mailman code?
Any comment is appreciated.
Thanks for listening :)
cu,
Oliver
--- Mailman/htmlformat.py.dist Wed Mar 3 00:04:15 2004
+++ Mailman/htmlformat.py Wed Mar 3 21:52:17 2004
@@ -28,6 +28,7 @@
import types
+import re
from Mailman import mm_cfg
from Mailman import Utils
@@ -413,7 +414,7 @@
if self.encoding:
encoding = 'enctype=%s' % self.encoding
output = '\n%sFORM action=%s method=%s %s\n' % (
-spaces, self.action, self.method, encoding)
+spaces, re.sub('^https?://[^/]+','',self.action), self.method, encoding)
output = output + Container.Format(self, indent+2)
output = '%s\n%s/FORM\n' % (output, spaces)
return output
--
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/
