Mail2CLOUD

Mail2CLOUD is an automated email backup service. It connects to your mailbox via IMAP or OAuth, downloads your emails, and uploads them directly to your own cloud storage or FTP server, with optional encryption. We never store your data — it goes straight to your account. You set it up once and it works continuously.

• 100% rule-based — no AI reads your emails
• Double encryption — files encrypted at rest + optional AES-256 ZIP password
• Zero-disk-touch — compression happens in memory, nothing decrypted on disk
• Progressive — after initial backup, only new emails are processed
• 12 cloud destinations — Google Drive, Dropbox, OneDrive, S3, FTP, SFTP, and more

The Mail2CLOUD dashboard at BOTS4.me/bots has the same layout as all BOTS4.me products: three panels.

Additionally, the Settings tab (gear icon) is where you connect email accounts and cloud accounts (Access Manager). The backup password, “Back up emails from the last” and “Keep deleted emails for” are set in the Mail2CLOUD panel of the Control tab.

The Logs tab shows real-time activity: what Mail2CLOUD did on each run, any errors, and operation results.

Toggle features on/off from the Features panel. Some features require a paid tier (shown as locked for free/basic users).

Folder Processing Order

Mail2CLOUD processes smaller folders first. This ensures small folders (like “Personal” or “Projects”) get fully backed up before large folders (like INBOX) consume the per-run email limit. Trash, Junk and Spam folders and the AutoSPAM working folders are skipped; Sent and Drafts are backed up.

Progressive Backup

After the initial full backup, Mail2CLOUD tracks what’s already been synced via manifests (internal state files). On subsequent runs, already-synced folders are skipped entirely. Only new and changed emails are processed — saving time and bandwidth.

Email Age Filtering

The “Back up emails from the last” setting (default 3 years; your plan can shorten it) determines how far back to look. Only emails within this window are backed up, and when an email becomes older than it, its backup copy is removed — the email itself stays in your mailbox. This prevents backing up ancient emails you no longer need while keeping your recent history safe.

Per-Run Limits

Each run processes a limited batch of emails across all folders, within your plan limits. This prevents overloading your email server or cloud storage. Multiple runs will progressively back up your entire mailbox.

File Structure

Each backed-up email becomes a folder (or compressed ZIP) containing the email text (HTML), metadata (JSON), raw source, and all attachments. The folder structure in cloud mirrors your mailbox folders.

Your backup follows your mailbox and your settings: copies are removed when “Back up emails from the last” or “Keep deleted emails for” says so. The Monthly archive (Family plan and above, Backup mode, off until you switch it on) keeps a second copy that Mail2CLOUD never removes: once a month every email backed up since the last archive gets a copy in a month folder on each of your cloud destinations. It runs on the first run of each month where the backup has nothing left to do (the first time on the day you switch it on); a missed day is caught up on the next run, and a month is never archived twice. Each archive copy (one per email and destination) counts like a backed-up email against your plan limits and credits.

Where It Is

Next to your live backup, in the same cloud folder: Archive/YYYY-MM/, then the same mailbox folder and mail folders as your backup — for example Archive/2026-10/john_example_com/INBOX/. Each email is stored as in your backup: a folder with message.eml and the attachments, or one ZIP file. The archive stays until you delete it yourself.

Only New Emails Each Month

The archive is incremental: a month folder holds only the emails that are not in an earlier month folder yet, so nothing is stored twice. Each mailbox’s month folder also gets an index file, M2C_archive_YYYY-MM.json, once that month’s archive is complete: it lists every email in the mailbox’s backup at that time and the month folder that holds its copy. With a Backup Password the index is stored as M2C_archive_YYYY-MM.json.zip, encrypted with the same password.

Restoring From the Archive

At BOTS4.me/bots → Mail2CLOUD → Restore emails, choose Restore from: Archive YYYY-MM instead of Live backup. You get your mailbox as it was backed up that month — also emails the live backup no longer keeps — and the restore works as usual: only the emails missing from your mailbox, into the RESTORED folder, within your plan’s daily restore limit. The choice appears once a month’s archive is complete and offers the last 12 monthly archives; archives you made stay restorable after a plan change.

Without the dashboard, use a mail client that can import .eml files into an IMAP mailbox: download a month folder and import its .eml files folder by folder into the matching mailbox folder. Start with the oldest month and work forward, because each month holds only that month’s new emails.

If your emails are ZIP files (Compression on, or a Backup Password set), unzip each one first — with the backup password it was made with, if one was set (any ZIP tool that supports AES-256) — then import the message.eml inside.

Not in any archive: an email whose backup copy was removed — by “Keep deleted emails for” or “Back up emails from the last” — before the next monthly archive ran.

• At-rest encryption: All files in the temporary buffer are encrypted using system-level encryption. No plaintext email data touches disk.
• AES-256 ZIP encryption: When you set a Backup Password, emails are compressed into AES-256 encrypted ZIP archives. Standard WinZip AES — compatible with any ZIP tool.
• Zero-disk-touch compression: Compression happens entirely in memory (BytesIO). The encrypted ZIP is written directly — no intermediate unencrypted files.
• Buffer cleanup: After successful upload to ALL cloud destinations, the local buffer is immediately deleted. If any upload fails, files are retained for retry.
• Your backups stay yours: they go directly to your own cloud account or FTP server. We keep no copy, and nobody at BOTS4.me reads or analyzes your email content.

The Logs tab shows what Mail2CLOUD did on each run. Common messages:

Mail2CLOUD does not email you after every backup run. Each run writes one row to the bot log — visible in the Logs tab of the dashboard and as a message in the LOGS folder inside your mailbox.

Instead you get one summary email — once a week by default (Monday morning), or once a day or once a month. Choose it under Summary email in the Mail2CLOUD settings; switch it off with the Email Reports toggle. It goes to your account email and to the Management emails from the General Dashboard. The summary shows:

• How much is backed up: for every folder, the emails in your mailbox, how many of them are backed up and the percentage. Folders that are not complete yet are listed first.
• This period: emails backed up, errors, and the time of the last backup
• Where your backup goes: every destination and whether it works, is catching up or needs reconnecting
• Your plan and limits: emails backed up today and this month against your plan’s limits, how long backups are kept, the restore limit, and on how many days a limit paused the backup
• Emails that could not be backed up: each one with its folder and the reason

Sync and restore still send their own report when they run, and problems (a destination that stops working, backups missing from your cloud) are emailed once when they happen.

• Where: every mailbox gets a LOGS folder inside the bot’s own folder, for example _Mail2ERP/LOGS. Each bot keeps its own.
• What: the same rows as the Logs tab, one message per row. Nothing is sent by email — the rows are written straight into the folder.
• Unread means it needs you: only rows that need your decision arrive unread. All other rows, warnings included, arrive already read.
• Housekeeping: the folder keeps the latest 100 rows for up to 30 days. The full log stays in your dashboard.
• Safe by design: genuine log messages exist only inside LOGS folders, never in your inbox, and the confirm page never asks for a password.
• Switch: Logs in your mailbox, in the bot’s feature list on the Control tab. On by default from the Personal plan.