• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Forwarding emails causes softfail on Gmail

Victor12

New Pleskian
HI!

I setup an email account into my Plesk 12 to automatic forwarding all emails to an gmail address. But Gmail put all mails received into the Spam folder.

I revised the mail Header and its a SPF softfail causes because my server is not rewritting the sender envelope.

How can I activate SRS on my Plesk or solve this issue?

Thanks!
 
Hi,
which email authentication protocols have you activated?
As Abdi suggested, SPF is one, but DomainKeys and/or DKIM and DNSr are always good to consider and activate too.
Use email tools as DNSstuff.com or many others you'll find in the Web which will make your email servers much more reliable.

Regards,
 
Hi Jorge! Thanks for replying.

I activated all security options but problem persists. More data.

Scenario:
- I have the domain mydomain.com correctly working on my Plesk 12 (Centos 7).
- I created new email address: [email protected]. All about this account works fine. I send mails and obtain SPF pass and DKIM validated.
- I activate the option to forwarding all mails received to [email protected] to [email protected].

When I access to my [email protected], All mails forwarded by my server go directly to the Gmail's Spam folder with an SPF softfail.

Take a look at this Example. I send a mail from [email protected] to [email protected]. This mail must be forwarded to [email protected]. This is the result.

Code:
Delivered-To: [email protected]
Received: by XX.XX.XX.XX with SMTP id z3csp1341637wjv;
        Mon, 23 Feb 2015 11:14:36 -0800 (PST)
X-Received: by XX.XX.XX.XX with SMTP id l12mr25111104wjr.139.1424718875839;
        Mon, 23 Feb 2015 11:14:35 -0800 (PST)
Return-Path: <[email protected]>
Received: from s1.mydomain.es (s1.mydomain.es. [X.XX.XX.X])
        by mx.google.com with ESMTPS id q8si19303121wiw.106.2015.02.23.11.14.35
        for <[email protected]>
        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
        Mon, 23 Feb 2015 11:14:35 -0800 (PST)
Received-SPF: none (google.com: [email protected] does not designate permitted sender hosts) client-ip=X.XX.XX.X;
Authentication-Results: mx.google.com;
       spf=none (google.com: [email protected] does not designate permitted sender hosts) [email protected];
       dkim=pass [email protected];
       dmarc=pass (p=NONE dis=NONE) header.from=yahoo.es
Received: (qmail 16737 invoked by uid 30); 23 Feb 2015 20:14:34 +0100
Delivered-To: [email protected]
Received: (qmail 16730 invoked from network); 23 Feb 2015 20:14:34 +0100
Received-SPF: none (no valid SPF record)
Received: from nm50-vm0.bullet.mail.ne1.yahoo.com (98.138.121.144)

I don´t know how to fix this.

Please, pay attention about the domain. My domain is mydomain.com but my server name is s1.mydomain.es. Could be this the cause?

Thanks!
 
Hi Victor12,

please check your SPF records. As you can see in the eMail, there is NONE configured for your domain ( which has to be done at the nameserver from your DOMAIN - provider and not only over the Plesk Control Panel.
 
We're observing this also. Situation is as described above.

* Domain example.org is hosted on a Plesk 12.5 server
* Email for [email protected] is configured to forward to [email protected]
* Domain example.org and example.com both have correctly configured SPF records for their (separate) mail hosting. SPF for example.org includes Plesk server 1.1.1.1, SPF for example.com includes external server 3.3.3.3
* Email is sent from [email protected] to [email protected]
* Plesk forwards this email to [email protected]
* Plesk does not rewrite the sender origin, so Gmail will evaluate this email as originating from example.com but received from 1.1.1.1

Resulting message headers look like this -

Delivered-To: [email protected]
Received: by 10.103.169.131 with SMTP id m3csp1252889vsh;
Mon, 20 Feb 2017 01:08:10 -0800 (PST)
X-Received: by 10.28.0.73 with SMTP id 70mr17063793wma.109.1487581690065;
Mon, 20 Feb 2017 01:08:10 -0800 (PST)
Return-Path: <[email protected]>
Received: from example.org (example.org. [1.1.1.1])
by mx.google.com with ESMTPS id k96si2846613wrc.18.2017.02.20.01.08.09
for <[email protected]>
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Mon, 20 Feb 2017 01:08:10 -0800 (PST)
Received-SPF: fail (google.com: domain of [email protected] does not designate 1.1.1.1 as permitted sender) client-ip=1.1.1.1;
Authentication-Results: mx.google.com;
spf=fail (google.com: domain of [email protected] does not designate 1.1.1.1 as permitted sender) [email protected]
Received: by example.org (Postfix, from userid 30) id AAEA6B00428; Mon, 20 Feb 2017 10:08:09 +0100 (CET)
X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from smtp.example.com (smtp.example.com [3.3.3.3]) by example.org (Postfix) with ESMTPS id 8FF17B0041D; Mon, 20 Feb 2017 10:08:09 +0100 (CET)
Received: from [3.3.5.7] (helo=mac-01452.example.com) by smtp.example.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.84_2) (envelope-from <[email protected]>) id 1cfjx3-0003oE-Aq; Mon, 20 Feb 2017 10:08:09 +0100
Content-Type: multipart/alternative; boundary="Apple-Mail=_21523DBF-FB9D-4B6B-B81D-E65A238390DD"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Example subject
From: External User <[email protected]>
In-Reply-To: <CAGB-W4hL8cFsN_PXQkCPkbVtn+yBYX9NJfCkoFnAGzGxGV3mqw@mail.gmail.com>
Date: Mon, 20 Feb 2017 10:08:31 +0100
Cc: Another User <[email protected]>
Message-Id: <[email protected]>
References: <CAGB-W4hL8cFsN_PXQkCPkbVtn+yBYX9NJfCkoFnAGzGxGV3mqw@mail.gmail.com>
To: Example User <[email protected]>
X-Mailer: Apple Mail (2.1878.6)
X-Original-Source-IP: 3.3.5.7
X-INED-Tid: 1cfjx3-0003oE-Aq

Is it possible to configure Plesk to autoforward in a way that does not fail SPF in this situation? It seems like Plesk would need to rewrite the message headers to alter the originating email address - but that feels problematic too?

Should [email protected] just configure their Gmail to retrieve messages from the mailbox [email protected]?
 
I have the same problem. Did someone find a solution for it?

My forwarded mails get this in the header (e.g. email from twitter forwarded to outlook.com, my server IP is replaced):
Received-SPF: Fail (protection.outlook.com: domain of bounce.twitter.com does not designate xxx.xxx.xxx.xxx as permitted sender)
 
Hi Atramasis,

such described issues ( with GMail - accounts! ) can as well happen, when you forward eMails from for example Twitter => Outlook365 => GMail => Your_Server . The fact is, that most of the time, there has been as well a DMARC - record setup, which "normally" shouldn't interfere with your SPF - record, but with forwarded eMails, GMail is not able to handle the setup as it should.

Pls. read for example: => https://productforums.google.com/forum/#!topic/gmail/fDJ0CbaU9Pw
The only solution I read about, was to remove one of the forwarders, but you might as well consider to contact Google itself, to investigate your issue(s) - the Plesk Community would be happy to read about other solutions/work-arounds as well!
 
In my case, there is no Gmail in the chain. It's more like Twitter => My Server => Outlook.com. In Outlook all mails go to junk folder and I think it could be because of SPF fail. Why is it saying "domain of bounce.twitter.com does not designate xxx.xxx.xxx.xxx as permitted sender"? It should by my domain and my IP or Twitter and their IP.
 
This is still a problem.

Plesk forwards the mail with from address from the original sender
[email protected] sends you an e-mail on [email protected]
you have a forward to [email protected]
gmail receives the mail and sees from [email protected] from your plesk server. But your plesk server isn't authorized to send mail from business.com
so gmail ditches the mail

you can't do anything about spf dkim dmarc because you don't manage the example domain business.com

plesk should forward the mail with from address [email protected]
 
Back
Top