Dave Baker

+Clients
  • Content count

    75
  • Joined

  • Last visited

  1. Wonderful! Thanks! This is the perfect way to stop notification emails that otherwise would continue to go out to the non-working email addresses. The notification emails (when someone posts a reply into a topic that the registered user is following, for example) can cause penalties against my site when Cisco or other anti-spam monitoring services detect that my site is sending emails to non-working email addresses at their corporate customers (usually because the registered user is no longer employed by their corporate customer).
  2. AlexWebsites, to change that phrase you want to use the Admin Control Panel to change and resave a particular template. Here are the contents of the default template for version 1.0.0 of the plugin ( Admin CP -> Customization -> Themes -> </> -> templates -> core -> global -> plugins -> notValidated3 ): <section class='ipsType_center ipsPad'> <br><br> <i class='ipsType_huge fa fa-envelope'></i> <h1 class='ipsType_veryLarge'>Change your email!</h1> <p class='ipsType_large'> Your e-mail <b>{{$mail = \IPS\Member::loggedIn()->email;}}{$mail}</b> not working! </p> <p class='ipsType_large'> For working with our site you must use only working email address! </p> <hr class='ipsHr'> <p class='ipsType_normal'> <a href='{url="app=core&module=system&controller=register&do=changeEmail" seoTemplate="register"}' data-ipsDialog data-ipsDialog-size='narrow' data-ipsDialog-title='{lang="reg_change_email"}' data-ipsDialog-modal='true' class='ipsButton ipsButton_light ipsButton_verySmall'>{lang="reg_change_email"}</a> <a href='{url="app=core&module=system&controller=login&do=logout" csrf="true" seoTemplate="logout"}' class='ipsButton ipsButton_light ipsButton_verySmall'>{lang="sign_out"}</a> </p> </section> So you'd want to change "For working with our site you must use only working email address!" to be anything else you'd prefer, and then click the Save button. I decided to soften some of the other language, too. Here is my version of the template: <section class='ipsPad'> <br> <br> <i class='ipsType_huge fa fa-envelope'></i> <h1 class='ipsType_veryLarge'>Please Change Your Email Address</h1> <p class='ipsType_large'> Email to this address is undeliverable: <br><b>{{$mail = \IPS\Member::loggedIn()->email;}}{$mail}</b> </p> <p class='ipsType_large'> A working email address is required before you can sign in as a registered member. Please click on the button below to change to a working email address. </p> <p class='ipsType_normal'> (We never disclose your email address or send marketing materials. Your email address is needed in case we need to contact you, or in case you choose to "follow" a particular topic or forum.) </p> <hr class='ipsHr'> <p class='ipsType_normal'> <a href='{url="app=core&module=system&controller=register&do=changeEmail" seoTemplate="register"}' data-ipsDialog data-ipsDialog-size='narrow' data-ipsDialog-title='{lang="reg_change_email"}' data-ipsDialog-modal='true' class='ipsButton ipsButton_light ipsButton_verySmall'>{lang="reg_change_email"}</a> <a href='{url="app=core&module=system&controller=login&do=logout" csrf="true" seoTemplate="logout"}' class='ipsButton ipsButton_light ipsButton_verySmall'>{lang="sign_out"}</a> </p> </section>
    I am so pleased to have the ability to paste a list of bouncing email addresses into this plugin, which then prevents the member from signing in until he has clicked a Change Email button, filled in a new email address, and then clicked on a confirmation button in an email that is sent to the new email address. The way it does this is simple: the members who have the bouncing email addresses are moved into Validating status, so the confirmation email is the same one that's sent when someone first registers as a user. They appear on the usual list of Validating members that's available via the Admin Control Panel. I use a third-party smtp server for the emails that are sent by the IPS Community Suite (rather than the built-in php sender) , so I make my list of bouncing emails from logs created by that server (SMTP.com).
  3. Slimer, when you say "To users with bad emails did not send any emails" do you mean that the plugin is stopping the Invision Forums software from generating any emails to the users whose email addresses were copy-pasted into config? For example, a user with a bad email address might be "following" a particular forum and specified that he wants a single email each day with all new content in that forum from that day. Does your plugin stop that email from going out? (This would be a good thing.)
  4. Wonderful! I am happy to pay for the new plugin, and am going to buy, download and install it now. Thanks so much.
  5. Well, no, Cyboman, my response to SLimer is "not constructive for others" to the extent you're wanting SLimer to do something the plug-in wasn't written to do, such as the toasting of bagels. As MediaDigi.com said earlier, use a commercial service and drop into their form a list of all of your registered users' email addresses, which you can export from the Members search feature in the AdminCP. This is a terrifically simple and effective plug-in when a list of bad email addresses is known.
  6. We find out about bad emails from a log that is kept by SMTP.com, which is the service we use to send out our emails. (Postfix on our server connects directly with SMTP.com.) The log shows bounces that come back to SMTP.com. We are very content with assembling a list of the bad emails manually, and would not need to have a plug-in automatically handle them. We are happy to manually add the most recently bouncing emails into the list that we previously saved into the form that pops up when clicking on the Edit link for your plug-in. Thanks!
  7. Slimer, I love this plug-in! I also need a way to know when the member has changed his or her email address. (I then move the member from a "Email Needs to be Changed" group back to the Registered group. By having an "Email Needs to be Changed" group, I can be sure that I don't send a bulk email to bad email addresses, because any bulk email is sent only to the Registered group and not to the Email Needs to be Changed group.) Could you add an email to the Admin when the member has changed his or her email address, or some kind of log that the Admin could check from time to time? Either one would be so helpful. I believe another author's plug-in will nag a member via a modal pop-up until the member has changed his or her bad email address, so maybe there is some code in that plug-in that could be useful to you. I have not installed that plug-in, so I do not know if it correctly works to stop the pop-ups when the member has changed his or her bad email address. Ideally the email to the Admin or the log would show the name of the member. But just having the old email address and the new address would be good enough because the Admin could search the members and find the name of the member. I would be happy to help pay for the development of this feature. Thank you!
  8. Here are the contents of my template for the first page that the member sees, advising him or her of the need to change the email address, in case it's useful to other people ( Admin CP -> Customization -> Themes -> </> -> templates -> core -> global -> plugins -> notValidated2 ): <section class='ipsType_center ipsPad'> <br><br> <i class='ipsType_huge fa fa-envelope'></i> <h1 class='ipsType_veryLarge'>Please Change Your Email Address</h1> <p class='ipsType_large'> Email to this address is being returned as undeliverable:<br><b>{{$mail = \IPS\Member::loggedIn()->email;}}{$mail}</b> </p> <p class='ipsType_large'> In order for you to receive email notifications about topics or forums you're following, a working email address is needed. Please change your email address. </p> <hr class='ipsHr'> <p class='ipsType_normal'> <a href='{url="app=core&module=system&controller=register&do=changeEmail" seoTemplate="register"}' data-ipsDialog data-ipsDialog-size='narrow' data-ipsDialog-title='{lang="reg_change_email"}' data-ipsDialog-modal='true' class='ipsButton ipsButton_light ipsButton_verySmall'>{lang="reg_change_email"}</a> <a href='{url="app=core&module=system&controller=login&do=logout" csrf="true" seoTemplate="logout"}' class='ipsButton ipsButton_light ipsButton_verySmall'>{lang="sign_out"}</a> </p> </section>
  9. Slimer, when the member has confirmed the change in email address by clicking on the button in the confirmation email, the plug-in sends an email to the old email address -- see the attached image -- but the email is being sent to "0" instead of sending it to the old email address. Could you please change the plug-in to send the email to the old email address? Also, I was going to suggest that you eliminate that email completely -- because we know it will bounce back, since it's going to the old (bad) email address -- but it's a nice thing for the Admin to receive the email when it bounces back, because the email shows the old and new email addresses, so the Admin has a record (a kind of a log) of what's happened.
  10. Slimer, I have downloaded your plug-in -- it is working very well! Can you please tell me how I can change the Russian text into English text, on the first modal box (the one with "Change Email Address" and "Sign Out" buttons).
    Splendid. Thanks so much! One of my members asked for this functionality within a week after I upgraded to version 4.
  11. Trouble with a link here -- the "read this for important information" link on this page takes me to https://community.invisionpower.com/4docs/getting-started/upgrading-from-3x-to-40-things-to-know-r136/?_fromLogin=1 ("Upgrading from 3.x to 4.0 - Things to know") but an important link on that page ("You may wish to use our requirements checker to be sure your server supports our software before proceeding.") is broken because it's taking me to the Contact Us page at https://www.invisionpower.com/contact-us instead. Does anybody know where to find the Requirements Checker? Thanks.