Skip to main content

Email piping stopped working

Has anyone seen this before, seems to have started recently.

We use Fluent Support with email piping. Mail arrives at my emailaddress say support@mydomain.com (Google Workspace) and is forwarded to our mailbox address whatever@fluent.support.

Any sender whose domain publishes a strict SPF record (-all) is rejected. Confirmed in our Google Workspace email log:

rejected by route2.mx.cloudflare.net [2606:4700:f5::e] β€” 550 5.7.1 2607:f8b0:4864:20::1148 isn't allowed to send email for theclient@theirdomain.com

The cause is standard SPF breakage on forwarding: the forwarding hop preserves the original envelope sender, so your Cloudflare inbound checks the sender's SPF record against a Google IP and rejects. The sender gets a bounce; we never see the ticket.

Niki Funch

Hello Marjan
I just saw I had got an e-mail from Jewel at the Support, saying that I had three e-mail accounts where e-mails are not being created as tickets.
To solve this, Fluent support team has created new forward inboxes for me, that I had to change in my CPanel.

And from now, it seems to be working. But they was flagged in their backlog or something, which caused them to sent me that e-mail.

Maybe you should contact the support team.

  • All e-mails did land in my different e-mail inboxes as normal, but they wasnt created as ticket answers. So no e-mails was lost though.