imap-backup
Backup and Migrate IMAP Email Accounts
Runs with mockssource: GitHubRubyMITcommit 9431475e561b
Ruby, MIT licensed. The project labels itself: backup, imap and ruby.
imap-backup runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
imap-backup 17.0.0.rc0 runs as a CLI tool; all 1047 non-container RSpec tests pass at 99.7% line coverage; RuboCop passes 200 files with 0 offenses; the 18 feature specs requiring Docker IMAP containers are skipped as those containers are unavailable
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 56 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Ruby not installed in container — no ruby, gem, or bundle found in PATH1 minute
- fiddle gem (C extension) failed to build: missing libffi.so symlink for linking1 minute
- Install time
- 3 minutes
- Cold machine to finish
- 7 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- bundle exec bin/imap-backup version prints 'imap-backup 17.0.0.rc0'; rake spec_unit: 1016 examples 0 failures; rake spec_non_container: 1047 examples 0 failures; rubocop: 200 files 0 offenses
- Model tokens used
- 107,360
- Exact commit tested
- 9431475e561b
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `bundle exec bin/imap-backup version` → `imap-backup 17.0.0.rc0` - `bundle exec bin/imap-backup help` → lists all 25+ subcommands - `rake spec_unit` → **1016 examples, 0 failures** - `rake spec_non_container` → **1047 examples, 0 failures** - `bundle exec rubocop` → **200 files inspected, 0 offenses** - Container-dependent integration tests (backup/copy/mirror/restore against real IMAP) require Dock… exec /bin/sh -lc 'echo "install_minutes: start at 05:19:30, bundle done at 05:22:05"' in /work/repo succeeded in 0ms: install_minutes: start at 05:19:30, bundle done at 05:22:05 tokens used 107,360
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 3 minutes, faster than the median of the 18 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Of the 19 backup projects Argusic has installed and timed, imap-backup was the 4th fastest to reach a running state, and 13 of 19 reached one at all.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.07 | |
| Argusic Runner | 1/3 | Did not run | 20.00 | 0.16 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/imap-backup)Questions
- Does imap-backup run?
- imap-backup runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 3 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test imap-backup?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 9431475e561b. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test imap-backup?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does imap-backup take to install?
- 3 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does imap-backup need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing imap-backup?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does imap-backup compare with the alternatives?
- Of the 19 backup projects Argusic has installed and timed, imap-backup was the 4th fastest to reach a running state, and 13 of 19 reached one at all.
- Where is the evidence for imap-backup?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.