Forum

Hi,

The "FIX" made to email forwarding around October 1st seems to be stripping out the originating headers from forwarded email.  Can you please set email forwarding to NOT strip out the originating headers?  Thanks.

Hello,

We have updated the email forwarding code, so this should resolve the issue.

Please let us know if you're still experiencing the same issue.  Send an email to [email protected].

Best Regards,
Dynadot Staff

I have the same problem as a_c_d_i_montrose_us_1 , and it started at the same time.  Today, June 30th, all of my emails forwarded from Dynadot display a "From" field that's not the address of the original sender, and the "To" and "Subject" fields are missing.

All of my forwarded emails through the afternoon of June 29th were fine.  But my forwarded emails starting early the morning of June 30th all have the same problem.

As groovy_md_us has reported, email coming into my domain is not being forwarded correctly.  It appears to be formatted improperly.  When I send mail directly to my ISP, it comes through correctly.  The problem started about 9:00pm EDT June 29, 2011.  Please help.

Thanks for the info

Thank you.  That information helped a lot.  The issue should now be resolved.

Additional info. I think Dynadot is causing the problem and has been for many months.

Here's part of the message source from an email that I configured one of my Dynadot domains to forward to a different email provider.

Received: from snd118155.britecast.com (64.88.181.55)
       by parkmail.dynadot.com with SMTP; 28 Jun 2011 17:47:05 +0000DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; s=c2m; d=microcentermail.com;

Where I highlighted above, it looks like Dynadot does not insert carriage return and newline characters (or similar) at the end of the info it inserts into the message header.

I just looked through the message source for my old email to see when the problem started. It started right around December 1, 2010.

Here's an example from November 22, 2010. Formatting is good.

Received: from mpja1.com (68.157.82.197)
       by parkmail.dynadot.com with SMTP; 23 Nov 2010 09:59:26 -0000
Received: from mpja1.com (unverified [127.0.0.1])

Here's another example from December 1, 2010. Formatting is bad.

Received: from relay00.pair.com (209.68.5.9)
       by parkmail.dynadot.com with SMTP; 1 Dec 2010 05:19:29 +0000Received: (qmail 16149 invoked by uid 0); 1 Dec 2010 05:19:25 -0000

Hope this helps.

Thanks.

Email that I forward to the same email provider from several other sources does not exhibit the problem.

Thanks.


 [This post has been edited by groovy_md_us on Jun 29, 2011 2:38pm.]

Hello,

We haven't changed our mail code in months.  I don't actually see the error when sending a test email.  Is it possible the receiving server is causing the formatting errors?

Best Regards,

Dynadot Staff

Resurrecting this topic. Recently, headers of forwarded email seem to have a formatting error. According to the email provider that I'm forwarding Dynadot email to:

parkmail.dynadot.com is scrambling the headers:

Received: from 74.69.219.209.transedge.com (209.219.69.74)
       by parkmail.dynadot.com with SMTP; 27 Jun 2011 20:00:09 +0000Received: from [236.20.28.53] (account [email protected] HELO cinuhi.tvjlbcb.biz)
       by 74.69.219.209.transedge.com

Notice how that "Received" line includes a previous "Received" line.

>- 27 Jun 2011 20:00:09 +0000Received: from

The two lines are run together.  The Dynadot server is inserting its "Received" line *in front of* the previous line, instead of inserting the information *above* the previous line like it is supposed to.

Those lines should look like this:

Received: from 74.69.219.209.transedge.com (209.219.69.74)
       by parkmail.dynadot.com with SMTP; 27 Jun 2011 20:00:09 +0000
Received: from [236.20.28.53] (account [email protected] HELO cinuhi.tvjlbcb.biz)
       by 74.69.219.209.transedge.com

Quick update.  I have tested the revised headers pretty extensively over the past few weeks.  So far, your new settings work perfectly.  No more unexpected munging.  Thanks!