billing help · For platform operators
Service guides
Email through SMTP2GO (sender domain, SPF, DKIM, DMARC), MaxMind GeoLite2 files, and keeping backups off the server.
Email through SMTP2GO
Receipts, password resets, invitations, alerts and digests are sent through SMTP2GO's HTTP API. Until email is configured, messages wait in the outbox (Super → Health & jobs) and nothing is lost.
1. Create the account#
Sign up at smtp2go.com. Choose a plan that covers your monthly volume: one email per payment, plus account emails, alerts and digests.
2. Verify the sender domain#
The sender address is receipts@ your domain (for example [email protected]). In SMTP2GO → Sending → Verified Senders → Sender Domains, add the domain. SMTP2GO shows DNS records to create at your DNS host:
| Record | Purpose |
|---|---|
CNAME records for DKIM (s….domainkey) | Signs every message so receivers can trust it |
CNAME for the return path (em….yourdomain) | Handles bounces and aligns SPF |
| CNAME for link tracking (optional) | Branded tracking links; leave tracking off for receipts |
Wait until SMTP2GO shows the records as verified.
3. SPF and DMARC#
- SPF: with SMTP2GO's return-path record, SPF aligns on that subdomain. If your domain already has an SPF record for other mail, keep a single SPF record and add
include:spf.smtp2go.comto it. - DMARC: publish a TXT record at
_dmarc.yourdomain, starting with monitoring and tightening later:
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain; adkim=r; aspf=r
After a few weeks of clean reports, move to p=quarantine, then p=reject.
4. Create the API key#
SMTP2GO → Sending → API Keys → Add API Key. Allow the /email/send endpoint; nothing else is needed. Copy the key (api-…).
5. Configure the platform#
Super → Settings → Email:
- Transport SMTP2GO, the sender address, the API key (stored sealed) and the API region of your account.
- Save, then Send test message. It goes to your own address and runs the sender at once.
6. Add the bounce and spam webhook#
The Email screen shows a webhook URL. In SMTP2GO → Settings → Webhooks, add it for bounce and spam events. Addresses that bounce hard or complain are then suppressed: no more email is sent to them, and the Email screen lists them so you can lift a suppression after the customer fixes their address.
Checking deliverability#
- Send the test message to a Gmail and an Outlook address and open Show original: SPF, DKIM and DMARC should all say PASS.
- Each workspace's emails use the workspace name as the sender name and its support email as Reply-To, so customers' replies go to the right store.
- If messages pile up in the outbox, the Email screen and Health & jobs show the last error from SMTP2GO.
GeoIP files from MaxMind
GeoIP files turn a visitor's IP address into a country, region, city and network (ASN). They feed the site analytics and the country of each payment. The platform reads the files with its own reader; no extension or library is needed, and IP addresses are never sent anywhere.
1. Create a MaxMind account#
Sign up for a free GeoLite account at maxmind.com and accept the GeoLite2 End User License Agreement. GeoLite data is free, with attribution: the platform's analytics pages already credit MaxMind.
2. Download the databases#
Account → Download Databases. Download, in MaxMind DB (.mmdb) format (the GZIP download contains the .mmdb file):
- GeoLite2 City (about 60 MB) — country, region, city;
- GeoLite2 ASN — network operator.
3. Put them in place#
Either:
- Upload them on Super → GeoIP. Each file is checked before it is used: it must open, be a City, Country or ASN database and answer test lookups. Uploads are audited and copied to the other server of a pair automatically; or
- copy them into
data/geo/on the server (ownerwww-data), when the City file is larger than PHP's upload limit.
Every *.mmdb in data/geo/ is considered. For each kind, the newest build wins; older files stay listed as not used and can be deleted.
4. Keep them current#
MaxMind publishes new builds twice a week, and its licence asks you to keep the data reasonably current. The GeoIP screen and the self-check warn when the active City file is older than 60 days. A simple routine: download and upload the two files once a month.
When you stop using the data, delete the files, as the licence requires.
Keeping backups off the server
Nightly archives are written to data/backups/ on the server itself. A copy only on the same server does not survive the loss of that server, so keep copies elsewhere. Automatic SFTP and S3 upload are planned for a later release; until then, copy archives yourself.
Text description
Every night the database is dumped as the backup user and packed into a tar archive together with config.php, uploads, GeoIP files and licensed downloads, plus a manifest with the size and SHA-256 of every member and the row count of every table. The archive is encrypted with AES-256-GCM in chunks, with a key derived from the master key, and written to data/backups. Retention keeps 7 daily, 4 weekly and 12 monthly archives. Every week the drill decrypts the newest archive, loads it into a scratch database, compares every table's row count and every file's checksum, and drops the scratch database. Download archives regularly to keep a copy off the server; keep the master key off the server too.
The two keys to recovery#
- An archive — encrypted; useless without the master key.
- The master key —
data/keys/master.key, shown once at installation. It also decrypts the gateway keys inside the database. Keep it in a password manager or a safe, never in the same place as the archives.
Copying archives#
- Download the newest archive on Super → Backups. The download is audited, and the response carries the archive's SHA-256 so you can check the copy.
- Or copy with
scporrsyncfrom another machine, then press I made an off-box copy on the same screen:
rsync -av --ignore-existing [email protected]:/var/www/encrypted.com/data/backups/ ~/billing-backups/
Each copy counts for 8 days; after that the screen and the self-check remind you again. A weekly copy is a sensible minimum; daily if you take many payments.
Opening an archive elsewhere#
On any machine with PHP and the release files:
php app/cli.php backup:decrypt billing-20261110-023700.bkp out.tar --key-file=master.key
tar -tf out.tar
backup:extract decrypts and unpacks in one step and checks every file against the manifest. The full restore procedure is in Backups and restore.