problem sending multiple listserv commands via email
I am having a problem sending multiple subscribe commands via email. The first command in my list is always processed but the remaining commands are always unprocessed or ignored. Thanks in advance for any help.
***Message Sent:
subscribe MyPassword nodigest address=email1@someaddress.com subscribe MyPassword nodigest address=email2@someaddress.com subscribe MyPassword nodigest address=email3@someaddress.com
***Response Received:
Results: Usage:
unsubscribe [password] [address=<address>] Unsubscribe from the mailing list. If given, your password must match your current password. If omitted, a confirmation email will be sent to the unsubscribing address. If you wish to unsubscribe an address other than the address you sent this request from, you may specify `address=<address>' (no brackets around the email address, and no quotes!)
Unprocessed: subscribe MyPassword nodigest address=email2@someaddress.com subscribe MyPassword nodigest address=email3@someaddress.com
Done.
Christine Cubillo wrote:
***Response Received:
Results: Usage:
unsubscribe [password] [address=<address>] Unsubscribe from the mailing list. If given, your password must match your current password. If omitted, a confirmation email will be sent to the unsubscribing address. If you wish to unsubscribe an address other than the address you sent this request from, you may specify `address=<address>' (no brackets around the email address, and no quotes!)
Unprocessed: subscribe MyPassword nodigest address=email2@someaddress.com subscribe MyPassword nodigest address=email3@someaddress.com
Done.
The second and subsequent commands are not processed because the first command results in an error. That's why you see a Usage: message.
It appears that something has been broken in your Mailman installation as the subscribe commands appear to be invoking the cmd_unsubscribe module rather than the cmd_subscribe module.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Thanks for responding. Sorry, I pasted the usage message from one of my unsubscribe tests. Here are the results I get when i attempt to subscribe multiple email addresses. The first subscribe command is always processed and the remaining subscribe commands are left unprocessed. Is there a way I can get all commands in my email to be processed?
The results of your email command are provided below. Attached is your original message.
Results: You are already subscribed!
Unprocessed: subscribe MyPassword nodigest address=address2@somewhere.net subscribe MyPassword nodigest address=address3@somewhere.net subscribe MyPassword nodigest address=address4@somewhere.net subscribe MyPassword nodigest address=address5@somewhere.net subscribe MyPassword nodigest address=address6@somewhere.net subscribe MyPassword nodigest address=address7@somewhere.net subscribe MyPassword nodigest address=address8@somewhere.net
Done.
On Tue, Nov 1, 2011 at 8:33 AM, Mark Sapiro <mark@msapiro.net> wrote:
Christine Cubillo wrote:
***Response Received:
- Results: Usage:
unsubscribe [password] [address=<address>] Unsubscribe from the mailing list. If given, your password must match your current password. If omitted, a confirmation email will be sent to the unsubscribing address. If you wish to unsubscribe an address other than the address you sent this request from, you may specify `address=<address>' (no brackets around the email address, and no quotes!)
Unprocessed: subscribe MyPassword nodigest address=email2@someaddress.com subscribe MyPassword nodigest address=email3@someaddress.com
Done.
The second and subsequent commands are not processed because the first command results in an error. That's why you see a Usage: message.
It appears that something has been broken in your Mailman installation as the subscribe commands appear to be invoking the cmd_unsubscribe module rather than the cmd_subscribe module.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Christine Cubillo wrote:
Thanks for responding. Sorry, I pasted the usage message from one of my unsubscribe tests. Here are the results I get when i attempt to subscribe multiple email addresses. The first subscribe command is always processed and the remaining subscribe commands are left unprocessed. Is there a way I can get all commands in my email to be processed?
You can include multiple commands in one email, but the first command which is unrecognized, fails or results in an error terminates processing.
In the case below, the first command attempted to subscribe an address which is already a member so it failed and the remaining commands were unprocessed.
All commands will be processed if and only if they are all valid and all succeed.
The results of your email command are provided below. Attached is your original message.
Results: You are already subscribed!
Unprocessed: subscribe MyPassword nodigest address=3Daddress2@somewhere.net subscribe MyPassword nodigest address=3Daddress3@somewhere.net subscribe MyPassword nodigest address=3Daddress4@somewhere.net subscribe MyPassword nodigest address=3Daddress5@somewhere.net subscribe MyPassword nodigest address=3Daddress6@somewhere.net subscribe MyPassword nodigest address=3Daddress7@somewhere.net subscribe MyPassword nodigest address=3Daddress8@somewhere.net
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/1/2011 12:29 PM, Mark Sapiro wrote:
In the case below, the first command attempted to subscribe an address which is already a member so it failed and the remaining commands were unprocessed.
Why is that an error? I would expect it to ignored, just like setting a property to it's current value.
z!
Carl Zwanzig wrote:
In the case below, the first command attempted to subscribe an address which is already a member so it failed and the remaining commands were unprocessed.
Why is that an error? I would expect it to ignored, just like setting a property to it's current value.
Because Mailman/commands/cmd_subscribe.py distinguishes it from success and calls it fatal. Granted, an argument could be made that it shouldn't be fatal and similarly that unsubscribe of a non-member address shouldn't be fatal either, but it isn't completely obvious that that should be the case.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/1/11 4:55 PM, Mark Sapiro wrote:
Carl Zwanzig wrote:
In the case below, the first command attempted to subscribe an address which is already a member so it failed and the remaining commands were unprocessed. Why is that an error? I would expect it to ignored, just like setting a property to it's current value.
Because Mailman/commands/cmd_subscribe.py distinguishes it from success and calls it fatal. Granted, an argument could be made that it shouldn't be fatal and similarly that unsubscribe of a non-member address shouldn't be fatal either, but it isn't completely obvious that that should be the case.
One issue I see with this behavior, is that this breaks the privacy that mailman gives to lists. The web interface is very careful to NOT let you know if a given address is subscribed or not (unless the list publishes its subscriber list). This gives a method that you can get a message to one email address indicating that another, unrelated, email address is subscribed to the list.
-- Richard Damon
participants (4)
-
Carl Zwanzig -
Christine Cubillo -
Mark Sapiro -
Richard Damon