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

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AIRAVATA-2509:
-----------------------------------------------------------

Commit 76fa9f91e48286b4c8f1c5b79c0d7607a9ec5e61 in airavata-php-gateway's branch refs/heads/develop from [~marcuschristie]
[ https://gitbox.apache.org/repos/asf?p=airavata-php-gateway.git;h=76fa9f9 ]

Merge pull request #79 from neeraj-lad/AIRAVATA-2509

[AIRAVATA-2509] Account confirmation, password reset emails not making it to user

> 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
(v7.6.3#76005)