Confirmation by reply not working
Hello,
I'm having problems with the confirmation by reply working. When a user is invited to the list, or when a user subscribes on the web for, or when a user subscribes by emailing -join@, they are sent the confirmation email.
If they replay to the email or create a new message and send ONLY the confirmation code as instructed, nothing happens. However, if they try again with the same confirmation code, they will get a response back that the confirmation code is no loger valid. This appears to indicate that mailman is receiving the email and processing it, but not actually subscribing them to the list.
This is happening after moving to CentOS 7 using PLESK 12.5...
Any ideas on what could be going on?
On 10/25/2015 06:01 PM, Keith Seyffarth wrote:
If they replay to the email or create a new message and send ONLY the confirmation code as instructed, nothing happens. However, if they try again with the same confirmation code, they will get a response back that the confirmation code is no loger valid. This appears to indicate that mailman is receiving the email and processing it, but not actually subscribing them to the list.
What is the subscribe_policy for the list (Privacy options... -> Subscription rules)? If 'Confirm and approve', are the subscriptions waiting approval by a moderator?
What's in Mailman's vette and subscribe logs?
Does web confirmation work?
Anything in Mailman's error log?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
If they replay to the email or create a new message and send ONLY the confirmation code as instructed, nothing happens. However, if they try again with the same confirmation code, they will get a response back that the confirmation code is no loger valid. This appears to indicate that mailman is receiving the email and processing it, but not actually subscribing them to the list.
What is the subscribe_policy for the list (Privacy options... -> Subscription rules)? If 'Confirm and approve', are the subscriptions waiting approval by a moderator?
It's just confirm. I don't see any way to approve a subscription, but that may be because qpproval is nto required.
What's in Mailman's vette and subscribe logs?
Both are empty for the last three days.
Does web confirmation work?
Yes.
Anything in Mailman's error log?
Oct 27 17:22:16 2015 (901) Uncaught runner exception: [Errno 9] Bad file descriptor Oct 27 17:22:16 2015 (901) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 263, in _dispose ret = res.process() File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 118, in process ret = self.do_command(cmd, args) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 146, in do_command return self.do_command(cmd, args) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 151, in do_command if handler.process(self, args): File "/usr/lib/mailman/Mailman/Commands/cmd_confirm.py", line 46, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/lib/mailman/Mailman/MailList.py", line 1257, in ProcessConfirmation self.ApprovedAddMember(userdesc, whence=whence) File "/usr/lib/mailman/Mailman/MailList.py", line 1015, in ApprovedAddMember kind, formataddr((name, email)), whence) File "/usr/lib/mailman/Mailman/Logging/Syslog.py", line 43, in write self.write_ex(kind, msg, args, kws) File "/usr/lib/mailman/Mailman/Logging/Syslog.py", line 52, in write_ex logf = self._logfiles[kind] = StampedLogger(kind) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 76, in __get_f _logexc(self, e) File "/usr/lib/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 9] Bad file descriptor
Oct 27 17:22:16 2015 (901) SHUNTING: 1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f
On 10/27/2015 04:28 PM, Keith Seyffarth wrote:
Anything in Mailman's error log?
Oct 27 17:22:16 2015 (901) Uncaught runner exception: [Errno 9] Bad file descriptor Oct 27 17:22:16 2015 (901) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 263, in _dispose ret = res.process() File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 118, in process ret = self.do_command(cmd, args) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 146, in do_command return self.do_command(cmd, args) File "/usr/lib/mailman/Mailman/Queue/CommandRunner.py", line 151, in do_command if handler.process(self, args): File "/usr/lib/mailman/Mailman/Commands/cmd_confirm.py", line 46, in process results = mlist.ProcessConfirmation(cookie, res.msg) File "/usr/lib/mailman/Mailman/MailList.py", line 1257, in ProcessConfirmation self.ApprovedAddMember(userdesc, whence=whence) File "/usr/lib/mailman/Mailman/MailList.py", line 1015, in ApprovedAddMember kind, formataddr((name, email)), whence) File "/usr/lib/mailman/Mailman/Logging/Syslog.py", line 43, in write self.write_ex(kind, msg, args, kws) File "/usr/lib/mailman/Mailman/Logging/Syslog.py", line 52, in write_ex logf = self._logfiles[kind] = StampedLogger(kind) File "/usr/lib/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__ Logger.__init__(self, category, nofail, immediate) File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 50, in __init__ self.__get_f() File "/usr/lib/mailman/Mailman/Logging/Logger.py", line 76, in __get_f _logexc(self, e) File "/usr/lib/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 9] Bad file descriptor
Oct 27 17:22:16 2015 (901) SHUNTING: 1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f
That's the problem. I'm not sure what's going on, but the issue is in writing to Mailman's 'subscribe' log. What does
ls -l /path/to/mailman/logs/
show?
Also, it may or may not be helpful, but if you could send me off list the /path/to/mailman/qfiles/1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f.pck file or alternatevely, post or send me the output from
/path/to/mailman/bin/dumpdb /path/to/mailman/qfiles/1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f.pck
it might help.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
That's the problem. I'm not sure what's going on, but the issue is in writing to Mailman's 'subscribe' log. What does
ls -l /path/to/mailman/logs/
show?
bounce error post qrunner smtp smtp-failure subscribe vette
Each of which has one or more archived log files. Subscribe is owned by root, others are owned by mailman.
Also, it may or may not be helpful, but if you could send me off list the /path/to/mailman/qfiles/1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f.pck file or alternatevely, post or send me the output from
/path/to/mailman/bin/dumpdb /path/to/mailman/qfiles/1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f.pck
it might help.
Can you help me figure out "/path/to/mailman/qfiles/?" I'm not finding anything like that in any of the mailman directories I can find...
thanks, Keith
On 10/27/2015 06:07 PM, Keith Seyffarth wrote:
That's the problem. I'm not sure what's going on, but the issue is in writing to Mailman's 'subscribe' log. What does
ls -l /path/to/mailman/logs/
show?
bounce error post qrunner smtp smtp-failure subscribe vette
I need 'ls -l'. I want to see the owner, group and mode of the files.
Each of which has one or more archived log files. Subscribe is owned by root, others are owned by mailman.
sudo chown mailman:mailman subscribe
may help.
Also, it may or may not be helpful, but if you could send me off list the /path/to/mailman/qfiles/1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f.pck file or alternatevely, post or send me the output from
/path/to/mailman/bin/dumpdb /path/to/mailman/qfiles/1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f.pck
it might help.
Can you help me figure out "/path/to/mailman/qfiles/?" I'm not finding anything like that in any of the mailman directories I can find...
Aaahh yes, you did say CentOS. And I gave you the wrong path anyway (I left out shunt). For RedHat/CentOS it's
/var/spool/mailman/shunt/1445988136.175048+4b651bb8e2ca5a8b65ef1b9f3c4a54e715f0686f.pck
See <http://wiki.list.org/x/8486953> to translate my paths to yours.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
I need 'ls -l'. I want to see the owner, group and mode of the files.
Sorry about that.
-rw-rw-r-- 1 mailman mailman 12745 Oct 27 20:20 smtp -rw-rw-r-- 1 root root 0 Oct 18 02:42 subscribe
[etc]
They all had the same permissions, and except "subscribe" they all had the same owner
Each of which has one or more archived log files. Subscribe is owned by root, others are owned by mailman.
sudo chown mailman:mailman subscribe
may help.
that actually did it. And subscribe from 'mass subscribe' or confirming by clicking the link also still work.
Thanks!
Keith
participants (2)
-
Keith Seyffarth -
Mark Sapiro