Create User Account fields on the kabootr dev, and test the kabootr with real data.

[gauravgoyal]

Before sending the mail, be 100% sure that no mail is sent to the actual user.

reference : innoraft/kabootr #36

[gauravgoyal]

@sumeetpareek Following user fields are created on kabootr dev :

• [x] Name
• [x] Address
• [x] City
• [x] District
• [x] State
• [x] Country
• [x] Gender
• [x] Age
• [x] Lok Sabha
• [x] Vidhan Sabha
• [x] Source Of Data
• [x] Date
• [x] Contact

[gauravgoyal]

@sumeetpareek For importing users we do not have their username, and as we are using feeds for importing users, both email and username are compulsory fields for user import. So to overcome this i am using email_registration (Contrib module), and feeds_email_registration (Sandbox module).

Email Registration module :- This module is in the dependancy of feeds_email_registration module.

feeds_email_registration module :- This module uses email for extracting the user name from the email. For e.g. if the mail of user is abc@xyz.com then user name will be abc, and if a new users comes with email abc@example.com then user name for this user will be abc_1.

[gauravgoyal]

@sumeetpareek db backup has been created at server, location : /home/db/before-live-data-test-2013-10-30.sql.gz

[gauravgoyal]

@mukeshagarwal @sumeetpareek for the testing of kabootr, we need to change all real emails to either our emails or we use mail_redirect module, now as amazon ses service send mails only to verified email addresses, we have to first verify all the emails and then only we can sent, so due to this reason i am thinking to go with our email addresses instead of using mail_redirect module. this will reduce the time for testing. Please Share your thoughts..?

[mukeshagarwal]

@gauravgoyal why not use mailinator instead of innoraft?

[gauravgoyal]

@mukeshagarwal If we use mailinator, we will not be able to see sent mail is went in inbox or spam

[mukeshagarwal]

then why not use a couple of innoraft's email and rest all as mailinator?

On Wed, Oct 30, 2013 at 7:19 PM, Gaurav Goyal notifications@github.comwrote:

@mukeshagarwal https://github.com/mukeshagarwal If we use mailinator, we will not be able to see sent mail is went in inbox or spam

— Reply to this email directly or view it on GitHubhttps://github.com/innoraft/kabootr/issues/41#issuecomment-27390078 .

Cheers, Mukesh

---

Innoraft Solutions http://www.innoraft.com/ | +91-8017220799

[tkuldeep]

@gauravgoyal @sumeetpareek @mukeshagarwal I am not getting what we want to test,

• As gaurav is saying our mail is going into inbox, or spam it will be decided by Amazon SES, not by us. We don't have control over it. As I have studied amazon SES, amazon always sends mail to inbox never spam. And our mail deliverability will be decided by mail quality that we send.

So according to me we have to focus into following

• Weather kaboot is generating correct user list by user filters.
• How much time kabootr is taking to send mail number of mails. So that we can control our sending limit, way of sending mail mean sending http request to amazon SES.
• Amazon Feedback notification.
• By watching our sending statistics we can use efficiently amazon SES.

[mukeshagarwal]

@tkuldeep well we know that Amazon is good but one of the reports that we would want is to know how many mails went to spam. Plus we need to verify ourselves whether emails are going to inbox only. We are not trying to ensure that it goes to inbox and not spam, as you said, we dont have any control on it.

I guess we need to make it batch process as the first thing, else php timeout could become an issue.

[tkuldeep]

@mukeshagarwal For sending mail mail, we are using two method. We can change this setting here http://dev-kabootr.innoraft.com/admin/config/services/simplenews/settings/mail

• All mail will be sent in batch process.
• or All mail will be sent in cron. And I am not sure, we will face php time out problem in cron run or not..

[mukeshagarwal]

@tkuldeep is this an option given to the admin? I think we should have just kept it as a batch process and not cron. Cron would mean, whenever the cron is run next, the mails will go out. But with mailing service, the customers would expect that the emails go out then. Thoughts?

[tkuldeep]

@mukeshagarwal Sorry I am unable to understand your phrase But with mailing service, the customers would expect that the emails go out then. Thoughts?

[mukeshagarwal]

@tkuldeep so the customer (who uses kabootr) will draft an email on kabootr and click on send. Now if this goes through cron, that would mean the emails will go out when the next cron is run. However, the customer would expect the emails to go out then only. Therefore, I suggest it should only be batch process.

[tkuldeep]

@gauravgoyal Please review my code in branch version_1, at any point if you are unable to understand my code, comment there, so that I can rectify that.

@sumeetpareek @mukeshagarwal Also please review my approach which I have used, as currently we have to change the way, kabootr is sending mail. In current approach we are not taking advantage of sending parallel http request and use of guzzle batch requesting system.

[mukeshagarwal]

Email that I got:

Email Header:

from: tkuldeep.singh@innoraft.com via amazonses.com to: mukesh.agarwal@innoraft.com date: Thu, Oct 31, 2013 at 12:53 PM subject: [Users From CANADA] Hey [simplenews-subscriber:user] mailed-by: amazonses.com

Email Content:

-------- HEY [SIMPLENEWS-SUBSCRIBER:USER] ------------------------------------ Hi All, This mail is sent to Test Kabootr \ Regards, Kabootr Users From CANADA http://dev-kabootr.innoraft.com/newsletter/users-canada -- Unsubscribe from this newsletter: http://dev-kabootr.innoraft.com/newsletter/confirm/remove/85988a2b867t6

[tkuldeep]

@mukeshagarwal @gauravgoyal For sending html mail, we have to use contrib module mimemail https://drupal.org/project/mimemail. I need some time to use it..