[jira] [Comment Edited] (AIRAVATA-2509) Account confirmation, password reset emails not making it to user

["Eroma (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AIRAVATA-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16313736#comment-16313736 ] 

Eroma edited comment on AIRAVATA-2509 at 1/5/18 7:48 PM:
---------------------------------------------------------

Tested in https://dev.seagrid.org and https://dev.scigap.org/
Test cases
https://dev.seagrid.org
1. Create a new gateway account in dev.seagrid using gmail account. - PASS
2. Create a new gateway account in dev.seagrid using institute (IU) account.
3. Create a new gateway account in dev.seagrid using gmail account and give a different gmail account for 'Email (again)'- PASS (Error message thrown saying that two doesn't match)
4. Create a new gateway account in dev.seagrid using institute account and give a different institute account for 'Email (again)' (if possible both of the same person)
5. Test email format validations in dev.seagrid - PASS (Can improve. @ sign and string ollowing that are checked at field level but .com is only validated after user clicks Create)
6. Test password reset for user with institute email. - PASS
7. Test password reset for user with gmail email.

https://dev.scigap.org/
1. Create a new gateway account in dev.scigap using gmail account.
2. Create a new gateway account in dev.scigap using institute (IU) account.
3. Create a new gateway account in dev.scigap using gmail account and give a different gmail account for 'Email (again)'
4. Create a new gateway account in dev.scigap using institute account and give a different institute account for 'Email (again)' (if possible both of the same person)
5. Test email format validations in dev.scigap
6. Test password reset for user with institute email.
7. Test password reset for user with gmail email.



was (Author: eroma_a):
Tested in https://dev.seagrid.org and https://dev.scigap.org/
Test cases
1. Create a new gateway account in dev.seagrid using gmail account.
2. Create a new gateway account in dev.seagrid using institute (IU) account.
3. Create a new gateway account in dev.seagrid using gmail account and give a different gmail account for 'Email (again)'
4. Create a new gateway account in dev.seagrid using institute account and give a different institute account for 'Email (again)' (if possible both of the same person)
5. Test email format validations in dev.seagrid
6. Create a new gateway account in dev.scigap using gmail account.
7. Create a new gateway account in dev.scigap using institute (IU) account.
8. Create a new gateway account in dev.scigap using gmail account and give a different gmail account for 'Email (again)'
9. Create a new gateway account in dev.scigap using institute account and give a different institute account for 'Email (again)' (if possible both of the same person)
10. Test email format validations in dev.scigap


> Account confirmation, password reset emails not making it to user
> -----------------------------------------------------------------
>
>                 Key: AIRAVATA-2509
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2509
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>            Reporter: Marcus Christie
>            Assignee: Neeraj Lad
>            Priority: Critical
>              Labels: newbie
>
> Email confirmation emails (when creating an account) and password reset emails aren't always making it to users.  There are at least a couple reasons for this:
> * the emails are getting flagged as spam and the user doesn't check the spam folder
> ** perhaps in some cases the emails never ever reach the user if they are marked as spam and stopped at the email server
> * the user mis-types their email address
> Possible fixes:
> * Can we find out what is causing emails to be flagged as spam? Is there a way to make the emails seem less "spammy"?
> ** See for example https://stackoverflow.com/a/396
> * Require that users type in their email address twice in order to confirm it. This should help prevent typos.
> * Can we determine if an email bounces back? This might be tricky since I think email bounce backs are asynchronous.  Perhaps having the user confirm their email address is the best we can do.
> Workarounds:
> * use CILogon instead of account creation/password reset.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)