headers
webulous | 7 Aug 2003 12:06
Picon
Picon
Favicon

archiving

I had an archive up and running and doing fine. I did not change anything to
the setting but messages are being send but not archived. Anyone have a hint
as to what the problem might be?

Also does anyone know if it possible to have the number of messages in a
thread mentioned in the archive.

thanks,

Jeroen
Permalink | Reply | 0 comments |
headers
Glenn Sieb | 1 Aug 2003 01:10
Favicon

I guess it's my week for problems, sorry :(

When I search two lists, I get this error: (Note: htdig is working for
other lists just fine, just not *these two* lists...)

htdig Archives Access Failure

 The requested list cannot be accessed. list:list.htsearch

If you want to make another attempt to access a list archive then go via
the list users information page.

If this problem persists then please e-mail the following information to
the mailman <at> lists.wingfoot.org:

    https://www.wingfoot.org/mailman/private/list/
    /mailman/mmsearch/list

Again, I run FreeBSD 4.8-STABLE, MM 2.1.2, Postfix 2.0.10,
postfix-to-mailman.py (for 2.1), and Apache 1.3.27 w/mod_perl.

I did the following steps:

1) check_perms -f (didn't find anything)
2) went to /usr/local/mailman/archives/private and did:
    chown -R mailman:mailman *
3) Restarted apache, same error
4) did /usr/local/mailman/bin/blow_away_htdig -v list
5) posted to list
6) did /usr/local/mailman/cron/nightly_htdig -v list
7) restarted apache (for good measure), same error
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Barrett | 1 Aug 2003 01:42
Picon
Favicon

Re: I guess it's my week for problems, sorry :(

I suggest you try the following procedure for the two problem list:

1. run bin/blow_away_htdig for the problem lists with the -c option to 
rebuild
per-list htdig conf files and delete existing per-list search indexes. 
This should delete the per-list htdig related stuff and remove the 
search form from those lists' archive TOC pages. It should not affect 
the HTML archives themselves

2. send a test message to each of the problem lists. This should ensure 
the per-list htdig related stuff (with the exception of the search 
indexes) is fully recreated and the search form is added back to those 
lists' archive TOC pages

3. run the nightly_htdig cron script from the command line for the two 
problem lists. This should rebuild the htdig search indexes

Let me know if this fixes the problem or not.

Were you originally running a version of the htdig integration patch 
earlier than that installed by htdig-2.1.1-0.2.patch? If so this may be 
the cause of problems with archived lists created under that earlier 
regime. The upgrade issue was covered in the INSTALL.htdig-mm file for 
htdig-2.1.1-0.2.patch or later and I am wondering if you have tripped 
over this issue.

The major change introduced by htdig-2.1.1-0.2.patch was that htsearch 
is not called directly by the search forms. For security reason a CGI 
called mmsearch is called which in turn uses htsearch. This is 
described in INSTALL.htdig-mm
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christine De La Rosa | 1 Aug 2003 01:48

RE: Analysis of reasons for bounce responses

This is the EXACT problem I am having with mailman, using cpanel and
exim.  I, however, am on a dedicated box and have root access.  I have
been working on this problem for over three weeks.  I am tired and
frustrated and wishing I knew a little more about mailman and its inner
workings.  I come from a majordomo background.  When I got this
dedicated server, it had mailman pre-installed so I thought kewl I will
use it instead.  It ran fabulously until cpanel did their last upgrade.
I have been in hell since then.  

I wish I could help you, but I have not been able to figure out even
from the logs what the issues are.  Granted, looking at the logs are
like gobbledigook to me.  So I have spent a lot of time searching the
archives for this problem.  Although, I haven't been able to find anyone
with my specific issue.  I can tell you that qrunner has been consuming
my cpu at astonishing rates.  But there is no rhyme or reason to that,
that I can see.  If I find anything out I will post it here.

Chris

-----Original Message-----
From: mailman-users-bounces+chris=christinedelarosa.com <at> python.org
[mailto:mailman-users-bounces+chris=christinedelarosa.com <at> python.org] On
Behalf Of Richard Barrett
Sent: Thursday, July 31, 2003 5:08 AM
To: Mailman
Subject: [Mailman-Users] Analysis of reasons for bounce responses

This is not my problem but one soemone approached me about off list.  
I'll summarise their situation and I would appreciate any thoughts,  
comments, sanity checking on my analysis.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Richard Barrett | 1 Aug 2003 02:29
Picon
Favicon

Re: Analysis of reasons for bounce responses

Chris

On Friday, August 1, 2003, at 12:48  am, Christine De La Rosa wrote:

> This is the EXACT problem I am having with mailman, using cpanel and
> exim.  I, however, am on a dedicated box and have root access.  I have
> been working on this problem for over three weeks.  I am tired and
> frustrated and wishing I knew a little more about mailman and its inner
> workings.

As I said in my post, this bounce issue is not, in my view, at heart a  
bug in Mailman. The evidence I saw of bounce notices from local MTA  
(Exim) say that the MTA is having problems getting outgoing mail off  
the system and finally bouncing it back to Mailman when it fails to do  
so.

If you are getting final bounce notices from Mailman when it disables a  
subscriber because of these problems what is the reason reported in the  
bounce message from the MTA, which should be attached to the bottom of  
the final bounce notification from MM? In the example final bounce  
notice passed to me for comment the MTA was reporting it was having an  
IP routing problem; that is hardly a Mailman generated problem as far  
as I can tell.

One of my problems with looking at this is I am trying to help out a  
fairly new user with a problem I have not seen on my systems, while I  
have no access to the Mailman or MTA logs on a system experiencing the  
problem. I have no standing with the CPanel owners to raise matters  
with them in case they are contributing to the problem with the way  
they set things up. Deeply frustrating.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Todd | 1 Aug 2003 02:43
Picon
Favicon

Re: Analysis of reasons for bounce responses


Christine De La Rosa wrote:
> When I got this dedicated server, it had mailman pre-installed so I
> thought kewl I will use it instead.  It ran fabulously until cpanel did
> their last upgrade.  I have been in hell since then.  

Unfortunately, I work on a site which is hosted using cPanel.  It's a far
cry from the problem free experience I have with my own mailman installs
which "just work."  When they finally did the upgrade to 2.1.2, I had some
immediate problems with bounces but then the server admin applied an update
from cPanel that seems to have fixed that.  I don't know it the bounces were
at all similar to what you're having, but I mention it in case you haven't
applied whatever updates cPanel has pushed out.  It was either a mailman or
exim update, I'm not sure since I don't admin the box.

Of course, the cPanel upgrade to 2.1.2 also broke some virtual host stuff
for me that I have yet to get the host to work out.  I have tried and tried
to contact the folks at cPanel directly to find out what patches they apply
to mailman and request the sources for those changes (as *required* by the
GPL) to no avail.  They have simply ignored me.  I find that really
annoying.  If anyone knows of a way to reach someone at cPanel, please let
us know.  I'd like to point out to them that they *need* to make their
changes available to the public.  I'm not a fan of folks making money off of
the work of open source software and then not even having the courtesy of
honoring the few license requirements there are.

--

-- 
Todd              OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp
============================================================================
I got stopped by a cop the other day.  He said, "Why'd you run that stop
(Continue reading)

Permalink | Reply | 0 comments |
headers
Scot Mc Pherson | 1 Aug 2003 03:17
Picon
Favicon

Threading preservation

Is there a configuration to turn on/off threading by message-ID?

--

-- 
Scot Mc Pherson
Linux From Scratch
http://www.linuxfromscratch.org/~scot/
Permalink | Reply | 0 comments |
headers
Glenn Sieb | 1 Aug 2003 05:33
Favicon

Re: I guess it's my week for problems, sorry :(

Richard Barrett wrote:

> I suggest you try the following procedure for the two problem list:

Hey Richard... as always, I appreciate your efforts :) I did what you
outlined, but it didn't work :(

> Were you originally running a version of the htdig integration patch
earlier than that installed by htdig-2.1.1-0.2.patch? If so this may be
the cause of problems with archived lists created under that earlier
regime. The upgrade issue was covered in the INSTALL.htdig-mm file for
htdig-2.1.1-0.2.patch or later and I am wondering if you have tripped
over this issue.

Correct, I was running the htdig-2.1-0.1.patch.

Unfortunately, now none of my searchables are working. Archiving seems
fine, but searching any list is producing (given a blank search term):

htdig Archives Access Failure

CGI problem. -5-Field count -4- fields: method,format,sort,config

If you want to make another attempt to access a list archive then go via
the list users information page.

If this problem persists then please e-mail the following information to
the mailman <at> lists.wingfoot.org:

    https://www.wingfoot.org/pipermail/listname/
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jon Carnes | 1 Aug 2003 05:46
Picon

Re: Analysis of reasons for bounce responses

If anyone has sysadmin access to a server running CPanel, I would be
happy do some trouble-shooting on the problem.

>From the aggregate complaints it sounds like Cpanel has introduced an
error with Exim. It could be something as simple as a timeout value.

Are the servers also running a local DNS server - and set to resolve
using 127.0.0.1 as the primary nameserver? There are so many things that
could be a problem...

On Thu, 2003-07-31 at 20:43, Todd wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Christine De La Rosa wrote:
> > When I got this dedicated server, it had mailman pre-installed so I
> > thought kewl I will use it instead.  It ran fabulously until cpanel did
> > their last upgrade.  I have been in hell since then.  
> 
> Unfortunately, I work on a site which is hosted using cPanel.  It's a far
> cry from the problem free experience I have with my own mailman installs
> which "just work."  When they finally did the upgrade to 2.1.2, I had some
> immediate problems with bounces but then the server admin applied an update
> from cPanel that seems to have fixed that.  I don't know it the bounces were
> at all similar to what you're having, but I mention it in case you haven't
> applied whatever updates cPanel has pushed out.  It was either a mailman or
> exim update, I'm not sure since I don't admin the box.
> 
> Of course, the cPanel upgrade to 2.1.2 also broke some virtual host stuff
> for me that I have yet to get the host to work out.  I have tried and tried
(Continue reading)

Permalink | Reply | 0 comments |
headers
Christine De La Rosa | 1 Aug 2003 06:30

RE: Analysis of reasons for bounce responses

Hi Richard,

Here is what I know so far, mail for most list members seem to be going
through for the most part.  About two weeks ago MM mass unscribed about
300 folx. Now we seem to have stablized the members but the owners of
the lists are getting routinely bounced.  Yahoo email address do not
have a problem, aol is a major headache as is hotmail.  What is
happening on my side is that the sub notices are never reaching the
owners, so they are bouncing like mad and eventually hit the excessive
bounce phase after five days (since we have the settings set to set to
nomail after 5 bounces and mailman set to send notifcations once a day).

I have been monitoring this list and the cpanel forums
(http://forums.cpanel.net) to see if this issue is resolved.  I have
tried several of the fixes they had on there to no avail.  Although they
have set out a new fix
http://forums.cpanel.net/showthread.php?s=&threadid=12740&highlight=mail
man for the qrunner eating up cpu, but I haven't tried it yet.  I am
basically trying to find bits and pieces and make them into a whole that
will fix my problems.    

 this is clipped and pasted from a final bounce message I am getting
from MM.  Since I don't really know how to read bounces I am not sure if
the issue is on my side, their side or somewhere in the middle.  Please
note that the email that bounced on the sub notice is getting all its
mail from just regular list mail.

Hope this helps!  Back to the quest!

Chris
(Continue reading)

Permalink | Reply | 0 comments |

Gmane