{"id":147418,"date":"2026-05-19T00:50:24","date_gmt":"2026-05-19T07:50:24","guid":{"rendered":"https:\/\/help.fooevents.com\/?post_type=docs&p=147418"},"modified":"2026-06-03T12:16:25","modified_gmt":"2026-06-03T19:16:25","slug":"fooemail","status":"publish","type":"docs","link":"https:\/\/help.fooevents.com\/fr\/docs\/topics\/fooevents-plugins\/fooemail\/","title":{"rendered":"FooEmail"},"content":{"rendered":"\n

FooEmail (currently in beta)<\/em> is a free WordPress plugin for logging emails sent from your site and improving email deliverability using SMTP and Brevo. It helps ensure that mission-critical emails such as FooEvents tickets, WooCommerce orders, contact form submissions, and password resets reach your customers’ inboxes without being flagged as spam or blocked by hosting providers.<\/p>\n\n\n\n

\n
Download FooEmail<\/svg><\/a><\/div>\n<\/div>\n\n\n\n

Download and install the free FooEmail plugin on your WordPress site.<\/em><\/p>\n\n\n\n

Key Features<\/h2>\n\n\n\n
\"FooEmail<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Email Logging<\/strong><\/p>\n\n\n\n

Every email sent from your WordPress site is captured in a detailed log that allows you to monitor delivery status and troubleshoot errors in real-time.<\/p>\n\n\n\n

Reliable Email Sending (SMTP & Brevo)<\/strong><\/p>\n\n\n\n

By default, WordPress uses the wp_mail<\/code> function, which relies on your web server\u2019s internal mailer. These mailers are often restricted or poorly configured, leading to high failure rates. FooEmail allows you to bypass these limitations by routing emails through professional Email Service Providers (ESPs) like Brevo<\/b> or a custom SMTP<\/b> server.<\/p>\n\n\n\n

Automated Data Management<\/strong><\/p>\n\n\n\n

Maintain a lean database and stay compliant with privacy regulations with automated cleanup tools.<\/p>\n\n\n\n

Setup Steps<\/h2>\n\n\n\n

Step 1: Install and Activate<\/h4>\n\n\n\n

Once activated, FooEmail will immediately begin capturing logs for all outgoing emails sent from your WordPress site.<\/p>\n\n\n\n

Note<\/strong>: The log email content option is not enabled by default to protect your privacy. However, email content is not stored and resends are unavailable while this is disabled. You can enable this on FooEmail<\/strong> > Settings<\/strong>.<\/p>\n\n\n\n

Step 2: Configure your Sender<\/h4>\n\n\n\n
    \n
  1. Navigate to FooEmail > Settings<\/b>.<\/li>\n\n\n\n
  2. Click the Email Sending<\/b> tab.<\/li>\n\n\n\n
  3. Choose your service (SMTP<\/b> or Brevo<\/b>) and enter the required credentials.<\/li>\n\n\n\n
  4. Check Force From Email<\/b> to maximize deliverability.<\/li>\n<\/ol>\n\n\n\n

    Step 3: Verify with a Test Email<\/h4>\n\n\n\n
      \n
    1. In the Email Sending<\/b> tab, click the Test Sending<\/b> sub-tab.<\/li>\n\n\n\n
    2. Enter your email address and click Send Test Email<\/b>.<\/li>\n\n\n\n
    3. Check the Emails<\/b> log page to confirm the status is “Sent.”<\/li>\n<\/ol>\n\n\n\n

      Email logging and delivery are separate: An email can be logged by FooEmail but still fail to send if the SMTP\/API provider rejects it. More information can be viewed on the FooEmail<\/strong> > Emails<\/strong> page.<\/p>\n\n\n\n

      Settings<\/h2>\n\n\n\n

      General<\/h4>\n\n\n\n
      Send Notifications<\/strong><\/td><\/tr>
      Enable notifications<\/strong><\/td>Check to receive email notifications when the email log exceeds limits.<\/td><\/tr>
      Recipient email<\/strong><\/td>Email address that will receive the email notifications when the email log exceeds limits.<\/td><\/tr>
      Number of logs<\/strong><\/td>Number that will trigger the email notifications.<\/td><\/tr>
      Delete old emails from log<\/strong><\/td><\/tr>
      Enable<\/strong><\/td>Check to automatically delete logs older than a certain age or when your log reaches a specific total count.<\/td><\/tr>
      Older than<\/strong><\/td>Age to check when to start automatically deleting logs.<\/td><\/tr>
      Total logs exceeds<\/strong><\/td>Total number of logs to trigger the automatic deletion.<\/td><\/tr>
      Privacy<\/strong><\/td><\/tr>
      Log email content<\/strong><\/td>Check to store email body\/content for previews and resends. When disabled, email content is not stored and resends are unavailable.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Email Sending<\/h4>\n\n\n\n
      Email Sending<\/strong><\/td><\/tr>
      Email Sending<\/strong><\/td>Choose which service to use for outgoing email. Options are WordPress Default, SMTP, and Brevo

      <\/p>\n

      To ensure your website\u2019s emails actually reach your users’ inboxes, you need to tell FooEmail how to send them. You can choose to connect to your own email server using SMTP or use a dedicated email delivery service like Brevo.<\/p><\/td><\/tr>

      SMTP Settings<\/strong>

      <\/p>\n

      You can usually obtain these details from your website hosting company (like Bluehost, SiteGround, etc.), your email provider (like Google Workspace or Microsoft 365), or your dedicated Email Service Provider. Search their help docs for “SMTP settings” or reach out to their support team.<\/p><\/td><\/tr>

      SMTP Host<\/strong><\/td>This is the web address of your email server. It usually looks something like smtp.yourdomain.com<\/code>, smtp.gmail.com<\/code>, or mail.yourprovider.com<\/code>.<\/td><\/tr>
      Port<\/strong><\/td>This is the specific “digital door” the server uses to send mail. This number is directly tied to your Encryption Type. Your provider will give you the exact number, but generally:

      <\/p>\n

        \n
      • Port 587<\/strong> is used for TLS encryption.<\/li>\n
      • Port 465<\/strong> is used for SSL encryption.<\/li>\n
      • Port 25<\/strong> is used if there is no encryption.<\/li>\n<\/ul>\n<\/td><\/tr>
      Encryption<\/strong><\/td>This tells the server how to safely scramble your email data while it travels across the internet. Your email provider will tell you which one to use.

      <\/p>\n

        \n
      • TLS<\/strong> is the most common and recommended modern security standard.<\/li>\n
      • SSL<\/strong> is an older, but still widely used security standard.<\/li>\n
      • None<\/strong> means no encryption (not recommended unless specifically instructed by your host).<\/li>\n<\/ul>\n<\/td><\/tr>
      Username<\/strong><\/td>The username you use to log into your email server. In almost all cases, this is simply your full email address (e.g., hello@yourwebsite.com<\/code>).<\/td><\/tr>
      Password<\/strong><\/td>The password associated with your SMTP Username. Note: If you use Gmail or Microsoft 365, you may need to generate a special “App Password” in your account security settings rather than using your normal login password.<\/td><\/tr>
      From Email<\/strong><\/td>This is the email address that your customers will see in the “From” line when they receive your message in their inbox. To ensure your emails don’t get blocked by spam filters, this should usually be the exact same email address you entered in the SMTP Username<\/strong> field above.

      <\/p>\n

      Force From Email<\/strong> (Highly Recommended): WordPress plugins sometimes try to send emails using default addresses like wordpress@yourwebsite.com<\/code>. However, strict email providers will block the email if the “From” address doesn’t exactly match your authenticated SMTP Username. By checking this box, FooEmail will override any other settings and force all outgoing emails to use your authorized SMTP email address, preventing frustrating delivery failures.<\/p><\/td><\/tr>

      From Name<\/strong><\/td>From Name: This is the friendly, human-readable name that appears next to the email address in your customer’s inbox. Instead of just seeing an email address, they will see a name they recognize. You can set this to your company name (e.g., “FooEvents Support”) or a specific person (e.g., “Jane from FooEvents”).<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

      Brevo<\/strong><\/h4>\n\n\n\n

      Brevo (formerly Sendinblue) is a dedicated email delivery service. Using a service like Brevo is often much more reliable than standard SMTP because their servers are strictly optimized for delivering high volumes of website emails.<\/p>\n\n\n\n

      FooEmail includes a direct integration with Brevo. Unlike SMTP, you do not need to use ports or hostnames; you simply need an “API Key,” which acts as a secure digital handshake between your website and your Brevo account.<\/p>\n\n\n\n

      How to Get Your Brevo API Key:<\/span><\/strong><\/p>\n\n\n\n

        \n
      1. Log in to your Brevo account dashboard<\/strong>.<\/li>\n\n\n\n
      2. In the top-right corner<\/strong> of the screen, click your account name<\/strong> to open the dropdown menu.<\/li>\n\n\n\n
      3. Click SMTP & API<\/strong>.<\/li>\n\n\n\n
      4. Make sure you are on the API Keys<\/strong> tab.<\/li>\n\n\n\n
      5. Click Generate a new API key<\/strong>.<\/li>\n\n\n\n
      6. Give your key a recognizable name so you remember what it is for later, e.g. FooEmail Website<\/strong>.<\/li>\n\n\n\n
      7. Click Generate<\/strong>.<\/li>\n\n\n\n
      8. Brevo will display a long string of letters and numbers. Copy the entire API key<\/strong>.<\/li>\n<\/ol>\n\n\n\n

        Important:<\/strong> Keep this key safe. Brevo will only show you the full API key once for security reasons.<\/p>\n\n\n\n

        Connect FooEmail to Brevo:<\/strong><\/p>\n\n\n\n

          \n
        1. Log in to your WordPress admin dashboard<\/strong>.<\/li>\n\n\n\n
        2. Navigate to the FooEmail Settings<\/strong> page.<\/li>\n\n\n\n
        3. Find the Sender<\/strong> option and select Brevo<\/strong> from the dropdown list.<\/li>\n\n\n\n
        4. A new field labeled Brevo API Key<\/strong> will appear.<\/li>\n\n\n\n
        5. Paste the API key you copied from Brevo into the Brevo API Key<\/strong> field.<\/li>\n\n\n\n
        6. Complete the remaining sender details:\n
            \n
          • From Email<\/strong><\/li>\n\n\n\n
          • From Name<\/strong><\/li>\n\n\n\n
          • Reply-To<\/strong><\/li>\n<\/ul>\n<\/li>\n\n\n\n
          • Scroll down and click Save<\/strong>.<\/li>\n<\/ol>\n\n\n\n

            Test your connection<\/strong>
            \nOnce your settings are saved, it’s recommended to test the connection. Use FooEmail’s built-in email testing tool to send a quick test message to your own email address (Test Sending).<\/p>\n\n\n\n

            Frequently Asked Questions<\/h2>\n\n\n\n

            Q: When should you use FooEmail?<\/b>
            \nA:<\/b> Use FooEmail to keep your website from issues such as missing ticket emails, WooCommerce order emails going to spam, password reset emails not arriving, customers reporting they never received emails, or hosting providers blocking mail.<\/p>\n\n\n\n

            Q: Does FooEmail replace other SMTP plugins?<\/b>
            \nA:<\/b> Yes. FooEmail is designed to be a lightweight, all-in-one solution for WordPress email delivery and logging, specifically optimized for high-volume plugins like FooEvents.<\/p>\n\n\n\n

            Q: Why do I see “SMTP Error: Data not accepted”?
            \n<\/b>A:<\/b> This is a server-side rejection. It usually means your “From” email does not match your SMTP username, or you have hit a sending limit with your provider (e.g., Hostinger).<\/p>\n\n\n\n

            Q: Can I resend tickets that failed to send?
            \n<\/b>A:<\/b> Yes. If you have Log email content<\/b> enabled in the Privacy settings, you can open any log entry and click Resend<\/b> to attempt delivery again.<\/p>\n\n\n\n

            Plugin Privacy & Data Retention<\/h2>\n\n\n\n

            What data does FooEmail collect and store?<\/b><\/h4>\n\n\n\n

            When an email is generated by WordPress (via the <\/span>wp_mail<\/span><\/code> function), FooEmail intercepts the email to process it and records a copy in its internal log. The following information is collected and stored in the database for each email:<\/span><\/p>\n\n\n\n

              \n
            • Recipient Information:<\/b> Email addresses and names for the To, CC, and BCC fields.<\/span><\/li>\n\n\n\n
            • Sender Information:<\/b> Email addresses and names for the From and Reply-To fields.<\/span><\/li>\n\n\n\n
            • Email Content:<\/b> The subject line, raw email body (which may contain personal information depending on the context of the email, such as order details or user data), and email headers.<\/span><\/li>\n\n\n\n
            • Attachment Metadata:<\/b> Information about any files attached to the email.<\/span><\/li>\n\n\n\n
            • Technical Data:<\/b> The IP address (<\/span>REMOTE_ADDR<\/span><\/code>) of the user who triggered the email, the User ID (if logged in), the date and time the email was created\/sent, and the active WordPress hook context.<\/span><\/li>\n\n\n\n
            • Delivery Status:<\/b> Provider responses, error codes, and success\/fail statuses.<\/span><\/li>\n\n\n\n
            • Tracking Data:<\/b> If email open tracking is enabled, it may store the IP address and timestamp of when the recipient opened the email.<\/span><\/li>\n<\/ul>\n\n\n\n

              Where is the data stored?<\/b><\/h4>\n\n\n\n

              All email logs and configuration settings are stored locally within your WordPress site’s database. Specifically, log entries are kept in a dedicated custom table (<\/span>[wp_prefix]_fooemail_log<\/span><\/code>).<\/span><\/p>\n\n\n\n

              How long is data retained?<\/b><\/h4>\n\n\n\n

              FooEmail includes a built-in automated <\/span>Data Retention<\/b> feature. Site administrators can configure the plugin to automatically delete email logs that are older than a specific number of days.<\/span><\/p>\n\n\n\n

                \n
              • If the retention limit is configured, older logs are automatically and permanently purged from the database via a daily WordPress cron job.<\/span><\/li>\n\n\n\n
              • Administrators can also manually delete individual logs or empty the entire log database at any time via the WordPress admin dashboard.<\/span><\/li>\n<\/ul>\n\n\n\n

                Who is the data shared with?<\/b><\/h4>\n\n\n\n

                By design, FooEmail does not send any data to FooEvents or any unauthorized third parties. However, the core purpose of the plugin is to route emails to external Email Service Providers (ESPs).<\/span><\/p>\n\n\n\n

                Depending on how the site administrator configures the plugin, the email data (including personal information) will be securely transmitted to the chosen external provider:<\/span><\/p>\n\n\n\n

                  \n
                • Brevo:<\/b> If the Brevo integration is active, email data is sent to Brevo’s API for delivery.<\/span><\/li>\n\n\n\n
                • Custom SMTP:<\/b> If the SMTP integration is active, email data is transmitted to the configured SMTP server (e.g., SendGrid, Mailgun, Google Workspace, etc.).<\/span><\/li>\n<\/ul>\n\n\n\n

                  Site administrators should ensure that their chosen ESP is compliant with their local privacy laws (such as GDPR or CCPA) and include the ESP in their site’s privacy policy.<\/span><\/i><\/p>\n\n\n\n

                  Does FooEmail use cookies?<\/b><\/h4>\n\n\n\n

                  No, the FooEmail plugin operates entirely in the backend to route and log outgoing emails. It does not set any frontend cookies on the visitor’s browser.<\/span><\/p>\n\n\n\n

                  Exporting and Erasing Data<\/b><\/h4>\n\n\n\n
                    \n
                  • Export:<\/b> Currently, FooEmail does not include a built-in automated export tool. Site administrators can view email logs and their technical details directly within the WordPress dashboard for monitoring and troubleshooting.<\/span><\/li>\n\n\n\n
                  • Erasure:<\/b> Site administrators have full control over the stored data. They can permanently delete specific log entries or use the bulk <\/span>“Empty Log”<\/b> action to clear all stored email data at once. Additionally, the automated <\/span>Data Retention<\/b> feature can be configured to permanently purge old logs based on age or total count.<\/span><\/li>\n<\/ul>\n\n\n\n

                    Tip for Site Admins:<\/b> If your website processes transactions or user registrations, you should add a brief clause to your website’s Privacy Policy notifying your users that transactional emails (and their contents) are temporarily logged in your site’s database for delivery monitoring and troubleshooting purposes.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

                    FooEmail (currently in beta) is a free WordPress plugin for logging emails sent from your site and improving email deliverability using SMTP and Brevo. It helps ensure that mission-critical emails such as FooEvents tickets, WooCommerce orders, contact form submissions, and password resets reach your customers’ inboxes without being flagged as spam or blocked by hosting […]<\/p>\n","protected":false},"featured_media":0,"parent":938,"menu_order":10,"template":"","doc_tag":[],"class_list":["post-147418","docs","type-docs","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/docs\/147418","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"version-history":[{"count":42,"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/docs\/147418\/revisions"}],"predecessor-version":[{"id":148850,"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/docs\/147418\/revisions\/148850"}],"up":[{"embeddable":true,"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/docs\/938"}],"wp:attachment":[{"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/media?parent=147418"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/help.fooevents.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=147418"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}