-
Notifications
You must be signed in to change notification settings - Fork 9
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
Feature Request #4
Comments
I have not had this problem. But as a test case, I tested these emails on a highly restrictive spam-filtered email server and had no problems. So, the issue may be with how your spam filter is set. Has this occurred at only one address? Or have several of your new registrants has this problem? Thanks. |
I had this issue on my first try. I am using "noreply@mydomain.com" as sender email and the confirmation mail was send to a gmx account without custom filters. But nevertheless it can always happen and some users are not that familar with those issues, so that an additional hint is just more custom friendly |
That may be your problem: noreply@mydomain.com. |
"mydomain" will be replaced with the real domain. I think it is more the issue that gmx does not like "noreply" even though that this is redirected to a collective account. But I have choosen noreply because I dont want answers on this mail. |
The plugin does not set its own email headers; it uses the Dokuwiki configuration. So, if this plugin's email is being rejected as spam, then any other similar mail sent from your site will also be treated as spam. |
Please add a hint in the $lang['confirmation'] that the user should check their spamfolder if they won't receive the email.
I have modified mine this way:
"$lang['confirmation'] ="
Confirmation link sent
An email with a confirmation link has been sent to your email address. Either click on that link or paste it into your browser. You will then be registered and will receive your password.In some cases it can happen that you have to check your Spamfolder to receive this email";"
The text was updated successfully, but these errors were encountered: