my other websites.
Mark Sapiro wrote:
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).
is may get overly complicated, so I might just create a dummy account
and publicise the login details on a page protected by .htaccess. Messy
but easy.
Phil
Mark Sapiro wrote:
Phil Ewels wrote:
I'd like to avoid using the standard private archives because that would
require users to
d up by an
automated script, which does it silently, so they are not getting any
welcome messages and will not know what their subscription password is.
I'll have a go using ?password=PASSWORD and see where I get to...
Cheers,
Phil
Mark Sapiro wrote:
Phil Ewels wrote:
I'd like to pro
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
mp;adminpw=
http://wiki.list.org/pages/viewpage.action?pageId=4030567
No cron / special permissions needed!
Cheers,
Phil
Mark Sapiro wrote:
Phil Ewels wrote:
To test, I've been running this cron command:
echo t...@testing.co.uk |
/usr/local/cpanel/3rdparty/mailman/bin/add_members -r
Hi all,
I have a registration form where users, amongst other things, choose a
number of mailing lists to sign up to. I don't want users to have to go
and individually sign up to each list, so I'm trying to automate the
signup process.
After doing a bit of reading around, the closest I've go
