Recent Spam

Hello Progress Community, 

 

In the early morning of August 9, we became the target of a spambot attack causing many of you to receive hundreds of emails. We understand the inconvenience and potential confusion this may have caused and deeply regret any disruption.  

 

At this time, there have been no reports of any direct operational impact to our customers or Community members nor has any private information been accessed. Please be assured that we take the security of our customers and Community seriously and are working diligently to resolve the issue.  

 

In the interim, we recommend Community members take the following actions: 

  • Please take steps to temporarily turn off notifications until further notice. (See the screenshots below this text)
  • If you have posted in the last 24 hours, please review to make sure your post is still available or please re-post.  
  • If you continue to see any strange or suspicious activity, please feel free to tag me in concerning posts by typing @Nichol Goldstein in a comment or email the Community Team at community@progress.com. 

 

How to change your notifications:

 

  • In a forum, go here:

Forum example 

  • In a group, go here:

 

Group Example 

 

Thank you for your understanding and patience. 

 

Nichol & the Community Team 

 


    • Nichol Goldstein (Progress)

      Thanks, Gilles!

       

      It seems this is happening to several different Salesforce community sites, so we're not alone in our suffering. Still, we're on it and we're doing our best to find a way to put a stop to it.

      • Mike Rockwell (Progress Software)

        I wonder if a real person is setting up accounts, and then using them for spam bots. Or maybe we need to make the registration process a little tougher for bots to register. Of course, wouldn't matter if is is stemming from something going on with Salesforce itself.

      • Nichol Goldstein (Progress)

        I promise you, we are working this puppy from every angle we can think of. At least we've trapped it on the back end for the time being. Let's hope we can keep it that way while we continue to look for more long term solutions.