Blocklist delisting forms sometimes ask for the IP address of the server that sent the message. This article explains why we don't publish that list and what to do instead.
Why there's no fixed list of IPs
Outbound mail from Maildoso mailboxes is sent through managed infrastructure with IP addresses that rotate over time. The address that sent a message last week may not be in use today, so a static list wouldn't be accurate or useful on a delisting form.
SURBL "multi" listings
A SURBL "multi" flag against a domain is a domain-level listing, not an IP-level one. Delisting requests for it are submitted for the domain, not for a sending IP.
In our experience this particular listing does not affect whether your emails reach the inbox. If your placement is fine, no action is needed.
You do not need to change any DNS records or ask us to change any. Authentication for your domain is already configured on our side.
Listings that do need action
Some listings are meaningful — a Spamhaus listing on a sending domain, for example, indicates a real reputation problem, most often caused by sending to unverified or low-quality lists. In that case the domain should be retired and replaced rather than delisted, and the sending list should be cleaned before starting again.
If a checker reports one of your IPs as blocklisted
Because addresses rotate, a flag on a single IP snapshot usually reflects an address that is no longer in your sending path. It isn't something you need to fix, and it's not a sign that your mailboxes are misconfigured.
Getting a specific case reviewed
If your emails are actually landing in spam and you want it looked at properly, contact us with your sending volume, the tool you're using for warmup, and a couple of example messages. We'll review your specific case rather than guessing from a checker's output.