Re: [Mailman-Users] Archives Permission Denied

On 2/25/2020 5:11 PM, Mark Sapiro wrote: > On 2/25/20 10:25 AM, Dennis Putnam wrote: > >> So shouldn't 'check_perms -f' have fixed that? > > check_perms is not perfect. See below for more. > > >> This is a server used strictly for mailman. There are only 2 users with >> access so I am not worried a

Re: [Mailman-Users] Archives Permission Denied

On 2/25/20 10:25 AM, Dennis Putnam wrote: > So shouldn't 'check_perms -f' have fixed that? check_perms is not perfect. See below for more. > This is a server used strictly for mailman. There are only 2 users with > access so I am not worried about the caveat in that article. It looks > like yo

Re: [Mailman-Users] Archives Permission Denied

On 2/25/2020 12:12 PM, Mark Sapiro wrote: > On 2/25/20 6:34 AM, Brian Carpenter wrote: >> On 2/25/20 5:49 AM, Dennis Putnam wrote: >>> IOError: [Errno 13] Permission denied: >>> '/var/lib/mailman/archives/private/rushtalk/2020-February.txt' >>> >>>   I ran check_perms and it found no issues. Howeve

Re: [Mailman-Users] Archives Permission Denied

On 2/25/20 6:34 AM, Brian Carpenter wrote: > On 2/25/20 5:49 AM, Dennis Putnam wrote: >> IOError: [Errno 13] Permission denied: >> '/var/lib/mailman/archives/private/rushtalk/2020-February.txt' >> >>   I ran check_perms and it found no issues. However, when I look at the >> ownership of the archive

Re: [Mailman-Users] Archives Permission Denied

On 2/25/20 5:49 AM, Dennis Putnam wrote: IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/rushtalk/2020-February.txt'  I ran check_perms and it found no issues. However, when I look at the ownership of the archives I get this: -rw-r--r--.    1 root mailman   72404 Feb

[Mailman-Users] Archives Permission Denied

I am in the process of migrating mailman to a new server. It seems to have been done correctly but mailman is unable to write to the archive files. IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/rushtalk/2020-February.txt'  I ran check_perms and it found no issues. Howe

Re: [Mailman-Users] Archives are returning HTTP 403 (Forbidden)

On 03/10/2017 08:22 PM, Dennis Carr wrote: > On Fri, 10 Mar 2017 11:51:19 -0800 > Mark Sapiro wrote: > >> What's in your web server error log for these 403s? > > AH01630: client denied by server > configuration: /var/lib/mailman/archives/public/ffml/, referer: > http://www.chez-vrolet.net/cgi-bi

Re: [Mailman-Users] Archives are returning HTTP 403 (Forbidden)

On Fri, 10 Mar 2017 11:51:19 -0800 Mark Sapiro wrote: > What's in your web server error log for these 403s? AH01630: client denied by server configuration: /var/lib/mailman/archives/public/ffml/, referer: http://www.chez-vrolet.net/cgi-bin/mailman/listinfo/ffml Time to do some debugging in that

Re: [Mailman-Users] Archives are returning HTTP 403 (Forbidden)

On 3/10/17 11:45 AM, Dennis Carr wrote: > On Fri, 10 Mar 2017 07:45:40 -0800 > Mark Sapiro wrote: >> >> The /var/lib/mailman/archives/private directory itself must either be >> o+x or owned by the web server user. > > Confirmed, they are indeed o+x and owned by www-data, group 'list'. What's

Re: [Mailman-Users] Archives are returning HTTP 403 (Forbidden)

On Fri, 10 Mar 2017 07:45:40 -0800 Mark Sapiro wrote: > On 03/10/2017 06:56 AM, Dennis Carr wrote: > > Of late, I've just received word that my archives are returning HTTP > > 403 - forbidden. So nobody can see them. > > > If these are public archives, i.e. 'pipermail' URLs, see the Warning >

Re: [Mailman-Users] Archives are returning HTTP 403 (Forbidden)

On 03/10/2017 06:56 AM, Dennis Carr wrote: > Of late, I've just received word that my archives are returning HTTP > 403 - forbidden. So nobody can see them. If these are public archives, i.e. 'pipermail' URLs, see the Warning box at . The /var/lib

[Mailman-Users] Archives are returning HTTP 403 (Forbidden)

Of late, I've just received word that my archives are returning HTTP 403 - forbidden. So nobody can see them. Checking the file system, it doesn't appear to be a Linux issue necessarily - permissions are set so anybody can read the directory. In general, /var is set 755, /var/lib/mailman and /var

Re: [Mailman-Users] archives not migrated properly

On 11/20/2014 11:38 PM, David Benfell wrote: > > I migrated from Linux to FreeBSD a few months ago and I'm just now > (yes, shame on me) noticing that my archives are broken. I've tried a > few things to fix this but I'm still getting 403 Forbidden. > > First, here is the current Apache (2.4) con

[Mailman-Users] archives not migrated properly

Hi all, I migrated from Linux to FreeBSD a few months ago and I'm just now (yes, shame on me) noticing that my archives are broken. I've tried a few things to fix this but I'm still getting 403 Forbidden. First, here is the current Apache (2.4) configuration: ServerAdmin benf...@parts-un

Re: [Mailman-Users] Archives stopped being created

Walter Logeman wrote: > >I looked at the archives for an active group we have and they stopped in >Julyou. > >The archives were set to yearly but appear to now show a monthly view. > >Any ideas? Check the list's Archiving Options settings. If that doesn't solve your issue, make sure ArchRunner i

[Mailman-Users] Archives stopped being created

Hi All I looked at the archives for an active group we have and they stopped in Julyou. The archives were set to yearly but appear to now show a monthly view. Any ideas? Cheers, Walter -- Mailman-Users mailing list Mailman-Users@python.org ht

Re: [Mailman-Users] Archives not updating

Robert (Bob) Hamilton wrote: > >Back in 2005 I installed Mailman on a hosting server and until now >the Archiving feature has worked flawlessly archiving all the >messages sent to the list until January 27th, 2012 when it stopped. I >have looked at all the setup features and everything is fine s

[Mailman-Users] Archives not updating

Hello, Back in 2005 I installed Mailman on a hosting server and until now the Archiving feature has worked flawlessly archiving all the messages sent to the list until January 27th, 2012 when it stopped. I have looked at all the setup features and everything is fine so I am not sure why this

[Mailman-Users] Archives Display Working Properly Now

: [Mailman-Users] Archives Display not Formatting Properly Friends, I'm migrating my list server from Solaris 10 w/Apache 2.2.17 to RHEL 6 w/Apache 2.2.19 (or .21). For the life of me, I can't get the archive display to show anything other than what I've posted below (which is

[Mailman-Users] Archives Display not Formatting Properly

Friends, I'm migrating my list server from Solaris 10 w/Apache 2.2.17 to RHEL 6 w/Apache 2.2.19 (or .21). For the life of me, I can't get the archive display to show anything other than what I've posted below (which is an Apache-httpd directory listing). If I have my Apache directory "options

Re: [Mailman-Users] archives of sibling lists

Lucio Chiappetti wrote: >I have set up (for a transitory activity lasting about one month) a couple >of lists (A and B) with real subscribers, and an umbrella list C with no >members, but having A and B as sibling lists. > >I have set up the lists with private archives. > >Now it is clear that

[Mailman-Users] archives of sibling lists

I have set up (for a transitory activity lasting about one month) a couple of lists (A and B) with real subscribers, and an umbrella list C with no members, but having A and B as sibling lists. I have set up the lists with private archives. Now it is clear that members of A or B can access the

Re: [Mailman-Users] Archives Link

Dennis Putnam wrote: > >The error is 403 with this URL: >http://myhost.mydomain.com/pipermail/listname/ > [...] > >ls -l /var/lib/mailman/archives >drwxrws--- 6 mail mail 1024 2011-02-23 04:55 private/ >drwxrwsr-x 2 mail mail 1024 2011-02-23 04:55 public/ /var/lib/mailman/archives/private must be

Re: [Mailman-Users] Archives Link

Sorry. It was half time during one of the NCCA games I was watching and in my haste I left out some details. The error is 403 with this URL: http://myhost.mydomain.com/pipermail/listname/ I've made no changes intentionally (wouldn't check_perms catch problems here). Here are the requisite directo

Re: [Mailman-Users] Archives Link

Dennis Putnam wrote: > >For reasons unknown I am suddenly not at to access list archives (as >admin). I ran check_perms but it found no problems and there is nothing >in the logs. Can someone suggest a course of action to debug this? TIA. To what archive URL are you going and what happens when yo

Re: [Mailman-Users] Archives Link

On Sun, Mar 20, 2011 at 08:50:47PM -0400, Dennis Putnam wrote: > For reasons unknown I am suddenly not at to access list archives (as > admin). I ran check_perms but it found no problems and there is nothing > in the logs. Which logs? > Can someone suggest a course of action to debug this? TIA.

[Mailman-Users] Archives Link

For reasons unknown I am suddenly not at to access list archives (as admin). I ran check_perms but it found no problems and there is nothing in the logs. Can someone suggest a course of action to debug this? TIA. signature.asc Description: OpenPGP digital signature --

Re: [Mailman-Users] Archives heading without domain name

"Danny hendrawan" wrote: >How to set the headings as per your Searchable Archives: >http://www.mail-archive.com/mailman-users%40python.org/ ? i.e. only >shows >member's name with domain name Use mail-archive.com as your list's archiver. -- Mark Sapiro - m...@msapiro.net Sent from my An

[Mailman-Users] Archives heading without domain name

Hi Mark and All, I set my archives list to 'private' mainly to protect email addresses of members being disclosed on the heading. I've set my heading to replace '@' with 'at' but still this can be easilly taken by anyone. i.e. 'john at domain.com' How to set the headings as per your Searchable

[Mailman-Users] Archives! Two neat demos from my GSoC students

As some of you may know, Mailman had a bunch of Google Summer of Code students working on our codebase via Systers, which hired students to do improvements on their Mailman-based list infrastructure. I was mentoring for the project which worked on the archives, where we had two students, Yian

Re: [Mailman-Users] Archives

> >> Issue #2 is once again an obvious thing to have checked, but I think > >> archiving must be disabled in mm_cfg.py with > >> > >> ARCHIVE_TO_MBOX = -1 > >Nothing set in mm_cfg.py for that but it is set to -1 in Defaults.py. > I > >just set it to 0, didn't even think about looking in there for i

Re: [Mailman-Users] Archives

Young, Darren wrote: >> >> Issue #2 is once again an obvious thing to have checked, but I think >> archiving must be disabled in mm_cfg.py with >> >> ARCHIVE_TO_MBOX = -1 >Nothing set in mm_cfg.py for that but it is set to -1 in Defaults.py. I >just set it to 0, didn't even think about looking in t

Re: [Mailman-Users] Archives

> The text/plain attachment was allowed, but the message was too big. I > trimmed the attachment leaving only a few relevant parts. See my > comments inline and at the end. I had a feeling it would be one or the other. > > >[...] > >drwxrwsr-x 2 rootmailman 4096 Jan 20 12:26 perl-ad-manager-

Re: [Mailman-Users] Archives

Young, Darren wrote: > >There's a lot in there so I attached it. Not sure if this list allows >attachments but I'll try here anyways. The text/plain attachment was allowed, but the message was too big. I trimmed the attachment leaving only a few relevant parts. See my comments inline and at the e

Re: [Mailman-Users] Archives

gt; Subject: RE: [Mailman-Users] Archives > > Young, Darren wrote: > > >> What is the timestamp if you do "ls -ld" here? > > > >[r...@bushlms01 archive]# pwd > >/usr/local/mailman/qfiles/archive > >[r...@bushlms01 archive]# ls -ld > >drw

Re: [Mailman-Users] Archives

Young, Darren wrote: >> What is the timestamp if you do "ls -ld" here? > >[r...@bushlms01 archive]# pwd >/usr/local/mailman/qfiles/archive >[r...@bushlms01 archive]# ls -ld >drwxrws--- 2 mailman mailman 4096 Jan 20 16:04 . So your messages are reaching the archive queue (because it is being upda

Re: [Mailman-Users] Archives

> What is the timestamp if you do "ls -ld" here? [r...@bushlms01 archive]# pwd /usr/local/mailman/qfiles/archive [r...@bushlms01 archive]# ls -ld drwxrws--- 2 mailman mailman 4096 Jan 20 16:04 . > I don't think any of this has anything to do with your archiving > problem. To summarize, > - for th

Re: [Mailman-Users] Archives

Young, Darren wrote: >Yea, ArchRunner is running: > >[r...@bushlms01 archive]# ps -eaf | grep -i arch >mailman 2090 2077 0 Jan20 ?00:00:00 /usr/bin/python >/usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s OK >/usr/local/mailman/qfiles/archive is empty: > >[r...@bushlms01 a

Re: [Mailman-Users] Archives

> Just picking up on something, did you enable archiving before a > post has been sent; i.e., has archiving been set before >1 message > has been sent to the list? > Yep, it was enabled first. -- Mailman-Users mailing list Mailman-Users@python.o

Re: [Mailman-Users] Archives

Original Message- > From: Mark Sapiro [mailto:m...@msapiro.net] > Sent: Wednesday, January 20, 2010 4:46 PM > To: mailman-users@python.org; Young, Darren > Subject: Re: [Mailman-Users] Archives > > Young, Darren wrote: > > > Not much, close in all of them: > >

Re: [Mailman-Users] Archives

On Wed, Jan 20, 2010 at 01:38:49PM -0600, Young, Darren wrote: > I've enabled archives on a mailing list with the following: > archive = yes > archive_private = public > However, in /usr/local/mailman/archives/public there's no directories > and in the browser I get a URL not found error. I've pos

Re: [Mailman-Users] Archives

Young, Darren wrote: > Not much, close in all of them: As I said in another recent reply - "If I had a nickel for every time I didn't realize the obvious ..." :) Is ArchRunner running? What's in /usr/local/mailman/qfiles/archive? > The only one that sticks out but was earlier: > > Jan 20 12:

Re: [Mailman-Users] Archives

0 12:34:52 2010 qrunner(7726): ValueError : day of year out of range > -----Original Message- > From: Mark Sapiro [mailto:m...@msapiro.net] > Sent: Wednesday, January 20, 2010 3:14 PM > To: Young, Darren; mailman-users@python.org > Subject: RE: [Mailman-Users] Archives > &g

Re: [Mailman-Users] Archives

Young, Darren wrote: >The only thing in mailman/archive/private/perl-ad-manager-users is the >index.html. Not much in the logs: > >[r...@bushlms01 logs]# grep perl-ad * This string won't appear in the error log entries. What's in Mailman's error log with timestamps close to these post log entri

Re: [Mailman-Users] Archives

mass sub > -Original Message- > From: Mark Sapiro [mailto:m...@msapiro.net] > Sent: Wednesday, January 20, 2010 1:57 PM > To: Young, Darren; mailman-users@python.org > Subject: Re: [Mailman-Users] Archives > > Young, Darren wrote: > > >I&#x

Re: [Mailman-Users] Archives

Young, Darren wrote: >I've enabled archives on a mailing list with the following: >archive = yes >archive_private = public >archive_volume_frequency = Monthly [...] >However, in /usr/local/mailman/archives/public there's no directories >and in the browser I get a URL not found error. I've posted a

[Mailman-Users] Archives

I've enabled archives on a mailing list with the following: archive = yes archive_private = public archive_volume_frequency = Monthly And the /pipermail/ URL points to /usr/local/mailman/archives/public (httpd.conf stuff): ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" Alias /pipermail/ /usr

Re: [Mailman-Users] Archives Index Page Blank

Brian Carpenter wrote: > >I think I figured out what the problem is. cPanel in its latest release is >now calculating the disk space used by an account's mailing list(s). The >error message I found regarding this particular user was "disk quoted >exceeded" messages. The problem here is this particu

Re: [Mailman-Users] Archives Index Page Blank

> -Original Message- > From: Mark Sapiro [mailto:m...@msapiro.net] > Sent: Thursday, January 07, 2010 9:45 PM > To: Brian Carpenter; mailman-users@python.org > Subject: Re: [Mailman-Users] Archives Index Page Blank > > Brian Carpenter wrote: > > > >I

Re: [Mailman-Users] Archives Index Page Blank

Brian Carpenter wrote: > >I was notified by a client that his archives for his list was not showing >up. When I investigated, I found out all of his archive index pages are >blank, i.e. file size 0. He has 13 lists. The server he is on is a shared >hosting server with other mailman lists (cpanel en

[Mailman-Users] Archives Index Page Blank

Hello MM Community I was notified by a client that his archives for his list was not showing up. When I investigated, I found out all of his archive index pages are blank, i.e. file size 0. He has 13 lists. The server he is on is a shared hosting server with other mailman lists (cpanel environm

Re: [Mailman-Users] Archives and International Character Sets(Mailman2.1.11)

Stefan Förster writes: > If changing a language definition like that, doesn't that mean one > will have to change the various predefined template files, all message > codes for that language and after that recreate the archive files? Normally, yes. But this is *English*. It's reasonably like

Re: [Mailman-Users] Archives and International Character Sets(Mailman2.1.11)

* Mark Sapiro wrote: > Stephen J. Turnbull wrote: > >> Mark Sapiro writes: >> >>> add_language('en', 'English (USA)', 'utf-8', 'ltr') >> >> Shouldn't this probably be default by now? > > > Yes, it should. But, we have superstitious beliefs that something > unintended will be broken by this. Y

Re: [Mailman-Users] Archives and International Character Sets(Mailman2.1.11)

Barry Warsaw writes: > On Mar 28, 2009, at 10:23 AM, Mark Sapiro wrote: > > Yes, it should. But, we have superstitious beliefs that something > > unintended will be broken by [setting the default encoding to > > UTF-8]. Oh, me too! The Ghost of Charsets Past will undoubtedly rise up to remind

Re: [Mailman-Users] Archives and International Character Sets(Mailman2.1.11)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mar 28, 2009, at 10:23 AM, Mark Sapiro wrote: Stephen J. Turnbull wrote: Mark Sapiro writes: add_language('en', 'English (USA)', 'utf-8', 'ltr') Shouldn't this probably be default by now? Yes, it should. But, we have superstitious belief

Re: [Mailman-Users] Archives and International Character Sets(Mailman2.1.11)

Stephen J. Turnbull wrote: >Mark Sapiro writes: > > > add_language('en', 'English (USA)', 'utf-8', 'ltr') > >Shouldn't this probably be default by now? Yes, it should. But, we have superstitious beliefs that something unintended will be broken by this. Yet, I continue to suggest it as a workarou

Re: [Mailman-Users] Archives and International Character Sets (Mailman2.1.11)

Mark Sapiro writes: > add_language('en', 'English (USA)', 'utf-8', 'ltr') Shouldn't this probably be default by now? I'm usually pretty hesitant to mess with existing defaults, but as I understand this there's actually corrupt data in the .txt files. This can be a real headache for people usin

Re: [Mailman-Users] Archives and International Character Sets (Mailman2.1.11)

Drew Tenenholz wrote: > >The list is a announce-only type in Russian (Cyrillic), but the >default language is set to English (so I can read the admin pages and >complete the necessary tasks). As I believe Mark mentioned before, >this means that the messages themselves (sent by the Russian >Mod

[Mailman-Users] Archives and International Character Sets (Mailman 2.1.11)

Guys -- I have a problem with the monthly archives from Mailman 2.1.11 (using Pipermail 0.09 [default]) and wonder if there is any help available. I've read several FAQs, but no luck in understanding the problem yet. The list is a announce-only type in Russian (Cyrillic), but the default lan

Re: [Mailman-Users] Archives Sort Order

Johnny Stork wrote: >Is there any way to force the sort order in the archives to show the >most recent at the top, rather than at the bottom? Not without modifying pipermail which would be a daunting task only for the extremely courageous. -- Mark Sapiro <[EMAIL PROTECTED]>The highway

[Mailman-Users] Archives Sort Order

Is there any way to force the sort order in the archives to show the most recent at the top, rather than at the bottom? -- Johnny Stork Open Enterprise Solutions "Empowering Business With Open Solutions" http://www.openenterprise.ca -- Mailma

Re: [Mailman-Users] Archives not accessible

[EMAIL PROTECTED] wrote: >I was able to get the hostname resolved by running the fix_url script. >Now I am running into a new problem. I am not able to access the >archives of the lists I just created. The first list says "Forbidden - >You don't have permission to access /pipermail/jewel/ on thi

[Mailman-Users] Archives not accessible

I was able to get the hostname resolved by running the fix_url script. Now I am running into a new problem. I am not able to access the archives of the lists I just created. The first list says "Forbidden - You don't have permission to access /pipermail/jewel/ on this server." My second list is m

Re: [Mailman-Users] archives generation on new server

Manuel Goepfert wrote: > >Actually already when generating my archives with bin/arch I have some >problems, the accents are not properly handled meaning I find the current >date/time in emails that are back in 2005 just because the month in the >header contains a "é" for example. Date: headers sh

Re: [Mailman-Users] archives generation on new server

Hi Mark, > I suspect the issue is that the archive pages are in one character set (iso-8859-1 ?) and the web server is declaring them to be something else (utf-8 ?). I was not clear in my initial email. Actually already when generating my archives with bin/arch I have some problems, the accents

Re: [Mailman-Users] archives generation on new server

Manuel Goepfert wrote: > >While moving the lists themself is really easy, I have an issue with the >archives. It seems that the "accents" like éèà are not properly handled. > >The content-type from the headers is charset=ISO-8859-1 > >I've tryed to google or look into the FAQ without success so far

[Mailman-Users] archives generation on new server

Hi Everybody, I'm currently moving to a new server my lists. Old version is 2.1.7 new version is 2.1.9 While moving the lists themself is really easy, I have an issue with the archives. It seems that the "accents" like éèà are not properly handled. The content-type from the headers is charset=IS

Re: [Mailman-Users] Archives Forbidden

Yes that did it! I had all the folders set correctly *except* for the /private folder itself. Changing that from root to www-data did it for me. Thanks! Rob Mark Sapiro wrote, On 6/9/2008 7:28 AM: Rob Brandt wrote: In any case, I changed it to: Order allow,deny Allow from all

Re: [Mailman-Users] Archives Forbidden

Rob Brandt wrote: >In any case, I changed it to: > > > Order allow,deny > Allow from all > Options Indexes FollowSymLinks > > >restarted apache and it's still Forbidden. And Bob Eager wrote (with a 'digest' subject): >Who owns the folders? They (and contents) need to be readable by

Re: [Mailman-Users] Archives Forbidden

although selinux itself isn't installed... Rob Brandt wrote: Hey, maybe so. I wasn't aware of it, but the packages libselinux1 2.0.55-0ubuntu4 and libsepol1 2.0.20-0ubuntu3 are installed. I'll look in to it. Rob Steven Stern wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/08/200

Re: [Mailman-Users] Archives Forbidden

Hey, maybe so. I wasn't aware of it, but the packages libselinux1 2.0.55-0ubuntu4 and libsepol1 2.0.20-0ubuntu3 are installed. I'll look in to it. Rob Steven Stern wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/08/2008 05:30 PM, Rob Brandt wrote: | I have a new installation I'm t

Re: [Mailman-Users] Archives Forbidden

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/08/2008 05:30 PM, Rob Brandt wrote: | I have a new installation I'm testing. I'm on a fresh install of | ubuntu, mailman compiled from scratch. | | Mostly working now, but the mailing list public archives are show as | forbidden in my browser.

Re: [Mailman-Users] Archives Forbidden

Not intentionally, and I just combed through the conf files and see no reference. In any case, I changed it to: Order allow,deny Allow from all Options Indexes FollowSymLinks restarted apache and it's still Forbidden. Rob Mark Sapiro wrote: Rob Brandt wrote: Yes, in apache2.

Re: [Mailman-Users] Archives Forbidden

Rob Brandt wrote: >Yes, in apache2.conf, I have: > > >Options Indexes FollowSymLinks > Do you implicitly not allow your access? You might need Order allow,deny Allow from all inside the Directory section if you have a Deny on a superordinate directory. What's in apache's error_log? --

Re: [Mailman-Users] Archives Forbidden

Yes, in apache2.conf, I have: Options Indexes FollowSymLinks I tried it without the trailing slash on the path too. Rob Brad Knowles wrote: On 6/8/08, Rob Brandt wrote: Mostly working now, but the mailing list public archives are show as forbidden in my browser. The data is actually th

Re: [Mailman-Users] Archives Forbidden

On 6/8/08, Rob Brandt wrote: Mostly working now, but the mailing list public archives are show as forbidden in my browser. The data is actually there in the folders, stored in private and symlinked to public. I've run permissions check and everything is OK (it says). What's my trouble?

[Mailman-Users] Archives Forbidden

I have a new installation I'm testing. I'm on a fresh install of ubuntu, mailman compiled from scratch. Mostly working now, but the mailing list public archives are show as forbidden in my browser. The data is actually there in the folders, stored in private and symlinked to public. I've ru

Re: [Mailman-Users] archives

Melinda Gilmore wrote: Is there a way to automate deletion by size of archives through mailman. Not with the standard software we ship, no. Has anyone done that out there. I want to delete any archives that have grown large in size by date preferrably. Check the patches page on SourceForg

[Mailman-Users] archives

Is there a way to automate deletion by size of archives through mailman. Has anyone done that out there. I want to delete any archives that have grown large in size by date preferrably. Melinda Gilmore Systems Engineer The Ohio State University Enterprise Messaging/OIT 614-292-4953 -

Re: [Mailman-Users] Archives for a single list mysteriously stopped

Chris Waltham wrote: > >I just ran a "arch --wipe ams-announce", and that seems to have fixed >the problem as a test message I sent this morning now appears in the >archives; as does other mail that was sent after March 19th and before >today. Just out of interest, what kind of things could s

[Mailman-Users] Archives for a single list mysteriously stopped

I have a list which is still passing messages correctly (the list is moderated) but messages are not appearing in the archives since March 19, 2008. And, no, I don't think I changed anything on that day. :-) A simple "check_perms" reports no issues at all, and archives for other lists are fu

Re: [Mailman-Users] Archives not showing complete email message

Paul Key wrote: > >I am also getting the following where the body of an email should be in >the list archives: > >Skipped content of type multipart/alternative-- next part >-- >A non-text attachment was scrubbed... >Name: not available >Type: image/jpeg >Size: 4631 bytes >

[Mailman-Users] Archives not showing complete email message

Hi I am also getting the following where the body of an email should be in the list archives: Skipped content of type multipart/alternative-- next part -- A non-text attachment was scrubbed... Name: not available Type: image/jpeg Size: 4631 bytes Desc: not available Url

Re: [Mailman-Users] Archives

| | Dave Foran wrote: | | >Allow me to ask this regarding Archives | > | >As stated I have some lists I created to replace what was being done by | >Smartlist, and the SmartList archive is extensive.. One going back maybe 8 | >years. | > | >Is there a feasible way to import the old archives into

Re: [Mailman-Users] Archives

Dave Foran wrote: >Allow me to ask this regarding Archives > >As stated I have some lists I created to replace what was being done by >Smartlist, and the SmartList archive is extensive.. One going back maybe 8 >years. > >Is there a feasible way to import the old archives into MailMan archives in

[Mailman-Users] Archives

Allow me to ask this regarding Archives As stated I have some lists I created to replace what was being done by Smartlist, and the SmartList archive is extensive.. One going back maybe 8 years. Is there a feasible way to import the old archives into MailMan archives in some fashion ?? I Guess I

Re: [Mailman-Users] Archives and bad timestamps

At 2:13 AM -0500 2006-08-12, Brad Knowles wrote: >> There doesn't seem to be an option for archive sequence in the admin >> pages, is there an option at the shell level to use the transit time >> instead of the original timestamp? Should there be? > > IIRC, if you select the appropriate opt

Re: [Mailman-Users] Archives and bad timestamps

At 7:47 PM -0700 2006-08-11, G. Armour Van Horn wrote: > I've just noticed that one of the lists I'm moderating shows messages > from next Monday in the private archive. The last message is timestamped > for 8:08 (Pacific, +0700) on 14 Aug, but was actually distributed by > Mailman at 08:51 on

[Mailman-Users] Archives and bad timestamps

I've just noticed that one of the lists I'm moderating shows messages from next Monday in the private archive. The last message is timestamped for 8:08 (Pacific, +0700) on 14 Aug, but was actually distributed by Mailman at 08:51 on 11 Aug. Unfortunately, the archive seems to be ordered by times

Re: [Mailman-Users] archives has bad group of list, how to fix?

Dragon wrote: >Jana Nguyen sent the message below at 14:02 7/28/2006: >>Hi there, >> >>I ran the "bin/check_perms script" and got the following output to be >>fix, I'm not sure what is the problem, and how to fix it: >> >>/usr/local/mailman/archives/public/birntest bad group (has: jnguyen, >>expec

Re: [Mailman-Users] archives has bad group of list, how to fix?

Jana Nguyen sent the message below at 14:02 7/28/2006: >Hi there, > >I ran the "bin/check_perms script" and got the following output to be >fix, I'm not sure what is the problem, and how to fix it: > >/usr/local/mailman/archives/public/birntest bad group (has: jnguyen, >expected mailman) (fixing) >

[Mailman-Users] archives has bad group of list, how to fix?

Hi there, I ran the "bin/check_perms script" and got the following output to be fix, I'm not sure what is the problem, and how to fix it: /usr/local/mailman/archives/public/birntest bad group (has: jnguyen, expected mailman) (fixing) p.s. 'jnguyen' is my username. Thanks! -

Re: [Mailman-Users] archives not generating in monthly index.

Guntupalli Karunakar wrote: > We are facing some problems with main html index missing index of >months - march, april 2006. > >running arch script for a list , generates the main index again >properly, but it is lost (march, april ones) after sometime, >typically after some more new mails are

[Mailman-Users] archives not generating in monthly index.

Hi all, We are facing some problems with main html index missing index of months - march, april 2006. eg see following lists http://mail.sarai.net/pipermail/deewan/ http://mail.sarai.net/pipermail/deewan/ the index doesnt show march 2006 & april 2006. Though they show up in this form. http://

Re: [Mailman-Users] Archives not working (yes, I broke it...)

Dragon wrote: > >But now the archive simply will not work. Nothing gets added to the archive >mbox file when I post to the list nor can I access the archive web pages >(and yes, I double-checked the list archive settings and made sure the >archive files are all still there). I am using the built

[Mailman-Users] Archives not working (yes, I broke it...)

I was doing some edits of the archive template files on my installation of Mailman 2.1.5 Long story short, I ran into some write permission problems when trying to upload my edited versions and in a fit of bone-headedness, I screwed up a bunch of permissions by over zealously using the -R optio

Re: [Mailman-Users] Archives

Raquel Rice wrote: a 'private' in the src/ directory, >> how does it compare to 'private.bad'. >>=20 >> You could just try >>=20 >> mv private.bad private >>=20 >> and see what happens. >>=20 >> --=20 >> Mark Sapiro=20 > >It seems to me that the problem lies with the >Debian maintainer of Mailman.

Re: [Mailman-Users] Archives

On Wed, 21 Dec 2005 12:38:13 -0800 Mark Sapiro <[EMAIL PROTECTED]> wrote: > Raquel Rice wrote: > > > >I do have a file named "private.bad" in the cgi-bin directory. I > >have no idea why it's named that way. (in other words, I didn't > >do it) > > How did you install Mailman? If you installed f

Re: [Mailman-Users] Archives

Hugh Esco wrote: > edit your apache config to read: > Alias /pipermail/ /usr/local/mailman/archives/ > not what you now have pointing directly to the private/ subdirectory. It needs to be Alias /pipermail/ /usr/local/mailman/archives/public/ not Alias /piperma

Re: [Mailman-Users] Archives

Raquel Rice wrote: > >I do have a file named "private.bad" in the cgi-bin directory. I >have no idea why it's named that way. (in other words, I didn't do >it) How did you install Mailman? If you installed from source and you still have the directory you ran configure and make in, what is in the

  1   2   3   >