0.9.1 (13-09-2013)
0.9.1/1 added support for Sender header (content form)
0.9.1/2 added support for built in "Email User" feature
0.9.1/3 added support for SendGrid
0.9.1/4 added support for bounce processing (Mandrill only atm)
I just did a test with the Email Users page. Sent an email via the Send Test Email button. I can see where it sent it in Mandrill Activity but it never shows up in my inbox.
I just did a test with the Email Users page. Sent an email via the Send Test Email button. I can see where it sent it in Mandrill Activity but it never shows up in my inbox.
Did you setup the domain correctly (DKIM, SPF)? If the email show up in Mandrill dashboard then the add-on works correctly. The rest is taken care by Mandrill. Depending on your email provider, your domain will need to be configured for the email to be delivered to the inbox (or it will be marked as spam).
Yes everything is setup correctly. It only broke with this update. Watched thread emails are also no longer working but they are showing up as sent in Mandrill.
They aren't showing up in Spam folder either. Simply not showing up at all.
Yes everything is setup correctly. It only broke with this update. Watched thread emails are also no longer working but they are showing up as sent in Mandrill
That's strange. Especially when the email is sent to Mandrill successfully. Please start a conversation with me to resolve this. Sorry for your problem.
The provider server is checked once a day, list of bounced email addresses will be used to find valid user with those addresses. Those users will be mark as need email confirmation + their email will be removed. User will see a notice saying the site cannot send email at their address, they need to update it with another address. After user enter a new address (they cannot use the bounced one, it will be denied), the normal email verification process happens.
The provider server is checked once a day, list of bounced email addresses will be used to find valid user with those addresses. Those users will be mark as need email confirmation + their email will be removed. User will see a notice saying the site cannot send email at their address, they need to update it with another address. After user enter a new address (they cannot use the bounced one, it will be denied), the normal email verification process happens.
Yes, currently it is logged to a .log file inside internal_data. In case people have trouble with the feature I will ask for that file to inspect. When everything runs smooth, I will ditch the log file.
The provider server is checked once a day, list of bounced email addresses will be used to find valid user with those addresses. Those users will be mark as need email confirmation + their email will be removed. User will see a notice saying the site cannot send email at their address, they need to update it with another address. After user enter a new address (they cannot use the bounced one, it will be denied), the normal email verification process happens.