Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Notifications: investigate Dataverse email handling issues by Yahoo and Gmail #4206

Closed
kcondon opened this issue Oct 13, 2017 · 3 comments
Closed

Comments

@kcondon
Copy link
Contributor

kcondon commented Oct 13, 2017

Note: this happens only on demo. on test boxes like internal, it is delivered fast and to the inbox

It appears Dataverse email notifications are not received well and consistently by email providers like Yahoo and Gmail but works better with test site Mailinator.

Email may not appear, appears slowly, shows up as spam. It is not yet clear if there is a pattern but it may be related to the html links and domains of such links in the mail body or perhaps a difference between sender and reply to addresses.

Yahoo appears to convert links to plain text so that indicates some additional processing based on html and it puts all email in spam. Email was slow to appear

@donsizemore
Copy link
Contributor

Kevin,

I'm just going through this with UNC Dataverse and UNC's hosted Office 365 mailsystem. E-mail verification messages from our Dataverse show up properly in my personal Gmail, but the Office365 spam checker strips the sentence containing the verification token.

Beyond having UNC whitelist us in three ways (spam, connection, spoofing), one recommendation I overlooked was to make the :SystemEmail setting match the address specified in domain.xml.

@kcondon
Copy link
Contributor Author

kcondon commented Oct 13, 2017

Cool, so do you think it is a domain mismatch issue between system email domain and the mail server domain in domain.xml?

Oh, I get it, the system email match the from address in domain.xml

@kcondon
Copy link
Contributor Author

kcondon commented Oct 13, 2017

@donsizemore You are the hero for the day! That seemed to fix the problem. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants