Aaryn Olsson | 1 Aug 2000 01:05
Picon

mailman-owner,aaryn <at> ag.arizona.edu,lab

Dear mailman-users,

I am upgrading from mailman-1.1 to 2.0beta4 and am having a very difficult 
and confusing time getting mailman to behave properly.

I issued the following commands to install mailman from the source directory:
	./configure --with-mail-gid=mailman --with-cgi-gid=nobody 
--prefix=/home/guest/mailman
	sendmail stop
	make install
	sendmail start

I successfully created a list (abc_test) and subscribed myself.  I received 
a message indicating the fact (See Item 1 below), but was unable to receive 
messages sent to the list.

Item 1:
 From my inbox:
	Date: Mon, 31 Jul 2000 14:49:45 -0700 (MST)
	From: abc_test-request <at> Ag.Arizona.Edu
	To: aaryn <at> Ag.Arizona.Edu
	Subject: Welcome to the "Abc_test" mailing list

	Welcome to the Abc_test <at> Ag.Arizona.Edu mailing list!

When I send a message to the list, nothing happens.  No errors are produced 
in any logs that I know of, no bounces are sent to myself as list 
subscriber nor as mailman-owner (See Item 2).

Item 2:
(Continue reading)

Dan Mick | 1 Aug 2000 01:39
Picon

Re: mailman-owner,aaryn <at> ag.arizona.edu,lab

> When I send a message to the list, nothing happens.  No errors are produced 
> in any logs that I know of, no bounces are sent to myself as list 
> subscriber nor as mailman-owner (See Item 2).

Are you certain it's not in qfiles?

Did you update crontab as INSTALL says to do?

Is mailman's gid 259?

> But it just disappears.  No messages pertaining to mailman are held in the 
> mail queue (We use sendmail 8.9.3).  When I run mail/wrapper post from the 
> command line, I get the error "Failure to exec script. WANTED gid 259, GOT 
> gid 0.  (Reconfigure to take 0?)."  When I run bin/check_perms, I get the 
> message, "No problems found."  This is what the permissions are on my mail 
> and scripts directory:
> 
> 
> 	ag: /home/guest/mailman/ > ls -al mail
> 	total 76
> 	drwxrwsr-x   2 root     mailman      512 Jul 31 15:25 ./
> 	drwxrwsr-x  17 mailman  mailman      512 Jul 31 14:49 ../
> 	-rwxr-sr-x   1 root     mailman    36780 Jul 31 15:25 wrapper*
> 
> 	ag: /home/guest/mailman/ > ls -al scripts
> 	total 54
> 	drwxrwsr-x   2 root     mailman      512 Jul 31 15:25 ./
> 	drwxrwsr-x  17 mailman  mailman      512 Jul 31 14:49 ../
> 	-rw-r--r--   1 root     mailman     1507 Jul 31 15:25 
answer_majordomo_mail
(Continue reading)

Aaryn Olsson | 1 Aug 2000 02:23
Picon

Re: mailman-owner,aaryn <at> ag.arizona.edu,lab

> > When I send a message to the list, nothing happens.  No errors are produced 
> > in any logs that I know of, no bounces are sent to myself as list 
> > subscriber nor as mailman-owner (See Item 2).
> 
> Are you certain it's not in qfiles?

They are in qfiles...

> Did you update crontab as INSTALL says to do?

No

> 
> Is mailman's gid 259?

Yes

It looks like crontab did it.  Thank you very, very much!  The
documentation wins again ;-)

Sincerely,
Aaryn Olsson

Robert Vasvari | 1 Aug 2000 04:07
Favicon

Mailman SMTP problem

As I set up a new list MailMan tries to send out the first mail to
the admin's mailaddress. Nothing goes out, I get this error in
~mailman/logs/error:

Jul 30 14:20:02 2000 (1140) Delivery exception: list.extend()  
argument must be a list
Jul 30 14:20:02 2000 (1140) Traceback (innermost last):
  File "/DATADISK/home/mailman/Mailman/Handlers/HandlerAPI.py", line  
82, in do_pipeline
    func(mlist, msg, msgdata)
  File "/DATADISK/home/mailman/Mailman/Handlers/Sendmail.py", line  
95, in process
    failedrecips.extend(chunk)
TypeError: list.extend() argument must be a list

I switched to sendmail delivery and it works for now.
Any thoughts?

			=[vrobi]=

--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Robert Vasvari
Object Warehouse Inc.
415-821-9287
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Chuck Dale | 1 Aug 2000 04:06

Re: mailman-owner,aaryn <at> ag.arizona.edu,lab

Hi Aaryn,

I had the same problem when upgrading to 2.0b4.

I forgot to insert the cron job as specified in INSTALL. Until then all
posts failed silently. 

Chuck

Wrote Aaryn Olsson on Mon, Jul 31, 2000 at 04:05:32PM -0700:
> Dear mailman-users,
> 
> I am upgrading from mailman-1.1 to 2.0beta4 and am having a very difficult 
> and confusing time getting mailman to behave properly.
> 
> I issued the following commands to install mailman from the source directory:
> 	./configure --with-mail-gid=mailman --with-cgi-gid=nobody 
> --prefix=/home/guest/mailman
> 	sendmail stop
> 	make install
> 	sendmail start
> 
> I successfully created a list (abc_test) and subscribed myself.  I received 
> a message indicating the fact (See Item 1 below), but was unable to receive 
> messages sent to the list.
> 
> Item 1:
>  From my inbox:
> 	Date: Mon, 31 Jul 2000 14:49:45 -0700 (MST)
> 	From: abc_test-request <at> Ag.Arizona.Edu
(Continue reading)

Dan Mick | 1 Aug 2000 04:14
Picon

Re: Mailman SMTP problem

> As I set up a new list MailMan tries to send out the first mail to
> the admin's mailaddress. Nothing goes out, I get this error in
> ~mailman/logs/error:
> 
> Jul 30 14:20:02 2000 (1140) Delivery exception: list.extend()  
> argument must be a list
> Jul 30 14:20:02 2000 (1140) Traceback (innermost last):
>   File "/DATADISK/home/mailman/Mailman/Handlers/HandlerAPI.py", line  
> 82, in do_pipeline
>     func(mlist, msg, msgdata)
>   File "/DATADISK/home/mailman/Mailman/Handlers/Sendmail.py", line  
> 95, in process
>     failedrecips.extend(chunk)
> TypeError: list.extend() argument must be a list
> 
> I switched to sendmail delivery and it works for now.
> Any thoughts?

Looks like a bug to me; I think that failedrecips line should
be failedrecips.extend([chunk]) for Python 1.5.2 anyway.

But it's probably a latent bug because Sendmail shouldn't be failing
to get you into that code.  It'd be worth fixing that line (as above)
and switching back to Sendmail.py to see what's going wrong to cause
sendmail failures.

I'll file the bug.

David Champion | 1 Aug 2000 12:04
Favicon

List of subscriptions

I've had users ask if there's any way to see a list of their
subscriptions on my server.  I know about the "Your other foo.mil
subscriptions", but is there any access to that information
(.../handle_opts/list/user) that does not require the user to know at
least one list they're on?

--

-- 
 -D.	dgc <at> uchicago.edu	NSIT	University of Chicago

Ralf Hildebrandt | 1 Aug 2000 13:16
Picon

Bug after update to 2.0beta4

Prior to the update to 2.0beta4 (have been running 2.0beta2 or 1) everything
has been running smoothly (except for the pending administrative requests --
thus I upgraded).

I used identical options when configure'ing Beta 4

After the update, nothing (!) happens when I send mail to any of my three
lists.

From my maillog:

Aug  1 12:43:50 stahlw06 postfix/local[10065]: 900E014554:
to=<litquiz <at> stahlw06.stahl.bau.tu-bs.de>, relay=local, delay=72, status=sent
("|/users2/mailman/mail/wrapper post litquiz")                      

(so /users2/mailman/mail/wrapper exits with status 0)

I did a bin/check_perms -- everything ok.
I then deleted the locks/* and logs/*, still nothing.

Mail is just swallowed, never to be seen again.

--

-- 
Ralf.Hildebrandt <at> innominate.de
Dipl.-Informatiker                                        innominate AG
System Engineer                                       networking people
tel: +49.30.308806-62 fax: -77  web: http://innominate.de  pgp: /pgp/rh
Ralf Hildebrandt | 1 Aug 2000 13:17
Picon

Bug after update to 2.0b4 II

PS: I found the mails all queued in /users2/mailman/qfiles
What now?

--

-- 
Ralf.Hildebrandt <at> innominate.de
Dipl.-Informatiker                                        innominate AG
System Engineer                                       networking people
tel: +49.30.308806-62 fax: -77  web: http://innominate.de  pgp: /pgp/rh
Chris Snyder | 1 Aug 2000 14:09

Re: Bug after update to 2.0b4 II

On Tue, 1 Aug 2000, Ralf Hildebrandt wrote:

>PS: I found the mails all queued in /users2/mailman/qfiles
>What now?
>

I haven't played with the older versions of the code, but did you upgrade
the cron jobs too?  Your problem looks like what a lot of people (myself
included) have run into lately - no cron, no mail.

Hm... maybe the cron entries should be stressed a little more or something
added to the FAQ about what happens if you don't add them.  Seems to be a
re-occuring issue of missing this part of the installation.

Chris.

+-------------------------------------------------------------------------+
 Chris Snyder  --  gopher <at> aol.net  --  WebOps SysAdmin  --  America Online
+-------------------------------------------------------------------------+
       There is a very fine line between "hobby" and "mental illness".

Gmane