Paper Lantern for cPanel accounts is being retired this year. Find out more »
cPanel & WHM Version 102 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!
This object is in archive! 

Email Remail/Resending instead of Forwarding

inspyre shared this idea 8 years ago
Needs Feedback

A plain message forward, as cPanel currenly uses for forwarding emails, simply redirects the email without changing any email headers. This often results in the email being flagged by anti-spam filters (including Gmail). Often this is because the sending IP doesn't match the sending domain's SPF records (for obvious reasons).


Remailing or resending would solve this problem, as the email would then be sent from an account on the cPanel server, with a reply-to address of the original sender, allowing it through spam filters and the emails would pass SPF checking.


cPanel should implement remailing in place of plain message forwarding, or at the very least in addition to forwarding, so that forwarded emails are less likely to be marked as spam at their final destination.

Best Answer
photo

I am confused. The behavior you're requesting (Additional "Received:" headers to indicate the mail's path) exists, and would actually be a violation of RFC to not have this included. Further, it's not something we can even control. It's a responsibility of the receiving server (GMail/etc in your example) to indicate and add these headers this so that the sender can't falsify them. We (cPanel & WHM) can't affect this since it's a receiver's duty to track that history.


The only case where this does not happen is where the forwarder destination is still local to the machine, at which point another "Received:" header isn't necessary/valid and it just copies the mail to the forwarder mailbox.


For all intents and purposes, Exim does "remail/resend" forwarded mail. It's the only way to send mail on. There's no difference in how the actual SMTP delivery occurs between a regular email or a forwarded email.


If you can provide very specific examples with headers to demonstrate what you're speaking of, perhaps I can better answer your inquiry. However, the behavior you're requesting is inherent in SMTP and Exim and therefore cPanel & WHM.


2014-06-30 UPDATE:

Further discussion internally has brought up that you may be requesting SRS support (Sender Rewriting Scheme)


http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme


Is this the case? If so, I can adjust the feature request accordingly to describe and cover this.

Replies (1)

photo
1

I am confused. The behavior you're requesting (Additional "Received:" headers to indicate the mail's path) exists, and would actually be a violation of RFC to not have this included. Further, it's not something we can even control. It's a responsibility of the receiving server (GMail/etc in your example) to indicate and add these headers this so that the sender can't falsify them. We (cPanel & WHM) can't affect this since it's a receiver's duty to track that history.


The only case where this does not happen is where the forwarder destination is still local to the machine, at which point another "Received:" header isn't necessary/valid and it just copies the mail to the forwarder mailbox.


For all intents and purposes, Exim does "remail/resend" forwarded mail. It's the only way to send mail on. There's no difference in how the actual SMTP delivery occurs between a regular email or a forwarded email.


If you can provide very specific examples with headers to demonstrate what you're speaking of, perhaps I can better answer your inquiry. However, the behavior you're requesting is inherent in SMTP and Exim and therefore cPanel & WHM.


2014-06-30 UPDATE:

Further discussion internally has brought up that you may be requesting SRS support (Sender Rewriting Scheme)


http://en.wikipedia.org/wiki/Sender_Rewriting_Scheme


Is this the case? If so, I can adjust the feature request accordingly to describe and cover this.

photo
1

Hi Brian and cPanel team


I came to this post after doing a search on Google and experiencing a problem which seems very similar to what inspyre is hinting to and may explain his suggestion.


Currently, the vast majority of my domain e-mails sent through my hosting company - set using cPanel - are arriving at the destination's mailserver identified with my ISP's home IP as a Source IP. To me, it looks as if their server's behaviour is like a plain mail forwarding, instead of remailing/resending, although it actually adds additional "Received:" headers.


The problem is that my ISP's home IP is still identified as the Source IP. This happens regardless of whether I send my domain's e-mails using the Outlook client or the hosting company's webmail, unlike if I send an e-mail using my Outlook.com account and regardless of whether I use the Outlook client or webmail. When I send an Outlook.com or even a Gmail.com e-mail, the Source IP is always the mailserver's.


This behaviour is sometimes causing my domain's e-mails being flagged by Gmail mailservers as "not being able to confirm that it was sent from the domain instead of a spam creator", although they still arrive at the destination's inbox, also sometimes ending in SPAM boxes of e-mails hosted with other hosting companies and - worse - vanishing completely without arriving at any recipient's boxes based on a Microsoft server - not even SPAM - or me getting any failed delivery error messages returned. Since all ISP's domestic IPs are listed on the Spamhaus Project's PBL list and since Microsoft uses this list to filter SPAM, they just get "erased".


What I find strange is that I would expect any major hosting company's mailserver to behave like Outlook's and Gmail's but - in my case - it is not. I would really like to understand what is going on and why my hosting company's mailserver is behaving like this, since support staff is not being very forthcoming with any solution at all, other than trying to sell me an additional service while giving me a standard reply that "our server is being blocked by Microsoft".


Funny enough, their support e-mails always arrive at my Outlook inbox.


If you or anyone at cPanel's team could shed some light into this issue, I would really appreciate it.


Thanks in advance.

Tiago Figueiredo


------------


The following are some header examples, where I've just replaced e-mail addresses for privacy:


Sending a domain hosted e-mail using the Outlook client:


Delivered-To: myname@gmail.com

Received: by 10.28.1.68 with SMTP id 65csp77651wmb;

Tue, 30 Aug 2016 16:45:39 -0700 (PDT)

X-Received: by 10.237.49.5 with SMTP id 5mr7551246qtg.136.1472600739826;

Tue, 30 Aug 2016 16:45:39 -0700 (PDT)

Return-Path: <myname@mydomain.com.br>

Received: from a2nlsmtp01-01.prod.iad2.secureserver.net (a2nlsmtp01-01.prod.iad2.secureserver.net. [198.71.224.24])

by mx.google.com with ESMTPS id v68si29494071qkd.230.2016.08.30.16.45.39

for <myname@gmail.com>

(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);

Tue, 30 Aug 2016 16:45:39 -0700 (PDT)

Received-SPF: pass (google.com: domain of myname@mydomain.com.br designates 198.71.224.24 as permitted sender) client-ip=198.71.224.24;

Authentication-Results: mx.google.com;

dkim=temperror (no key for signature) header.i=@mydomain.com.br;

spf=pass (google.com: domain of myname@mydomain.com.br designates 198.71.224.24 as permitted sender) smtp.mailfrom=myname@mydomain.com.br

Received: from a2plcpnl0318.prod.iad2.secureserver.net ([198.71.230.75])

by : HOSTING RELAY : with SMTP

id eshqbDcoZJZqHeshqbcsf3; Tue, 30 Aug 2016 16:44:38 -0700

DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;

d=eyebrand.com.br; s=default; h=Content-Type:MIME-Version:Message-ID:Date:

Subject:To:From:Sender:Reply-To:Cc:Content-Transfer-Encoding:Content-ID:

Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc

:Resent-Message-ID:In-Reply-To:References:List-Id:List-Help:List-Unsubscribe:

List-Subscribe:List-Post:List-Owner:List-Archive;

bh=nBZTk+lhWpdoyEl6pLCDMnDujWHMKUz8gin/XZbHEJE=; b=AQ9YzfiQ/dgLR+Bi1VuHhbZVER

Lcz3BcwvNRRvAf9F9ufOYU1XZb1SIjpIP9b5Zb48nI5nAYgaON4eN5Q00bZ4y71NzyvsdgFragSWJ

OAba985mGzn3qJaupyXqBfSscAGRg6YLA98DbahpQmA3ukPUOdLEeJSO+rCLK+eu5PrUzud0BFW5S

tGi3muz4AFatNC5BY50r6fve8Hvyy3eqY0t8OKPaAM/tCPlSiNhjvBn1IWpZd7Q2CTv0zKIIIOWvJ

CmQJTtl7ff7fOve/DR384lV/BEeHha1Lx5m38avz33WpghScoTfbsZuJuuCJmh4ZjW8BHW2tIMY7L

8YHC8l+g==;

Received: from [201.6.229.48] (port=29434 helo=mydomain)

by a2plcpnl0318.prod.iad2.secureserver.net with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)

(Exim 4.87)

(envelope-from <myname@mydomain.com.br>)

id 1beshq-002YeO-GQ

for myname@gmail.com; Tue, 30 Aug 2016 16:44:38 -0700

From: "My Name" <myname@mydomain.com.br>

To: <myname@gmail.com>

Subject: teste

Date: Tue, 30 Aug 2016 20:44:33 -0300

Message-ID: <000a01d20318$7ae08a80$70a19f80$@mydomain.com.br>

MIME-Version: 1.0

Content-Type: multipart/alternative;

boundary="----=_NextPart_000_000B_01D202FF.55957560"

X-Mailer: Microsoft Outlook 16.0

Thread-Index: AdIDGGS/LAGTo/N2TLG6tOnhZ9HIuw==

Content-Language: pt-br

X-AntiAbuse: This header was added to track abuse, please include it with any abuse report

X-AntiAbuse: Primary Hostname - a2plcpnl0318.prod.iad2.secureserver.net

X-AntiAbuse: Original Domain - gmail.com

X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]

X-AntiAbuse: Sender Address Domain - mydomain.com.br

X-Get-Message-Sender-Via: a2plcpnl0318.prod.iad2.secureserver.net: authenticated_id: myname@mydomain.com.br

X-Authenticated-Sender: a2plcpnl0318.prod.iad2.secureserver.net: myname@mydomain.com.br

X-Source:

X-Source-Args:

X-Source-Dir:

X-CMAE-Envelope: MS4wfG6Z1lGtilMZzhhAtJL80hKn0/FC2y3ut3JvICA4B4f1UaTJSkCcgtRy/Rp8cU0Q2hvl+LMYwxOxdA2EtU1VLFZaZs2frlWnMIAd4uzFU3dqURR58z+P

2ZuPHJcJ0qrxM1aT/sd9DiefafuqQTKhGmrYi++nQX6z4JZaU2sz0IUnB9hTS75FArtKl/GHlTQUh3r7Iu4wjfs/P87sR5VUTOZXp9SlPwxydqFRuK6SQz3R


Sending a domain hosted e-mail using webmail:


Delivered-To: myname@gmail.com

Received: by 10.28.1.68 with SMTP id 65csp105619wmb;

Tue, 30 Aug 2016 18:31:38 -0700 (PDT)

X-Received: by 10.200.47.253 with SMTP id m58mr8167216qta.60.1472607098753;

Tue, 30 Aug 2016 18:31:38 -0700 (PDT)

Return-Path: <myname@mydomain.com.br>

Received: from a2nlsmtp01-01.prod.iad2.secureserver.net (a2nlsmtp01-01.prod.iad2.secureserver.net. [198.71.224.24])

by mx.google.com with ESMTPS id o129si29955275qka.188.2016.08.30.18.31.38

for <myname@gmail.com>

(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);

Tue, 30 Aug 2016 18:31:38 -0700 (PDT)

Received-SPF: pass (google.com: domain of myname@mydomain.com.br designates 198.71.224.24 as permitted sender) client-ip=198.71.224.24;

Authentication-Results: mx.google.com;

dkim=temperror (no key for signature) header.i=@mydomain.com.br;

spf=pass (google.com: domain of myname@mydomain.com.br designates 198.71.224.24 as permitted sender) smtp.mailfrom=myname@mydomain.com.br

Received: from a2plcpnl0318.prod.iad2.secureserver.net ([198.71.230.75])

by : HOSTING RELAY : with SMTP

id euMPbEYQvJZqHeuMPbdYoK; Tue, 30 Aug 2016 18:30:37 -0700

DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;

d=mydomain.com.br; s=default; h=Message-ID:Subject:To:From:Date:

Content-Transfer-Encoding:Content-Type:MIME-Version:Sender:Reply-To:Cc:

Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender:

Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id:

List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;

bh=IZzGk5hdbwv1XsfTE2Dngp1hMDfBwbnO3RaSFfeDt+k=; b=mnx4BW8mgchGZTMcPVQBuxHD8

6MnPkuDilganZKzPs+DqU3tXBZR0veYlS2GTUDXEb2zVqrd9JbAR3nAK3pn3L8exFZHCOrOlB5OnL

YeJ8WZrcss+RcJRNNxaTlyXpMOtYI2/E+bH9Ch7xqZ1oGODQwaaxC/p1mYRsMh/uh8c+3C3Uol9rn

TtwJ2zCgTayNquFI8h4Q3TWm1NtofoK8KeTuXS7Mb80/SOqJZL1NK23y0Cyi4rWudCq4e5mEjT4df

+84xnpVzOS+8lx4nP+Vm94YJ2iTIaWVsmIdGcaiFRy43esZWy+0l0r2tbWXdy77TajwB5V6Eylwbf

f4w8eD5zA==;

Received: from [127.0.0.1] (port=55665 helo=a2plcpnl0318.prod.iad2.secureserver.net)

by a2plcpnl0318.prod.iad2.secureserver.net with esmtpa (Exim 4.87)

(envelope-from <myname@mydomain.com.br>)

id 1beuMO-003Es2-Uv

for myname@gmail.com; Tue, 30 Aug 2016 18:30:36 -0700

MIME-Version: 1.0

Content-Type: text/plain; charset=US-ASCII;

format=flowed

Content-Transfer-Encoding: 7bit

Date: Tue, 30 Aug 2016 19:30:31 -0600

From: myname@mydomain.com.br

To: myname@gmail.com

Subject: teste

Message-ID: <9716802bf2952b2b63de5025b7c7dc4b@mydomain.com.br>

X-Sender: myname@mydomain.com.br

User-Agent: Roundcube Webmail/1.1.4

X-AntiAbuse: This header was added to track abuse, please include it with any abuse report

X-AntiAbuse: Primary Hostname - a2plcpnl0318.prod.iad2.secureserver.net

X-AntiAbuse: Original Domain - gmail.com

X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]

X-AntiAbuse: Sender Address Domain - mydomain.com.br

X-Get-Message-Sender-Via: a2plcpnl0318.prod.iad2.secureserver.net: authenticated_id: myname@mydomain.com.br

X-Authenticated-Sender: a2plcpnl0318.prod.iad2.secureserver.net: myname@mydomain.com.br

X-Source:

X-Source-Args:

X-Source-Dir:

X-CMAE-Envelope: MS4wfDqBEi1RQ/epl5GfKfjsrrjOqBYOqv+acAM6PhcX5o0lUueftTdID3Ie+sPE4phK/IHwiT1JmWBEhncnsGbLyKpJe3QC9R+2mNvO3fx5pe8QYIAnKtM2

3wmLIBISoqpU9NsFNWeLQzjIYM5B2uvu0HsAU9ypTvB8srWoiKhdH2HNMHFhadNrrndleHSotGcSBOQxfbKoFupWeOQA9spv2/rIiIdPLUBB/MOkt2GTAyod


Sending an Outlook.com e-mail using Outlook client:


Received: (qmail 16096 invoked by uid 30297); 31 Aug 2016 00:07:40 -0000

Received: from unknown (HELO sg2plibsmtp01-1.prod.sin2.secureserver.net) ([182.50.144.33]) (envelope-sender <myname@outlook.com>) by sg2plsmtp19-01.prod.sin2.secureserver.net (qmail-1.03) with SMTP for <myname@mydomain.com.br>; 31 Aug 2016 00:07:40 -0000

Received: from BAY004-OMC3S23.hotmail.com ([65.54.190.161]) by sg2plibsmtp01-1.prod.sin2.secureserver.net with bizsmtp id dc7e1t00N3VNx5501c7fLf; Tue, 30 Aug 2016 17:07:40 -0700

Received: from BAY407-EAS31 ([65.54.190.188]) by BAY004-OMC3S23.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Tue, 30 Aug 2016 17:07:38 -0700

X-TMN: [cOoPN7IynkZ9ZdEQViDflzCLNqpsRcjT]

X-Originating-Email: [myname@outlook.com]

Message-ID: <BAY407-EAS31F6B95784696885F0B13088E30@phx.gbl>

Return-Path: myname@outlook.com

From: My Name <myname@outlook.com>

To: <myname@mydomain.com.br>

Subject: teste

Date: Tue, 30 Aug 2016 21:07:39 -0300

MIME-Version: 1.0

Content-Type: multipart/alternative; boundary="----=_NextPart_000_0048_01D20302.8ABD10B0"

X-Mailer: Microsoft Outlook 16.0

Thread-Index: AdIDG673bgm42/dWTY2aI+e3WxTTJQ==

Content-Language: pt-br

X-OriginalArrivalTime: 31 Aug 2016 00:07:38.0184 (UTC) FILETIME=[AEFAD480:01D2031B]

X-Nonspam: None

photo
Leave a Comment
 
Attach a file