Re: [Mailman-Users] Email subscription not working
On Thu, 8 Jan 2009, Mark Sapiro wrote:
Dan Mahoney, System Admin wrote:
Hey all, I'm hitting a little snag. Email subscribe isn't doing anything.
Postfix delivers the email to mailman, but then as far as I can tell,
nothing more happens with it.
Where would be the best place to debug this from a mailman perspective?
Jan 7 21:05:34 lister postfix/qmgr[97071]: DDFD010E528:
from=ionlyhavethisfortest...@gmail.com, size=2716, nrcpt=1 (queue
active)
Jan 7 21:05:35 lister postfix/local[38795]: DDFD010E528:
to=testing-j...@lister.isc.org, relay=local, delay=0.18,
delays=0.01/0/0/0.17, dsn=2.0.0, status=sent (delivered to command:
/usr/local/mailman/mail/mailman join testing)
Jan 7 21:05:35 lister postfix/qmgr[97071]: DDFD010E528: removed
And that's where it stops. The address doesn't show in any logs or
anything from that point forward.
The above says Postfix successfully piped the mail to the wrapper which
presumably invoked the 'join' script to queue the mail in the
'commands' queue.
From there it is processed by CommandRunner.
Step 1) is CommandRunner running or is the message still sitting in
qfiles/commands ?
I don't see a persistent process with that name, but qfiles/commands is
empty.
Anything obvious I should be checking? Perhaps the possibility that the
to address is getting altered in transit? Does mailman log discarded
subscription messages? Is there a debug option?
The message got delivered to the correct address according to Postfix.
Messages with precedence 'bulk', 'junk' or 'list' are discarded, but
the discard is logged in Mailman's vette log with a message like
Precedence: xxx message discarded by: testing-requ...@example.com
This hasn't been logged at all. In fact a grep for the address on all
logfiles gives nothing. However, see my next bit...
If you have an autoresponder set for requests to this list, the message
will be autoresponded to per the autoresponder settings and logged in
the vette log as replied and discard.
Also look for messages in Mailman's error (and other) logs with
timestamp within a few seconds of Jan 7 21:05:35.
Oh here's something:
Jan 07 21:05:05 2009 (69945) Uncaught runner exception: 'NoneType' object
has no attribute 'lower'
Jan 07 21:05:05 2009 (69945) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 114, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, in
_dispose
res.do_command('join')
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, in
do_command
return handler.process(self, args)
File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, in
process
if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'
Jan 07 21:05:05 2009 (69945) SHUNTING:
1231362305.1949821+1175967c099dad2a1abd84668491378c9ec3d2f3
Jan 07 21:05:35 2009 (69945) Uncaught runner exception: 'NoneType' object
has no attribute 'lower'
Jan 07 21:05:35 2009 (69945) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 114, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, in
_dispose
res.do_command('join')
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, in
do_command
return handler.process(self, args)
File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, in
process
if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'
Jan 07 21:05:35 2009 (69945) SHUNTING:
1231362335.060303+d4ab606e4d64c835df5f64f7aaff37fe61bee8e8
Jan 07 21:05:47 2009 (69945) Uncaught runner exception: 'NoneType' object
has no attribute 'lower'
Jan 07 21:05:47 2009 (69945) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 114, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, in
_dispose
res.do_command('join')
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, in
do_command
return handler.process(self, args)
File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, in
process
if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'
Known bug?
OS is FreeBSD, if it matters.
-Dan
--
What's with the server farm down in the basement?
-Spider, Three Skulls
Re: [Mailman-Users] Email subscription not working
Dan Mahoney, System Admin wrote:
Jan 07 21:05:47 2009 (69945) Uncaught runner exception: 'NoneType' object
has no attribute 'lower'
Jan 07 21:05:47 2009 (69945) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 114, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 185, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, in
_dispose
res.do_command('join')
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, in
do_command
return handler.process(self, args)
File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, in
process
if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'
Known bug?
Yes, it is a known bug, introduced in 2.1.10 and fixed in 2.1.11. I had
a fleeting thought about that when replying previously, but neglected
to mention it.
The attached cmd_subscribe.patch.txt will fix it.
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
=== modified file 'Mailman/Commands/cmd_subscribe.py'
--- Mailman/Commands/cmd_subscribe.py 2008-03-20 03:07:51 +
+++ Mailman/Commands/cmd_subscribe.py 2008-04-23 14:32:48 +
@@ -71,7 +71,8 @@
return STOP
argnum += 1
# Fix the password/digest issue
-if digest is None and password.lower() in ('digest', 'nodigest'):
+if (digest is None
+and password and password.lower() in ('digest', 'nodigest')):
if password.lower() == 'digest':
digest = 1
else:
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Email subscription not working
Dan Mahoney, System Admin wrote: Hey all, I'm hitting a little snag. Email subscribe isn't doing anything. Postfix delivers the email to mailman, but then as far as I can tell, nothing more happens with it. Where would be the best place to debug this from a mailman perspective? Jan 7 21:05:34 lister postfix/qmgr[97071]: DDFD010E528: from=ionlyhavethisfortest...@gmail.com, size=2716, nrcpt=1 (queue active) Jan 7 21:05:35 lister postfix/local[38795]: DDFD010E528: to=testing-j...@lister.isc.org, relay=local, delay=0.18, delays=0.01/0/0/0.17, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman join testing) Jan 7 21:05:35 lister postfix/qmgr[97071]: DDFD010E528: removed And that's where it stops. The address doesn't show in any logs or anything from that point forward. The above says Postfix successfully piped the mail to the wrapper which presumably invoked the 'join' script to queue the mail in the 'commands' queue. From there it is processed by CommandRunner. Step 1) is CommandRunner running or is the message still sitting in qfiles/commands ? Anything obvious I should be checking? Perhaps the possibility that the to address is getting altered in transit? Does mailman log discarded subscription messages? Is there a debug option? The message got delivered to the correct address according to Postfix. Messages with precedence 'bulk', 'junk' or 'list' are discarded, but the discard is logged in Mailman's vette log with a message like Precedence: xxx message discarded by: testing-requ...@example.com If you have an autoresponder set for requests to this list, the message will be autoresponded to per the autoresponder settings and logged in the vette log as replied and discard. Also look for messages in Mailman's error (and other) logs with timestamp within a few seconds of Jan 7 21:05:35. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] email subscription sends two messages
Don Hone wrote: Using Mailman version: 2.1.9 [Corrected message] I sent a subscribe command to join a mailing list and received two confirmation messages. Could this be the result of putting the word subscribe into the subject as well as the body? If not, any other ideas? Could this be a bug or should we use only body or subject for the command? Both the subject and the body of a message sent to the list-request address are scanned for commands. If the subject doesn't contain a valid command, it is ignored, but whether or not the subject contains a valid command, the body is processed line by line until an error occurs, an 'end' command is reached or there are no more lines. If you put subscribe in both the subject and body of a message to the list-request address, the two subscribe commands are both processed. If you want to consider that a bug, you can, but consider that you might want to request subscription for two addresses in one request email. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Email subscription
Melinda Gilmore wrote: I have been searching the archives and have not been able to find my answer. I just want to be able to subscribe by email. Does not seem to be working. Do you send to [EMAIL PROTECTED] blah blah and then subscribe. Is there something else that needs to be running on the machine. I just have a simple set up with Mailman 2.0 and sendmail. Any direction would be greatly appreciated. If this is really Mailman 2.0, I think you have to send a 'subscribe' command to [EMAIL PROTECTED] blah blah. The listname-subscribe and listname-join addresses were first introduced in Mailman 2.1. If it's really Mailman 2.1, and you get no response to a message to listname-subscribe, see http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp. Also check the list's Privacy options...-Subscription rules-subscribe_policy. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org 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/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] email subscription/unsubscription question
Yes, RTFM. Website Administration wrote: Hi, Is it possible to setup subscription and unsubscription (ie the user sends a message to the list with SUBSCRIBE in the subject) to my lists via email? If so, how? Thanks Adriaan -- 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/ -- 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/
Re: [Mailman-Users] email subscription/unsubscription question
At 1:56 PM +0200 2004/05/17, Website Administration wrote: Is it possible to setup subscription and unsubscription (ie the user sends a message to the list with SUBSCRIBE in the subject) to my lists via email? Mailman does this by default. -- 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. SAGE member since 1995. See http://www.sage.org/ for more info. -- 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/
RE: [Mailman-Users] Email Subscription
sure, just send mail to listname[EMAIL PROTECTED] with the subject subscribe sans the quotes And does the sysadmin have to have set up a username listname-request for this to work? Otherwise, wouldn't it just get rejected with user not found or some such? [Taking great glee in adding spamsters to the list in mm_cfg.py and wondering why that doesn't seem to be happening to this list.] John G. Otto, Eagle Scout, Knight, Cybernetic Praxeologist Existence, Consciousness, Identity, Life, Liberty, Property, Privacy, Justice -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
Re: [Mailman-Users] Email Subscription
And does the sysadmin have to have set up a username listname-request for this to work? Otherwise, wouldn't it just get rejected with user not found or some such? No. If your MTA is sendmail or sendmail compatable then it checks first in /etc/aliases for any aliases (or address translations): mailman: jonc abuse: jonc ithelp: jonc, jaimiel, lward In the above example abuse, ithelp, and mailman are not users on the system, but jonc, jaimiel, and lward are users on the system. -- Mailman-Users maillist - [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users
RE: [Mailman-Users] Email Subscription
sure, just send mail to listname[EMAIL PROTECTED] with the subject "subscribe" sans the quotes -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Francis YapSent: Friday, November 16, 2001 11:39 AMTo: [EMAIL PROTECTED]Subject: [Mailman-Users] Email Subscription Wondering if there is a way that the user can subscript to the mailing just using email? rgds Francis
