Re: [Mailman-Users] misfeature/bug in MM 2.1
On Sat, 18 Jan 2003 15:43:06 -0500 Barry A Warsaw <[EMAIL PROTECTED]> wrote: > I got working a prototype integration of Mailman and spambayes, and > I'll probably be checking this into cvs when I get back . I'd > label it as an interesting experiment, but whether it'll be useful > remains to be seen. I doubt it will eliminate the need for other > upstream spam catching tools. :looks pointedly at TMDA (especially for the control addresses). -- J C Lawrence -(*)Satan, oscillate my metallic sonatas. [EMAIL PROTECTED] He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live. -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] how to access mailman in web browser
I installed Linux 8 and it comes with mailman but i dont know how to access this on web browser please help how to go abut thank u, -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Archives in HTML?
Thanks Barry - I already got MHonArc running - just need to learn how to customize how the screens Look. :) Jim Hale --- 'The OS Tells The PC What To Do With Itself" - Me, 1990 --- Visit Our MIDI & Digital Audio Website at http://hale.dyndns.org -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Barry A. Warsaw Sent: Saturday, January 18, 2003 1:00 PM To: Jim Hale Cc: Mailing List - Mailman Subject: Re: [Mailman-Users] Archives in HTML? > "JH" == Jim Hale <[EMAIL PROTECTED]> writes: JH> I started a mailing list for 'Blinkies' and 99% of the JH> messages that come thru are in HTML. They come thru my list JH> just fine, but the archives are majorly ugly. Is there a way JH> to have the HTML messages display in HTML in the archives? JH> Using 2.1 Release. :) While others have given good advice about mhonarc, you might also want to look at the ARCHIVE_HTML_SANITIZER variable in Defaults.py. It controls what Pipermail does with html attachements. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jim-ml%40halemail.d yndns.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/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] user feedback on plain digests
On Saturday, January 18, 2003, at 10:47 PM, Bryan Fullerton wrote: On Thursday, January 16, 2003, at 07:36 PM, Barry A. Warsaw wrote: One of my goals for the digester was that either digest could be burst and the individual messages would look exactly as if they had arrived independently. Or at least, they'd be useable to do follow ups back to the list. Maybe that's unreasonable for plain text digests. If so, the current code may need a more invasive surgery. Sounds fine for the general case as long as I can (preferably easily) customize my specific case to only display specific headers in a specific order. Which is what I have now with the patch from Tokio Kikuchi. Erm, for plain text digests that is. :) Bryan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: Problems with content filtering
"Paul Kleeberg" <[EMAIL PROTECTED]> wrote in message news:a05200f09ba4fc58a4544@[192.168.1.12]... > A message was sent out to the subscribers with the appropriate > subject line and list-specific header lines but this is what appeared > in the body of the message: >/root/hPnn4E: Permission denied Paul: I ran into the EXACT same problem ... it has something to do with where lynx creates work files ... I don't know what it is. I solved the problem by changing the HTML to Plaintext command to links... Download links from http://artax.karlin.mff.cuni.cz/~mikulas/links/ and install it. Then add/change the following in mm_cfg.py ... HTML_TO_PLAIN_TEXT_COMMAND = '/usr/local/bin/links -dump %(filename)s' ... and restart qrunner. Works great. david -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] user feedback on plain digests
On Thursday, January 16, 2003, at 07:36 PM, Barry A. Warsaw wrote: One of my goals for the digester was that either digest could be burst and the individual messages would look exactly as if they had arrived independently. Or at least, they'd be useable to do follow ups back to the list. Maybe that's unreasonable for plain text digests. If so, the current code may need a more invasive surgery. Sounds fine for the general case as long as I can (preferably easily) customize my specific case to only display specific headers in a specific order. Which is what I have now with the patch from Tokio Kikuchi. Bryan -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Problems with content filtering
Thank you all for the help on the regular expression. Again I am probably missing the obvious but it is beyond my skill level to decipher. I would like only plain text messages to go out to the list, converting non-text messages to plain text and stripping attachments. I am not sure if that is possible. But I have run into a problem: I am using RedHat 8.0 and have upgraded from Mailman 2.0.13 to 2.1. In order to keep file locations the same, I ran configure with --prefix=/var/mailman --with-cgi-gid=apache --with-mail-gid=mail. In the /etc/smrch directory I created ln -s ../../var/mailman/mail/mailman mailman. Things appear to work fine until I turn on the content filter, left the black list blank, added "text/html" to the white list, turned on the convert text/html to plain text and send a message of Content-Type: text/html; charset="us-ascii" to the list. A message was sent out to the subscribers with the appropriate subject line and list-specific header lines but this is what appeared in the body of the message: /root/hPnn4E: Permission denied Looking at the /var/log/mailman/error file I see: Jan 18 18:10:04 2003 (23871) HTML->text/plain error: 256 Suggestions? Paul -- Paul Kleeberg [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] user feedback on plain digests
Hi, Barry. Barry A. Warsaw wrote: "BF" == Bryan Fullerton <[EMAIL PROTECTED]> writes: BF> When I get a chance later today I'll be trying the patch Tokio BF> Kikuchi sent to mailman-developers - hopefully it will resolve BF> the excess headers issue. I'm off the net at the moment so I can't look at the patch, but I can guess what it does. If I'm right will it bother folks that reducing the number of headers in the plain text digest will also reduce the number of headers in the MIME digest? No. I didn't touch the MIME part of the digester. Only plain text headers are reduced (and cofigurable in mm_cfg.py). One of my goals for the digester was that either digest could be burst and the individual messages would look exactly as if they had arrived independently. Or at least, they'd be useable to do follow ups back to the list. Maybe that's unreasonable for plain text digests. If so, the current code may need a more invasive surgery. After I submitted the patch, I had a chance to review Scrubber.py. I think I have re-invented a scrubber with less capablity. Maybe we should use the Scrubber.py for plain text digests. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Sub-lists and authorized posting
Done. Added as patch #670522 On Sat, 2003-01-18 at 12:27, Barry A. Warsaw wrote: > > "NN" == Nathan Neulinger writes: > > NN> I managed to make a patch to do this based on the > NN> "list_exploder" patch that is in the sourceforge patches area > NN> for 2.0. > > NN> I've got a patch against 2.1 if anyone is > NN> interested. Basically lets you put: > > NN> +list@thisdomain > > NN> in the *_these_nonmembers boxes, and it will expand that to > NN> the contents of that list when checking for authorization to > NN> post/etc. > > Please submit a SF patch for this. It sounds like a useful patch! > Maybe it'll make it into MM2.2. > > -Barry -- Nathan Neulinger EMail: [EMAIL PROTECTED] University of Missouri - Rolla Phone: (573) 341-4841 Computing Services Fax: (573) 341-4216 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] misfeature/bug in MM 2.1
> "JAE" == Jeff A Earickson <[EMAIL PROTECTED]> writes: JAE> In my study of my mailing lists today (both new in MM 2.1, JAE> and upgraded from 2.0.13), I made the sad discovery that JAE> generic_nonmember_action = 0 JAE> for **all** of my lists. The "bend over and take spam" JAE> setting. I noticed that DEFAULT_GENERIC_NONMEMBER_ACTION is JAE> set to one in Mailman/Defaults.py, but I don't think this JAE> setting works properly. If it did work properly, I would JAE> argue that the default should be 2 (reject), not 1 (hold for JAE> administrator). Why should the list administrator be JAE> bothered with having to tend admin requests from spammers and JAE> other idiots? Mailman isn't an anti-spam program, although it has some modest anti-spam defenses. Since there are lots of anti-spam programs out there, it should be pretty easy to install a good anti-spam program upstream of Mailman. I just gave a talk at the MIT spam conference about our approach and will be putting our slides up on the web somewhere soon (probably on spamconference.org -- not sure yet). BTW, on the train to said conference, I got working a prototype integration of Mailman and spambayes, and I'll probably be checking this into cvs when I get back . I'd label it as an interesting experiment, but whether it'll be useful remains to be seen. I doubt it will eliminate the need for other upstream spam catching tools. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailpasswds
> "sp" == sean pambianco <[EMAIL PROTECTED]> writes: sp> Is there anyway to run the mailpasswds cron jobs for just one sp> list as opposed for all lists on my mailman server? cron/mailpasswds -l onelist See -h for details. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] BCC allowed?
> "CH" == Carl Holtje <[EMAIL PROTECTED]> writes: CH> While the power of denying a list to be specified in a BCC CH> field is certainly undeniable, I'd like the ability to accept CH> a post that has the list BCCd if the sender is a list member CH> -- is this possible? For MM2.1, look under Privacy -> Recipient filters. You might want to edit either require_explicit_destination or acceptable_aliases. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archives in HTML?
> "JH" == Jim Hale <[EMAIL PROTECTED]> writes: JH> I started a mailing list for 'Blinkies' and 99% of the JH> messages that come thru are in HTML. They come thru my list JH> just fine, but the archives are majorly ugly. Is there a way JH> to have the HTML messages display in HTML in the archives? JH> Using 2.1 Release. :) While others have given good advice about mhonarc, you might also want to look at the ARCHIVE_HTML_SANITIZER variable in Defaults.py. It controls what Pipermail does with html attachements. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: [Mailman-Developers] spam filter
> "KW" == Kory Wheatley <[EMAIL PROTECTED]> writes: KW> I would like to discard any email that comes from the from KW> address "[EMAIL PROTECTED]". In MM2.1, this is easy. Add [EMAIL PROTECTED] to your Privacy->Sender filters->discard_these_nonmembers. In MM2.0 the best you can do is catch "From: [EMAIL PROTECTED]" and manually discard them. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
RE: [Mailman-Users] Sub-lists and authorized posting
> "NN" == Nathan Neulinger writes: NN> I managed to make a patch to do this based on the NN> "list_exploder" patch that is in the sourceforge patches area NN> for 2.0. NN> I've got a patch against 2.1 if anyone is NN> interested. Basically lets you put: NN> +list@thisdomain NN> in the *_these_nonmembers boxes, and it will expand that to NN> the contents of that list when checking for authorization to NN> post/etc. Please submit a SF patch for this. It sounds like a useful patch! Maybe it'll make it into MM2.2. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Can users request old digests?
> "EL" == Ed Leafe <[EMAIL PROTECTED]> writes: EL> I recently received a request from a user who receives and EL> archives the digest version of the list, and due to ISP EL> problems he recently missed a few issues. He has used lists EL> where you can send email to the list requesting specific EL> digest back issues; is such a capability part of Mailman? No, but it's a good idea. Please submit a feature request. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] user feedback on plain digests
> "BF" == Bryan Fullerton <[EMAIL PROTECTED]> writes: BF> When I get a chance later today I'll be trying the patch Tokio BF> Kikuchi sent to mailman-developers - hopefully it will resolve BF> the excess headers issue. I'm off the net at the moment so I can't look at the patch, but I can guess what it does. If I'm right will it bother folks that reducing the number of headers in the plain text digest will also reduce the number of headers in the MIME digest? One of my goals for the digester was that either digest could be burst and the individual messages would look exactly as if they had arrived independently. Or at least, they'd be useable to do follow ups back to the list. Maybe that's unreasonable for plain text digests. If so, the current code may need a more invasive surgery. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] mailinglists for multiple domains on one server
> "RBP" == Richard B Pyne <[EMAIL PROTECTED]> writes: RBP> However, the create cgi will not permit including the RBP> @dom.ain in the list name and therefore defaults to the RBP> default domain (which mailman appears to allow only to be the RBP> domain listed in the PTR dns record for the IP address of the RBP> machine). Not true. New lists will inherit the domain that you used to visit the create cgi. E.g. If I go to http://mail.python.org/mailman/create to create my new list, it'll show up in the python.org domain. If instead I use http://lists.zope.org/mailman/create, it'll show up in the zope.org domain. -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 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Help with a regular expression
I don't know what the I or | or whatever that is does - I assume it
does the same thing as {0,1}. But the important difference between the
rule I use:
RewriteRule ^/(mailman[/]{0,1}){0,1}$/mailman/listinfo [L,R]
and the ones you suggested is that mine also redirects requests for /
to /mailman/listinfo. You may or may not want that functionality, of
course. Again, I don't claim to be an expert in any of this stuff...
considering your comments, perhaps this would be the best for what I
want to do:
RewriteRule ^/(mailman(|/)){0,1}$ /mailman/listinfo [PT]
I don't know if you can use nested parentheses, and I don't know if the
PT flag is something I'd want, but whatever works...
Greg
On Saturday, January 18, 2003, at 02:15 PM, Richard Barrett wrote:
At 14:46 18/01/2003, Greg Westin wrote:
I think what you want to do to fix this is add a carat ("^") before
the
first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if "/mailman" occurs at the beginning of
the string.
Personally, I use a little more inclusive regular expression, because
I
want it to also redirect any requests for the top level
(http://lists.example.com) to the listinfo page:
RewriteRule ^[/]{0,1}(mailman[/]{0,1}){0,1}$/mailman/listinfo
[L,R]
What's wrong with:
RedirectMatch permanent ^/mailman(|/)$ /mailman/listinfo
or, if you have mod_rewrite and the rewrite engine on:
RewriteRule ^/mailman(|/)$ /mailman/listinfo [R,L]
or even better:
RewriteRule ^/mailman(|/)$ /mailman/listinfo [PT]
The latter has the advantage, courtesy of the PT flag, of delivering
the /mailman/listinfo page immediately instead of making the browser
do a second request (each time it visits) to follow the redirection
response produced by the initial request, if that request's URI path
was /mailman or /mailman/
I claim to be no master of regular expressions, though... because wow
that looks ugly. That notwithstanding, I think my advice on your
situation is correct.
Greg
On Saturday, January 18, 2003, at 02:09 AM, Paul Kleeberg wrote:
I know this is a simple question but I don't have the knowledge to
figure it out.
I am running RedHat 8.0 and which came with Mailman 2.0.13. It
suggests adding the following to the httpd.conf file:
# Uncomment the following line, replacing www.example.com with your
server's
# name, to redirect queries to /mailman to the listinfo page
(recommended).
# RedirectMatch /mailman[/]*$ http://www.example.com/mailman/listinfo
That used to work fine. I just upgraded to Mailman 2.1. I created
the list "mailman" as instructed at the end of section 4 of the
INSTALL document but cannot get to the administrative page
http://www.example.com/mailman/admin/mailman or the list overview
page
http://www.example.com/mailman/listinfo/mailman because
"RedirectMatch" thinks it is http://www.example.com/mailman and just
redirects it the top level listinfo page.
I am aware that I have two options:
1. Rename the "mailman" list
2. Remove the "RedirectMatch" statement from the httpd.conf file.
Is there a third? I tried fiddling with the regular expression, but
I
just do not know what I am doing. Any help would be appreciated.
Paul
--
Paul Kleeberg, M.D. O o [EMAIL PROTECTED]
Family Physicians' E-Net-+---+- Voice: 612-840-3744
5025 Mulcare Drive |_o_| Family Practice &
Columbia Heights, MN 55421 USA / \|/ \ Information Services
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
greg%40gregwestin.com
--
http://www.gregwestin.com
Contact info: http://www.gregwestin.com/contact.php
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
r.barrett%40openinfo.demon.co.uk
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
greg%40gregwestin.com
--
http://www.gregwestin.com
Contact in
Re: [Mailman-Users] Help with a regular expression
At 14:46 18/01/2003, Greg Westin wrote:
I think what you want to do to fix this is add a carat ("^") before the
first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if "/mailman" occurs at the beginning of
the string.
Personally, I use a little more inclusive regular expression, because I
want it to also redirect any requests for the top level
(http://lists.example.com) to the listinfo page:
RewriteRule ^[/]{0,1}(mailman[/]{0,1}){0,1}$/mailman/listinfo
[L,R]
What's wrong with:
RedirectMatch permanent ^/mailman(|/)$ /mailman/listinfo
or, if you have mod_rewrite and the rewrite engine on:
RewriteRule ^/mailman(|/)$ /mailman/listinfo [R,L]
or even better:
RewriteRule ^/mailman(|/)$ /mailman/listinfo [PT]
The latter has the advantage, courtesy of the PT flag, of delivering the
/mailman/listinfo page immediately instead of making the browser do a
second request (each time it visits) to follow the redirection response
produced by the initial request, if that request's URI path was /mailman or
/mailman/
I claim to be no master of regular expressions, though... because wow
that looks ugly. That notwithstanding, I think my advice on your
situation is correct.
Greg
On Saturday, January 18, 2003, at 02:09 AM, Paul Kleeberg wrote:
I know this is a simple question but I don't have the knowledge to
figure it out.
I am running RedHat 8.0 and which came with Mailman 2.0.13. It
suggests adding the following to the httpd.conf file:
# Uncomment the following line, replacing www.example.com with your
server's
# name, to redirect queries to /mailman to the listinfo page
(recommended).
# RedirectMatch /mailman[/]*$ http://www.example.com/mailman/listinfo
That used to work fine. I just upgraded to Mailman 2.1. I created
the list "mailman" as instructed at the end of section 4 of the
INSTALL document but cannot get to the administrative page
http://www.example.com/mailman/admin/mailman or the list overview page
http://www.example.com/mailman/listinfo/mailman because
"RedirectMatch" thinks it is http://www.example.com/mailman and just
redirects it the top level listinfo page.
I am aware that I have two options:
1. Rename the "mailman" list
2. Remove the "RedirectMatch" statement from the httpd.conf file.
Is there a third? I tried fiddling with the regular expression, but I
just do not know what I am doing. Any help would be appreciated.
Paul
--
Paul Kleeberg, M.D. O o [EMAIL PROTECTED]
Family Physicians' E-Net-+---+- Voice: 612-840-3744
5025 Mulcare Drive |_o_| Family Practice &
Columbia Heights, MN 55421 USA / \|/ \ Information Services
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/ greg%40gregwestin.com
--
http://www.gregwestin.com
Contact info: http://www.gregwestin.com/contact.php
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/r.barrett%40openinfo.demon.co.uk
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Postfix style virtual domains
Can someone point me in the right direction to make a patch. I am using Postfix virtual domains, and I need to make a patch to make newlist add '@localhost' to the end of each entry in virtual-mailman as in: default entry: [EMAIL PROTECTED] mylist needs to be: [EMAIL PROTECTED] mylist@localhost Otherwise, postfix 2.0.0.2 rewrites the address and sends it to mylist@$mydomain, which gets sent off to another machine instead of being delivered locally and processed through aliases to send it to mailman. Thanks, --Richard -- Richard B. Pyne, NZ7K [EMAIL PROTECTED] http://pyne.kinfolk.org/rbp2 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Help with a regular expression
Just in case anyone was actually thinking of using that regexp I sent,
my limited knowledge tells me that this would be a slightly better
incarnation:
RewriteRule ^/(mailman[/]{0,1}){0,1}$ /mailman/listinfo [L,R]
Greg
On Saturday, January 18, 2003, at 09:46 AM, Greg Westin wrote:
I think what you want to do to fix this is add a carat ("^") before
the first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if "/mailman" occurs at the beginning of
the string.
Personally, I use a little more inclusive regular expression, because
I want it to also redirect any requests for the top level
(http://lists.example.com) to the listinfo page:
RewriteRule ^[/]{0,1}(mailman[/]{0,1}){0,1}$/mailman/listinfo
[L,R]
I claim to be no master of regular expressions, though... because wow
that looks ugly. That notwithstanding, I think my advice on your
situation is correct.
Greg
On Saturday, January 18, 2003, at 02:09 AM, Paul Kleeberg wrote:
I know this is a simple question but I don't have the knowledge to
figure it out.
I am running RedHat 8.0 and which came with Mailman 2.0.13. It
suggests adding the following to the httpd.conf file:
# Uncomment the following line, replacing www.example.com with your
server's
# name, to redirect queries to /mailman to the listinfo page
(recommended).
# RedirectMatch /mailman[/]*$ http://www.example.com/mailman/listinfo
That used to work fine. I just upgraded to Mailman 2.1. I created
the list "mailman" as instructed at the end of section 4 of the
INSTALL document but cannot get to the administrative page
http://www.example.com/mailman/admin/mailman or the list overview
page http://www.example.com/mailman/listinfo/mailman because
"RedirectMatch" thinks it is http://www.example.com/mailman and just
redirects it the top level listinfo page.
I am aware that I have two options:
1. Rename the "mailman" list
2. Remove the "RedirectMatch" statement from the httpd.conf file.
Is there a third? I tried fiddling with the regular expression, but
I just do not know what I am doing. Any help would be appreciated.
Paul
-- Paul Kleeberg, M.D. O o [EMAIL PROTECTED]
Family Physicians' E-Net-+---+- Voice: 612-840-3744
5025 Mulcare Drive |_o_| Family Practice &
Columbia Heights, MN 55421 USA / \|/ \ Information Services
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
greg%40gregwestin.com
--
http://www.gregwestin.com
Contact info: http://www.gregwestin.com/contact.php
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
greg%40gregwestin.com
--
http://www.gregwestin.com
Contact info: http://www.gregwestin.com/contact.php
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Help with a regular expression
I think what you want to do to fix this is add a carat ("^") before the
first slash:
RedirectMatch ^/mailman[/]*$ http://www.example.com/mailman/listinfo
That way, it only catches it if "/mailman" occurs at the beginning of
the string.
Personally, I use a little more inclusive regular expression, because I
want it to also redirect any requests for the top level
(http://lists.example.com) to the listinfo page:
RewriteRule ^[/]{0,1}(mailman[/]{0,1}){0,1}$/mailman/listinfo
[L,R]
I claim to be no master of regular expressions, though... because wow
that looks ugly. That notwithstanding, I think my advice on your
situation is correct.
Greg
On Saturday, January 18, 2003, at 02:09 AM, Paul Kleeberg wrote:
I know this is a simple question but I don't have the knowledge to
figure it out.
I am running RedHat 8.0 and which came with Mailman 2.0.13. It
suggests adding the following to the httpd.conf file:
# Uncomment the following line, replacing www.example.com with your
server's
# name, to redirect queries to /mailman to the listinfo page
(recommended).
# RedirectMatch /mailman[/]*$ http://www.example.com/mailman/listinfo
That used to work fine. I just upgraded to Mailman 2.1. I created
the list "mailman" as instructed at the end of section 4 of the
INSTALL document but cannot get to the administrative page
http://www.example.com/mailman/admin/mailman or the list overview page
http://www.example.com/mailman/listinfo/mailman because
"RedirectMatch" thinks it is http://www.example.com/mailman and just
redirects it the top level listinfo page.
I am aware that I have two options:
1. Rename the "mailman" list
2. Remove the "RedirectMatch" statement from the httpd.conf file.
Is there a third? I tried fiddling with the regular expression, but I
just do not know what I am doing. Any help would be appreciated.
Paul
--
Paul Kleeberg, M.D. O o [EMAIL PROTECTED]
Family Physicians' E-Net-+---+- Voice: 612-840-3744
5025 Mulcare Drive |_o_| Family Practice &
Columbia Heights, MN 55421 USA / \|/ \ Information Services
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/
greg%40gregwestin.com
--
http://www.gregwestin.com
Contact info: http://www.gregwestin.com/contact.php
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
