Email forwarding: mailfwd2.zoneedit.com not updating.

grnbrg

New Member
I've created a new mail forward.

If I spam it with 10-20 test messages, roughly half go to the new defined target, and half are passed on to default *@domain catchall. All of the messages sent to the default are routed by mailfwd2. This has been the case for at least the last 24 hours.

It looks like the tool that updates the mail aliases is broken.
 

grnbrg

New Member
No. Mailing is originating from a work address.

Representative samples:
Code:
Delivered-To: grnbrg@gmail.com
Received: by 10.107.163.75 with SMTP id m72csp32402ioe;
Wed, 23 Sep 2015 10:34:16 -0700 (PDT)
X-Received: by 10.50.73.41 with SMTP id i9mr25477480igv.14.1443029653638;
Wed, 23 Sep 2015 10:34:13 -0700 (PDT)
Return-Path: <grnbrg@requiem.cc.umanitoba.ca>
Received: from mailfwd2.zoneedit.com (mailfwd2.zoneedit.com. [166.88.18.34])
by mx.google.com with ESMTP id kj6si1398411igb.35.2015.09.23.10.34.13
for <grnbrg@gmail.com>;
Wed, 23 Sep 2015 10:34:13 -0700 (PDT)
Received-SPF: neutral (google.com: 166.88.18.34 is neither permitted nor denied by best guess record for domain of grnbrg@requiem.cc.umanitoba.ca) client-ip=166.88.18.34;
Authentication-Results: mx.google.com;
spf=neutral (google.com: 166.88.18.34 is neither permitted nor denied by best guess record for domain of grnbrg@requiem.cc.umanitoba.ca) smtp.mailfrom=grnbrg@requiem.cc.umanitoba.ca
Received: from requiem.cc.umanitoba.ca (requiem.cc.umanitoba.ca [130.179.8.18])
by mailfwd2.zoneedit.com (Postfix) with ESMTP id 71DFE202555D
for <pagedt@grnbrg.org>; Wed, 23 Sep 2015 10:34:07 -0700 (PDT)
Received: by requiem.cc.umanitoba.ca (Postfix, from userid 2317)
id DAAA1431532E; Wed, 23 Sep 2015 12:34:04 -0500 (CDT)
Date: Wed, 23 Sep 2015 12:34:04 -0500
To: pagedt@grnbrg.org
Subject: Test 20-15
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20150923173404.DAAA1431532E@requiem.cc.umanitoba.ca>
From: grnbrg@requiem.cc.umanitoba.ca (Brian Greenberg)

This is a test.

and

Code:
Received: from UMCE3CIP01.ad.umanitoba.ca (130.179.21.17) by
UMCE3EXHC01.ad.umanitoba.ca (10.0.1.20) with Microsoft SMTP Server id
14.3.224.2; Wed, 23 Sep 2015 12:34:24 -0500
Received: from mailfwd1.zoneedit.com ([23.27.50.10]) by
UMCE3CIP01.ad.umanitoba.ca with ESMTP; 23 Sep 2015 12:34:08 -0500
Received: from requiem.cc.umanitoba.ca (requiem.cc.umanitoba.ca
[130.179.8.18]) by mailfwd1.zoneedit.com (Postfix) with ESMTP id 87DA2278626C
for <pagedt@grnbrg.org>; Wed, 23 Sep 2015 13:34:07 -0400 (EDT)
Received: by requiem.cc.umanitoba.ca (Postfix, from userid 2317) id
DECD4431532F; Wed, 23 Sep 2015 12:34:04 -0500 (CDT)
Date: Wed, 23 Sep 2015 12:34:04 -0500
To: <pagedt@grnbrg.org>
Subject: Test 20-16
User-Agent: Heirloom mailx 12.5 7/5/10
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <20150923173404.DECD4431532F@requiem.cc.umanitoba.ca>
From: Brian Greenberg <grnbrg@requiem.cc.umanitoba.ca>
Return-Path: grnbrg@requiem.cc.umanitoba.ca
X-MS-Exchange-Organization-AuthSource: UMCE3EXHC01.ad.umanitoba.ca
X-MS-Exchange-Organization-AuthAs: Anonymous
MIME-Version: 1.0

This is a test.



Brian.
 

grnbrg

New Member
I hate it when people report problems with email, and don't provide full headers.

Not going to be That Guy. :)


Brian.
 

grnbrg

New Member
I just created a brand new test mailforward. Identical behaviour.
mailfwd2.zoneedit.com sent test messages to the catchall address.
mailfwd1.zoneedit.com sent test messages to the newly defined forward address.

Edit: Created a second new test address, forwarded to a different domain. Same behaviour.

Brian.
 

sandy

Administrator
Staff member
something up on the Gmail side when sending. Our systems folks are looking into this presently

thanks
sandy
 

grnbrg

New Member
something up on the Gmail side when sending. Our systems folks are looking into this presently

thanks
sandy
GMail is not sending anything. They are the recipient for one half of the issue and completely uninvolved in the second.

The issue is between the server(s) running the customer control panel and the server(s) that receive and redirect mail as mailfwd2.
 

sandy

Administrator
Staff member
yes... resolution is in.

I am very sorry for the inconvenience

thanks
sandy
 
Top