• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 2699
  • Last Modified:

malformed email header stopping e-mail from entering major ISP's What is wrong with this header?

This header get into gmail and other mail programs, but gets blocked by AOL, verizon, comcast, or Network solutions web based e-mail programs.  It is not sent to the users spam box but is rejected by the ISP even before the letter enters their system.

This e-mail does make it to my personal box, and others like hotmail, but will not make it to the other ISPs like AOL.

I think something is wrong with this header.

X-Account-Key: 	account3	
X-UIDL: 	1b66c3af33e39ee3	
X-Mozilla-Status: 	0001	
X-Mozilla-Status2: 	00000000	
Return-Path: 	<taf@wiz.WIZARDPROGRAMS.COM>	
X-Original-To: 	jon@thralow.com	
Delivered-To: 	jthralow@mail.dodaday.com	
Received: 	from wiz.WIZARDPROGRAMS.COM (unknown []) by mail.dodaday.com (Postfix) with ESMTP id ED77311974010 for <jon@thralow.com>; Thu, 20 Sep 2007 10:05:47 -0500 (CDT)	
Received: 	from taf by wiz.WIZARDPROGRAMS.COM with local (Exim 4.68) (envelope-from <taf@wiz.WIZARDPROGRAMS.COM>) id 1IYNb9-0001uI-1j for jon@thralow.com; Thu, 20 Sep 2007 10:05:47 -0500	
To: 	jon<jon@thralow.com>	
From: 	jthralow@gmail.com	
Subject: 	test	
MIME-Version: 	1.0	
Content-Type: 	text/html; boundary="8=--"	
Message-Id: 	<E1IYNb9-0001uI-1j@wiz.WIZARDPROGRAMS.COM>	
Date: 	Thu, 20 Sep 2007 10:05:47 -0500	
X-AntiAbuse: 	This header was added to track abuse, please include it with any abuse report	
X-AntiAbuse: 	Primary Hostname - wiz.WIZARDPROGRAMS.COM	
X-AntiAbuse: 	Original Domain - thralow.com	
X-AntiAbuse: 	Originator/Caller UID/GID - [32004 509] / [47 12]	
X-AntiAbuse: 	Sender Address Domain - wiz.WIZARDPROGRAMS.COM

Open in new window

  • 5
  • 3
1 Solution
What error do you get when they reject the mail?

You could send a test to me at test@cdlive.co.uk and I can check all the headers, rbls etc...
jthralowAuthor Commented:
I do not get any error no bounce that I can find it just seems to go into a hole.
It would make more sense if it ended up in a spam filter, but it does not get that far.

This header is generated from a Perl script and I assume it is from the header as It makes it fine to most ISPs just these large ones do not like something about it.

Are there carriage returns and line feeds in the transcript?  (There don't appear to be any).
We Need Your Input!

WatchGuard is currently running a beta program for our new macOS Host Sensor for our Threat Detection and Response service. We're looking for more macOS users to help provide insight and feedback to help us make the product even better. Please sign up for our beta program today!

jthralowAuthor Commented:
I think the formating may be off from uploading it here.
I can send something to you directly if you would like.

Did you send the test email to me?
Please post here if you do send it.
jthralowAuthor Commented:
I have sent a few tests to you.
Let me know what you find.
1) Received: from 7610.wingsix.com (unknown [])
The email is coming from the IP address above but there does not seem to be a reverse DNS (PTR record) associated with it. You should contact whichever ISP provided this IP address to you and ask them to set a PTR record for it pointing back to 7610.wingsix.com.

2) The 7610.wingsix.com address the emails are coming from does not exist. You will need to create it.

You were not on any RBLs and the actual email did not trigger and spam rules other than it only contained a html email and no plain text version aswell.

I suggest you fix those two dns issues. and then implement SPF (www.openspf.org) which is just a TXT entry in the DNS. And then after 24 hours to allow the DNS changes to take effect go to http://www.dnswl.org and add your IP address to the free whitelist.
jthralowAuthor Commented:
I am on it.  I will see if that solves the issue.
jthralowAuthor Commented:
That did it grblades.
It was a DNS issue that held the letters back from the Major ISPs.
They are all going through now.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

WEBINAR: GDPR Implemented - Tips & Lessons Learned

Join the WatchGuard team on Thursday, March 29th as we recount some valuable lessons learned in weighing the needs of a business against the new regulatory environment, look ahead at the two months left before implementation, and help you understand the steps you can take today!

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now