forever pending subscriptions
Hi.
I'm using mailman on a lot of different machines with the Exim MTA in version 3.16 and everything worked fine with beta2.
In the last weeks i tried a few times to upgrade to beta6 or rc1. But this always ends up in a very strange behavior. Since i am not the only one who reported this to the mailman-users-list and got no answer i also send this mail to the developers list, because i think it may be a bug.
The Following happens:
After upgrading to rc1 without any errors from make install mailman still works fine, but it does no subscriptions any longer. A user who signs up in the listinfo page gets his confirmation mail and after he/she confirmed the message (and the MTA delivered it w/o error) nothing happens. The subscribe log still shows the user as pending and nothing happens.
Any suggestion would be appreciated.
thx
andreas
andreas gietl gietl internet services fon +49 9402 2551 fax +49 9402 2604 mobile +49 171 60 70 008 gietl@gietl.com
############################################ # Das Handbuch sagt, das Programm benötige # # Windows 95 oder besser. Also habe ich # # Linux installiert! # ############################################
I just tested this again yesterday, and it worked for me.
Andreas Gietl wrote:
Hi.
I'm using mailman on a lot of different machines with the Exim MTA in version 3.16 and everything worked fine with beta2.
In the last weeks i tried a few times to upgrade to beta6 or rc1. But this always ends up in a very strange behavior. Since i am not the only one who reported this to the mailman-users-list and got no answer i also send this mail to the developers list, because i think it may be a bug.
The Following happens:
After upgrading to rc1 without any errors from make install mailman still works fine, but it does no subscriptions any longer. A user who signs up in the listinfo page gets his confirmation mail and after he/she confirmed the message (and the MTA delivered it w/o error) nothing happens. The subscribe log still shows the user as pending and nothing happens.
Any suggestion would be appreciated.
thx
andreas
andreas gietl gietl internet services fon +49 9402 2551 fax +49 9402 2604 mobile +49 171 60 70 008 gietl@gietl.com
############################################ # Das Handbuch sagt, das Programm benötige # # Windows 95 oder besser. Also habe ich # # Linux installiert! # ############################################
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
"AG" == Andreas Gietl gietl@gietl.com writes:
AG> After upgrading to rc1 without any errors from make install
AG> mailman still works fine, but it does no subscriptions any
AG> longer. A user who signs up in the listinfo page gets his
AG> confirmation mail and after he/she confirmed the message (and
AG> the MTA delivered it w/o error) nothing happens. The subscribe
AG> log still shows the user as pending and nothing happens.
"DM" == Dan Mick Dan.Mick@west.sun.com writes:
DM> I just tested this again yesterday, and it worked for me.
Me too.
When you do a "bin/dumpdb data/pending_subscriptions.db" do you still see the pending subscription in there? Do you still see the confirmation message in qfiles? If so, are there any obvious errors in logs/error? Does it have the expected Subject: header (i.e. at the end of the line, "request xxxxxx" where those x's are the numbers).
-Barry
"Barry A. Warsaw" wrote:
"AG" == Andreas Gietl gietl@gietl.com writes:
AG> After upgrading to rc1 without any errors from make install AG> mailman still works fine, but it does no subscriptions any AG> longer. A user who signs up in the listinfo page gets his AG> confirmation mail and after he/she confirmed the message (and AG> the MTA delivered it w/o error) nothing happens. The subscribe AG> log still shows the user as pending and nothing happens."DM" == Dan Mick Dan.Mick@west.sun.com writes:
DM> I just tested this again yesterday, and it worked for me.Me too.
When you do a "bin/dumpdb data/pending_subscriptions.db" do you still see the pending subscription in there?
Yeah, the subscription is still in there!
Do you still see the
confirmation message in qfiles?
Yeah, the confirmation message is in there!
If so, are there any obvious errors
in logs/error?
nothing. i of course checked that!
Does it have the expected Subject: header (i.e. at the
end of the line, "request xxxxxx" where those x's are the numbers).
Yeah. it does have. Do you need any further information?
-Barry
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
"AG" == Andreas Gietl gietl@gietl.com writes:
>> Do you still see the
>> confirmation message in qfiles?
AG> Yeah, the confirmation message is in there!
>> If so, are there any obvious errors
>> in logs/error?
AG> nothing. i of course checked that!
>> Does it have the expected Subject: header (i.e. at the
>> end of the line, "request xxxxxx" where those x's are the
>> numbers).
AG> Yeah. it does have.
AG> Do you need any further information?
Yes, do a bin/dumpdb qfiles/<confirmation_message>.db and look for the `pipeline' entry.
That should show us where things are getting stuck. -Barry
any further ideas?
i'm sorry, but there is no pipeline entry:
that's the db-file: { 'filebase': 'ccfe93988bf681ad271ad049fa54dcd7260a60ac', 'listname': 'bittecomgietltest2', 'torequest': 1, 'version': 2}
and this is the .msg file:
From gietl@gietl.com Sat Nov 04 13:52:46 2000
Received: from [195.227.84.2] (helo=d1.x-mailer.de) by d18.x-mailer.de with esmtp (Exim 3.16 #1) id 13s2oQ-0003e1-00 for bittecomgietltest2-request@bitte.com; Sat, 04 Nov 2000 13:52:46 +0100 Received: from p3ee039ab.dip.t-dialin.net ([62.224.57.171] helo=gietl.com) by d1.x-mailer.de with esmtp (Exim 3.16 #1) id 13s2n9-0004iW-00 for bittecomgietltest2-request@bitte.com; Sat, 04 Nov 2000 13:51:27 +0100 Message-ID: 3A0406EC.6C4B8583@gietl.com Date: Sat, 04 Nov 2000 13:54:04 +0100 From: Andreas Gietl gietl@gietl.com X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: bittecomgietltest2-request@bitte.com Subject: Re: Bittecomgietltest2 -- confirmation of subscription -- request 569170 References: E13s2o6-0003dd-00@d18.x-mailer.de Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
bittecomgietltest2-request@bitte.com wrote:
Bittecomgietltest2 -- confirmation of subscription -- request 569170
We have received a request from p3ee039ab.dip.t-dialin.net for subscription of your email address, gietl@gietl.com, to the bittecomgietltest2@bitte.com mailing list. To confirm the request, please send a message to bittecomgietltest2-request@bitte.com, and either:
- maintain the subject line as is (the reply's additional "Re:" is
ok),
- or include the following line - and only the following line - in the
message body:
confirm 569170
(Simply sending a 'reply' to this message should work from most email interfaces, since that usually leaves the subject line in the right form.)
If you do not wish to subscribe to this list, please simply disregard this message. Send questions to bittecomgietltest2-admin@bitte.com.
barry@wooz.org wrote:
"AG" == Andreas Gietl gietl@gietl.com writes:
>> Do you still see the >> confirmation message in qfiles? AG> Yeah, the confirmation message is in there! >> If so, are there any obvious errors >> in logs/error? AG> nothing. i of course checked that! >> Does it have the expected Subject: header (i.e. at the >> end of the line, "request xxxxxx" where those x's are the >> numbers). AG> Yeah. it does have. AG> Do you need any further information?Yes, do a bin/dumpdb qfiles/<confirmation_message>.db and look for the `pipeline' entry.
That should show us where things are getting stuck. -Barry
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
Has this problem been solved ?
If so , please tell me how, thanks!
On Mon, 06 Nov 2000 17:33:48 +0100 Andreas Gietl gietl@gietl.com wrote:
any further ideas?
i'm sorry, but there is no pipeline entry:
that's the db-file: { 'filebase': 'ccfe93988bf681ad271ad049fa54dcd7260a60ac', 'listname': 'bittecomgietltest2', 'torequest': 1, 'version': 2}
and this is the .msg file:
From gietl@gietl.com Sat Nov 04 13:52:46 2000
Received: from [195.227.84.2] (helo=d1.x-mailer.de) by d18.x-mailer.de with esmtp (Exim 3.16 #1) id 13s2oQ-0003e1-00 for bittecomgietltest2-request@bitte.com; Sat, 04 Nov 2000 13:52:46 +0100 Received: from p3ee039ab.dip.t-dialin.net ([62.224.57.171] helo=gietl.com) by d1.x-mailer.de with esmtp (Exim 3.16 #1) id 13s2n9-0004iW-00 for bittecomgietltest2-request@bitte.com; Sat, 04 Nov 2000 13:51:27 +0100 Message-ID: 3A0406EC.6C4B8583@gietl.com Date: Sat, 04 Nov 2000 13:54:04 +0100 From: Andreas Gietl gietl@gietl.com X-Mailer: Mozilla 4.73 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: bittecomgietltest2-request@bitte.com Subject: Re: Bittecomgietltest2 -- confirmation of subscription -- request 569170 References: E13s2o6-0003dd-00@d18.x-mailer.de Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
bittecomgietltest2-request@bitte.com wrote:
Bittecomgietltest2 -- confirmation of subscription -- request 569170
We have received a request from p3ee039ab.dip.t-dialin.net for subscription of your email address, gietl@gietl.com, to the bittecomgietltest2@bitte.com mailing list. To confirm the request, please send a message to bittecomgietltest2-request@bitte.com, and either:
- maintain the subject line as is (the reply's additional "Re:" is
ok),
- or include the following line - and only the following line - in the
message body:
confirm 569170
(Simply sending a 'reply' to this message should work from most email interfaces, since that usually leaves the subject line in the right form.)
If you do not wish to subscribe to this list, please simply disregard this message. Send questions to bittecomgietltest2-admin@bitte.com.
barry@wooz.org wrote:
> "AG" == Andreas Gietl gietl@gietl.com writes:
>> Do you still see the >> confirmation message in qfiles? AG> Yeah, the confirmation message is in there! >> If so, are there any obvious errors >> in logs/error? AG> nothing. i of course checked that! >> Does it have the expected Subject: header (i.e. at the >> end of the line, "request xxxxxx" where those x's are the >> numbers). AG> Yeah. it does have. AG> Do you need any further information?Yes, do a bin/dumpdb qfiles/<confirmation_message>.db and look for the `pipeline' entry.
That should show us where things are getting stuck. -Barry
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
-- andreas gietl gietl internet services fon +49 9402 2551 fax +49 9402 2604 mobile +49 171 60 70 008 gietl@gietl.com
############################################ # Das Handbuch sagt, das Programm ben鲷ige # # Windows 95 oder besser. Also habe ich # # Linux installiert! # ############################################
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
Trying to come back to this problem. It looks like Eric Wang is also seeing problems, so there must be /something/ going on. I can't figure out what though, so perhaps one of you guys can give me ssh access to the host in question?
"AG" == Andreas Gietl gietl@gietl.com writes:
AG> i'm sorry, but there is no pipeline entry:
| that's the db-file:
| { 'filebase': 'ccfe93988bf681ad271ad049fa54dcd7260a60ac',
| 'listname': 'bittecomgietltest2',
| 'torequest': 1,
| 'version': 2}
Okay, this looks pretty good, assuming the file is qfiles/ccfe93988bf681ad271ad049fa54dcd7260a60ac.db
We don't get a pipeline' key in the dictionary because, by virtue of thetorequest' key, qrunner sends this message through the email
command parser instead of the delivery pipeline. So far so good.
AG> and this is the .msg file:
[...most headers deleted...]
| To: bittecomgietltest2-request@bitte.com
| Subject: Re: Bittecomgietltest2 -- confirmation of subscription --
| request 569170
| References: <E13s2o6-0003dd-00@d18.x-mailer.de>
| Content-Type: text/plain; charset=iso-8859-1
| Content-Transfer-Encoding: 8bit
I notice that the Subject: line is wrapped, but not in an rfc 822 valid way. I'm assuming that something got munged in the forwarding of the message to this list, and that the text `request 569170' is actually at the end of the Subject: line.
In my own tests, if the message looked exactly as you sent it, with
the line being wrapped and request' showing in column zero, the mailcmd parser will generate an error message back to the sender. But you're not seeing that. If therequest' line were wrapped a la rfc
822, Mailman should be able to grok out the command just fine. But
you're not seeing that either.
Another log file to look at: doe you see anything in logs/bounce? I don't expect you to -- just wondering.
We're at the point of using debug statements now, and I don't want to bore mailman-users with that. If I can't get ssh access to your installation, let's carry on the debugging conversation on mailman-developers only.
-Barry
At 2:13 PM -0500 11/9/00, barry@wooz.org wrote:
| Subject: Re: Bittecomgietltest2 -- confirmation of subscription -- | request 569170
I had one of these this week. the Subject line was wrapped 'request\n\t<number>' and mailman didn't handle it. To my knowledge subject should never wrap anyway, and when I looked in my inbox archives, it was the users mail client that had done it. It looked like a client issue, but it gave us the clue to help him work around it.
"CVR" == Chuq Von Rospach chuqui@plaidworks.com writes:
CVR> I had one of these this week. the Subject line was wrapped
CVR> 'request\n\t<number>' and mailman didn't handle it. To my
CVR> knowledge subject should never wrap anyway, and when I looked
CVR> in my inbox archives, it was the users mail client that had
CVR> done it. It looked like a client issue, but it gave us the
CVR> clue to help him work around it.
Hmm. I just tested this (wrapping before and after `request' with \n\t) and it works for me. The rfc822 module /should/ be able to handle this and return a Subject with the continuation lines.
-Barry
barry@wooz.org wrote:
Trying to come back to this problem. It looks like Eric Wang is also seeing problems, so there must be /something/ going on. I can't figure out what though, so perhaps one of you guys can give me ssh access to the host in question?
I've also reported the same problems. After much woe, I am back at beta6, which seems to have fixed my web interface problems and does not present the confirmation issue.
I would love to help, but at this point I have over 2000 pissed off users, and I can't risk another upgrade to test. I may do so in the future, but only if I have a solid way of backing out.
I am also strongly considering a return to majordomo.
Thanks,
| Dan |
"DS" == Dan Simoes dans@audifans.com writes:
>> Trying to come back to this problem. It looks like Eric Wang
>> is also seeing problems, so there must be /something/ going on.
>> I can't figure out what though, so perhaps one of you guys can
>> give me ssh access to the host in question?
DS> I've also reported the same problems. After much woe, I am
DS> back at beta6, which seems to have fixed my web interface
DS> problems and does not present the confirmation issue.
We tracked Andreas' problem down to the qrunner cron job not being installed, a common problem for upgraders from what I've seen. Please first be absolutely sure this isn't your problem! You can test this by cd'ing into /home/mailman and running
% python -S cron/qrunner
if that unclogs things, your cron isn't set up right. If not, then we'll need to look at things more closely. To start with, you can send me the output of "bin/dumpdb qfiles/whatever.db" and the associated .msg file. Also, look in the log files, especially logs/error and see if there's anything relevant.
DS> I would love to help, but at this point I have over 2000
DS> pissed off users, and I can't risk another upgrade to test. I
DS> may do so in the future, but only if I have a solid way of
DS> backing out.
Well, you may have to set up a test list in a different installation until you're confident that 2.0rc1 works for you.
DS> I am also strongly considering a return to majordomo.
I hope that won't be necessary, and I'm willing to help debug the problem.
-Barry
barry@wooz.org wrote:
We tracked Andreas' problem down to the qrunner cron job not being installed
Well, there's a new one.
Not mentioned anywhere in the installation docs, either.
Glad we had to get Barry to debug this one.
participants (6)
-
Andreas Gietl -
barry＠wooz.org -
Chuq Von Rospach -
Dan Mick -
Dan Simoes -
Eric Wang