Email Remail/Resending instead of Forwarding
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.
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
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.
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.
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.
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 have been locked on this page!