James Davis wrote:
>Running mailman 2.1.9-7 on Debian 4.0.
>
>The archive for one of my lists played up today and two extra entries
>appeared containing only the tail end of a seperate post. It turns out
>that the archive software got confused when it came across a line in the
>body that started "
Running mailman 2.1.9-7 on Debian 4.0.
The archive for one of my lists played up today and two extra entries
appeared containing only the tail end of a seperate post. It turns out
that the archive software got confused when it came across a line in the
body that started "From" and had been properl
Hi drz,
You wrote on Fri Feb 11 20:57:07 CET 2005:
> I am using Mailman on Debian linux and have just upgraded to the
> latest mailman software. ...
I had the same problem. Maybe
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=294817
helps you too.
I have also edited Private.py.
HTH,
--
[EMAIL PROTECTED] wrote:
>When I go to the aliases files, pipermail is set to: /pipermail/:
>/var/lib/mailman/archives/public
And is it enabled to follow symlinks?
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense
I am using Mailman on Debian linux and have just upgraded to the latest mailman
software. I am having a problem with accessing the archives with the web
interface and consistently get "You are not authorized to view this page"
error. The path is: http://www.enabling.org/pipermail///
When I go
Adam
The --wipe command did the trick
Thanks for the help
Jared
--- Adam Steer <[EMAIL PROTECTED]> wrote:
> If check_perms works fine, then look at permissions
> where your mbox
> files live.
>
> If they're all good, then try using the '--wipe'
> option when rebuilding
> archives:
>
> /[path
If check_perms works fine, then look at permissions where your mbox
files live.
If they're all good, then try using the '--wipe' option when rebuilding
archives:
/[path.to]/mailman/bin/arch --wipe [list]
/[path.to]/mailman/archives/private/[list].mbox/[list].mbox
...a bit of a clean up before r
Jared Nyland wrote:
>In trouble shooting this issue a little bit more. It
>looks like the lists that I had to move from one
>server to another the archives are not working
>correctly. If I create a new list on the new server
>everything seems to work just fine.
>
>Is there a step I forgot when mi
In trouble shooting this issue a little bit more. It
looks like the lists that I had to move from one
server to another the archives are not working
correctly. If I create a new list on the new server
everything seems to work just fine.
Is there a step I forgot when migrating lists over to
a new
Jared Nyland wrote:
>
>I am having troubles with the archives displaying for
>the month of August. When I run arch in the bin
>directory everything shows up working great. Do I
>need to setup a cron job to do this for me or should
>this automatically work by default.
>
bin/arch is only intended
Hi,
I am having troubles with the archives displaying for
the month of August. When I run arch in the bin
directory everything shows up working great. Do I
need to setup a cron job to do this for me or should
this automatically work by default.
Thanks in advance
Jared
___
Hello Members,
I have Fedora Core 1 and mailman-2.1.4-1.
When I try to see the archives from the admin webpage
(http://myhostname/mailman/admin/mylistname), everything is OK.
If I start from the listinfo page and check the archives (after passing my e-address
and passwd) I can see the monthly t
> Ok, its Monday so maybe I'm missing something. I've tried to find the answer
to my problem on Google and this list's searchable archives, but I failed to
find one so here goes.
>
> I'm using Mailman 2.0.13 on Redhat 7.2, with Apache 2.0.40, Python 2.2.1, and
Sendmail 8.11.6. Install was suc
Ok, its Monday so maybe I'm missing something. I've tried to find the answer to my
problem on Google and this list's searchable archives, but I failed to find one so
here goes.
I'm using Mailman 2.0.13 on Redhat 7.2, with Apache 2.0.40, Python 2.2.1, and Sendmail
8.11.6. Install was successful
Dave Weiner <[EMAIL PROTECTED]> said:
>
> I've got a strange problem with the archives. Mailman 2.0.10, Python
> 2.2 on a Red Hat 7.1 box. Apache is configured correctly (all web
> features except the archive work), the list is working, etc.
>
> When I go to the list archive page (either publi
set up two test-lists on my new listserver and posted messages to
it. All seems to work ok, but the archive does not work.
The lists are named "test" and "test2".
If I look at pipermail/test2 I get a page.
The Test2 Archives
You can get more information about this list or you can download the ful
I've got a strange problem with the archives. Mailman 2.0.10, Python
2.2 on a Red Hat 7.1 box. Apache is configured correctly (all web
features except the archive work), the list is working, etc.
When I go to the list archive page (either public or private), I get
You can get more information
I have several lists running on a server and I cannot access the archives on
any or them.
I have tried everything but it looks like it could be a bug.
Any assistance would be much appreciated!
Thanks!
Nicole
When I select "visit the listname Archives" I get:
http://domain.com/ma
18 matches
Mail list logo
