Drupal module tutorial (7.x)

This content has been moved to acquia.com.

Mollom Support now powered by Acquia

Just over two years ago this month, Mollom announced that Acquia acquired Mollom. Since then, Mollom has become integrated into Acquia, including our support, which is now provided by Acquia’s global support organization.

Reflecting this change, and as Mollom looks to streamline backend administrative functions, we are excited to merge our externally-facing Support systems into Acquia’s. What does this mean for Mollom customers? Not much will change. Customers will receive the same great support from the same great team. One thing that is changing: as of Thursday, 21 August 2014, any new Support requests filed through Mollom’s online form will receive email responses from “Acquia Support.” Also, the creation of new tickets via email will not be supported anymore. If you want to submit a ticket, use our online form.

We recently passed an exciting milestone at Mollom: over 6 billion spam messages blocked. We’re looking forward to providing great support to our customers as we block the next 6 billion!

For more information about submitting support requests and about other service offerings, be sure to check out this Mollom Support resource.

Involving your community with moderation

Mollom performs best when it can learn from others. Up until now, Mollom has only been able to learn from content moderators who report content as spam, profanity, or other unwanted designations. This places the responsibility of your site's content quality and Mollom's education on a relatively small number of site administrators who are responsible for review of the content deemed acceptable for display on their site.

Now Mollom Drupal users can enable our "Flag as Inappropriate" feature to allow other user roles to flag content that may be objectionable on your site. Your entire community can be more involved in the process of keeping your site quality high while at the same time providing feedback to Mollom to enable it to become a smarter spam-fighter.

Read more

Introducing the new Mollom Java client library

I'm excited to announce the launch of the newest version of the Mollom Java client library. This latest version is a complete rewrite of the library with a modernized architecture, making it even easier to integrate with Mollom.

The library is open sourced under the MIT license. All usage documentation and source code is stored on https://github.com/Mollom/MollomJava. Pre-built JARs are also available on GitHub. For usage guides, please refer to the README.md within the library.
For the maven users out there, we also host a maven public repository that you can use to pull the client library:

    <name>Mollom Maven Repository</name>

If you have any questions, comments or issues with the latest version of the Java client library, please let me know in the comments. Of course, being an open sourced project, also feel free to contribute back if there are any improvements that you would like to add.

Introducing new expected languages feature

LanguagesI'm excited to announce the latest feature to further improve the Mollom's ability to protect your sites from spam and unwanted content: Expected Languages.
As you may already know, Mollom has the ability detect the language of all content for classification, with over 99% precision for over 53 languages. With the new Expected Languages feature, you can now specify the subset of languages that you expect on each of your sites. Mollom will penalize and filter out posts in all other languages, keeping your site cleaner, effortlessly.

To enable the feature, navigate to the "Site Manager" on mollom.com by clicking "Manage sites" from the top bar. From there, click "Edit site" for any site that you would like to enable the Expected Languages feature on. Under the Expected Languages section, you can choose any language you would like to accept on your site from the drop down of supported languages. You're also able to choose multiple languages if you have a multilingual site. Leaving this section empty will revert to the original default behavior of accepting all languages. Once you are done, click "Update site" and your changes will be immediately effective.

This feature has been in testing for the past few months and has proven extremely useful to the our beta testers. We are now releasing this feature to the public for all of our customers to use. Please let us know what you think about this new feature in the comments.