Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-24440

Forwarding from CLO to dm-staff not working

    XMLWordPrintable

    Details

    • Type: Story
    • Status: To Do
    • Resolution: Unresolved
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      My understanding is that posting in the “DM Team” section of community.lsst.org ought to result in the post being forwarded to dm-staff@lists.lsst.org.

      But I made this post the other day, and it hasn't made it to the mailing list (and doesn't appear in the archive).

      I don't actually know if this is a SQuaRE issue, an IT issue, or something different. Can you advise please? Thanks!

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          jsick Jonathan Sick added a comment -

          I checked our Mandrill account and I don't see any message going out to lists.lsst.org. In fact, I don't think we've had a mailbox email since February? It'd have to check more carefully because our frequency of new posts is slightly low, but I do think the Community Mailbot service is down.

          Normally I'd say we'd just restart the service, but I'm not so sure about that. The Mailbot dates back to 2015 and it was written before I really knew how to write services. For instance, I'm not totally confident in its ability to be started back up without sending extra emails.

          I think we should port Mailbot over to Kubernetes and drive it from Discourse's webhook feature. That would get the service off its old EC2 instance, bring it in line with how we're building services so its easier for everyone to maintain, configure (e.g. add new mail forwards), and monitor, and also make it more real-time (no more polling for new posts).

          What do you say to this, Frossie Economou?

          Show
          jsick Jonathan Sick added a comment - I checked our Mandrill account and I don't see any message going out to lists.lsst.org. In fact, I don't think we've had a mailbox email since February? It'd have to check more carefully because our frequency of new posts is slightly low, but I do think the Community Mailbot service is down. Normally I'd say we'd just restart the service, but I'm not so sure about that. The Mailbot dates back to 2015 and it was written before I really knew how to write services. For instance, I'm not totally confident in its ability to be started back up without sending extra emails. I think we should port Mailbot over to Kubernetes and drive it from Discourse's webhook feature. That would get the service off its old EC2 instance, bring it in line with how we're building services so its easier for everyone to maintain, configure (e.g. add new mail forwards), and monitor, and also make it more real-time (no more polling for new posts). What do you say to this, Frossie Economou ?
          Hide
          Permalink
          jsick Jonathan Sick added a comment -

          After talking it over, we'll try to revive the existing service, using a test config to make sure there aren't any start-up issues.

          Show
          jsick Jonathan Sick added a comment - After talking it over, we'll try to revive the existing service, using a test config to make sure there aren't any start-up issues.

            People

            Assignee:
            jsick Jonathan Sick
            Reporter:
            swinbank John Swinbank
            Watchers:
            Jonathan Sick
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:

                Jenkins

                No builds found.