Source
Deliverability infrastructure — found from sitemap — Apsis One
Checked for Apsis One on 10 Nov 2026
- Page
- https://help.apsis.one/en/articles/6929868-keep-deliverability-high
- Checked
- 10 Nov 2026, 12:10 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:14c0a6b16e973b979b58a9441d8562b570fe26e119a91b9f7d66152b897a245c
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Delivery rate target Report an error
“A healthy list should achieve a delivery rate around 99% — 100% is almost impossible for any list of meaningful size.”
-
Greylisting retry Report an error
“Apsis's mail servers are configured to detect greylisting and automatically retry after 15 minutes (instead of the standard 2-hour retry interval for regular temporary bounces).”
-
Soft bounce retry Report an error
“The system retries every hour for up to 48 hours after the initial send time.”
-
Hard bounce limit Report an error
“After 3 hard bounces for the same Profile, Apsis One stops sending to that address altogether. If the third hard bounce happened in a previous sending, the Profile is excluded from future sends automatically.”
-
Spam complaint threshold Report an error
“Google recommends staying below 0.1% (1 complaint per 1,000 delivered emails).”
-
Fbl gmail limitation Report an error
“Not all email providers participate in FBLs — notably, Gmail does not send spam complaints through Feedback Loops. To see spam complaint data for Gmail recipients, you need to set up Google Postmaster Tools for your sending domain.”
-
Double optin Report an error
“Double opt-in requires new subscribers to confirm their email address by clicking a link in a confirmation email. This prevents spambot signups, typos, and fake addresses from entering your list”
-
Third party lists prohibited Report an error
“Never import third-party lists Do not import files with addresses or information provided by a third party. These lists violate consent requirements and will damage your sender reputation.”
-
Spf preconfigured Report an error
“No action needed — SPF is pre-configured on the Apsis One technical sender domain (apsisone.com).”
-
Dkim setup Report an error
“Set up during onboarding with your Apsis Consultant. You provide a domain and selector; Apsis creates the key pair; you publish the TXT record in your DNS.”
-
Dmarc customer configured Report an error
“Configure on your domain's DNS. DMARC policies are set by you (or your IT team).”
-
Dkim dmarc required Report an error
“Since mid-2025, major email providers (Google, Yahoo, Microsoft) actively enforce DKIM and DMARC as requirements for bulk senders. Without both in place, your emails are at serious risk of being blocked or sent to spam.”
-
Custom domain Report an error
“Setting up a Custom domain for links and system pages adjusts URLs in your emails and system-generated pages (like the web version and unsubscribe page) to display your own domain instead of the default Apsis tracking domain.”
-
Warmup threshold Report an error
“The warm-up process applies to any account that intends to send to more than 10,000 recipients per day.”
-
Managed ip Report an error
“Apsis One sends the email from a managed IP address via your private technical sender domain.”
-
Bounces export Report an error
“Export the Bounces tab to see individual bounce codes and reasons.”
-
Escalation Report an error
“For help with bad statistics, reach out to Customer Service and pause the warm-up process until the issue is resolved.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The CRM Manager Deliverability infrastructure
- The Data Protection Officer Deliverability infrastructure
- The Deliverability Engineer Deliverability infrastructure
- The Shop Owner Deliverability infrastructure
- The Integrator Deliverability infrastructure
- The Skeptic Deliverability infrastructure
- The Skeptic Consent, proof & tracking limits