[OSGeo] #3489: discourse mail being skipped

#3489: discourse mail being skipped
--------------------------------+---------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: new
Priority: normal | Milestone: 2025 (robe)
Component: SysAdmin/Discourse | Keywords:
--------------------------------+---------------------------
I looked at the discourse mail log, and it appears a lot of email
addresses are being skipped for email send. I think this is because our
black list issue of last week, cause discourse is set to start skipping if
it hits a bounce threshold and then it schedules a time to take off the
skipped list.

Most have skipped set to like January 6th or later.
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3489: discourse mail being skipped
--------------------------------+----------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: closed
Priority: normal | Milestone: 2025 (robe)
Component: SysAdmin/Discourse | Resolution: fixed
Keywords: |
--------------------------------+----------------------------
Changes (by robe):

* resolution: => fixed
* status: new => closed

Comment:

I've reset the bounce count back to 0 so emails should start going thru
again.

I also added these to instructions on
Making sure you're not a bot!

The date parameter I didn't want to reset any harder bounces but probably
wasn't necessary as anyone being
skipped because of bouncing should quickly get back on if email is still
bouncing.
{{{
cd /var/discourse
./launcher enter import
su postgres
psql
\c discourse
  UPDATE user_stats SET bounce_score = 0, reset_bounce_score_after = NULL
WHERE bounce_score > 0 AND reset_bounce_score_after BETWEEN '2025-12-18'
AND '2026-01-10';
}}}
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.

#3489: discourse mail being skipped
--------------------------------+----------------------------
Reporter: robe | Owner: sac-tickets@…
     Type: task | Status: closed
Priority: normal | Milestone: 2025 (robe)
Component: SysAdmin/Discourse | Resolution: fixed
Keywords: |
--------------------------------+----------------------------
Comment (by robe):

Oops that didn't seem to work, must be some caching in the app.

Proper way to do it is:
Reset a User's Bounce Score - Site Management - Discourse Meta

-- showed 45updated though I think when I did with psql, I got over 100 so
maybe the other did do something
{{{
#our container is called import
cd /var/discourse
./launcher enter import
rails c
UserStat
   .where('bounce_score > 0' )
   .update_all(bounce_score: 0.0, reset_bounce_score_after: nil)
exit
}}}
--
Ticket URL: <Making sure you're not a bot!;
OSGeo <Gter - OSGeo;
OSGeo committee and general foundation issue tracker.