Managed email-threat protection for Malaysian SMEs

Email Managed Services, powered by MailScan

EMS screens every message for malware, ransomware, phishing, BEC and spam — then posts a plain-language alert to your WhatsApp or Telegram group the moment a threat is caught. You keep your mail server; we do the running, the tuning and the watching.

What every subscription includes

One core protection covers every delivery model — the difference is how much control you keep over your mail and your data.

75 antivirus engines
Every suspicious attachment is validated by signature, heuristic and cloud lookup across 75 engines.
Self-learning classifiers
Bayesian spam and phishing filters trained on live traffic, with neural-network weight optimisation.
Sender reputation
Per-customer allow and block lists; hosted customers also draw on pooled global blacklists.
Reversible neutralisation
Malicious mail goes to Quarantine, suspected spam to Junk. Logged, auditable, never silently deleted.
Chat-native alerting
Threat type, what it does and what to do — posted to your WhatsApp or Telegram group, target within 5 minutes.
Managed operations
Monitored 24/7, with a monthly executive report in English and Bahasa Malaysia.

Two delivery models

Both carry the same core protection. You choose by how much control you keep over your mail and your data — and Model 1 adds one thing Model 2 cannot: rules built for you alone.

Model 1 — On-PremiseModel 2 — Hosted
Where mail goesStays in your infrastructureOur Malaysian data centre, under a data-processing agreement
DeploymentOur engine on a small customer VM (2 vCPU / 2 GB); connects over IMAP — no MX change, no downtimeCustomer sets up their own account in our system
Works withAny mail server — Exchange, Postfix, cPanel, ISP-hosted IMAPAny domain with controllable MX records
IntelligenceYour lists + our base packFull pooled cross-customer blocklists and tuned rules
Custom rulesYes — written uniquely for your business, small customisation feeNo — standard rule set only
AI layerOptional local LLM node on a customer GPU machineRuns in our environment
Go-live≤2 working days from VM provisioning< 1 hr from setup time
Best forProfessional firms, factories, GLCs — data-sensitive businessSMEs wanting zero infrastructure effort

Can't decide? Run the 30-day pilot on Model 2 — it needs no hardware, and if residency concerns surface you can move to Model 1 at no penalty.

Model 1 only

Custom rules, built for your business

Because the engine runs on your own box, we can write scanning rules that fit how your business actually receives mail. Not available on Model 2 — Hosted, which runs a standard rule set shared across tenants.

Worked example
A supplier e-mails an updated bank account, or the message comes from a look-alike domain.
Payment-change request from [supplier]. Bank details differ from the ones we have on file. Do not transfer — call them on the number in your records first.

EMS trips the rule, holds the message out of the inbox, and posts that alert to your group.

Who uses them
Each rule is built for one customer, from that customer's own traffic.
  • Accounting and legal firms — flag any mail from a client domain carrying a new bank account or payment instruction.
  • Manufacturing and trading SMEs — accept invoices only from known vendor domains; quarantine attachments from anyone else.
  • Clinics, schools and associations — alert when a mailbox sends a patient or student list to an external address.
  • MSPs — per-client rules that mirror each client's own vendors and finance contacts.

Our team writes each rule with you, tailored to your mail pattern. A small customisation fee applies. New rules are typically live within 5 working days, and urgent rules same day through your alert group. Every rule change is logged, auditable and reversible.

Compliance and trust

Designed so PDPA obligations are engineerable, not argued around.

Data residency by design
On Model 1, email content never leaves the customer environment; only SHA-256 attachment fingerprints query reputation services.
DPO support
EMS produces the evidence trail — who, what, verdict, action, timestamp — that makes PDPA breach notification practical to fulfil.
In-country hosting
On Model 2, cross-border transfer concerns (PDPA s.129) are engineered out, not argued around.
Transparency
Every automated action is logged and reversible.

Who it's for

Accounting, legal and secretarial firms
High BEC exposure, high confidentiality duty
Manufacturing and trading SMEs
On self-hosted Exchange or cPanel — invoice-fraud targets
Clinics, private schools and associations
PDPA-covered data, lean IT
MSPs and IT service providers
White-label EMS as an add-on for their client base

Start with a 30-day pilot

Commission the pilot on one live domain — we suggest your most-used one. At pilot end you get an incident report, alert samples and a fixed quote. No commitment.