A salesperson deletes the thread that proves the delivery, or ransomware renames every mailbox. We keep a separate journaled copy of all mail, retained for seven years and searchable in seconds, with access locked away from the people who send it.
Journal copy, not a mailbox export
Seven years, searchable
Separate role for audits
If any of these has already happened once, the archive is overdue.
✕A client disputes a quotation and the thread is gone, deleted by someone who has left the company.
✕Ransomware encrypted a shared drive, and nobody can say what was agreed by email that week.
✕An auditor asks for 2019 correspondence and IT starts opening individual Outlook files one by one.
✕You have a nightly backup, but restoring one mailbox means restoring the whole server.
What gets archived, and how
✓Journaling captures every inbound and outbound message across all mailboxes, including attachments.
✓A store separate from live mail: deleting a mail from Outlook does not touch the archived copy.
✓Search by sender, recipient, date, subject or attachment name, then export a case as PDF or EML.
✓Seven years by default, with legal hold on a named matter so nothing expires mid-dispute.
✓Access separation: the archive role is not the mailbox admin, and every search is written to a log.
✓Encrypted at rest with an offsite copy and a documented restore test — a real thread, not a screenshot.
What we need: admin access to the mail platform (or a capture address we may add), the retention your auditor expects, and one person to sign off the first restore test.
What an archive costs, and what a backup does not do
Cloud archives in the region run per user per month; a server licence is a one-off plus a Windows host. Ours is a flat yearly price.
Service
Typical arrangement
With SifuMail
15-user cloud archive
✕RM 1,300–2,600 / year
✓RM 900 / year, Nett
Retention
✕as long as the mailbox exists
✓seven years, deletion-proof
Storage
✕per-user quota, mixed with live mail
✓pooled, held apart from mailboxes
Recovering one thread
✕restore the whole mailbox backup
✓search and export in minutes
Who can read it
✕whoever holds the admin password
✓separate audit role, logged
Nett — No SST charged
Policy, capture, proof
1
Policy in 30 minutes
We list the mailboxes, the retention you must meet and who may search; you approve that policy in writing before anything is deployed.
2
Switch capture on
A separate store is built, journaling starts, and a week of real mail is captured before anyone depends on it.
3
Prove a restore, then pay
We restore one real thread you choose, show the search log, and the invoice follows that acceptance.
Ask for a restore, not a demo
A dashboard proves nothing. Ask us to restore a thread from a date you name, in front of you, and to show who searched the archive last month. If that cannot be done inside your own instance, the retention promise is decoration.
A host backup snapshots a whole server, and it usually sits in the same account you are trying to protect against. Journaling captures each message as it passes, into a store with its own credentials, so ransomware or a deleted mailbox cannot reach it.
No. Capture happens at the mail server, not on their devices. The archive is a second copy they never see unless you grant someone the audit role — and granting it is logged.
Malaysian tax and company law expect seven years of records, which is why seven is our default. If a dispute or investigation is live, legal hold overrides the policy so nothing expires while it matters.
Their access is removed the same day and the mailbox is kept, not deleted, until you decide. The journal copy stays searchable by the people you nominate, including mail they already deleted themselves.
Get a written retention policy, not a brochure
Send your mailbox count and the retention your auditor expects. You get the yearly price, the one-time setup and a restore test date — before anything is deployed.
Reply within one business day (Mon–Fri, 9am–6pm MYT).