138 Procedure for signing on new users We need to think about how we want to allow new users to sign on to the site and become authorized 'bloggers'. We probably want a system that doesn't require using a computer, but can be handled from a phone as well. Do we want any kind of user approval? 2009-03-20 2009-04-07 90 20.0 41.959999971092 Fri Mar 20 17:44:41 -0700 2009 Tue Oct 20 10:14:58 -0700 2009 At this point: # anybody who stumbles onto the site and signs up starts out as 'active' and they receive a password through email. They need to get the attention of an administrator (which they can do with the "contact vozmob" menu) to request being promoted to blogger and be able to post or comment. # anyone who sends an MMS or SMS to the site gets assigned a random user name (like "6ff87c7f-35b6d1e7") and is automatically a blogger, but they can't sign on to the site until an admin sets up a password for them. It's not clear how these users would get our attention unless they know one of us.

I think we want it to work like this: A new user hears about the site at a center or on the street (say, during a march or action). A vozmob correspondent talks to them, explains how to send a story to the site, and gives them a card with instructions as well as contact info. Then... 1. I think the first thing they send should be an mms (photo / picture message), if possible. That way, we will get the correct address to send them mms based on their provider (for example, when I send an mms to test ^@^ vozmob.net, it arrives at the site from 1234567890@vzwpix.com. This is the same address to send me mms.) 2. If we want to make it as simple as possible for the user, then we could check to see whether it's their first post (or if they're unregistered). If so, then in addition to posting their story under an anonymous username, we also send them a message back: > 'Thanks / Gracias! U can see ur story at / se puede ver su historia en http://vozmob.net/[storylink]. > [actually, maybe we should do this for every post?] > > If u want a vozmob blog, reply "YES" to this msg / Si quiere un blog en vozmob, contesta "SI" a este mensaje. Is that too many characters? 3. Anway, if they write back "YES" or "SI" then we give them these instructions in the appropriate language: > Great! Reply to this message with the name you'd like for your blog, and we'll create it. [should we ask them to just use one word, with no spaces or special characters? Or just let them put whatever they want. I think drupal usernames can handle spaces, etc.] > Excelente! Conteste este mensaje con el nombre que quiere para su blog, y lo construiremos [?] 4. If the name they want is available, then we change their random username to the one they wrote, generate a random password, and send one more message back to them: > Congratulations, [username], your blog has been created. To post new stories, just send them to [groupaddress @ vozmob.net]. To edit your stories, go to vozmob.net and login with your username [username] and password [random pass]. Please change your password the first time you login. If you forget your password, just text 'password' to 'help AT vozmob.net.' Thanks! > Felicidades, [usuario], su blog ha sido actualizado. Para escribir nuevas historias, mandelas a [direccion del grupo @ vozmob.net]. Para editar sus historias, ir a vozmob.net y login con su nomber de usuario [usuario] y contraseña [contraseña randon]. Favor de cambiar su contraseña la primera vez que entra. Si olvide su contraseña, mandar un texto 'contraseña' al 'ayuda AT vozmob.net.' Gracias! 5. If the username they want is already taken, we have to send a message like: > Sorry, that blog name is already taken. Please reply to this message with another name for your blog and we'll get you set up. > Disculpe, el nombre que ha escogido ya parece a otra persona. Favor de responder a este mensaje con otro nombre para su blog y lo arreglamos. Some notes if we use this process: - we gotta make sure to only do all this if they're unregistered. - we gotta set up help / ayuda @ vozmob DOT net, to respond with a number of possible requests. Starting with the most crucial (password), but potentially a lot of stuff (groups/list management, instructions for how to post, instructions for how to do various things directly from the phone...) - actually, until we get 'help' set up, we can always just tell people that if they forget their password or need help they can just call us. And provide a phone number for support. Maybe this is better for the moment ;)

We're switching this to Gaba and making it urgent since it has to work really nicely before Mayday! Gaba, in terms of testing it out, since mms come in through the gmail accounts you should be able to do a good chunk of the setup and testing just using gmail. Once that part is working well, we will do tests with actual phones :)

Attached is what I am understanding of what you said. So we are saying that some users can interact with the site (registering, posting) without never going to check the website. Is not better to ask the bloggers to complete the registration online if they want to post frequently and only use the post-to-the-site anonymously from the phone for the people that are gonna post sporadically? Right now we have mailhandler and mailsave to process the post-from-the-phone. Mailhandler is reading the mail and automatically creating a node with the mail. Mailsave is handling the attachments in the mails. For this user case we would like to trigger an event "send an sms asking for username" in case that the mobile phone number that they are sending the mail from is not registered in the vozmob site. For that I could modify the mailhandler to use the sms framework module and then use the sms framework module to process the conversation with the new user. !http://dev.vozmob.net/attachments/34/registerUser.jpeg!

Our use case is that many users may only access vozmob via phone. A core group of users will mostly access vozmob by sending stories from phones, but will often (several times a week) login to edit stories. Many users will receive stories from vozmobcms on their phones only. Here's my stab at the user registration flow chart :) !http://dev.vozmob.net/attachments/36/user-reg-flow.gif! note: anon username is no longer random, it's vozmob-1234 (etc) note: at step 5, should be: "if you would like to register, send your username to register AT vozmob.net"

gaba re: your comment: >For that I could modify the mailhandler to use the sms framework module and then use the > sms framework module to process the conversation with the new user. we need to discuss the different solutions to decide which makes the most sense. SMS framework is one possibility, but I'm not sure what mark is using in order to send MMS to phones (modifying sms framework or something else?) Basically, we have to decide how our system communicates with the user: 1. sending an actual sms? 2. sending an sms by using the phone provider email to sms gateway? 3. sending an mms by using the phone provider email to mms gateway? (2 and 3 might make a difference since some providers send emails from different addresses depending on whether it came as sms or mms...?) 3. makes the most sense to me, but we can discuss... Once we know that, then we decide, how exactly to send the mms (what modules / custom code to use)?

re: the language question, just realized: actually, we are setting up many email addreses [12:17pm] schock: basically an addy for each group [12:17pm] schock: like 'foodnotbombs AT vozmob.net' [12:17pm] schock: idepsca AT vozmob.net [12:17pm] schock: so each one will have a default language [12:17pm] schock: and that will determine the language of the interaction that happens

Looks like we might be able to do most (or all?) of this using actions? http://vozmob.virishi.net/es/admin/settings/actions

SMS framework provides an API for sending SMS messages to users. It will work with whatever SMS gateway module is installed (e.g. sending via commercial SMS gateway or via carrier's email gateway). I think this is sufficient unless there's some reason you need to send MMS during registration? The registration happens in our custom sms mailsave "cleanup" filter, sms.inc. If we start adding a lot more functionality to it we might want to make it a full-fledged module with configuration page etc. (and even release it on drupal.org).

So we discussed and clarified some parts of this process on today's call. * we will set up a separate email address, like 'registrar AT vozmob.net,' to handle the registration interaction. Starting with step 5 in our flow chart above (system asks user if they want to register), messages will come from that address. * The user replies to that address, so we know that messages coming in to that address are registration messages rather than stories to be posted to the site. > gaba: check the send_to_address, if it is the receiving mail then check the receiving_address and change the username for that receiving_address user > gaba: receiving mail means registration mail * Note that we still have to pay attention to the default language of the sender, and send them registration questions/info in the appropriate language. We know the default language based on the default language of the address they sent their first post to. * We also talked about how for the moment this process can just be hardcoded, but later we will want to refactor it and set it up to make it customizable via the admin GUI.

let me know if you'd like me to set up that adress, and what it should forward to. maybe one per language? registrar AT vozmob.net and signup AT vozmob.net ?

Francois Bar wrote: > let me know if you'd like me to set up that adress, and what it should forward to. > maybe one per language? registrar AT vozmob.net and signup AT vozmob.net ? Yes! It should forward to the same one where we are receiving the posts for the site. The only different (on the technical side) is that we are gonna filter the mails that have "To: registrar AT vozmob.net" in their headers and consider them as registration information instead of new nodes.

Wouldn't it make troubleshooting easier if the email account for these is separate?

OK, new version of the flow based on today's irc meeting: !user-reg-flow-v2.png! Suggested Text for each step: Step 4: > es: Gracias! Se puede ver su historia en http://vozmob.net/[storylink]. > en: Thanks! You can see your story at http://vozmob.net/[storylink]. Step 5: > es: Si quiere un blog en vozmob, simplemente conteste este mensaje con el nombre que quiere usar [?]. > en: If you want a vozmob blog, just reply to this message with the name you'd like to use. * [note: should we ask them to just use one word, with no spaces or special characters? Or just let them put whatever they want. I think drupal usernames can handle spaces, etc.] IF: If the name they want is available, then we change their random username to the one they wrote, generate a random password, and send one more message back to them: > es: Felicidades, [usuario], su blog ha sido actualizado. Para escribir nuevas historias, mandelas a [direccion del grupo @ vozmob.net]. Para editar sus historias, ir a vozmob.net y login con su nombre de usuario [usuario] y contraseña [contraseña randon]. Gracias! * [note: "Favor de cambiar su contraseña la primera vez que entra." but we can do that when they actually log in.] * [note: "Si olvide su contraseña, mandar un texto 'contraseña' al 'ayuda AT vozmob.net.'"] > en: Congratulations, [username], your blog has been created. To post new stories, send them to [groupaddress @ vozmob.net]. To edit your stories, go to vozmob.net and login with your username [username] and password [random pass]. Thanks! * [note: if the user actually signs in, we might want to ask them to change their password to something else.] * [note: we need a pword recovery system. "If you forget your password, just text 'password' to 'help AT vozmob.net.'"] IF: the user replies no ("no" "No" "NO" "N" "n" etc), then should we say anything at all? like: > es: OK, gracias por su historia! > en: OK, thanks for your story! ALSO: if they say no, maybe we need to set a state for the user [like confirmed.anonymous] so that we don't ask them to sign up everytime they post? IF: the username they want is already taken, or won't work (too long, bad characters, etc) we have to send a message like: > es: Disculpe, el nombre que ha escogido ya parece a otra persona o no funcionaria. Favor de responder a este mensaje con otro nombre para su blog y lo arreglamos. Gracias. > en: Sorry, that name is already taken or won't work. Please reply to this message with another name for your blog and we'll get you set up. Thank you.

done. registrar at vozmob and signup at vozmob now both forward to shmivacy

Just set up vozmob.registrar AT gmail.com, and added it to mailhandler. let's forward registrar at vozmob and signup at vozmob there instead, that will make troubleshooting registration problems easier.

Bump. Gaba, what's the status with this issue? It hasn't been updated for 3 weeks.

I'm stuck with the problem that all the sms are being published to the site by mailhandler. I'm trying to modify mailhandler (or find a patch in drupal) to select what to publish depending on the mail configured and adding none to the options.

@gaba: to not publish you should simply be able to set the $node to FALSE in a hook (in either a mailhandler or mailsave hook -- the latter being what I used in sms.inc; it's all the same because a mailsave hook is part of mailsave module's mailhandler hook).

Another way to do it, but only works if the registration interaction happens via a specific mailbox: in mailhandler default commands, simply add the line: "status: 0" which will result in the node being created, but not published.

This post describes a solution to our problem with the 'from' / 'reply to' headers: http://www.alleged.org.uk/pdc/2008/08/21.html

Please test!

Sorry, this isn't quite at 100% yet... not until this all works, in multiple languages, has been tested: http://dev.vozmob.net/issues/138#note-23

Do we have the language specific mails already done ? What are they?

we have the following set up: signup AT vozmob (Active) forwarded to: vozmob.registrar AT gmail registrar AT vozmob (Active) forwarded to: vozmob.registrar AT gmail

ok. And do we have one with specific language for when people send their posts? It's for when we reply saying "Thanks for your posting" or "Gracias por su mensaje" a usuarios aun no registrados.

one more thing, the code is written and i need to update the language specific mails (hardcoded until we put this in a separate module...)

we have a whole bunch of addresses... some with mailhandler set as 'language specific', others not... do you just need some spanish and english mboxes for testing? (if so: mms AT vozmob is spanish, southla AT vozmob is english) But more generally, could this be something that is determined by looking at the language setting for each mailbox on mailhandler? would be best, as we're likely to add new addresses, change old ones, etc.

> But more generally, could this be something that is determined by looking at the language setting for each mailbox on mailhandler? would be best, as we're likely to add new addresses, change old ones, etc. Yeah, that's what we're doing. See the chart above at http://dev.vozmob.net/issues/138#note-23 ;)

Just sent a test message to sandbox AT vozmob. Received spanish language confirmation and request to register, from info AT vozmob. That's still wrong. Will next try sending messages directly to the registration addys to see if that part works.

Sasha Costanza-Chock wrote: > Just sent a test message to sandbox AT vozmob. Received spanish language confirmation and request to register, from info AT vozmob. That's still wrong. > > Will next try sending messages directly to the registration addys to see if that part works. sandbox@vozmob is not setup. I feel that we are getting confused with how the mails should be working for this process. Can we specify this? How we know that the mail (in this example sandbox@vozmob) should be setup for spanish or english? In this moment we are doing it harcoded but should we have an specific pattern for the mail names in spanish and other in english (xxx-es@vozmob versus xxx-en@vozmob)? When we put this in a separate module it should be configurable.

> sandbox@vozmob is not setup. I feel that we are getting confused with how the mails should be working for this process. Can we specify this? How we know that the mail (in this example sandbox@vozmob) should be setup for spanish or english? In this moment we are doing it harcoded but should we have an specific pattern for the mail names in spanish and other in english (xxx-es@vozmob versus xxx-en@vozmob)? When we put this in a separate module it should be configurable. I think the confusion is because we have to set up a flow for sandbox first, in order to test, then once its working move it to production site. So here's some clarification: *For testing on sandbox* 1. new user sends first mms to sandbox AT vozmob.net, which forwards to vozmob.sandbox AT gmail, and has default language es. 2. they should receive a confirmation and an invitation to create a blog, in spanish. This message should come FROM reg-prueba AT vozmob. 3. user replies with their preferred name, and that message goes TO reg-prueba AT vozmob, (which currently forwards to vozmob.sandbox - does it need to go to a different, dedicated 'vozmob.sandbox.registrar' mailbox?) 4. If the name is not available, we ask them to try another. If it is ok, then we say: es: Bienvenid@s, [usuario]. Puedes entrar al sitio vozmob.net con la contraseña [contraseña randon]. Gracias! To test out the language part, we can either just switch the default language to 'en' in mailhandler default commands for sandbox, or we can set up a separate addy and mailbox like sandbox-en. In either case, we should be checking the default language in mailhandler, and if it's english, all the dialogue is in english, and it can come from reg-test AT vozmob (which currently forwards to: vozmob.sandbox AT gmail) *For the production site* 1. new users may be sending their first mms to any one of many addresses/mailboxes: http://dev.vozmob.net/projects/vozmob/wiki/VozMobForwards 2. they should receive a confirmation and an invitation to create a blog, in the language specified in the mailhandler default commands for the mailbox they posted to. This message should come FROM registrar AT vozmob or signup AT vozmob, depending on the language. 3. user replies with their preferred name, and that message goes TO either registrar or signup AT vozmob (which both currently forward to vozmob.registrar AT gmail) 4. If the name is not available, we ask them to try another. If it is ok, then we say: es: "Hola, [usuario]. Su contraseña es [contraseña randon]. Bienvenid@s a vozmob.net!", or en: "Hi, [user]. Your password is [random password]. Welcome to vozmob.net!" does this help?

Great! Now this is totally not hardcoded and we check the language in the settings of the mail address in mailhandler. It is working. Please, test again.

I just tested it out by sending a message to sandbox AT vozmob PUNTO net, i got the reply in english "thanks! do you want to have a blog in vozmob..." and it still came from info @ vozmob.net... Going to try responding, but sending the message to 'reg-test AT vozmob' and see what happens.

The new module for setting up the correct from header, is setting up the header to the mail in the info of the vozmob site. We need to override that and send from registrar when users are registering.

In order for the returnpath module to set the return path to the from address, we need to implement hook_mail_alter() in one of our modules so we can set $message['headers']['Return-Path'] to whatever it needs to be set to. Of course we presumably need to set this to different values depending on the type of message we're sending out. Right now the Return-Path header is being set to the main site email address by drupal core and then returnpath module is passing this Return-Path thru to the sendmail command-line flag (a.k.a. last parameter of mail() function). If we customize the Return-Path header then returnpath module will use it instead.

It works! And in both english and spanish :) Now we just need to move it to production. And gaba, can you post here a link to your code, then close out the issue? thx.

The code is in github: http://github.com/gabelula/vozmob/tree/8cab1540d9f331bfffc8b281d1f66fb6ec9ed739/html/sites/all/modules/mailsave

did some refactoring to move the code from mailsave/cleanup directory to sms_registration and add a configuration page. needs some testing though (on sandbox).

This stopped working and now I fixed the bugs in sandbox. Needs more testing.

Reassigning to MFB. We need one more round of testing of sms/mms registration, then it should be moved to production. This is very high priority.

Fixed the sandbox instance, so registration is ready for more testing there. Lots of modules we need were disabled, probably due to importing the production db. For the moment we probably shouldn't import the production db into sandbox, unless there's a good reason. Because sandbox is often quite far ahead of production in terms of new modules being enabled etc. What we need is an update script (e.g. as part of the vozmob module's .install file) so, when loading an old database onto current codebase, we can easily catch it up to the current state. Of course this sort of automated update script is also needed when vozmob is released as a distribution.

Idea: resolve this issue and open up new bugs or feature requests for anything else outstanding?