Phil Ewels wrote:
>Ah, so this is what I initially thought, but the problem with that is my
>installation of Mailman - it is a central installation which serves
>lists to a whole range of different domains, so putting a .htaccess
>restriction in the archives folder would then stop access to the
On Mon, Feb 08, 2010 at 03:40:44PM +, Phil Ewels wrote:
> I'd like to protect my mailing list archives behind some .htaccess
> protection, but my mailman installation is a central one which serves a
> number of different websites.
>
> I was thinking I could get around this by using a script
Ah, so this is what I initially thought, but the problem with that is my
installation of Mailman - it is a central installation which serves
lists to a whole range of different domains, so putting a .htaccess
restriction in the archives folder would then stop access to the
archives for all of m
Phil Ewels wrote:
>So everyone will be using the same login details for the .htaccess
>protection (it's a fairly small group of users who need to access these
>pages, who all trust each other and having one login for all saves a lot
>of hassle). So no dynamic modification needed (if I understan
So everyone will be using the same login details for the .htaccess
protection (it's a fairly small group of users who need to access these
pages, who all trust each other and having one login for all saves a lot
of hassle). So no dynamic modification needed (if I understand you
correctly).
Us
Phil Ewels wrote:
>I'd like to avoid using the standard private archives because that would
>require users to log in a second time, with a second username and
>password. I'm attempting to hide everything behind a single .htaccess wall.
OK, but I don't think dynamically modifying .htaccess can
I'd like to avoid using the standard private archives because that would
require users to log in a second time, with a second username and
password. I'm attempting to hide everything behind a single .htaccess wall.
The other reason is that the users are currently being signed up by an
automate
Phil Ewels wrote:
>
>I'd like to protect my mailing list archives behind some .htaccess
>protection, but my mailman installation is a central one which serves a
>number of different websites.
Why not just use private archives? You could use a .htaccess file to
prevent access by URL if you reall
Hi all,
I'd like to protect my mailing list archives behind some .htaccess
protection, but my mailman installation is a central one which serves a
number of different websites.
I was thinking I could get around this by using a script to automate a
log in to the archives and then scraping the
