Most teams building link networks with RankerX spend their setup time on proxies, user agents, and content templates. The mailbox credentials are an afterthought, usually a spreadsheet column labeled “email” and a shared password pasted next to it. Then a host migration happens, or a provider changes a port, and half the accounts stop verifying. The missing item is almost always the same: the exact IMAP hostname, port, and SSL mode recorded per host, not just per team.

Why “the email works” is not a credential record

A catch-all domain accepts all addresses on the domain, which is exactly why it is the standard choice for RankerX email setup. One domain gives you unlimited email addresses for account registrations, and RankerX builds links via those registrations, so every profile needs a working mailbox behind it. The catch-all part handles incoming mail. It says nothing about how RankerX retrieves that mail to click confirmation links.

That retrieval step is where the gaps show up. RankerX requires email verification mailboxes, and it stores the connection details per account profile, not in one global setting. If your checklist says “IMAP: yes” and nothing else, you have documented an intention, not a configuration. When a profile fails to confirm an account, you cannot tell from the sheet whether the problem is the password, the hostname, the port, or the SSL mode. Skepticism is warranted here: a checklist item that cannot distinguish between four failure modes is not a checklist item, it is decoration.

The fix is unglamorous. Every mailbox record should carry the full connection tuple: hostname, port, encryption mode, username format, and whether authentication uses a full address or a bare local part. Add the provider name and the date the settings were confirmed. Five extra fields turn a support mystery into a two-minute fix.

The checklist itself, field by field

Write the checklist so that someone who has never touched the account can rebuild the connection from the record alone. The test is simple: hand the sheet to a new team member and ask them to configure a POP3 account or an IMAP account in a mail client. If they have to guess anything, the record is incomplete.

• IMAP hostname. The exact string, not a marketing name. Providers often use a different host for IMAP than for their webmail or SMTP service, and subdomains matter. A hostname like imap.provider.example is not interchangeable with mail.provider.example.
• Port and SSL mode. Record both together, because they travel as a pair. Port 993 with implicit SSL is the common IMAP default; port 143 usually means STARTTLS, and port 110 is unencrypted POP3 with 995 as its SSL counterpart. Note the mode explicitly: implicit SSL, STARTTLS, or none.
• SMTP credentials. Verification mail is inbound, but password resets and support flows are outbound. Record the SMTP host, port, and whether it uses the same login as IMAP. Many providers require a separate app password.
• Login format. Full address versus local part. This trips up bulk provisioning more than any other field, because a host that accepts [email protected] on one port may reject it on another.
• Provider and plan. Note the hosting tier and whether the catch-all mailbox shares infrastructure with other customers. A shared-subdomain plan behaves differently from a dedicated domain when you need to prove ownership or request a port change.

Keep one row per mailbox, not one row per domain. A catch-all domain may route to a single catch-all mailbox, but teams often split traffic across several mailboxes for volume reasons, and each one has its own credentials. If you run AllMail, the record also includes the plan type, since a shared-subdomain plan starts at $0.49 per month while a dedicated .com domain costs $6.29 per month, and the two can sit on different host settings.

Where the stale-settings trap bites

Here is the failure pattern worth designing around. A team standardizes on one provider for a year and hardcodes its IMAP hostname into a template, a script, or muscle memory. Then they switch providers for cost or deliverability reasons. RankerX email accounts has more details on this topic. DNS gets updated, the new catch-all domain starts receiving mail, and everyone assumes the job is done. Weeks later, a batch of RankerX profiles fails verification because each stored profile still points at the old hostname with the old port and SSL mode.

RankerX stores credentials per account, so a host migration requires updating every stored profile, not just the DNS. That is the sentence to put at the top of the migration runbook. Count your profiles before you switch, schedule the edit as a batch operation, and re-verify a sample of ten accounts before declaring the migration complete. The same logic applies to smaller changes: a provider that moves from port 143 with STARTTLS to port 993 with implicit SSL has effectively created a new host configuration for every profile that uses it.

Provisioning, rotation, and payment details that belong on the same sheet

Credential management does not stop at connection strings. Note how mailboxes get created, who can create them, and what naming convention applies, so that email provisioning stays consistent when the person who built the original list moves on. If the provider supports email aliases or wildcard email routing, record the pattern, because a wildcard alias can replace dozens of individually created addresses and simplify the sheet considerably. Email forwarding rules deserve a line too: a forward that silently drops mail will look identical to a wrong password from the RankerX side.

Retention is the other field people forget. AllMail retains mail for 14 days, which is fine for verification windows but means you should not treat the mailbox as an archive. Set the expectation in the checklist: confirmation emails are consumed within days, and anything older is gone. Teams that assume permanent storage waste hours debugging “missing” mail that was simply expired.

Payment and access details round out the record. AllMail accepts USDT and USDC payments and offers no KYC, which suits teams that prefer not to attach corporate identity documents to bulk mailbox infrastructure. Note the funding method and renewal date on the same sheet as the credentials, because an expired plan produces the same symptom as a bad password: verification emails stop arriving. AllMail supports POP3 and IMAP over SSL, so the connection tuple maps cleanly onto its service, and a crypto email hosting provider with a stable hostname is easier to document than one that rotates endpoints.

Treat the sheet as sensitive. It holds working credentials for an anonymous email service used to run link building email accounts, and a leak means someone else can confirm accounts in your name. Store it in a password manager with per-user access, not in a shared drive, and rotate passwords on a schedule you actually follow.

Start by auditing ten existing mailboxes against the five-field tuple above. Whatever is missing in those ten is missing everywhere, and filling it in now costs less than diagnosing a failed verification batch later. Pick one hostname convention, write down the port and SSL mode next to it, and make the record mandatory before any new profile goes into RankerX.