Re: [Mailman-Users] I guess it's my week for problems, sorry :(

[Richard Barrett]

On Friday, August 1, 2003, at 04:33  am, Glenn Sieb wrote:

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

The error response is saying that a field in the search form that 
mmsearch.py insists be present is missing.

The required fields are called: 'method', 'format', 'sort', 'config' 
and 'words'.

The 'words' field appears to be missing, this being the text field in 
which the words to be sought are entered on the form.

The template for the search form is in templates/en/TOC_htsearch.html.

The default value for the words field is the empty string with the tag 
for the field defined as 'input type="text" size="30" name="words" 
value=""'

Take a look at the HTML form definition source of a list TOC page for a 
list that is suffering this problem and compare it with 
templates/en/TOC_htsearch.html.

This may give some clue as to the cause of this problem.

The blow_away_htdig etc routine I described and as described in 
INSTALL.htdig-mm should renew per-list search forms from the 
TOC_htsearch.html template.

Let me know how you get on.

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 [EMAIL PROTECTED]:

https://www.wingfoot.org/pipermail/listname/
/mailman/mmsearch/listname
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

*nod* I see that... nifty :)

Again, thank you for your help... :)
Glenn

---
Richard Barrett   http://www.openinfo.co.uk
--
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

RE: [Mailman-Users] Analysis of reasons for bounce responses

[Christine De La Rosa]

Oh I forgot to add, that my dedicated is also a nameserver (domain.com)
with about 10 hosted domains (domain1.com, domain2.com...)

Chris

-Original Message-
From: Richard Barrett [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 31, 2003 7:30 PM
To: Christine De La Rosa
Cc: 'Mailman'
Subject: Re: [Mailman-Users] 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.

Let me know if you gain any insight or information related to this.

> 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.

Mailman can consume large amounts of CPU when the MTA it is trying to  
hand mail over to repeatedly returns temporary failures. MM can be too  
aggressive in repeatedly trying to get the MTA to either accept or  
permanently fail the handover. There are changes in the Mailman CVS to  
moderate MM's efforts in this respect but so far as I know those  
changes are not available as a patch for MM 2.1.2 stable. This issue  
may be affecting you but I am no expert myself in setting up Exim so as

to avoid this undesirable interaction; I do not see it with my Sendmail

setup. There have been posts to mailman-users on the topic of high CPU  
utilisation. This one fromJon Carnes relates to Postfix MTA but its  
substance/recommendations may be applicable to Exim:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg17786.html

>  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: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> 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.
>
> Situation:
>
> 1. List admin's domain is hosted by a server run by a hosting company.
>
> 2. The server is (probably) running Linux
>
> 3. Mailman 2.1.2 is provided on the server with, I believe, CPanel
>
> 4. The server's MTA appears to be Exim 4.20 handling both incoming and
> outgoing messages to/from Mailman
>
> 5. Mailman list's basically work OK much of the time
>
> 6. Periodically messages out from Mailman are being bounced en masse
> leading to the subscriber accounts being disabled
>
> 7. The bounce response attached to the bounce action notice produced
by
>
> Mailman when subscribers are disabled in these circumstances is from
> the server local MTA. The MTA lists what appears to be all the
> addresses to which the outgoing message was sent with a note against
> each saying "unrouteable mail domain maildomain.tld". The bounce
> response asserts that this is a permanent failure. The messages are
> each being sent to a number of different mail domains not just a
single
>
> one
>
> 8. The list admin with 

RE: [Mailman-Users] Analysis of reasons for bounce responses

[Christine De La Rosa]

I checked my hosts file here it is

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1   alpha.domain2.com localhost
64.62.144.106   alpha.domain2.com localhost

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Jon Carnes
Sent: Thursday, July 31, 2003 10:47 PM
To: Todd
Cc: 'Mailman'
Subject: Re: [Mailman-Users] 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 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
> sign?"  I said, "Because I don't believe everything I read."
> -- Stephen Wright
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3rc2 (GNU/Linux)
> Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
> 
> iD8DBQE/KbfEuv+09NZUB1oRAuC3AKCsj14RKywYjQtf3cXdIbFW2tOGtgCgsI7w
> jQdIuKN2/Ut9E4BwKyiOH/o=
> =27TD
> -END PGP SIGNATURE-
> 
> --
> 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/jonc%40nc.rr.com


--
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/chris%40christinede
larosa.com



--
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

RE: [Mailman-Users] Analysis of reasons for bounce responses

[Christine De La Rosa]

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



This is a Mailman mailing list bounce action notice:

List:   Vegas
Member: [EMAIL PROTECTED]
Action: Subscription disabled.
Reason: Excessive or fatal bounces.



The triggering bounce notice is attached below.

Questions? Contact the Mailman site administrator at
[EMAIL PROTECTED]

From: "Mail Delivery System" <[EMAIL PROTECTED]> 
To: [EMAIL PROTECTED] 
Subject: Mail delivery failed: returning message to sender 
Date: Mon, 28 Jul 2003 08:02:13 -0700 


This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) 
failed:

  [EMAIL PROTECTED]
SMTP error from remote mailer after MAIL 
FROM:<[EMAIL PROTECTED]>:
host mailin-01.mx.aol.com [152.163.224.26]: 550 REQUESTED ACTION 
NOT TAKEN:
DNS FAILURE
  [EMAIL PROTECTED]
SMTP error from remote mailer after MAIL 
FROM:<[EMAIL PROTECTED]> SIZE=2643:
host nymx-2.nyroc.rr.com [24.92.226.164]: 553 5.1.8 
<[EMAIL PROTECTED]>... Domain of sender address 
[EMAIL PROTECTED] does not exist

-- This is a copy of the message, including all the headers. 
--

Return-path: <[EMAIL PROTECTED]>
Received: from alpha.domain2.com ([127.0.0.1])
by alpha.domain2.com with esmtp (Exim 4.20)
id 19h9UO-0006jA-VB; Mon, 28 Jul 2003 08:00:40 -0700
Received: from [127.0.0.1] (helo=alpha.domain2.com)
by alpha.domain.com with esmtp (Exim 4.20) id 19h9U7-0006h2-MD
for [EMAIL PROTECTED]; Mon, 28 Jul 2003 08:00:23 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: 3 Finewine moderator request(s) waiting
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-ID: 
<[EMAIL PROTECTED]>
Date: Mon, 28 Jul 2003 08:00:01 -0700
Precedence: bulk
X-BeenThere: [EMAIL PROTECTED]
X-Mailman-Version: 2.1.2
List-Id: 
X-List-Administrivia: yes
Sender: [EMAIL PROTECTED]
Errors-To: [EMAIL PROTECTED]

The [EMAIL PROTECTED] mailing list has 3 request(s) waiting 
for
your consideration at:


Please attend to this at your earliest convenience.  This notice of
pending requests, if any, will be sent out daily.

Pending subscriptions:
[EMAIL PROTECTED] (Sue) Sat Jul 19 17:23:45 2003
[EMAIL PROTECTED] (deborah) Thu Jul 24 22:38:08 2003
[EMAIL PROTECTED] (Jen) Sun Jul 27 04:36:20 2003

_



-Original Message-
From: Richard Barrett [mailto:[EMAIL PROTECTED] 
Sent: Thursday, July 31, 2003 7:30 PM
To: Christine De La Rosa
Cc: 'Mailman'
Subject: Re: [Mailman-Users] 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 r

Re: [Mailman-Users] Analysis of reasons for bounce responses

[Jon Carnes]

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
> 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
> sign?"  I said, "Because I don't believe everything I read."
> -- Stephen Wright
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.3rc2 (GNU/Linux)
> Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.
> 
> iD8DBQE/KbfEuv+09NZUB1oRAuC3AKCsj14RKywYjQtf3cXdIbFW2tOGtgCgsI7w
> jQdIuKN2/Ut9E4BwKyiOH/o=
> =27TD
> -END PGP SIGNATURE-
> 
> --
> 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/jonc%40nc.rr.com


--
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

Re: [Mailman-Users] I guess it's my week for problems, sorry :(

[Glenn Sieb]

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 [EMAIL PROTECTED]:

https://www.wingfoot.org/pipermail/listname/
/mailman/mmsearch/listname

> 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

*nod* I see that... nifty :)

Again, thank you for your help... :)
Glenn


--
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

[Mailman-Users] Threading preservation

[Scot Mc Pherson]

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

-- 
Scot Mc Pherson
Linux From Scratch
http://www.linuxfromscratch.org/~scot/

--
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

Re: [Mailman-Users] Analysis of reasons for bounce responses

[Todd]

-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
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
sign?"  I said, "Because I don't believe everything I read."
-- Stephen Wright

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3rc2 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.

iD8DBQE/KbfEuv+09NZUB1oRAuC3AKCsj14RKywYjQtf3cXdIbFW2tOGtgCgsI7w
jQdIuKN2/Ut9E4BwKyiOH/o=
=27TD
-END PGP SIGNATURE-

--
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

Re: [Mailman-Users] Analysis of reasons for bounce responses

[Richard Barrett]

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.

Let me know if you gain any insight or information related to this.

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.
Mailman can consume large amounts of CPU when the MTA it is trying to  
hand mail over to repeatedly returns temporary failures. MM can be too  
aggressive in repeatedly trying to get the MTA to either accept or  
permanently fail the handover. There are changes in the Mailman CVS to  
moderate MM's efforts in this respect but so far as I know those  
changes are not available as a patch for MM 2.1.2 stable. This issue  
may be affecting you but I am no expert myself in setting up Exim so as  
to avoid this undesirable interaction; I do not see it with my Sendmail  
setup. There have been posts to mailman-users on the topic of high CPU  
utilisation. This one fromJon Carnes relates to Postfix MTA but its  
substance/recommendations may be applicable to Exim:

http://www.mail-archive.com/[EMAIL PROTECTED]/msg17786.html

 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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]  
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.
Situation:

1. List admin's domain is hosted by a server run by a hosting company.

2. The server is (probably) running Linux

3. Mailman 2.1.2 is provided on the server with, I believe, CPanel

4. The server's MTA appears to be Exim 4.20 handling both incoming and
outgoing messages to/from Mailman
5. Mailman list's basically work OK much of the time

6. Periodically messages out from Mailman are being bounced en masse
leading to the subscriber accounts being disabled
7. The bounce response attached to the bounce action notice produced by

Mailman when subscribers are disabled in these circumstances is from
the server local MTA. The MTA lists what appears to be all the
addresses to which the outgoing message was sent with a note against
each saying "unrouteable mail domain maildomain.tld". The bounce
response asserts that this is a permanent failure. The messages are
each being sent to a number of different mail domains not just a single
one

8. The list admin with the problem has no access to either the Mailman
or MTA logs
9. The server administrator is supposedly claiming that these bounces
are a result of "a bug in Mailman for which no patch is available"
My analysis is:

1. The problem is not obviously due to any bug in Mailman

2. The problem is more likely due to an IP routing problem which
periodically afflicts the server and its ability to reach the MTAs for
the mail domains addressed by the outgoing messages
3. The MTA is accepting t

RE: [Mailman-Users] Analysis of reasons for bounce responses

[Christine De La Rosa]

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: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] 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.

Situation:

1. List admin's domain is hosted by a server run by a hosting company.

2. The server is (probably) running Linux

3. Mailman 2.1.2 is provided on the server with, I believe, CPanel

4. The server's MTA appears to be Exim 4.20 handling both incoming and  
outgoing messages to/from Mailman

5. Mailman list's basically work OK much of the time

6. Periodically messages out from Mailman are being bounced en masse  
leading to the subscriber accounts being disabled

7. The bounce response attached to the bounce action notice produced by

Mailman when subscribers are disabled in these circumstances is from  
the server local MTA. The MTA lists what appears to be all the  
addresses to which the outgoing message was sent with a note against  
each saying "unrouteable mail domain maildomain.tld". The bounce  
response asserts that this is a permanent failure. The messages are  
each being sent to a number of different mail domains not just a single

one

8. The list admin with the problem has no access to either the Mailman  
or MTA logs

9. The server administrator is supposedly claiming that these bounces  
are a result of "a bug in Mailman for which no patch is available"

My analysis is:

1. The problem is not obviously due to any bug in Mailman

2. The problem is more likely due to an IP routing problem which  
periodically afflicts the server and its ability to reach the MTAs for  
the mail domains addressed by the outgoing messages

3. The MTA is accepting the outgoing messages from Mailman and then  
finding it has problems of its own in delivering mail which are  
unrelated to Mailman as the origin of the messages

But I have to concede I know nothing about Exim 4.20. I know even less  
about CPanel.

Any thoughts or anatomically feasible suggestions welcome.



-
Richard Barrett  
http://www.openinfo.co.uk


--
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/chris%40christinede
larosa.com



--
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

Re: [Mailman-Users] I guess it's my week for problems, sorry :(

[Richard Barrett]

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

On Friday, August 1, 2003, at 12:10  am, Glenn Sieb wrote:

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 [EMAIL PROTECTED]:

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
I have a /usr/local/www/cgi-bin/htsearch.. it works for other lists.. 
:-/

If I just go to the archives and click "Search" on these broken lists, 
I get:

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 [EMAIL PROTECTED]:

https://www.wingfoot.org/mailman/private/list/
/mailman/mmsearch/list
I even found an obscure reference and did the following:

for list in `./list_lists | awk '{print $1}' | grep -v 50`; do 
./withlist
-l -r fix_url $list;done

That also didn't fix it.. :-/

This is happening in both Mozilla and IE on my system...

Help?
*makes offers of chocolate*
Thanks in advance,
Glenn
---
The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear
"All acts of Love and Pleasure are Her rituals"-Charge of the Goddess
---
Richard Barrett   http://www.openinfo.co.uk
--
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

[Mailman-Users] I guess it's my week for problems, sorry :(

[Glenn Sieb]

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 [EMAIL PROTECTED]:

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

I have a /usr/local/www/cgi-bin/htsearch.. it works for other lists.. :-/

If I just go to the archives and click "Search" on these broken lists, I get:

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 [EMAIL PROTECTED]:

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

I even found an obscure reference and did the following:

for list in `./list_lists | awk '{print $1}' | grep -v 50`; do ./withlist
-l -r fix_url $list;done

That also didn't fix it.. :-/

This is happening in both Mozilla and IE on my system...

Help?
*makes offers of chocolate*

Thanks in advance,
Glenn
---
The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear
"All acts of Love and Pleasure are Her rituals"-Charge of the Goddess


--
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

Re: [Mailman-Users] Sending mail question

[Richard Barrett]

On Thursday, July 31, 2003, at 10:07  pm, Raquel Rice wrote:

On Tue, 29 Jul 2003 18:59:25 -0500
"Christine De La Rosa" <[EMAIL PROTECTED]> wrote:
Prior to the upgrade on my server my mail was being sent out by
[EMAIL PROTECTED] now it is being sent by [EMAIL PROTECTED]
Is this a correct setting?

Thanks
Christine
Christine,

I don't know what version you upgraded to, but looking at the
"Sender:" header of my lists and the same header of this list, it
appears that it is "[EMAIL PROTECTED]".
With MM 2.1.x the envelope sender is the listname-bounces alias. The 
+user=email bit is only present if VERP is being used for the list.

--
Raquel

Before you speak, it is necessary for you to listen, for God speaks
in the silence of the heart.
  --Mother Teresa


--
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

Re: [Mailman-Users] mailman won't send out mail

[Todd]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Brad Knowles wrote:
> At 10:29 AM -0500 2003/07/31, Justin Rush wrote:
>
>> Thanks alot to all those that replied and helped me out.  Adding those
>> lines to my config file fixed the problem.  However, for somereason the
>> qrunner was not running, so I started it manually.  What is the best to
>> way to start this on boot?
>
>   It should be a cron job.  See the documentation.

The qrunners are daemonized in MM 2.1, not cron jobs as in 2.0 and earlier.
Still, checking the docs is always a good idea.  :)

- -- 
Todd  OpenPGP -> KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp

Everyone wants to live at the expense of the state.  They forget that the
state lives at the expense of everyone.
-- Frederic Bastiat, 1848

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3rc2 (GNU/Linux)
Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl.

iD8DBQE/KYwCuv+09NZUB1oRAkv3AJsHLd8RE1S76bplr7JzAJTPGf2SsACeLxxD
w3V6x342ORkYtqy2ZPK2AcM=
=uWIX
-END PGP SIGNATURE-

--
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

Re: [Mailman-Users] mailman won't send out mail

[Brad Knowles]

At 10:29 AM -0500 2003/07/31, Justin Rush wrote:

 Thanks alot to all those that replied and helped me out.  Adding those
 lines to my config file fixed the problem.  However, for somereason the
 qrunner was not running, so I started it manually.  What is the best to
 way to start this on boot?
	It should be a cron job.  See the documentation.

--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)
--
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

[Mailman-Users] Mac OS X Jaguar + Mailman v2.1.2 + Sendmail setupnotes

[james o]

well, it took me a couple hours to get mailman v2.1.2 running on OS X 
server 10.2.6. i thought i'd share some pitfalls.

i pretty much followed setup instructions from, 
http://maxo.captainnet.net/installs/mailman.html
with a few exceptions:

Cron Issues:
-my Cron daemon would send this message out; shell-init: could not get 
current directory: getcwd: cannot access parent directories: Permission 
denied put the cron jobs into user 'root' instead of 'mailman'
%cd /usr/local/mailman/cron/
%crontab -u mailman crontab.in << use this instead >> %crontab -u root 
crontab.in

-Sendmail enabler - a great utility to get sendmail running on Mac OS X 
and save you a bunch of time:
http://www.roadstead.com/weblog/Tutorials/SMSource.html  Sendmail 
enabler is nice because you don't have to edit the sendmail.cf 
local-hosts and aliases config files(which really isn't that 
difficult). it also repairs directory perms as well.  add your domains 
and aliases to the appropriate windows under the "option" button.

-after any change to your aliases file run
%newaliases
to sync the aliases.db file with aliases.  this keeps sendmail happy
-sendmail needs to have a sym link to the mailman wrapper.  except, i 
never found a mailman wrapper file.  instead, i created a link to 
/usr/local/mailman/mail/mailman inside of /usr/adm/sm.bin (i had to 
create /adm/sm.bin)  i tried the default dir of /usr/sm.bin but that 
didn't work.  create the link inside
[/usr/adm/sm.bin] % ln -s /usr/local/mailman/mail/mailman

-make sure mailmanctl is running
[wo1:local/mailman/bin] % ./mailmanctl start
-i downloaded mailman startup script from : (can't find this right 
now...  i'll reply with the link)

-another helpful link:
http://www.afp548.com/Articles/Jaguar/mailman21-new.html
-after setting up your first list run
%check_perms -f
to fix perms... as some get messed up.
hth,
./james
{ primax STUDIO : http://primaxSTUDIO.com : 513.772.1223  }

--
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

Re: [Mailman-Users] Mailman 2.1.2, Postfix 2.0.13, virtual domains

[Richard Pyne]

This, along with per-domain create passwords are by far at the top of 
my feature wish-list. Aliasing is a royal PITA because it is a 
completely manual process which gets completely out of hand when you 
are hosting many domains/lists on one machine.

On Thursday 31 July 2003 11:42 am, Glenn Sieb wrote:
> If Mailman had a little more (no offense, I just can't think of a
> better term to use) intelligence in it, when you set up for virtual
> domains it'd do things like create a directorynamespace like
> /usr/local/mailman/lists/domain2.com/, etc. so you *could* put
> lists with the same name in different domains...

-- 
Richard B. Pyne
[EMAIL PROTECTED]

--
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

Re: [Mailman-Users] Four simple questions not answered by the FAQ.

[John DeCarlo]

chas,

Here are some answers, anyway.

schuetzen wrote:

Four basic questions

1.  I have 12 lists I want to be plain text
2.  I want them to have NO attachments  

Where are the (setup) switches to make the above happen?
On the list admin page, go to the Content Filtering section.  Change 
"Should Mailman filter ..." to Yes.  If you leave the rest at default 
values, including Yes for "Should Mailman convert text/html parts to 
plain text?", your list will only have plain text messages with no 
attachments.

3.  I want to have a single page for moderation efforts.

Where is or how do I do this?
Not sure what you mean by this.  You mean instead of having different 
"Sections" with a menu at the top, you want everything on one page?  I 
can look at the code and see if I can figure anything out along these 
lines if you want.

4.  Why can I not see all 30 or 50 members of a list as we used to in pre
2.1.x??
Where is that switch?
Have you tried changing or setting DEFAULT_ADMIN_MEMBER_CHUNKSIZE in 
mm_cfg.py?  The description is in Defaults.py.

This IS the "factory" list for Mailman, right? Or should I be going to another
source?
Hmmm.  Don't know what you mean.  This is not the developer list. 
Mostly people answer who are other users.

--

John DeCarlo, My Views Are My Own



--
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

Re: [Mailman-Users] Mailman 2.1.2, Postfix 2.0.13, virtual domains

[Jon Carnes]

On Thu, 2003-07-31 at 13:42, Glenn Sieb wrote:
> Jim Breton said:
> > I have set up the above on a FreeBSD 4.7 system with the intention of
> > being able to host per-virtual-domain mailing lists.
> 
> Yay! Another FBSD user! :)
> 
> > I want to be able to have:
> >
> > [EMAIL PROTECTED]
> > and
> > [EMAIL PROTECTED]
> >
> > as completely separate, autonomous lists.
> 
> Can't do it :( It'd have to be:
> 
> [EMAIL PROTECTED]
> [EMAIL PROTECTED]
> 
> If Mailman had a little more (no offense, I just can't think of a better
> term to use) intelligence in it, when you set up for virtual domains it'd
> do things like create a directorynamespace like
> /usr/local/mailman/lists/domain2.com/, etc. so you *could* put lists with
> the same name in different domains...

Well, technically, you could have two or more parallel installs of
Mailman.  There are quite a few folks who do that when they have just a
few virtual domains to worry about.

Also, you can alias
  [EMAIL PROTECTED] ==> list01-domain2
And let the (hidden) real name of the list be list01-domain2.
Of course then you have to do a lot of editing of the web-pages to
display the domain information that you want.

That is the way I normally do it.  The webpages all aliases properly as
do the email addresses, so the end-user is non the wiser.

And yes, it sure would be easier if mailman used only the virtual host
information when setting up it's web pages and sending out its emails.

Good Luck


--
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

Re: [Mailman-Users] Mailman 2.1.2, Postfix 2.0.13, virtual domains

[Glenn Sieb]

Jim Breton said:
> I have set up the above on a FreeBSD 4.7 system with the intention of
> being able to host per-virtual-domain mailing lists.

Yay! Another FBSD user! :)

> I want to be able to have:
>
> [EMAIL PROTECTED]
> and
> [EMAIL PROTECTED]
>
> as completely separate, autonomous lists.

Can't do it :( It'd have to be:

[EMAIL PROTECTED]
[EMAIL PROTECTED]

If Mailman had a little more (no offense, I just can't think of a better
term to use) intelligence in it, when you set up for virtual domains it'd
do things like create a directorynamespace like
/usr/local/mailman/lists/domain2.com/, etc. so you *could* put lists with
the same name in different domains...

> And if so, I've been having trouble attempting to set it up.  Despite
> adding virtual domains to the POSTFIX_STYLE_VIRTUAL_DOMAINS variable in
> mm_cfg.py, as well as trying to add "add_virtualhost('mail.domain2.com')
> invocations to mm_cfg.py, Mailman _always_ tries to create lists in the
> default domain.
>
> Example:
>
> $ bin/newlist [EMAIL PROTECTED]
> ... (list created)
>
> data/virtual-mailman:
>
> [EMAIL PROTECTED]  virt4
> [EMAIL PROTECTED]virt4-admin
> ...
>
>
> $ bin/newlist [EMAIL PROTECTED]
> ...
> List already exists: virt4

This happens because of the prior explanation...

Hope this helps...

Glenn
---
The original portions of this message are the copyright of the author
(c)1998-2002 Glenn E. Sieb.ICQ UIN: 300395IRC Nick: Rainbear
"All acts of Love and Pleasure are Her rituals"-Charge of the Goddess


--
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

[Mailman-Users] Mailman 2.1.2, Postfix 2.0.13, virtual domains

[Jim Breton]

Hi all,

I have set up the above on a FreeBSD 4.7 system with the intention of
being able to host per-virtual-domain mailing lists.

I want to be able to have:

[EMAIL PROTECTED]
and
[EMAIL PROTECTED]

as completely separate, autonomous lists.

First, is this even possible using stock Mailman?

And if so, I've been having trouble attempting to set it up.  Despite
adding virtual domains to the POSTFIX_STYLE_VIRTUAL_DOMAINS variable in
mm_cfg.py, as well as trying to add "add_virtualhost('mail.domain2.com')
invocations to mm_cfg.py, Mailman _always_ tries to create lists in the
default domain.

Example:

$ bin/newlist [EMAIL PROTECTED]
... (list created)

data/virtual-mailman:

[EMAIL PROTECTED]  virt4
[EMAIL PROTECTED]virt4-admin
...


$ bin/newlist [EMAIL PROTECTED]
...
List already exists: virt4


Or, if I create the virtual one first, it creates the list in the default
domain anyway.

Am I doing something wrong, or is this impossible?  If it cannot be done
with Mailman, is there some other MLM I should be looking at?

Thanks.

--
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

[Mailman-Users] Memory problem with mailman 2.1.2 under solaris 5.6

[Nicolas C.]

Hi,

my workstation SUN U10 begin to be very slow.

The top return:

load averages:  0.87,  0.76,  0.92
129 processes: 114 sleeping, 2 running, 12 zombie, 1 on cpu
CPU states: % idle, % user, % kernel, % iowait, % swap
Memory: 512M real, 58M free, 591M swap in use, 430M swap free

  PID USERNAME THR PRI NICE  SIZE   RES STATE   TIMECPU COMMAND
16522 bssref 4  330  259M  218M sleep   8:24  5.36% python
27064 bssref 1  330 1272K 1024K cpu 0:00  0.55% top


the process 16522 with the 200MB+ of memory is "qrunner --runner=Outgoin.."
Is it normal ?,  the other python process can be 100MB.

I tried to stop then start maiman, but the memory return to this value.

Mailman is in version 2.1.2, python in 2.2.1,  and OS is Solaris 5.6
There is no huge list on the workstation.

any idea ?

regards,


--
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

Re: [Mailman-Users] Keep attachments in archive

[Arlen Walker]

On Thursday, July 31, 2003, at 11:41  AM, Tom Crummey wrote:

What version of mailman are you using?
Sorry, 2.1.2, using the default archive pipermail (0.0.9)

Have fun,
Arlen
-
In God We Trust, all others must supply data
--
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

[Mailman-Users] Edit rejection notice text

[Todd Felmly]

Is there a way to edit the text contained in _non-member_ rejection
notices?

I.e., if a non-member posts to a list and the Action to take for
postings from non-members for which no explicit action is defined
setting is set for reject, this is what the user gets:

"You are not allowed to post to this mailing list, and your message has
been automatically rejected.  If you think that your messages are
being rejected in error, contact the mailing list owner at [EMAIL PROTECTED]"

Where is this template at? I've searched through the archives/en
directory and can't find it.

Thanks!

Todd



--
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

[Mailman-Users] Keep attachments in archive

[Arlen Walker]

I'm looking for a useful way to keep the attachments of a message in the 
archive. Currently, the archive is renaming all the attachments, and the 
name is important, or at least the extension is, because the new name 
the archive is choosing is absolutely incorrect for the file, which 
renders the archived attachment useless as the user has no idea what 
program to use to open the sttachment with.

Have fun,
Arlen
-
In God We Trust, all others must supply data
--
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

Re: [Mailman-Users] mailman won't send out mail

[Jon Carnes]

On Thu, 2003-07-31 at 11:29, Justin Rush wrote:
> Thanks alot to all those that replied and helped me out.  Adding those 
> lines to my config file fixed the problem.  However, for somereason the 
> qrunner was not running, so I started it manually.  What is the best to 
> way to start this on boot?
> 

Since you are using Red Hat 9, use the chkconfig utility (or you could
use the Services gui that comes in the System Settings/Server Settings
menu).

chkconfig --list mailman
mailman 0:off   1:off   2:off   3:off   4:off   5:off   6:off

chkconfig --level 345 mailman on
# this will turn the mailman daemon on automatically when the server is
booted.

Hope this helps - Jon Carnes

> On 31 Jul 2003, Jon Carnes wrote:
> 
> > 
> > Put the following in your /var/mailman/Mailman/mm_cfg.py file:
> > MAILMAN_USER = 'mailman'
> > MAILMAN_GROUP = 'mailman'
> > 
> > Also you will need to put in your hosts real domain name:
> > #DEFAULT_EMAIL_HOST = 'porky.devel.redhat.com'
> > #DEFAULT_URL_HOST = 'porky.devel.redhat.com'
> > DEFAULT_EMAIL_HOST = 'list.anncons.org'
> > DEFAULT_URL_HOST = 'list.anncons.org'
> > DEFAULT_URL_PATTERN = 'http://%s/mailman/'
> > 



--
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

[Mailman-Users] vanishing messages, v2.1.2

[phil . clarke]

Hi all,

An odd problem ... A hosting company provides me with Mailman 2.1.2 lists
and web admin tools.  I've created lists of about 5 subscribers and sent
messages to subscribers with no problems.

I then do a bulk load of about 40 addresses.  After this, if I create a
message and send it to the list it appears in the archives as expected, but
it *doesnt* arrive at the recipient addresses (and without shell access I
cant see where the messages stall). Once Ive attempted this, everyone's
bounce score is 1.0, but the administrators arent being emailed about the
bounces.

But if I "reply to" a message sent via the list before the bulk load, then
this new reply behaves correctly, ie it appears in the archive and *is* sent
to all recipients. Also if I post from an unsubscribed address and approve
the post as moderator, that post behaves correctly.

Any idea whats going on?  Why would the reply-to's and moderator posts make
it through but not the new posts?

thanks ... Phil

--
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

RE: [Mailman-Users] archiving

[Sylvain Langlade]

>
> 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?

IIRC, I once got this problem with HTML messages produced with standard
email client. If your list is configured to accept such messages without
stripping the HTML part, the message is not archived (you have to do it
manually with $prefix/bin/arch).

I had to configure all lists to strip out the HTML part of all incoming
message. Which leads to a problem for HTML-only messages produced by web
client like Hotmail...

So try to send a raw text message to your list and see if it appears in the
archives.

HTH


--
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

Re: [Mailman-Users] mailman won't send out mail

[Justin Rush]

Thanks alot to all those that replied and helped me out.  Adding those 
lines to my config file fixed the problem.  However, for somereason the 
qrunner was not running, so I started it manually.  What is the best to 
way to start this on boot?

On 31 Jul 2003, Jon Carnes wrote:

> On Thu, 2003-07-31 at 11:00, Justin Rush wrote:
> > While trying to do /sbin/service mailman start ... I get the following 
> > error.
> > 
> > Traceback (most recent call last):
> >   File "/var/mailman/bin/mailmanctl", line 524, in ?
> > main()
> >   File "/var/mailman/bin/mailmanctl", line 319, in main
> > check_privs()
> >   File "/var/mailman/bin/mailmanctl", line 274, in check_privs
> > gid = grp.getgrnam(mm_cfg.MAILMAN_GROUP)[2]
> > KeyError: getgrnam(): name not found
> > 
> > I tried doing a rpm -U on the python devel package, but the error still 
> > persists.
> > 
> 
> Put the following in your /var/mailman/Mailman/mm_cfg.py file:
> MAILMAN_USER = 'mailman'
> MAILMAN_GROUP = 'mailman'
> 
> Also you will need to put in your hosts real domain name:
> #DEFAULT_EMAIL_HOST = 'porky.devel.redhat.com'
> #DEFAULT_URL_HOST = 'porky.devel.redhat.com'
> DEFAULT_EMAIL_HOST = 'list.anncons.org'
> DEFAULT_URL_HOST = 'list.anncons.org'
> DEFAULT_URL_PATTERN = 'http://%s/mailman/'
> 
> Lord knows what the Mailman packager for RedHat was smoking the day he
> did this RPM...
> 
> Good luck - Jon Carnes
> 
> > On 31 Jul 2003, Jon Carnes wrote:
> > 
> > > First idea is to check to check out the FAQ, but the most common problem
> > > here is that you didn't: service mailman start
> > > 
> > > Good Luck
> > > 
> > > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> > > 
> > > On Thu, 2003-07-31 at 10:17, Justin Rush wrote:
> > > > Hi,
> > > >   I am trying to get mailman working on my new redhat 9 servers and 
> > > > mailman refuses to send out mail.  I tried copying my mailman directory 
> > > > from the working server (running redhat 7.3), but that didn't work.  I 
> > > > also tried installing the newest rpm 2.1-8.  I see in the maillog that it 
> > > > does recieve the mail:
> > > > 
> > > > Jul 31 09:12:36 hundo sendmail[20921]: h6VECahH020921: 
> > > > from=<[EMAIL PROTECTED]>, size=866, class=0, nrcpts=1, 
> > > > msgid=<[EMAIL PROTECTED]>, 
> > > > proto=ESMTP, daemon=MTA, relay=mail.scout.wisc.edu [144.92.170.199]
> > > > Jul 31 09:12:36 hundo sendmail[20922]: h6VECahH020921: 
> > > > to="|/var/mailman/mail/mailman post test", 
> > > > ctladdr=<[EMAIL PROTECTED]> (8/0), delay=00:00:00, 
> > > > xdelay=00:00:00, mailer=prog, pri=31090, dsn=2.0.0, stat=Sent
> > > > 
> > > > However, nothing follows after that line.
> > > > Sendmail will work just fine if I telnet to it and send mail, so mailman 
> > > > must be the problem.
> > > > 
> > > > Does anyone have any ideas?
> > > 
> 

-- 
Justin Rush
Technical Specialist
Internet Scout Project
[EMAIL PROTECTED]


--
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

RE: [Mailman-Users] Attachments not at end + archive

[Brad Knowles]

At 5:11 PM +0200 2003/07/31, CARTER Anthony wrote:

 Yes, using MIME digests...However, will the attachments still be available.
 Some come as non-text, and I need to have the attachments available.
	I'm not sure how attachments would be handled in non-MIME format. 
I would be interested to know what would happen.

	I suspect that attachments would not be handled well in non-MIME 
format, and that the only solution to your problem is to modify the 
mailman digestifier code so that it uses inline MIME multipart/mixed 
bodyparts, but I don't know what it would take to make it do that.

	Certainly, many incoming messages might have to be changed (since 
on a per-message basis, having all the attachments at the bottom 
shouldn't be a problem).  This would most likely break PGP signed 
messages, and I'm not sure what might happen to others.

--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)
--
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

Re: [Mailman-Users] archiving

[Jon Carnes]

Check your cron to make sure it is still running.

Other than that, you will need to include more information:
  Version of Mailman that you are running, How it was installed (via
rpm, apt-get, source, provided by host), the MTA that you are using, and
the Operating System that your host is running.

Good luck - Jon Carnes
 
On Thu, 2003-08-07 at 06:06, webulous wrote:
> 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
> 
> 
> --
> 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/jonc%40nc.rr.com


--
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

Re: [Mailman-Users] mailman won't send out mail

[Jon Carnes]

On Thu, 2003-07-31 at 11:00, Justin Rush wrote:
> While trying to do /sbin/service mailman start ... I get the following 
> error.
> 
> Traceback (most recent call last):
>   File "/var/mailman/bin/mailmanctl", line 524, in ?
> main()
>   File "/var/mailman/bin/mailmanctl", line 319, in main
> check_privs()
>   File "/var/mailman/bin/mailmanctl", line 274, in check_privs
> gid = grp.getgrnam(mm_cfg.MAILMAN_GROUP)[2]
> KeyError: getgrnam(): name not found
> 
> I tried doing a rpm -U on the python devel package, but the error still 
> persists.
> 

Put the following in your /var/mailman/Mailman/mm_cfg.py file:
MAILMAN_USER = 'mailman'
MAILMAN_GROUP = 'mailman'

Also you will need to put in your hosts real domain name:
#DEFAULT_EMAIL_HOST = 'porky.devel.redhat.com'
#DEFAULT_URL_HOST = 'porky.devel.redhat.com'
DEFAULT_EMAIL_HOST = 'list.anncons.org'
DEFAULT_URL_HOST = 'list.anncons.org'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'

Lord knows what the Mailman packager for RedHat was smoking the day he
did this RPM...

Good luck - Jon Carnes

> On 31 Jul 2003, Jon Carnes wrote:
> 
> > First idea is to check to check out the FAQ, but the most common problem
> > here is that you didn't: service mailman start
> > 
> > Good Luck
> > 
> > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> > 
> > On Thu, 2003-07-31 at 10:17, Justin Rush wrote:
> > > Hi,
> > >   I am trying to get mailman working on my new redhat 9 servers and 
> > > mailman refuses to send out mail.  I tried copying my mailman directory 
> > > from the working server (running redhat 7.3), but that didn't work.  I 
> > > also tried installing the newest rpm 2.1-8.  I see in the maillog that it 
> > > does recieve the mail:
> > > 
> > > Jul 31 09:12:36 hundo sendmail[20921]: h6VECahH020921: 
> > > from=<[EMAIL PROTECTED]>, size=866, class=0, nrcpts=1, 
> > > msgid=<[EMAIL PROTECTED]>, 
> > > proto=ESMTP, daemon=MTA, relay=mail.scout.wisc.edu [144.92.170.199]
> > > Jul 31 09:12:36 hundo sendmail[20922]: h6VECahH020921: 
> > > to="|/var/mailman/mail/mailman post test", 
> > > ctladdr=<[EMAIL PROTECTED]> (8/0), delay=00:00:00, 
> > > xdelay=00:00:00, mailer=prog, pri=31090, dsn=2.0.0, stat=Sent
> > > 
> > > However, nothing follows after that line.
> > > Sendmail will work just fine if I telnet to it and send mail, so mailman 
> > > must be the problem.
> > > 
> > > Does anyone have any ideas?
> > 


--
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

Re: [Mailman-Users] Analysis of reasons for bounce responses

[J C Lawrence]

On Thu, 31 Jul 2003 11:08:26 +0100 
Richard Barrett <[EMAIL PROTECTED]> wrote:

> 7. The bounce response attached to the bounce action notice produced
> by Mailman when subscribers are disabled in these circumstances is
> from the server local MTA. The MTA lists what appears to be all the
> addresses to which the outgoing message was sent with a note against
> each saying "unrouteable mail domain maildomain.tld". The bounce
> response asserts that this is a permanent failure. The messages are
> each being sent to a number of different mail domains not just a
> single one

DNS _or_ IP routing is periodically screwed.  Why?  Dunno.

-- 
J C Lawrence
-(*)Satan, oscillate my metallic sonatas. 
[EMAIL PROTECTED]   He lived as a devil, eh?  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.

--
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

RE: [Mailman-Users] Attachments not at end + archive

[CARTER Anthony]

Yes, using MIME digests...However, will the attachments still be available.
Some come as non-text, and I need to have the attachments available.

Thanks,
Anthony

-Original Message-
From: Brad Knowles [mailto:[EMAIL PROTECTED]
Sent: 31 July 2003 17:02
To: CARTER Anthony
Cc: '[EMAIL PROTECTED]'
Subject: Re: [Mailman-Users] Attachments not at end + archive


At 4:38 PM +0200 2003/07/31, CARTER Anthony wrote:

>  Archives are working and attachments are being stripped and all. Perfect.
>  However, when there is a thread, the text is all first, and the
attachments
>  for all messages are placed at the bottom of the entire thread.
>
>  Is there a way to embed the attachments in the message that sent it.

You're using MIME format digests, right?  Have you tried turning
that off?

-- 
Brad Knowles, <[EMAIL PROTECTED]>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
 -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++)
R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)

--
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

[Mailman-Users] new install question

[Ivan Dimitrov]

Hi list
I've been trying to install mailman-2.1.2 following the INSTALL file and
at configuring the list I've created here is the message I got:

[EMAIL PROTECTED]:/usr/local/mailman# bin/config_list -i
data/sitelist.cfg mailman
Traceback (most recent call last):
  File "bin/config_list", line 339, in ?
main()
  File "bin/config_list", line 334, in main
do_input(listname, infile, checkonly, verbose)
  File "bin/config_list", line 240, in do_input
mlist = MailList.MailList(listname, lock=not checkonly)
  File "/usr/local/mailman/Mailman/MailList.py", line 122, in __init__
self.Lock()
  File "/usr/local/mailman/Mailman/MailList.py", line 159, in Lock
self.Load()
  File "/usr/local/mailman/Mailman/MailList.py", line 613, in Load
self.CheckValues()
  File "/usr/local/mailman/Mailman/MailList.py", line 644, in
CheckValues
if '' in urlparse(self.web_page_url)[:2]:
  File "/usr/lib/python2.2/urlparse.py", line 53, in urlparse
tuple = urlsplit(url, scheme, allow_fragments)
  File "/usr/lib/python2.2/urlparse.py", line 83, in urlsplit
i = url.find(':')
AttributeError: 'NoneType' object has no attribute 'find'


Can You please help me fix the problem.
Thanks in advance
-- 

Hi! I'm your friendly neighbourhood signature virus.
Copy me to your signature file and help me spread!

--
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

Re: [Mailman-Users] Attachments not at end + archive

[Brad Knowles]

At 4:38 PM +0200 2003/07/31, CARTER Anthony wrote:

 Archives are working and attachments are being stripped and all. Perfect.
 However, when there is a thread, the text is all first, and the attachments
 for all messages are placed at the bottom of the entire thread.
 Is there a way to embed the attachments in the message that sent it.
	You're using MIME format digests, right?  Have you tried turning that off?

--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)
--
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

Re: [Mailman-Users] mailman won't send out mail

[Brad Knowles]

At 9:17 AM -0500 2003/07/31, Justin Rush wrote:

   I am trying to get mailman working on my new redhat 9 servers and
 mailman refuses to send out mail.
	See 
 
and 
.

--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)
--
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

[Mailman-Users] archiving

[webulous]

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


--
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

Re: [Mailman-Users] mailman won't send out mail

[Justin Rush]

While trying to do /sbin/service mailman start ... I get the following 
error.

Traceback (most recent call last):
  File "/var/mailman/bin/mailmanctl", line 524, in ?
main()
  File "/var/mailman/bin/mailmanctl", line 319, in main
check_privs()
  File "/var/mailman/bin/mailmanctl", line 274, in check_privs
gid = grp.getgrnam(mm_cfg.MAILMAN_GROUP)[2]
KeyError: getgrnam(): name not found

I tried doing a rpm -U on the python devel package, but the error still 
persists.

On 31 Jul 2003, Jon Carnes wrote:

> First idea is to check to check out the FAQ, but the most common problem
> here is that you didn't: service mailman start
> 
> Good Luck
> 
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> 
> On Thu, 2003-07-31 at 10:17, Justin Rush wrote:
> > Hi,
> >   I am trying to get mailman working on my new redhat 9 servers and 
> > mailman refuses to send out mail.  I tried copying my mailman directory 
> > from the working server (running redhat 7.3), but that didn't work.  I 
> > also tried installing the newest rpm 2.1-8.  I see in the maillog that it 
> > does recieve the mail:
> > 
> > Jul 31 09:12:36 hundo sendmail[20921]: h6VECahH020921: 
> > from=<[EMAIL PROTECTED]>, size=866, class=0, nrcpts=1, 
> > msgid=<[EMAIL PROTECTED]>, 
> > proto=ESMTP, daemon=MTA, relay=mail.scout.wisc.edu [144.92.170.199]
> > Jul 31 09:12:36 hundo sendmail[20922]: h6VECahH020921: 
> > to="|/var/mailman/mail/mailman post test", 
> > ctladdr=<[EMAIL PROTECTED]> (8/0), delay=00:00:00, 
> > xdelay=00:00:00, mailer=prog, pri=31090, dsn=2.0.0, stat=Sent
> > 
> > However, nothing follows after that line.
> > Sendmail will work just fine if I telnet to it and send mail, so mailman 
> > must be the problem.
> > 
> > Does anyone have any ideas?
> 

-- 
Justin Rush
Technical Specialist
Internet Scout Project
[EMAIL PROTECTED]


--
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

Re: [Mailman-Users] mailman won't send out mail

[Jon Carnes]

First idea is to check to check out the FAQ, but the most common problem
here is that you didn't: service mailman start

Good Luck

Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py

On Thu, 2003-07-31 at 10:17, Justin Rush wrote:
> Hi,
>   I am trying to get mailman working on my new redhat 9 servers and 
> mailman refuses to send out mail.  I tried copying my mailman directory 
> from the working server (running redhat 7.3), but that didn't work.  I 
> also tried installing the newest rpm 2.1-8.  I see in the maillog that it 
> does recieve the mail:
> 
> Jul 31 09:12:36 hundo sendmail[20921]: h6VECahH020921: 
> from=<[EMAIL PROTECTED]>, size=866, class=0, nrcpts=1, 
> msgid=<[EMAIL PROTECTED]>, 
> proto=ESMTP, daemon=MTA, relay=mail.scout.wisc.edu [144.92.170.199]
> Jul 31 09:12:36 hundo sendmail[20922]: h6VECahH020921: 
> to="|/var/mailman/mail/mailman post test", 
> ctladdr=<[EMAIL PROTECTED]> (8/0), delay=00:00:00, 
> xdelay=00:00:00, mailer=prog, pri=31090, dsn=2.0.0, stat=Sent
> 
> However, nothing follows after that line.
> Sendmail will work just fine if I telnet to it and send mail, so mailman 
> must be the problem.
> 
> Does anyone have any ideas?


--
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

Re: [Mailman-Users] Email addresses in archive

[Jon Carnes]

On Thu, 2003-07-31 at 09:56, CARTER Anthony wrote:
> Is there a way that I can make peoples email addresses in the archive
> become:
> 
> [EMAIL PROTECTED]
> 
> rather than:
> 
> xxx.yyy at server.com (with a link to the mailman listinfo page).
> 
> Thanks,
> 
> Anthony
> 

Add this to your ~mailman/Mailman/mm_cfg.py file and then change the
value from  1 to 0.

# Pipermail archives contain the raw email addresses of the
# posting authors. Some view this as a goldmine for spam
# harvesters.  Set this to true to moderately obscure email
# addresses, but note that this breaks mailto: URLs
# in the archives too.
ARCHIVER_OBSCURES_EMAILADDRS = 1

Hope this helps - Jon Carnes


--
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

[Mailman-Users] Attachments not at end + archive

[CARTER Anthony]

Ok,

Archives are working and attachments are being stripped and all. Perfect.
However, when there is a thread, the text is all first, and the attachments
for all messages are placed at the bottom of the entire thread.

Is there a way to embed the attachments in the message that sent it. For
example, current:

Message 1
-
Message 2
-
Message n
-
Attachment

I would like:

Message 1
-
Message 2
Attachment
--
Message n
--

Any ideas?

Thanks,
Anthony

--
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

Re: [Mailman-Users] ip_addresse rather than hostname in forms?

[Ed Wilts]

On Thu, Jul 31, 2003 at 01:05:41PM +, Kirk R. Wythers wrote:
> How can I configure a list to use an ip address in its listname instead
> of the hostname? For example I'd like all references to the list to be
> based on the machines ip address (i.e on the listinfo page "To post a
> message to all the list menebers, send email to [EMAIL PROTECTED],
> rather than [EMAIL PROTECTED], or when monthly reminders go out to
> use [EMAIL PROTECTED] as well.
> 
> Is this possible?

It should be possible, but I'd seriously question the reason for doing
so.  It's trivial and cheap these days to set up your own domain and
have it hosted by a free DNS provider like zoneedit.com.  Even dynamic
IP users (like I am) can make this work without a lot of hassles and
expense.

For your hostname, try the IP address in square brackets, like
[1.2.3.4].  Mail to [EMAIL PROTECTED] should work, but as I said, you
really, really don't want to do this.

.../Ed
-- 
Ed Wilts, Mounds View, MN, USA
mailto:[EMAIL PROTECTED]

--
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

[Mailman-Users] mailman won't send out mail

[Justin Rush]

Hi,
  I am trying to get mailman working on my new redhat 9 servers and 
mailman refuses to send out mail.  I tried copying my mailman directory 
from the working server (running redhat 7.3), but that didn't work.  I 
also tried installing the newest rpm 2.1-8.  I see in the maillog that it 
does recieve the mail:

Jul 31 09:12:36 hundo sendmail[20921]: h6VECahH020921: 
from=<[EMAIL PROTECTED]>, size=866, class=0, nrcpts=1, 
msgid=<[EMAIL PROTECTED]>, 
proto=ESMTP, daemon=MTA, relay=mail.scout.wisc.edu [144.92.170.199]
Jul 31 09:12:36 hundo sendmail[20922]: h6VECahH020921: 
to="|/var/mailman/mail/mailman post test", 
ctladdr=<[EMAIL PROTECTED]> (8/0), delay=00:00:00, 
xdelay=00:00:00, mailer=prog, pri=31090, dsn=2.0.0, stat=Sent

However, nothing follows after that line.
Sendmail will work just fine if I telnet to it and send mail, so mailman 
must be the problem.

Does anyone have any ideas?

-- 
Justin Rush
Technical Specialist
Internet Scout Project
[EMAIL PROTECTED]


--
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

Re: [Mailman-Users] Email addresses in archive

[Richard Barrett]

On Thursday, July 31, 2003, at 02:56  pm, CARTER Anthony wrote:

Is there a way that I can make peoples email addresses in the archive
become:
[EMAIL PROTECTED]

rather than:

xxx.yyy at server.com (with a link to the mailman listinfo page).

Thanks,

take a look at this recent post to mailman-users list:

http://www.mail-archive.com/mailman-users%40python.org/msg18477.html

also for MM 2.1.2 the 'Membership exposure' options on the Privacy web 
admin GUI page for a list

Anthony


--
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

Re: [Mailman-Users] ip_addresse rather than hostname in forms?

[Kirk R. Wythers]

What would happen if I simply changed the 

Host name this list prefers for email. 
(Details for host_name)

line, on the administrative interface page?


On Thu, 2003-07-31 at 14:11, Richard Barrett wrote:

> SMTP mail addressing is done in terms of domains, that is the FQDN of 
> mail hosts. For instance MX records are usually specified in respect of 
> FQDNs with nary a IP number in sight. This, for instance, this allows 
> mail hosts on private IP numbers to function  so long as some publicly 
> IP numbered mail relay with access to that internal network will relay 
> mail for the privately IP numbered mail host. Most MTAs check the 
> acceptability of domains in mail addresses by doing DNS lookup.
> 
> I do not think using IP numbers instead of FQDNs is going to work but I 
> am open to being corrected.
> 
> What problem are you trying to solve with your proposal?
> 
> > Thanks,
> >
> > Kirk
> >
-- 
Kirk R. Wythers Department of Forest Resources  
Tel: 612.625.2261   University of Minnesota
Fax: 612.625.5211530 Cleveland Ave. N
Email: [EMAIL PROTECTED]Saint Paul, MN 55108 USA


--
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

Re: [Mailman-Users] ip_addresse rather than hostname in forms?

[Richard Barrett]

On Thursday, July 31, 2003, at 02:05  pm, Kirk R. Wythers wrote:

How can I configure a list to use an ip address in its listname instead
of the hostname? For example I'd like all references to the list to be
based on the machines ip address (i.e on the listinfo page "To post a
message to all the list menebers, send email to 
[EMAIL PROTECTED],
rather than [EMAIL PROTECTED], or when monthly reminders go out to
use [EMAIL PROTECTED] as well.

Is this possible?

I think you are going to be out of luck.

SMTP mail addressing is done in terms of domains, that is the FQDN of 
mail hosts. For instance MX records are usually specified in respect of 
FQDNs with nary a IP number in sight. This, for instance, this allows 
mail hosts on private IP numbers to function  so long as some publicly 
IP numbered mail relay with access to that internal network will relay 
mail for the privately IP numbered mail host. Most MTAs check the 
acceptability of domains in mail addresses by doing DNS lookup.

I do not think using IP numbers instead of FQDNs is going to work but I 
am open to being corrected.

What problem are you trying to solve with your proposal?

Thanks,

Kirk



--
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

[Mailman-Users] Email addresses in archive

[CARTER Anthony]

Is there a way that I can make peoples email addresses in the archive
become:

[EMAIL PROTECTED]

rather than:

xxx.yyy at server.com (with a link to the mailman listinfo page).

Thanks,

Anthony

--
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

Re: [Mailman-Users] Analysis of reasons for bounce responses

[Jon Carnes]

On Thu, 2003-07-31 at 06:08, Richard Barrett wrote:
> 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.
> 
> Situation:
> 
> 1. List admin's domain is hosted by a server run by a hosting company.
> 
> 2. The server is (probably) running Linux
> 
> 3. Mailman 2.1.2 is provided on the server with, I believe, CPanel
> 
> 4. The server's MTA appears to be Exim 4.20 handling both incoming and  
> outgoing messages to/from Mailman
> 
> 5. Mailman list's basically work OK much of the time
> 
> 6. Periodically messages out from Mailman are being bounced en masse  
> leading to the subscriber accounts being disabled
> 
> 7. The bounce response attached to the bounce action notice produced by  
> Mailman when subscribers are disabled in these circumstances is from  
> the server local MTA. The MTA lists what appears to be all the  
> addresses to which the outgoing message was sent with a note against  
> each saying "unrouteable mail domain maildomain.tld". The bounce  
> response asserts that this is a permanent failure. The messages are  
> each being sent to a number of different mail domains not just a single  
> one
> 
> 8. The list admin with the problem has no access to either the Mailman  
> or MTA logs
> 
> 9. The server administrator is supposedly claiming that these bounces  
> are a result of "a bug in Mailman for which no patch is available"
> 
> My analysis is:
> 
> 1. The problem is not obviously due to any bug in Mailman
> 
> 2. The problem is more likely due to an IP routing problem which  
> periodically afflicts the server and its ability to reach the MTAs for  
> the mail domains addressed by the outgoing messages
> 
> 3. The MTA is accepting the outgoing messages from Mailman and then  
> finding it has problems of its own in delivering mail which are  
> unrelated to Mailman as the origin of the messages
> 
> But I have to concede I know nothing about Exim 4.20. I know even less  
> about CPanel.
> 
> Any thoughts or anatomically feasible suggestions welcome.
> 
I have seen this behavior a few times and in each case it was resource
problem on the server.  They need to check on the memory of the box and
how much is being used during the bounces.  I'm afraid it is only
something that the sysadmin can really do.

I have also seen this problem when the /var directory was made too
small. Could this be a problem with the users services being chrooted
and them running out of quota space while processing large messages?

Good Luck - Jon Carnes


--
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

[Mailman-Users] Error from Mailman

[Tom Crummey]

Hello,

I've recently upgraded my Mailman version from 2.1 to 2.1.2 and now when I
try to update a list of non-member addresses whose posts should be 
discarded I get:

Traceback (most recent call last):
  File "/home/mailman/scripts/driver", line 87, in run_main
main()
  File "/home/mailman/Mailman/Cgi/admin.py", line 169, in main
change_options(mlist, category, subcat, cgidata, doc)
  File "/home/mailman/Mailman/Cgi/admin.py", line 1223, in change_options
gui.handleForm(mlist, category, subcat, cgidata, doc)
  File "/home/mailman/Mailman/Gui/GUIBase.py", line 152, in handleForm
doc.addError(
  File "/home/mailman/Mailman/htmlformat.py", line 340, in addError
self.AddItem(Header(3, Bold(FontAttr(
TypeError: not enough arguments for format string



Python information:

Variable Value
sys.version 2.2.2 (#4, Jul 24 2003, 19:20:45) [C]
sys.executable /usr/local/bin/python2.2
sys.prefix /usr/local
sys.exec_prefix /usr/local
sys.path /usr/local
sys.platform sunos5


 HTTP_REFERER  
http://www.ee.ucl.ac.uk/mailman/admin/engd-re/?VARHELP=privacy/sender/discard_th
ese_nonmembers
 
Anyone seen this or able to suggest a cause? I'm not sure what format string
the error message is referring to.

Thanks.

Tom.


 Tom Crummey, Systems and Network Manager,  EMAIL: [EMAIL PROTECTED]
 Department of Electronic and Electrical Engineering,  
 University College London,   TEL: +44 (0)20 7679 3898
 Torrington Place,FAX: +44 (0)20 7388 9325
 London, UK, WC1E 7JE. 



--
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

[Mailman-Users] ip_addresse rather than hostname in forms?

[Kirk R. Wythers]

How can I configure a list to use an ip address in its listname instead
of the hostname? For example I'd like all references to the list to be
based on the machines ip address (i.e on the listinfo page "To post a
message to all the list menebers, send email to [EMAIL PROTECTED],
rather than [EMAIL PROTECTED], or when monthly reminders go out to
use [EMAIL PROTECTED] as well.

Is this possible?

Thanks,

Kirk 




--
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

Re: [Mailman-Users] Mailman 2.1.2 on Mac OS X 10.2.6 withpostfix

[Brad Knowles]

At 10:42 PM +0200 2003/07/30, Gerben Wierda wrote:

 But what is not working is mail. No message is being sent, nothing
 appears in postfix's logs nor in mailman's logs. Without clues I
 have no idea on how to debug this. Is there anyone who can help me out?
	Have you send the FAQ entry at 
?

--
Brad Knowles, <[EMAIL PROTECTED]>
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
-Benjamin Franklin, Historical Review of Pennsylvania.
GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+() DI+() D+(++) G+() e++> h--- r---(+++)* z(+++)
--
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

[Mailman-Users] Analysis of reasons for bounce responses

[Richard Barrett]

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.

Situation:

1. List admin's domain is hosted by a server run by a hosting company.

2. The server is (probably) running Linux

3. Mailman 2.1.2 is provided on the server with, I believe, CPanel

4. The server's MTA appears to be Exim 4.20 handling both incoming and  
outgoing messages to/from Mailman

5. Mailman list's basically work OK much of the time

6. Periodically messages out from Mailman are being bounced en masse  
leading to the subscriber accounts being disabled

7. The bounce response attached to the bounce action notice produced by  
Mailman when subscribers are disabled in these circumstances is from  
the server local MTA. The MTA lists what appears to be all the  
addresses to which the outgoing message was sent with a note against  
each saying "unrouteable mail domain maildomain.tld". The bounce  
response asserts that this is a permanent failure. The messages are  
each being sent to a number of different mail domains not just a single  
one

8. The list admin with the problem has no access to either the Mailman  
or MTA logs

9. The server administrator is supposedly claiming that these bounces  
are a result of "a bug in Mailman for which no patch is available"

My analysis is:

1. The problem is not obviously due to any bug in Mailman

2. The problem is more likely due to an IP routing problem which  
periodically afflicts the server and its ability to reach the MTAs for  
the mail domains addressed by the outgoing messages

3. The MTA is accepting the outgoing messages from Mailman and then  
finding it has problems of its own in delivering mail which are  
unrelated to Mailman as the origin of the messages

But I have to concede I know nothing about Exim 4.20. I know even less  
about CPanel.

Any thoughts or anatomically feasible suggestions welcome.

 
-
Richard Barrett  
http://www.openinfo.co.uk

--
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