SpamExperts

Professional Email Security Solution

SpamExperts provides professional email security in the cloud or on premises, with accuracy, efficiency and user-friendliness. The two key services include incoming filtering for spam/viruses and outgoing filtering for IP reputation. You remain in full control of your solutions, while SpamExperts takes care of managing email security issues, offering complete peace of mind through redundant and fully managed email security systems, all available in the cloud. With the implementation of SpamExperts you save costs that may occur due to spam attacks, viruses or malware.

Resell SpamExperts - Become a LuxCloud partner

LuxCloud offers a one-stop shop for white label cloud business applications. More info.

Key features

Immediate detection of new spam outbreaks

Secure your network from spam, virus, phishing and malware attacks.

Increased email continuity

Add redundancy and continuity to your email delivery process.

Periodic spam reports

Status updates through a comprehensive log-search tool with advanced quarantine options.

Avoid being blacklisted

Ensure your network doesn’t send out spam without your knowledge.

Improved employee productivity

Employees don’t have to deal with daily spam messages anymore.

Free with Hosted365, Exchange 2013 and Open-Xchange

When you resell Hosted365, Exchange 2013 and Open-Xchange, SpamExperts is included.

Additional information

SpamExperts Product Sheet

Generate Periodic Protection Reports

For each domain (or for specific recipients at a domain) a daily or weekly report can be generated and is delivered via email. The report can be sent either as a PDF attachment or as inline HTML. The PDF report outlines a summary of the spam and viruses that the filtering service has protected the domain (or address) from receiving and also includes information about the total volume of mail processed for the chosen domain.

To generate the report, you need to:

  • Go to SpamExperts management console
  • Access ‘Periodic Domain Report’ or ‘Periodic User Report’
  • Select the necessary options to activate the report

Periodic user-based protection reports

With this option you can enable periodic protection reports based on users. You can add users, either individually or via the .csv upload function for multiple users.

When this is set, the individual email users of a domain will receive daily or weekly reports with their own blocked spam mails, they will also be able to release any messages that are incorrectly blocked messages directly from the email.

The PDF report outlines a summary of the spam and viruses that the filtering service has protected the domain (or address) from receiving, and also includes information about the total volume of mail processed for the said user.

The report also includes a detailed table (for auditing purposes) of messages that were rejected but not quarantined. A similar table is also included of messages that were quarantined, including links to release each message directly.

The option “Automatically activate for all recipient” means that when spam is delivered to new users not yet known to our systems, they will automatically be added to the Periodic User Report.

Search the FAQs

Use the form below to search the FAQs


What do the SpamExperts Sender/Recipient Whitelist/Blacklist terms mean?

How can I control spam?

How can I change the SpamExperts Quarantine Threshold level?

How does SpamExperts check email fields for invalid characters?

What is SpamExperts Periodic Protection report?

What is SpamExperts periodic user-based protection report?

How to release emails that have been detected as spam?

What is the correct MX record input with activated SpamExperts?

A spam message got through SpamExperts filter. What can be done to prevent this in the future?

How can I check outgoing SpamExperts logs?

I want to add addresses to whitelist/blacklist, but I can only login in SpamExperts as an e-mail user. Is there a away of access SE on a domain level?

I've received an email that should have been blocked but was accepted by SE. Why this happened and how can I prevent it from happening again?