Karl Zander wrote:
> The python code from Mark below worked nicley to convert
> the date formats. My imported archives are visiable in
> Mailman.
I've followed this thread, as Mailman site administrator at two different
sites (and continents :) and will try to see whether it may help me to
inte
In the internal code for (La)TeX system, the control sequences
use the @ character as a text character; on TeX related lists
there are often examples of such internal code. Unfortunately,
the archiver (mailman 2.1.2) converts a '[EMAIL PROTECTED]' pattern
to an email address. So, if a posting h
Richard Barrett writes:
> These files are actually created from the template file
> $prefix/templates/en/htdig_conf.txt
>
> If that file has been corrupted then all per-list htdig conf files
> subsequently created would also be damaged.
That file is OK. I wondered what the 5 lists with g
Richard Barrett <[EMAIL PROTECTED]> wrote:
> For one of the lists with the problem, what is the value of the
> 'script_name:' variable in the list's htdig conf file; look in
> $prefix/archives/private//htdig/.conf
>
> I would expect the following line in the fptex.conf file:
>
> script_name:
Richard Barrett writes:
> > while
> > the first page with search results looks fine, attempts to access
> > consequent pages
>
> What do you mean by 'subsequent pages'
Sorry if the explanation was not clear. If I search a list for
a pattern and the search returns 10+ pages of matches, cl
Some time ago the archive search on tug.org got broken; while
the first page with search results looks fine, attempts to access
consequent pages return error:
htdig Archives Access Failure
Path info. No list -2-
It looks like all 45+ lists are affected (I checked only four).
Does anyone
To Barry and the development team:
Thank you for MM2.1 final, your efforts and time
(and a great Christmas gift as well!)
Kaja
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ:
Hello Richard,
> I have posted on sourceforge MM 2.1 compatible versions of my patches to
> support integration of MM with htdig.
Many thanks for making the patches so quickly.
> The order in which the patches should be applied is as follows:
>
>
>http://sourceforge.net/tracker/index.p
Eric Trager writes:
> The problem we are having is that the monthly messages for the different
> lists and users all end up with the same Return-Path, Sender, and
> Errors-to headers, which contain the address of the admin for one of the
> lists (it so happens it's the first list that was cr
Richard Barrett writes:
> It looks as though you may not have applied the precursor
> indexing-2.0.13-0.2.patch
Yes, that is correct - I forgot to apply the indexing patch :(
The indexing patch followed by htdig patch applied cleanly.
Thank you for pointing it out.
Kaja
-
Odhiambo Washington writes:
> Probably the way you downloaded the patches...
> How did you do it?
> I've downloaded them before and they applied cleanly.
Thanks! The patch file must have been corrupted. I downloaded
it again and the result is better, but the patch doesn't apply
quite cleanl
Hi,
After unpacking the sources for mailman v. 2.0.13,
I tried to apply htdig-2.0.13-0.1.patch which failed.
Then I noticed the htdig-2.0.13-0.2.patch. Unfortunately
this patch is failing too:
[mailman-2.0.13]$ patch -p1 < htdig-2.0.13-0.2.patch
patching file INSTALL
patching file
Barry A. Warsaw wrote:
> I recommend anybody running any version of
> Mailman 2.0.x to upgrade to 2.0.9, the latest stable release.
The htdig patch by Richard Barrett is not compatible with the new
version of Mailman. Are there plans for a new revision of this patch?
I enclose the output
Barry A. Warsaw writes:
> http://www.python.org/cgi-bin/faqw-mm.py
>
> There's only 3 questions and answers there so far, but you can help
> make it a better FAQ! I'm opening up access so that anybody can add
> or change FAQ entries. This is an honor system, and the password is
> "M
Greetings,
Last Monday, one of our mailing lists went mad and sent multiple copies
of the same digest to the list's digest users. It happened after (my)
working hours and by the time I had a chance to react, all digest users
(but one!) received 395 copies of the same digest. What is worse, thi
We've had a major problem with a digest which was sent in hundreds
of copies; it started yesterday, sunday, at noon (when digests are
being mailed). I found the digest 'stuck' in qfiles and, after removing
it, along with all postings with the digest inside, it finally looked
like the situat
16 matches
Mail list logo
