solved Is it possible to use the Mailgun list of "Bounces and Failures" to move unused accounts offline, or out?

With Kickbox testing at 20 mails per day, I can set up a "Fail action" that moves accounts into an offline quota, and from there I can eventually delete them (one by one).

Meanwhile, Mailgun has produced a comprehensive list of member email "Bounces and Failures", but no "Fail action" setting is apparent to me in the ACP.

I have about 3000 accounts that have invalid email addresses, according to Mailgun. Most have not yet been picked up by Kickbox.

Ideally, the Bounces and Failures list would be bundled together with the "Last login" information from each account, in one table, alongside a delete button or selection box that can then be used to carry out actions such as "Transfer selected accounts to X quota" or "Delete selected accounts".

That would allow for convenient removal of inactive accounts that are still visible when visitors to the site search the member profiles.


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
updated by @researchcooperative: 11/11/18 03:49:37PM

That's a real nice idea that would be very useful to many.

I would add one addition to it- to also include a column showing the disk space that account uses on your site... the same disk space info we can currently see in our 'Profile Browser'. That way, we could investigate before deleting a member that had contributed a lot of valuable site content that we might not want to inadvertently remove even though they are no longer active. If the disk space for that member is 0 kb, we know we'll not be losing any good site content when deleting them.

As things are currently set up, it's annoying and time consuming to 1) Check the quota we've setup to automatically isolate kickbox email 'fails' into a to-be-deleted quota, then 2) have to go to the User Browser to see the last log in date, and 3) go to the Profile Browser (or the profile page itself) to check if the member has a lot of site content I might not want to delete.... before actually deleting the account. Steps 2 and 3 require copy/paste search for the member in each profile and user Browser.
I've been following all these steps for years now when I periodically go check my 'kickbox fail' Quota.


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015

Based on my experience, deleting users when their email bounces is a bad idea - email bounces for all sorts of reasons (mailbox fill, temporary DNS issues, SMTP server configuration issues, etc.) - deleting a user "automatically" is almost always going to cause an issue at some point.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

I don't think it's being proposed that the deletion would be automatic. Rather, it's being suggested that the further info (last login, site content/data amount) be shown in the (bounced email) quota browser together with a shift-select delete box where one could delete a swath of users in one go if we could see they were long gone and had never contributed anything on the site. The delete function should also have the option of deleting both their user account and any profiles associated with them, of course.

PJ brings up a very good enhancement that I've wished for as well. It would be great to have the 'bounced-email' members appear in a quota browser that shows not only their last date of login, but also their site data/content amount- these two pieces of info alongside each user in that quota browser would be perfect to check before deleting them. It's highly unlikely that it could be a loss to delete any member who hadn't logged in for several years and had never contributed any site content or posted anything at all. Not saying auto-delete... just to add info so we could better evaluate a deletion first, and then shift-select more than one at a time based on the various crucial info we can see in the browser for that quota.
The kickbox feature of dumping members into a specified quota if their emails bounce is really valuable. To make it three times more useful, adding these other two critical bits of info when viewing that quota's members would be a terrific tool in first verifying then removing deadwood.... without having to go to like three different quota browsers to check this info on each member before deleting. Which is what I've been having to do for a couple years now.


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015

I second everything Strumelia has construed!


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)

Right now in the user browser you can already sort by last login - I think the easiest thing to do would just add a visual indicator to let you know that the user's email is bounced or bad - you can then delete them right there if you want. This also let's you see their profile so you can see what their content is, etc.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Thinking about this some more it's not quite as straight forward as it may seem. Imagine that an email is sent to a user account, and it bounces due to a temporary issue (mailbox full, etc.). The system them "tags" that account as being undeliverable. Due to the way Mailgun works, it will not try to redeliver to that address. So you then come along and see that it is undeliverable and delete the account, even though the situation was temporary.

So my recommendation here would be to NOT look at email bounces, but rather look at last login - if your goal is to prune inactivate accounts, their bounce state isn't really going to do that for you. We have quite a number of users (hosted users even!) who have had their email bouncing for months and yet they are still active.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Those are some good points Brian. But your 'active' users with bounced emails would still have recent login dates, so perhaps a browser where we can see two or three of these factors all at once would be the safest and most useful way to delete defunct members without having to jump to three diff places to check on a member's status before deciding to delete them.


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015

Of course - this is why I mentioned above that anything added would be added in the User Browser - there's no plans to duplicate functionality in multiple places.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

The next release of the User module has some updates that should help here:

- There's a new setup that allows other modules to present information directly in the user browser
- The MailGun and Kickbox modules have been updated to show you if an email address is bouncing, undeliverable, etc. right in the user browser
- the amount of disk space a profile is using also now shows in the User browser (as well as still showing in the profile browser)

Hopefully this gives you a bit more info to make decisions on when browsing your user accounts. This is in testing right now and will be in the next round of updates.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Um. I can see the column with user logins, but the order is according to signup ID at left. I don't see any obvious "column sort" toggle... ??


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)

PJ, you just click the column title "Last Log in" to resort by that date. Click it again to resort back and forth between most recent login members and most long-ago member login dates.


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015

These added User Browser features/info are TERRIFIC. They look good. Thank you Brian SO much for taking the trouble to add these things for us, it will really facilitate the process of pruning long-defunct inactive members.
YAAAAAAAY!
And thank you PJ for this thread- it's something I've thought would be useful as well, for a long time.


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015
updated by @strumelia: 08/08/18 05:41:19PM

Yikes! A lot of good changes to learn about with the latest module updates.

Thanks all.


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)

True! In fact I printed out the changelog for the User Accounts Module right before updating, so I could look through it carefully after the update concerning the new features I should check out. :D


--
...just another satisfied Jamroom customer.
Migrated from Ning to Jamroom June 2015