FAQ

Open FreddyMail > Designer, choose the WooCommerce email type (for example order confirmation, shipping or refund) and adjust logo, brand colors and content blocks via drag and drop, without writing HTML. Then send a test order in staging and review the real email in Gmail, Outlook and on a phone.

FreddyMail combines an HTML designer, SMTP delivery and logs in one plugin, so you do not need three separate plugins for design, delivery and diagnostics.

In the FreddyMail Designer open the New order or Order confirmation type and replace header, product table and footer via the block editor. Save, trigger a test order and review the result in the log.

Yes. The designer has a dedicated template for completed shipping with logo, brand colors, tracking number and optional content blocks.

Under FreddyMail > Sending choose SendGrid as the provider, paste the API key, set a verified sender address and send a test email. The log shows the provider response.

Pick Mailgun as the Pro provider, enter the API key and your verified Mailgun sending domain, then send a test mail. The log shows status code and Mailgun response.

Choose Amazon SES as the provider (Pro), enter IAM credentials and region and use a SES-verified domain or address as sender. Then send a test email and check the log entry.

Open FreddyMail > Logs first and check whether the email was generated at all. Common causes are a missing SMTP provider, wrong sender address, missing SPF or DKIM records or a competing SMTP plugin.

Configure SPF, DKIM and DMARC for your sender domain and use a real SMTP or API provider instead of PHP mail(). FreddyMail logs every outgoing email and shows the provider response to help with diagnostics.

FreddyMail > Logs lists every outgoing email with timestamp, recipient, email type, status, provider response and a resend action.

Yes. Every log entry has a resend action, provided the delivery configuration is correct.

SPF, DKIM and DMARC are three DNS records that legitimize your sender. Without them, Gmail, Outlook and other major providers filter almost every email to spam or block it. FreddyMail shows which records you need in the provider setup.

Under FreddyMail > Sending you find a test mail button with live debug output. Afterwards review the log entry and check the email in the recipient inbox.

Free covers SMTP delivery and logs. Pro unlocks the HTML designer, WooCommerce templates and additional premium providers. License and billing run through Freemius.

Current prices and plans are shown directly in the Freemius checkout and are authoritative there. The website mirrors the current plans.

Paste the license key from the Freemius purchase email under FreddyMail > License and activate it. If needed, look up the key in your Freemius account at users.freemius.com.

Yes. FreddyMail picks up emails sent through the WordPress wp_mail function. Developers register custom types through the freddymail_register_email_type filter and assign a template.

WP Mail SMTP and Fluent SMTP focus mostly on delivery. FreddyMail adds an HTML email designer, WooCommerce templates and an integrated log, so delivery, design and diagnostics live in one plugin.

No. FreddyMail is built for transactional WordPress and WooCommerce emails such as password reset, order confirmation or admin notifications. Newsletters belong to a dedicated newsletter tool.

Free supports classic SMTP with any SMTP host. Pro adds native API providers: SendGrid, Mailgun, Brevo and Amazon SES. Pick a provider in the Sending tab.

Upload the plugin ZIP under Plugins > Add New, activate FreddyMail and open the FreddyMail menu item in the WordPress admin. Configure delivery before using designs in production.

Open the dashboard, check delivery status, send a test email and review FreddyMail > Logs. The setup is only ready when the test email is logged successfully.

Yes, especially for WooCommerce or active membership sites. Test providers, designs and order emails in staging so real customers do not receive test emails.

This is not recommended. If two plugins handle mail delivery, logs and delivery behavior become hard to understand. Use only one delivery plugin in production.

You normally need administrator rights for setup, provider credentials, designs and logs.

Without configuration, WordPress often uses server mail. That is unreliable and hard to diagnose. SMTP or API delivery improves deliverability and troubleshooting.

SMTP is universal and quick to set up. API providers often provide clearer error codes, better scaling and more control.

SPF, DKIM and DMARC are configured at the domain or email provider and help recipients trust the sender.

The domain may not be verified, DKIM may be missing, the API key may be wrong, the provider may still be in sandbox mode or the sender address may not match the verified domain.

The provider accepted the email. It does not guarantee inbox placement because spam filters and recipient rules can still apply afterwards.

Check provider limits, reduce test bursts, avoid mass sending through transactional endpoints and contact the provider if the limit is too low.

Go to FreddyMail > Designer. Choose an existing template or create a new one in the library if available. Start with a preset, adjust background, header and body, save and send a test email.

Logo, mobile width, text contrast, link color, button rendering and spacing between sections. Then send test emails to Gmail, Outlook and a smartphone.

Email clients render HTML differently. The preview helps during design, but it does not replace a real test email.

Open FreddyMail > Email types, select the type, assign the matching template and then trigger the related WordPress or WooCommerce event.

Yes. Order confirmations, cancellations, refunds and admin notifications often need different templates.

Use a small, optimized image over HTTPS. It should be sharp on mobile without making the email unnecessarily large.

Yes, if the exported HTML is built for email clients. HTML from website builders often fails in Outlook, Gmail or mobile clients. Always send real test emails after importing.

An email type describes why a message is sent, for example password reset, new user account, WooCommerce order or a plugin email.

A plugin may generate mail in an unusual way or another delivery plugin may intercept it first. Check logs, active plugins and the triggering event.

Open the WordPress login page, start password reset for a test user and then check FreddyMail > Logs and the received email.

Create a test user or use staging. Then check whether FreddyMail recognizes the type and applies the correct template.

Yes. Developers register custom types with the freddymail_register_email_type filter. The type then appears under Email types, can receive a template and should be verified in the log with a real trigger.

Under FreddyMail > Logs. You can see timestamp, recipient, email type, status and provider responses or errors.

Under FreddyMail > Settings in the Logs & Data section you can delete all log entries and configure automatic retention.

As short as possible and as long as necessary. For many sites, 14 to 30 days is enough because logs may contain personal data.

Check whether WordPress created the email, whether FreddyMail is active and whether another SMTP or mail logging plugin takes over delivery first.

Check host, port, encryption, username, password, API key, sender domain and provider limits. Then send a test email and review the new log entry.

Yes, but remove secrets. Helpful details include error message, provider response, email type, timestamp, WordPress/PHP version and reproduction steps.

Success only means the provider accepted the email. Then check SPF, DKIM, DMARC, sender reputation, content, subject and the spam folder.

Create a product and a test order in staging. Change the order status so WooCommerce triggers emails. Then check FreddyMail > Logs and the delivered email.

Customer order confirmation, admin notification, completed order, cancelled order, failed order and refund.

Check whether WooCommerce generated the email, whether the mail type is enabled, whether FreddyMail is active and whether another SMTP or logger plugin interferes.

Check order status, WooCommerce email settings, customer address, log status, provider response and spam folder. Then repeat with a test order.

Yes. Customer emails should be clear, branded and readable. Admin emails may be more compact because they are operational.

Only with caution. Staging, test products, test customers and clearly marked test orders are better.

Payments, invoices, license keys, subscriptions, upgrades, downgrades and refunds are handled through Freemius.

In the Freemius account at users.freemius.com. Login usually uses the email address used for purchase.

Monthly and yearly licenses include support while the license is active. Lifetime licenses include 12 months of support.

In the Freemius account and usually in the purchase confirmation email. Use the purchase email address if you have multiple accounts.

The subscription no longer renews. Access to updates and support depends on the license model and Freemius status.

The refund policy shown in the Freemius checkout for FreddyMail is authoritative.

Logs may contain recipient address, subject, email type, timestamp, status and technical provider responses. Retention should therefore be limited.

If FreddyMail sends personal emails or stores logs on your WordPress site, your privacy policy should explain email delivery, the provider in use and the log retention period.

FreddyMail version, WordPress version, PHP version, provider, delivery method, affected email type, error message, relevant log entries and reproduction steps.

No. Never send SMTP passwords, API keys, Freemius secrets or private credentials through the support form.

Describe expected result, actual result, timestamp, affected domain, email type, provider response and whether production or staging is affected.

Freemius is the right contact for payment issues, invoices, subscription management, credit cards, tax details or refund processing.