Self-hosted email fetcher: IMAP (ISP mailbox) → Gmail API import. Replaces Gmail’s deprecated POP3 fetch.

• Polls an ISP mailbox via IMAPS (port 993).
• Imports messages with Gmail API (not SMTP); applies a Gmail label, preserves headers and date.
• Deletes from ISP only after Gmail confirms import. Idempotent (UID + message hash).

Requirements: Python 3.11+, IMAP credentials, Google Cloud project with Gmail API and OAuth2 (Web application).

You use a computer with a browser (to get the token) and a Debian server (Odroid, Raspberry Pi, etc.) where the app runs. Follow the steps in order.

Step 1. Get credentials.json from Google Cloud

1. Go to Google Cloud Console → create or select a project.
2. APIs & Services → Library → search “Gmail API” → Enable.
3. OAuth consent screen: External → add app name → Scopes → add https://www.googleapis.com/auth/gmail.modify → Test users → add the Gmail address that will receive the imported mail.
4. Credentials → Create credentials → OAuth client ID → Application type Web application.
5. Authorized redirect URIs → add http://127.0.0.1:8765/auth/gmail/callback and http://localhost:8765/auth/gmail/callback.
6. Create → download the JSON. Save it as credentials.json in a folder (e.g. Desktop or ~/fetch2gmail-auth).

Step 2. Install Python 3.11+ and pipx

• Windows: Install Python 3.11+ (check “Add Python to PATH”). Open Command Prompt or PowerShell: pip install pipx then pipx ensurepath. Close and reopen the terminal.
• Linux: sudo apt install pipx then pipx ensurepath. Reopen the terminal (or run source ~/.bashrc) so ~/.local/bin is on PATH.

Step 3. Install fetch2gmail

pipx install fetch2gmail

Step 4. Get the token

In the same folder where credentials.json is, run:

fetch2gmail auth

A browser opens. Sign in with the Gmail account that will receive the imported mail and click Allow. token.json is saved in that folder. Press Ctrl+C to stop the auth server.

Step 5. Copy these two files to the server

Copy credentials.json and token.json to your Debian server. You will put them in the app data directory in the next section.

Step 6. Create the data directory and add the files

Pick one directory for all app files (e.g. /opt/fetch2gmail or /home/odroid/fetch2gmail). Create it and put credentials.json and token.json there:

sudo mkdir -p /opt/fetch2gmail
sudo chown "$USER" /opt/fetch2gmail
# Copy credentials.json and token.json into /opt/fetch2gmail (from step 5)

Use the same path in the steps below (replace /opt/fetch2gmail and the username if you use something else).

Step 7. Install pipx and fetch2gmail on the server

Run these from any directory (you do not need to be in /opt/fetch2gmail):

sudo apt install pipx
pipx ensurepath
# Log out and back in (or source ~/.bashrc) so ~/.local/bin is on PATH
pipx install fetch2gmail

The app will find your token and files in /opt/fetch2gmail because in step 9 you install a single systemd service that sets WorkingDirectory and FETCH2GMAIL_CONFIG to that directory. If you set the UI password from the CLI (step 8), cd into /opt/fetch2gmail first so .ui_auth is created there.

Step 8. Set the UI username and password

The web UI is protected by a username and password (stored as a hash in .ui_auth). You can set it from the CLI or from the UI:

• From the CLI: Run cd /opt/fetch2gmail then fetch2gmail set-ui-password and enter username and password when prompted.
• From the UI: If .ui_auth does not exist yet, open the web UI and you will see the Set UI password wizard. Set a username and password there; after that, the UI will require them (HTTP Basic Auth). You cannot create config or use the app until a UI password is set.

Step 9. Install and enable the systemd service (one service: web UI + background fetch)

One service runs the web UI and polls your ISP mailbox on a schedule (every 5 minutes by default). Generate the unit file and install it:

fetch2gmail install-service --user YOUR_USER --dir /opt/fetch2gmail -o /tmp/fetch2gmail.service
sudo mv /tmp/fetch2gmail.service /etc/systemd/system/fetch2gmail.service
sudo systemctl daemon-reload
sudo systemctl enable fetch2gmail
sudo systemctl start fetch2gmail

Replace YOUR_USER with the user that owns /opt/fetch2gmail (e.g. odroid). Replace /opt/fetch2gmail if you used a different data directory. The command finds fetch2gmail on your PATH; if it is elsewhere, add --exec /path/to/fetch2gmail.

Alternatively, print the unit file and pipe it into place:

fetch2gmail install-service --user YOUR_USER --dir /opt/fetch2gmail | sudo tee /etc/systemd/system/fetch2gmail.service > /dev/null
sudo systemctl daemon-reload
sudo systemctl enable fetch2gmail
sudo systemctl start fetch2gmail

Step 10. Configure ISP mail in the web UI

Open http://<server-ip>:8765 in your browser (e.g. http://192.168.1.10:8765). Log in with the UI username and password from step 8. You will see the initial setup form. Enter your IMAP host, username, password, mailbox, and Gmail label, then click Create config. The app stores your password securely and will poll your ISP mailbox on a schedule (every 5 minutes by default). You do not need to edit any config file by hand.

Done. To watch logs: journalctl -u fetch2gmail -f.

Everything runs on one machine (laptop or desktop) that has a browser. You get token.json via fetch2gmail auth (CLI); the web UI does not have "Sign in with Google". Then set a UI password and configure ISP mail in the UI. Follow the steps in order.

Step 1. Get credentials.json from Google Cloud

Same as Use case 1, step 1. Save credentials.json in a folder you will use as the app data directory (e.g. ~/fetch2gmail).

Step 2. Install Python 3.11+ and pipx

Same as Use case 1, step 2 (Windows or Linux).

Step 3. Install fetch2gmail

pipx install fetch2gmail

Step 4. Create the data directory and add credentials

Create the folder and put credentials.json there (you do not have a token yet):

mkdir -p ~/fetch2gmail
# Copy credentials.json into ~/fetch2gmail

Use the same path in the steps below (replace ~/fetch2gmail if you use something else).

Step 5. Get token.json (CLI)

cd into your data directory and run fetch2gmail auth. A browser opens; sign in with the Gmail account that will receive the imported mail and click Allow. token.json is saved in that folder. Press Ctrl+C to stop the auth server.

Step 6. Install and enable the systemd service

Same as Use case 1, step 9: one service (web UI + background fetch). Replace YOUR_USER and the path with yours:

fetch2gmail install-service --user YOUR_USER --dir /home/YOUR_USER/fetch2gmail | sudo tee /etc/systemd/system/fetch2gmail.service > /dev/null
sudo systemctl daemon-reload
sudo systemctl enable fetch2gmail
sudo systemctl start fetch2gmail

Step 7. Set UI password and configure ISP mail

Open http://127.0.0.1:8765 in your browser. If .ui_auth does not exist yet, you will see the Set UI password wizard; set a username and password there (or run fetch2gmail set-ui-password from the CLI). Then use the initial setup form to enter your IMAP host, username, password, mailbox, and Gmail label, and click Create config. The app stores your password securely and the timer runs the fetch on the schedule you set (every 5 minutes by default).

Done.

Your Google OAuth client must use Web application (not Desktop) and have these Authorized redirect URIs:

• http://127.0.0.1:8765/auth/gmail/callback
• http://localhost:8765/auth/gmail/callback

Google does not allow redirect URIs that use an IP address. That is why the token must be obtained on a machine where the app can use localhost (Use case 1 steps 1–4 on a PC; Use case 2 on the same machine).

The app runs the fetch every 5 minutes by default (background poller in the same process as the web UI). You can change the interval in the web UI (Config) or in config.json (poll_interval_minutes).

All app files live in one directory: config.json, credentials.json, token.json, and optionally .env (IMAP password; the UI can store it for you). The app creates state.db and .ui_auth there. Set WorkingDirectory and FETCH2GMAIL_CONFIG to this directory in systemd.

• Do not commit credentials.json, token.json, or config.json with secrets. Restrict file permissions to the user running the service.
• The UI is protected by a username and password in .ui_auth (when set). Get token.json via fetch2gmail auth (CLI only; there is no "Sign in with Google" in the UI).
• The Gmail scope requested is gmail.modify (read and modify labels/messages only).

One instance = one IMAP mailbox → one Gmail account. To run multiple accounts (e.g. two ISP mailboxes forwarding to two Gmail addresses), run multiple instances, each with its own data directory and its own port so the UIs don’t conflict.

Second instance (example):

1. Create a second data directory and put config and credentials there (e.g. /opt/fetch2gmail2 with its own config.json, credentials.json, token.json, .env). Use the same GCP credentials.json if you like; get a separate token.json for the second Gmail account (run fetch2gmail auth and sign in with the second Gmail, then copy that token.json into the second directory).

2. Generate a second systemd unit with a different port and unit name:

   fetch2gmail install-service --user YOUR_USER --dir /opt/fetch2gmail2 -o /tmp/fetch2gmail2.service

3. Install the second unit under a different name so both can run, then edit its ExecStart to add a port:

   sudo mv /tmp/fetch2gmail2.service /etc/systemd/system/fetch2gmail2.service
   sudo nano /etc/systemd/system/fetch2gmail2.service

   In the editor, find the ExecStart= line and make sure it includes a port flag, for example:

   ExecStart=/home/YOUR_USER/.local/pipx/venvs/fetch2gmail/bin/fetch2gmail serve --host 0.0.0.0 --port 8766
   

   Also set WorkingDirectory and Environment=FETCH2GMAIL_CONFIG to the second directory (e.g. /opt/fetch2gmail2, /opt/fetch2gmail2/config.json). Then reload and enable:

   sudo systemctl daemon-reload
   sudo systemctl enable fetch2gmail2
   sudo systemctl start fetch2gmail2

   Run fetch2gmail set-ui-password once from the second directory (or with FETCH2GMAIL_CONFIG set to the second config) so the second UI is protected.

4. Open the first UI at http://server:8765 and the second at http://server:8766. Each has its own config, token, and poller.

You need a different port per instance — each fetch2gmail serve binds to one port, so a second instance must use --port 8766 (or another free port).

"Background fetch skipped: IMAP password could not be decrypted" — The encrypted IMAP password in .env was created with a different encryption key (e.g. different config directory or .cookie_secret). Re-enter the IMAP password in the UI (Config section) and Save to re-encrypt it.

To see what the service is doing (background poller, fetch results, errors), stream the logs:

journalctl -u fetch2gmail -f

You’ll see messages like "Poller: next fetch in Xs", "Poller: running fetch now", and "Background fetch: imported=...". Use Ctrl+C to stop following. For a second instance (e.g. fetch2gmail2), use journalctl -u fetch2gmail2 -f.

fetch2gmail serve — defaults and options

• Default: The app uses the current working directory as the data directory: it looks for config.json, credentials.json, token.json, and .env in the directory you run the command from. So from a folder that already has those (or at least credentials and token), run fetch2gmail serve and open http://127.0.0.1:8765.
• Options:
  • --port 8766 — Use a different port (default 8765). Useful if 8765 is in use or you run multiple instances.
  • --host 0.0.0.0 — Bind to all interfaces (e.g. to reach the UI from another device on the LAN). Default is 127.0.0.1 (localhost only).
  • FETCH2GMAIL_CONFIG=/path/to/config.json — Use a different data directory. The path must be the full path to config.json inside that directory; the app will look for credentials, token, and .env in the same directory. Use this when you run fetch2gmail serve from one place (e.g. your git clone) but want to use config and data from another (e.g. /home/sarah/Desktop/config.json).

To check your installed version: fetch2gmail --version.

If you installed with pipx, upgrade to the latest release with:

pipx upgrade fetch2gmail

You do not need to stop the service, remove the systemd unit, or uninstall first. The service will use the new version the next time it runs (e.g. after a reboot), or restart it now to pick up the update:

sudo systemctl restart fetch2gmail

Your config, token, and data directory are unchanged.

Machine used only to get the token (no system service): After copying credentials.json and token.json to the server, remove the app: pipx uninstall fetch2gmail. Reinstall with pipx install fetch2gmail if you need to run fetch2gmail auth again later.

Machine where the app runs (system service + app): To remove everything so you can reinstall or run from source and see your changes:

1. Stop and disable the systemd service, then remove the unit file:

   sudo systemctl stop fetch2gmail
   sudo systemctl disable fetch2gmail
   sudo rm /etc/systemd/system/fetch2gmail.service
   sudo systemctl daemon-reload

   (To confirm the service is gone: systemctl status fetch2gmail should report "not found".)

2. Uninstall the app:

   • If you installed with pipx: pipx uninstall fetch2gmail
   • If you installed from source in a venv: deactivate the venv (deactivate) and delete the project directory (e.g. rm -rf ~/fetch2gmail), or just use a different terminal and run from your dev clone with pip install -e . so the installed copy is no longer used.

3. Optionally remove the data directory (config, credentials, token, state, UI password file):

   rm -rf /opt/fetch2gmail

   Use the path you used as the data directory (e.g. /opt/fetch2gmail or ~/fetch2gmail). Only do this if you no longer need the config or token; back them up first if you might reuse them.

To test local changes: Uninstall the system copy (steps 1 and 2 above), then from your git clone run python3 -m venv .venv, source .venv/bin/activate, pip install -e .. Use that terminal to run fetch2gmail serve (or reinstall the system service later with fetch2gmail install-service and point it at your data directory).

To run from a git clone (e.g. to test changes before pushing):

1. Clone and go into the repo:

   git clone https://github.com/yourusername/fetch2gmail.git
   cd fetch2gmail

2. Create and activate a virtual environment:

   • Linux / macOS: python3 -m venv .venv then source .venv/bin/activate
   • Windows (PowerShell): python -m venv .venv then .venv\Scripts\Activate.ps1
   • Windows (Command Prompt): python -m venv .venv then .venv\Scripts\activate.bat

3. Install the package in editable mode (so changes in the repo are used when you run the app):

   pip install -e .

   Optional, for tests: pip install -e ".[dev]"

4. Run and test (use the same terminal with the venv active; no pipx needed—the editable install provides the fetch2gmail command):

   • fetch2gmail serve — Run the web UI. Default: uses the current directory for config, credentials, and token. So put credentials.json and token.json in your project directory (or any folder), cd there, run fetch2gmail serve, and open http://127.0.0.1:8765. Optionally add --port 8766 to use another port. No need to set FETCH2GMAIL_CONFIG when you run from the directory that has your data.
   • fetch2gmail auth — Get token. cd into the directory that has credentials.json (or pass --credentials and --token), then run it; a browser opens for Google sign-in and token.json is written there. Use --port 8766 if 8765 is in use.
   • fetch2gmail run or fetch2gmail run --dry-run — If you have config.json and secrets set up (again, run from the data directory or set FETCH2GMAIL_CONFIG).

Using a different data directory: If you want to run fetch2gmail serve from your git clone but use config and data from another folder (e.g. credentials.json and token.json on your Desktop), set FETCH2GMAIL_CONFIG to the full path to config.json in that folder (e.g. FETCH2GMAIL_CONFIG=/home/sarah/Desktop/config.json). config.json does not need to exist yet—the UI creates it when you complete the setup form.

5. Before pushing: test the build so the package still builds and you catch errors:

   pip install build
   python -m build

   This creates dist/ with the sdist and wheel. See docs/PUBLISHING.md for Test PyPI and release steps.

MIT. See LICENSE.