MessageFlow
MessageFlowPricingBlogAPI docs
EN
EN
  • MessageFlow Documentation
  • 🚀ACCOUNT
    • Dashboard
    • User panel
      • Settlements
      • Settings
        • Security
        • IP Authorization
        • Two-Factor Authentication (2FA)
        • API
        • Webhooks
      • Notifications
      • Operation list
      • File manager
      • GDPR
    • Login and account management
      • How to create an account?
      • Logging into the platform
      • Resetting the password
      • Changing your password in the App
      • Two-step authentication (2FA)
      • Resetting 2FA Settings
    • User and role management
      • Adding a user
      • Assigning permissions
      • User account activation
      • Editing and deleting a user
  • 💬CONTACTS
    • Adding contacts
      • Adding contacts manually
      • Importing contact lists (CSV, Excel)
      • Additional fields
    • Segmentation of customers
    • Archiving groups
  • Deleting groups
  • ✨COMMUNICATION CHANNELS IN THE PANEL
    • E-mail
      • Overview
      • Dashboard
      • Campaigns
        • Campaign list
        • Exporting campaigns from the list
        • Creating e-mail campaigns
          • Designing messages with a drag-and-drop editor
          • Email creation specifications
          • Personalizing email campaigns
          • Creating and downloading message templates
        • Booster for e-mail campaigns
          • Instructions for sending an e-mail campaign with the Booster option
          • Reports & analytics
      • Analytics, audiences and reports
        • Monitoring deliverability, opens, clicks
        • Storage of email campaign reports
        • Email address archiving, removing hard-bouncing addresses, unsubscribes
      • Outgoing
        • Outgoing List
        • Export list
      • Settings
        • Adding a sign-out page
    • SMS
      • Overview
      • Dasboard
      • Campaigns
        • Campaign list
        • Exporting campaigns from the list
        • Creating SMS campaign
        • Booster for SMS campaign
          • Instructions for sending an SMS campaign with the Booster option
          • Reports & analytics
      • Analytics, audiences and reports
        • Reporting and analysis of SMS campaign results
        • Storage of SMS campaign data
        • Archiving recipients, removing recipients with ERROR status
      • Incoming
        • List of incoming
        • Export list
      • Outgoing
        • Outgoing list
        • Export list
      • Settings
        • List of links with suffixes
        • Unsubscribe pages
      • Common settings
        • Sender IDs
      • Integration with short codes
      • SMS Billing
    • Mobile push
      • Overview
      • Dashboard
      • Campaigns
        • Campaign list
        • Export list
        • Push campaign configuration
        • Booster for mobile push campaign
          • Instructions for sending a mobile push campaign with the Booster option
          • Reports & analytics
      • Outgoing
        • Outgoing list
        • Export list
      • Analytics and report
        • Push campaign report
        • Push campaign data storage
      • Common settings
        • Applications
        • Adding test device
      • Segmentation
    • RCS
      • RCS message types
      • What is a Brand Bot?
      • How to run RCS?
      • Tips for creating a campaign
      • Technical specifications of the RCS service
  • 🖥️API CHANNELS
    • E-mail API
      • Dashboard
      • E-mails report
      • Tag report
      • Domains report
      • Blacklist Report
      • Whitelist report
      • Settings
    • Mobile push API
      • Overwiev
      • Dashboard
      • Outgoing
        • Outgoing list
        • Export
    • SMS API
      • Overview
      • Dashboard
      • Incoming
        • Incoming list
        • Export
      • Outgoing
        • Outgoing list
        • Export
  • ⚙️TECHNICAL SUPPORT CENTER
    • Integrations
      • Integration with Salesforce
      • Integration with SalesManago
      • Integration with Synerise
      • Integration with IdoSell
    • Senders Authorization
      • How to Authorize Senders in MessageFlow?
        • Domains Authorization
        • Authorizing domains with web hosts
          • Authorizing a domain hosted at Nazwa.pl
          • Authorization of a domain hosted at Home.pl
          • Authorizing a domain hosted at cyber_Folks
          • Authorizing a domain hosted on Zenbox
          • Authorizing a domain hosted on OVHcloud
          • Authorizing a domain hosted on GoDaddy
        • SPF Record Configuration
    • System requirements
    • Technical assistance
    • API documentation
    • FAQ
  • Trust Center
    • Account Security
      • Password Management
      • Two-Factor Authentication (2FA)
      • IP Access Control
      • User & Role Management
    • Communication Channel Security
      • Email Communication Security
      • SMS Communication Security
      • RCS, Mobile Push & Viber Security
    • Data & Infrastructure Security
      • Our Commitment to Security
      • Data Center Security
      • Technical & Organisational Measures (TOMS)
      • Service Protection (WAF)
      • List of Procedures
    • Data Protection & Compliance
      • Legal Framework
      • Personal Data Processing at MessageFlow
      • Data Processing Agreement (DPA)
      • Document Templates
      • Sub-processors
    • Certifications & Audits
      • ISO Certifications
      • Security & Penetration Testing
      • Industry Standards & Affiliations
    • Abuse Prevention
      • MessageFlow Shield 360: Proactive Threat Protection
      • Recognising and Analysing Suspicious Messages (User Guidance)
      • Abuse Policy and Reporting
    • Security FAQ
Powered by GitBook
On this page
  • Sender Authorization
  • SPF (Sender Policy Framework): Authorizing Your Servers
  • DKIM (DomainKeys Identified Mail): Guaranteeing Message Integrity
  • DMARC (Domain-based Message Authentication, Reporting & Conformance): Enforcing Your Policy
  • BIMI (Brand Indicators for Message Identification): Visual Trust
  • Message-in-Transit Encryption (TLS): Securing the Journey
  1. Trust Center
  2. Communication Channel Security

Email Communication Security

PreviousCommunication Channel SecurityNextSMS Communication Security

Last updated 2 days ago

Email is a powerful and universal channel, but its open architecture requires specific security protocols to function securely. Properly configuring your sending domain is the most important action you can take to improve your email deliverability and protect against fraud.

Sender Authorization

This is the process of proving you have the right to send emails from your domain. It involves configuring standards like SPF, DKIM, and DMARC to build a trustworthy sender reputation. For a comprehensive guide, please see our detailed .

SPF (Sender Policy Framework): Authorizing Your Servers

What it is: SPF is an email authentication method that specifies which mail servers (by their IP addresses) are authorized to send email on behalf of your domain.

How it works: You publish a list of approved sending servers in a special TXT record in your domain's DNS. When a recipient's mail server receives an email from your domain, it checks the SPF record to see if the sending server's IP address is on your authorized list. If it matches, the email passes the SPF check.

Why it matters: SPF is your first line of defence against basic email spoofing, where an attacker sends emails that appear to be from you.

DKIM (DomainKeys Identified Mail): Guaranteeing Message Integrity

What it is: DKIM provides a way to "sign" your emails with a digital signature, ensuring that the message content has not been tampered with during transit.

How it works: When you send an email through MessageFlow, we use a private cryptographic key to create a unique digital signature based on the content of the email. This signature is added to the email's headers. The corresponding public key is published in your domain's DNS. The recipient's mail server retrieves this public key to verify the signature. If the verification is successful, it proves two things: that the email genuinely came from your domain, and that its content (including attachments) has not been altered.

Why it matters: DKIM provides a strong guarantee of message authenticity and integrity, protecting against more sophisticated phishing and man-in-the-middle attacks.

DMARC (Domain-based Message Authentication, Reporting & Conformance): Enforcing Your Policy

What it is: DMARC is a policy layer that builds on SPF and DKIM. It tells receiving mail servers what to do with emails that fail SPF or DKIM checks and provides valuable feedback reports.

How it works: You publish a DMARC record in your DNS that defines your policy. This policy can be:

  • p=none: The "monitoring" policy. It tells servers to deliver the email and just send you a report. This is the recommended starting point to gather data.

  • p=quarantine: Tells servers to treat failed emails with suspicion, usually by placing them in the spam or junk folder.

  • p=reject: The strictest policy. It instructs servers to completely reject emails that fail authentication. DMARC reports (RUA/RUF) give you priceless insight into who is sending email from your domain, helping you identify legitimate sources and detect abuse.

Why it matters: DMARC gives you control over your email domain, protects your brand from being used in phishing attacks, and is a prerequisite for BIMI.

BIMI (Brand Indicators for Message Identification): Visual Trust

What it is: BIMI is an email standard that allows you to display your brand's official logo next to your authenticated messages directly in the recipient's inbox.

How it works: To implement BIMI, you must first have a strong DMARC policy in place (p=quarantine or p=reject). You then need to publish another DNS record that points to your brand's logo in a specific SVG format. For some mail providers, the logo must also be verified and certified through a document called a Verified Mark Certificate (VMC).

Why it matters: BIMI provides an immediate, powerful visual cue of authenticity, increasing brand recognition, recipient trust, and potentially boosting engagement rates.

Message-in-Transit Encryption (TLS): Securing the Journey

What it is: Transport Layer Security (TLS) is a cryptographic protocol that encrypts the connection between mail servers.

How it works: When MessageFlow sends an email to a recipient's mail server, it first attempts to establish a secure TLS connection (known as a "TLS handshake"). If successful, the entire content of the email is encrypted for its journey across the internet. This prevents third parties from eavesdropping on or intercepting the communication between the servers.

Why it matters: TLS ensures the privacy and confidentiality of your email communications, protecting sensitive information as it travels from our servers to the recipient's provider. MessageFlow supports and prioritizes TLS encryption for all email sending.

Sender Authorization documentation