Advertisement
Help Keep Boards Alive. Support us by going ad free today. See here: https://subscriptions.boards.ie/.
https://www.boards.ie/group/1878-subscribers-forum

Private Group for paid up members of Boards.ie. Join the club.
Hi all, please see this major site announcement: https://www.boards.ie/discussion/2058427594/boards-ie-2026

Gmail rejections driving me up the walls

  • 21-06-2026 07:24AM
    #1
    Registered Users, Registered Users 2 Posts: 7,725 ✭✭✭


    I have my own domain name and associated e-mail address, hosted on freehostia (for more than a decade). I use thunderbird for composition and sending of e-mails, and outgoing mail is routed through my ISP's SMTP server with SPF configured to allow this … at least for the seven IP addresses I know of.

    Lately, if I compose a new message in thunderbird and send it to a gmail address, it disappears. Not received, not bounced back, just "never happened"

    If I receive a message from a gmail address and reply, then that message goes through (with "sender authenticated" noted in the header of the reply) … sometimes. Other times, my message is flagged as spam in the gmail inbox. Or just not received. Or very occasionally, gets bounced back with a "sender not authenticated" notice if my ISP has added yet another IP address.

    WTF is going on? And how do I fix it? This is the account/e-mail address I use for all my creative/cultural stuff and in full festival season, I need to know that my recipients are getting the programme and planning info I send them.



Comments

  • Registered Users, Registered Users 2 Posts: 7,200 ✭✭✭DopeTech


    Detailed response from Gemini:


    What you are experiencing is the fallout of major, sweeping security updates implemented by Gmail, Yahoo, and other major email providers.
    In short, the old way of sending email (relying solely on basic SPF and an ISP’s SMTP server) is effectively dead. Gmail now aggressively filters or outright drops ("black-holes") emails that do not pass strict authentication standards. Because you are routing your emails through your ISP's SMTP server, your setup is failing these checks.

    Why Your Emails Are Disappearing

    Your current email setup relies on a fundamental contradiction that modern spam filters hate:

    Your Domain Name (Freehostia)  ——>  Sent via ISP SMTP (Vodafone, Comcast, etc.)  ——>  Gmail
    
    
    1. The SPF Game of Whack-a-Mole: You mentioned trying to maintain 7 IP addresses in your SPF record. ISPs dynamically change, load-balance, and add new outbound mail servers constantly. If your ISP routes your email through an 8th IP address you haven't whitelisted, your SPF fails, and Gmail rejects the email.
    2. Missing DKIM (The Real Culprit): Gmail now heavily relies on DKIM (DomainKeys Identified Mail). DKIM adds a cryptographic signature to the header of your email. Because you are composing in Thunderbird and blasting it through a generic ISP SMTP server, your emails lack a signature matching your Freehostia domain.
    3. No DMARC Alignment: Since your SPF is frequently broken and you have no DKIM, your emails fail DMARC alignment. When a message completely fails authentication, Gmail doesn't even bother putting it in the spam folder; it silently deletes it to protect users from phishing.
    4. Why Replies "Sometimes" Work: When you reply to an email, Gmail sometimes relaxes its rules slightly because an established conversation thread exists, or the routing header falls into a temporary "authenticated sender" cache.

    How to Fix It (The Permanent Solution)

    To guarantee festival planning info gets delivered, you need to stop using your ISP's SMTP server and align your records.

    Step 1: Switch Thunderbird to Freehostia’s SMTP

    Instead of using your ISP to send mail, use Freehostia’s actual outgoing mail servers. This ensures the email originates from the place that actually owns your domain.

    1. Open Thunderbird and go to Account Settings.
    2. Scroll down to Outgoing Server (SMTP).
    3. Edit your outgoing server (or add a new one) and input Freehostia’s official SMTP settings (usually mail.yourdomain.com or a specific Freehostia server string found in your Freehostia Control Panel).
    4. Use Port 465 (SSL/TLS) or Port 587 (STARTTLS) and enter your full Freehostia email password.

    Step 2: Set Up DKIM in Freehostia

    Log into your Freehostia Control Panel and check their Email Manager or DNS Manager.

    • Look for an option to Enable DKIM for your domain.
    • Freehostia will generate a TXT Record (it will look like a long string of random characters starting with v=DKIM1; p=...).
    • If Freehostia manages your DNS, it will apply automatically. If your domain's DNS is managed elsewhere (like Namecheap or GoDaddy), copy that TXT record over to your DNS provider.

    Step 3: Fix Your SPF Record

    Once you switch to Freehostia's SMTP, you can stop chasing your ISP's IP addresses. Update your domain's SPF TXT record to only include Freehostia.
    It should look something like this:

    v=spf1 include:freehostia.com ~all
    
    

    (Note: Check Freehostia's specific documentation to see if they prefer an include string or a specific IP range).

    Step 4: Add a DMARC Record

    Gmail now essentially requires a DMARC record to prove you take security seriously. Go to your DNS provider and add a new TXT Record:

    • Host/Name: _dmarc.yourdomain.com (make sure to include the underscore)
    • Value: v=DMARC1; p=none;

    💡

    Note:

    Setting p=none is a "monitoring" mode. It tells Gmail:

    "Hey, I have a DMARC policy, but if something fails, don't block it yet."

    This will immediately satisfy Gmail's basic security checks without risking blocking your own legitimate emails while you transition.

    Summary Checklist

    Once you make these changes, you can use a free tool like Mail-tester.com or MxToolbox. Send a test email from Thunderbird to the address they provide, and it will give you a scorecard showing if your SPF, DKIM, and DMARC are perfectly aligned. Do this before sending out the festival itinerary!



  • Registered Users, Registered Users 2 Posts: 7,725 ✭✭✭CelticRambler


    … or say fekkit and go back to old-school texting!

    But thanks. That sort of explains why things are so patchy.

    This isn't limited to any one particular event or one particular set of correspondents, and is entirely voluntary. Not sure I want to pay for separate smtp servers for every e-mail address I send from, so will have to re-think the whole situation.



Advertisement
Advertisement