Email Forwarding

How are you forwarding? Through webmail? Some client? Also, forward and delete or forward and save?

Using the same site/client, can you send outgoing mail normally? Also, do they show up in your inbox if they are not being forwarded?

I am using the settings within your webmail portal and tried forwarding to one account with the same result, and get the same thing when forwarding to my gmail account. It does the same thing whether forwarding and saving, or forwarding and deleting.  All emails that go to my Cox account along with my test emails which I try to forward go into my in box.   I am trying to auto forward and delete  so that I only have to set up and manage one email account on my smartphone devices and laptop.

How soon do you get the bounce back? I wonder if Cox's MTA(email server) is so backed up thats trying to send multiple times, and the server rejects the new send data in the headers. Its a long shot, but would fit the reports of delayed email so common on this forum over the last few weeks. Has this been happening long?

Also, who do you get the bounce back from? The full error message would help, or better yet, if you can post the headers. You can find these by clicking the "Detail" button with the email open in Webmail. Be sure to edit out any personal info.

The message originates from the email providers where the message is forwarded, and occurs immediately with a message returned that contains the error code:

Your message was rejected by mx1.inbox.hunttelecom.com(or my gmail account) for the following reason:

      Messages should have one or no Message-ID headers, not 2.

 The following recipients did not receive this message:

      <xxxxx@deltawavecomm.com>

  Please reply to <Postmaster@cox.net>

 if you feel this message to be in error.

Here are the details for a typical rejected email:

Reporting-MTA: dns; fed1rmfepi201.cox.net

Arrival-Date: Thu, 4 Dec 2014 10:00:53 -0500
Received-From-MTA: dns; fed1rmimpi112 (68.230.241.188)

Original-Recipient: RFC822;<xxxxxxx@cox.net>
Final-Recipient: RFC822; <xxxxxxx@cox.net>
Action: failed
Status: 5.1.1
Remote-MTA: dns; mx1.inbox.hunttelecom.com (173.212.61.109)
Diagnostic-Code: smtp; 550 Messages should have one or no Message-ID headers, not 2.
X-Actual-Recipient: RFC822; <xxxxx@deltawavecomm.com>

I fell down a google rabbit hole trying to figure this one out.  Everything I could find was either a email client issue, or script error from people who have automated email notification integrated into their website. Neither fit your case. Also checked http://postmaster.cox.net/ but they had no mention of the error. Finally, I tried forwarding my Cox email to my Gmail inside webmail, and sent a test message without any issues. I did notice that deltawavecomm.com is a Cox hosted website, but since your having the same issue forwarding to Gmail, I don't see how that is relevent. The only thing I can figure is it's some kind of bug with the webmail that is effecting just you, or isolated groups. I just don't know why.

Can you send a normal message to XXX@deltawavecomm.com via webmail? 

Also, it seems Classic webmail doesn't show the full headers, but some slimmed down version. Can you log into Enhanced Webmail and from inside email > Options > View Source. My test email headers below for comparison

Last, when did you send the email example above? Was it on Dec 4th?

Return-Path: <xxxxx@gmail.com>
Received: from eastrmimpi211 ([68.230.241.252]) by eastrmfepi202.cox.net
(InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP
id <20141217150517.WLCD14861.eastrmfepi202.cox.net@eastrmimpi211>
for <xxxxxxx@cox.net>; Wed, 17 Dec 2014 10:05:17 -0500
Received: from mail-qg0-f43.google.com ([209.85.192.43])
by eastrmimpi211 with cox
id Uf5E1p01K0weFsp01f5Ffy; Wed, 17 Dec 2014 10:05:15 -0500
Message-Id: <Uf5E1p01K0weFsp01f5Ffy>
X-CT-Score: NA
X-Authority-Analysis: v=2.0 cv=A9qyydqG c=1 sm=1 a=pGLkceISAAAA:8
a=A92cGCtB03wA:10 a=k2GXVZ5VwK86dXqfSkUA:9 a=QEXdDO2ut3YA:10
a=P_Pa8KEnoS0A:10 a=HjUhbfr36v4A:10 a=hwRSXJ7R/se50RLk3JJFug==:117
X-CM-Score: 0.00
Received: by mail-qg0-f43.google.com with SMTP id z107so895511qgd.2
for <xxxxxxxx@cox.net>; Wed, 17 Dec 2014 07:05:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=mime-version:date:message-id:subject:from:to:content-type;
bh=vqhXQR6ZwI+poQALpseTs6lOEsyJYl3uwEJdOZPetsU=;
b=MOkCVrxdqrd8UKamaNBdNy0UPulEwD73JUnmO0mDvIMVHTbaZ0rp1EwXdb7J5/v3UR
kC7VxKfA7QthxdaBzdvhy7+UIUE5A3oGBLNvsYpQzzJq5R8Yu8P45j20P4J0OZgLoHqb
sjlpTGdSrPDeBXlIKN7SKYwjbqKybOxK4pv+dlXIepvitm4CQOZNINZo61NvQxmlHLfI
a8U6m8ToC0OkBhgUlfk/mvjpw/HZDU7bcdB7L9cIZPXu5IqlWifpfaeO/CaiwIKeccMa
Ugchd6xUBuv0LxZgVANr5rzInhgOu9kY2IkFPDQWbcr0Zhhd89QrrxwEFKQbxvyzPROc
gvGw==
MIME-Version: 1.0
X-Received: by 10.224.67.132 with SMTP id r4mr13099816qai.1.1418828716417;
Wed, 17 Dec 2014 07:05:16 -0800 (PST)
Received: by 10.229.176.135 with HTTP; Wed, 17 Dec 2014 07:05:16 -0800 (PST)
Date: Wed, 17 Dec 2014 10:05:16 -0500
Message-ID: <CAPgJdqsz1-oXffZ95k4RPgZC3fGf9Ft5-uiQa41gmC8CPh3DFA@mail.gmail.com>
Subject: test 2
From: Me <xxxxxx@gmail.com>
To: xxxxxxx@cox.net
Content-Type: multipart/alternative; boundary=001a11c3dd5ea3a876050a6acd55

Good evening:

The following was shared with me by one of my email providers - Hunt Telecom out of New Orleans:

"Cox.Net is forwarding messages without implementing the sender-rewrite scheme. Wildblue.net  has published a strict SPF policy entry that indicates only certain IP addresses are allowed to send mail from that domain.

Since Cox.net is forwarding the mail without rewriting the sender,  the forwarded e-mail message

violates  Wildblue.net's  policy   regarding what mail server IP address is allowed to send the message."

Does this help?  Everything was working fine until about a week prior to my post.  Perhaps Cox changed something in the meantime?