Frequently Encountered Issues
- 554 Message rejected: Email address is not verified
- Domain name is not visible
- Email Forwarding: Why Messages Sometimes Land in Spam (and How to Improve It)
- Email Solution - Invalid owner handle!
554 Message rejected: Email address is not verified
Our Email Solution uses Amazon SES for sending outgoing emails from email accounts. Amazon Simple Email Service (Amazon SES) is a cloud-based email service provider that can integrate into any application for high-volume email automation.
To be able to send emails through Amazon SES, domains need to be verified first. For verification, three CNAME records will need to be added for domains.
If you are not able to send emails due to error "554 Message rejected: Email address is not verified. The following identities failed the check in region.....", it indicates CNAME records required for Amazon SES verification are either missing or the CNAME records added are incorrectly.
Please check RCP (Reseller Control Panel) >> Email Accounts >> Domains tab >> Click on DNS button (under Actions) shown on the right of the domain to see exact CNAME records for your email domains.
To check added CNAME records, you may use command line tools like dig or host or online tools.
Sample online tools for CNAME lookup:
Google Admin Toolbox Dig
MXToolBox CNAME Lookup
Domain name is not visible
When adding a domain name to our platform, it's crucial to use the specific domain handler associated with its registration. Using an incorrect or different domain handler might result in an error when attempting to add the domain name.
-
Select "Add Domain":
- Locate the "Add Domain" button or option and click on it to initiate the process.
-
Enter Domain Details:
- Enter the exact domain name you wish to add. Ensure that the domain handler information matches the one used during the domain's registration process.
Domain Handler Importance:
- The domain handler is crucial as it acts as an identifier for the domain's management on our platform.
- Using an incorrect domain handler will lead to an error when attempting to add the domain name.
Email Forwarding: Why Messages Sometimes Land in Spam (and How to Improve It)
When using our email forwarding service, you may occasionally find that some emails land in the recipient’s Spam/Junk folder. This article explains how our forwarding works, why spam can still happen even with proper authentication, and what you can do to improve deliverability.
How Our Email Forwarding Works
All forwarded messages are sent from: forwarded@op-email.eu
To keep reply behavior natural, we set the Reply-To header to the original sender’s address. That means:
- The recipient sees the message from forwarded@op-email.eu.
If they click Reply, their email client automatically addresses the reply to the original sender.
The original sender information is preserved in headers for traceability.
Why this approach?
Using a fixed, authenticated sender ensures strong SPF/DMARC alignment with our domain (op-email.eu), improving consistency across providers.
What We Do to Support Deliverability
- SPF: All outbound IPs are authorized under the SPF record for op-email.eu.
- DKIM: Forwarded messages are DKIM-signed by op-email.eu.
- DMARC: Evaluates against op-email.eu and will pass via SPF or DKIM alignment.
Consistent envelope: A single, authenticated sender reduces false positives with strict filters.
Note: Any original DKIM signature from the source sender may not validate after forwarding because some headers change. The message remains authenticated via our op-email.eu DKIM/SPF.
Why Emails May Still Go to Spam
Email content & formatting: Spam-like language, suspicious links, or risky attachment types can trigger filters.
Original sender reputation: A poor reputation for the original sender’s domain/IP can influence filtering.
Recipient mailbox algorithms: Providers (e.g., Gmail/Outlook) weigh user behavior, past engagement, and proprietary signals.
Low engagement: If recipients rarely open or interact with your messages, providers may downrank future emails.
What You Can Do
- Allowlist: Ask recipients (or their IT) to allowlist op-email.eu or specifically forwarded@op-email.eu.
Mark “Not Spam”: When misclassified, marking as “Not spam” trains the mailbox provider.
Improve content quality: Avoid spammy phrases, link shorteners, or executable attachments; keep a healthy text-to-image ratio.
Encourage best practices: Ask frequent senders to maintain valid SPF/DKIM for their own domain and avoid spam-triggering content.
Consider direct mailbox access: For the highest deliverability control, use IMAP/POP to read the mailbox directly (see below).
Alternative: Use Direct Mailbox Access
For best results and full control (no forwarding involved), connect your email client directly to the mailbox via IMAP/POP3:
Provider-specific help:
Gmail – https://support.google.com/mail/answer/6304825?hl=en
Yahoo – http://help.yahoo.com/kb/SLN28341.html
This avoids forwarding-related heuristics and keeps authentication tied to the mailbox provider end to end.
FAQs
Will recipients always see forwarded@op-email.eu as the sender?
Yes. That’s by design for authentication consistency. Replies will still go to the original sender via the Reply-To header.
Does this pass DMARC?
Yes. DMARC aligns to op-email.eu (the visible From domain). We sign with DKIM and authorize SPF for that domain.
Can we still trace the original sender?
Yes. The original From address is placed in Reply-To and preserved in standard headers so recipients and mail admins can see who originated the message.
Email Solution - Invalid owner handle!
You may encounter the error "Invalid owner handle!" when trying to add a domain to the email service.
If the domain is registered through Openprovider, the handle used to add the domain to email service must match the domain’s registrant handle (owner handle). Using a different handle will trigger the error.
For domains registered with other providers, this validation does not apply. You can use any handle under your account when adding the domain to the email service.