On Friday, July 25, 2003, at 08:40 AM, Nicolas C. wrote:
Hi,
<snip>
To my config, I have 3 more fields too and the archive work well:
PUBLIC_ARCHIVE_URL = "/MHonArc/%(listname)s" PUBLIC_EXTERNAL_ARCHIVER = "/MHonArc/bin/mhonarc -add -outdir /MHonArc/html/%(listname)s >> /tmp/out_external_archiver" PRIVATE_EXTERNAL_ARCHIVER = "/MHonArc/bin/mhonarc -add -outdir /MHonArc/html/%(listname)s >> /tmp/out_external_archiver"
I don't know why there is not PRIVATE_ARCHIVE_URL in the config ... that's
missing to make external archiver private list.
Private archives in a Mailman sense are accessed via a Mailman CGI program, normally using the URI /mailman/private. This URI leads to the Mailman script $prefix/Mailman/Cgi/private.py being invoked to authenticate the request and deliver the page if the user is authorised to see it.
If you want Mailman's private.py script to enforce private list access restrictions and deliver archive pages generated by your external archiver then it will have to generate them where the private.py script expects to find them. Mailman code uses the MM config variable PRIVATE_ARCHIVE_FILE_DIR to find the directory beneath which list archives are stored. It looks for a sub-directory called <listname> for a list's HTML archives; typically this will end up as directory $prefix/archives/private/<listname>
If you want private archives in a Mailman sense, you must change either your external archiver's configuration, or Mailman's configuration, or both so that they agree on the directory where a list's private archives are stored.
A point to note is that, in a Mailman sense, all list archives are stored under the directory defined by PRIVATE_ARCHIVE_FILE_DIR. The directory defined by MM config variable PUBLIC_ARCHIVE_FILE_DIR just holds symlinks to subdirectories under PRIVATE_ARCHIVE_FILE_DIR for those lists that are currently defined as have public archives; changin a list's archive from public to private and vice versa is done by creating of deleting such symlinks. With the standard MM installation, the directory defined by PRIVATE_ARCHIVE_FILE_DIR is the resolution of the URI part of the URL defined by PUBLIC_ARCHIVE_URL.
If you configure your external archiver to store archive pages where MM expects them, then private/public lists will work as normal. So too will the integrated htdig search facility available through patch #444884, which preserves the privacy of searchable private archives.
It is always pointing towards the mailman HTML mailing list and not the external archiver. The use of "add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)", is confused to me, may be this is usefull with several domain,
That is exactly why it exists. Indeed it is vital to doing virtual hosting.
but I still didn't understand why this is needed. regards,
<snip>
------------------------------------------------------ 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/archive%40jab.org
