RE: RES: RES: Email oddity -- MIDRANGE-L

My suggestion is to give it time. If the SysAdmin did get the PTR correct,
this should all be solved over the next few hours. Seems that the unknown
is (can be) an effect of lack of rDNS. What might be happening is that
there are superficial servers now seeing the rDNS, but it hasn't made its
way into the heart yet.

Of course, I'm hanging on to the assumption that that's the current issue.
Could be wrong, and there could be another behind this one. If possible
(and I stole this phrase from my research this evening) that SysAdmin should
be hit with a clue-by-four. Maybe spend some time with a mail admin that's
done it for a living.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"April 1. This is the day upon which we are reminded of what we are on the
other three hundred sixty-four."
-- Mark Twain

Full headers with message originating from the i, but private email as
original sender. I see two interesting entries. Return-Path and still
see unknown as response to HELO.

John McKee

Return-Path: <>
Received: from mail7.wildflower.net (mail7.wildflower.net
[24.249.116.47])by mail8.wildflower.net (IceWarp 10.0.7) with ESMTP id
WZB12617 for <JMMCKEE@xxxxxxxxxxxxxx>; Fri, 13 May 2011 15:14:17 -0500
X-ASG-Debug-ID: 1305317657-285a9d280001-7i1fjv
Received: from BAXTER.X.X.NET ([X.X.X.X]) by mail7.wildflower.net
with ESMTP id 0Zl3ySRL22YCVtaE for <JMMCKEE@xxxxxxxxxxxxxx>; Fri, 13
May 2011 15:14:17 -0500 (CDT)
X-Barracuda-Envelope-From:
X-Barracuda-Apparent-Source-IP: 68.93.9.131
DATE: Fri, 13 May 2011 15:13:47 -0500
From: QGATE@xxxxxxxxxxxxxx [+]
TO: <JMMCKEE@xxxxxxxxxxxxxx> [+]
SUBJECT: UNDELIVERABLE MAIL
X-Barracuda-Connect: UNKNOWN[X.X.X.X]
X-Barracuda-Start-Time: 1305317657
X-Barracuda-URL: http://24.249.116.47:8000/cgi-mod/mark.cgi
X-ASG-Orig-Subj: UNDELIVERABLE MAIL
X-Virus-Scanned: by bsmtpd at wildflower.net
X-Barracuda-Bayes: INNOCENT GLOBAL 0.5177 1.0000 0.7500
X-Barracuda-Spam-Score: 1.98
X-Barracuda-Spam-Status: No, SCORE=1.98 using per-user scores of
TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=3.0
tests=BSF_SC5_MJ1963, EMPTY_ENV_FROM, MISSING_MID, NO_REAL_NAME,
RDNS_NONE, UPPERCASE_50_75, UPPERCASE_50_75_2
X-Barracuda-Spam-Report: Code version 3.2, rules version
3.2.2.63644Rule breakdown below pts rule name description ---- --------
-------------- -------------------------------------------------- 0.14
MISSING_MID Missing Message-Id: header 0.00 EMPTY_ENV_FROM Empty
Envelope From Address 0.00 NO_REAL_NAME From: does not include a real
name 0.00 UPPERCASE_50_75 message body is 50-75% uppercase 0.10
RDNS_NONE Delivered to trusted network by a host with no rDNS 0.50
BSF_SC5_MJ1963 Custom Rule MJ1963 0.49 UPPERCASE_50_75_2 message body
is 50-75% uppercase
Message-Id: <20110513201419.6D29417B8FA6@xxxxxxxxxxxxxxxxxxxx>
-----Original message-----
From: jmmckee jmmckee@xxxxxxxxxxxxxx
Date: Fri, 13 May 2011 14:24:39 -0500
To: "Midrange Systems Technical Discussion" midrange-l@xxxxxxxxxxxx
Subject: Re: RES: RES: Email oddity

This just in to my personal email, the original Received from (before

my trashing) looked a lot better. Something new this time: Received
from unknown (HELO sftnail01.X.X.net).

Something else missing that the admin needs to know to fix?

John McKee

Return-Path: <John.McKee@xxxxxxxx>
Received: from mail7.wildflower.net (mail7.wildflower.net

[24.249.116.47])by mail8.wildflower.net (IceWarp 10.0.7) with ESMTP id
WXF42322 for <jmmckee@xxxxxxxxxxxxxx>; Fri, 13 May 2011 13:44:22 -0500

X-ASG-Debug-ID: 1305312262-285b44160001-bZofqT
Received: from smtp.X.net (smtp.X.net [1.1.1.1]) by

mail7.wildflower.net with ESMTP id drOfAOsMUhkpB3iW for
<jmmckee@xxxxxxxxxxxxxx>; Fri, 13 May 2011 13:44:23 -0500 (CDT)

X-Barracuda-Envelope-From: John.McKee@xxxxx
X-Barracuda-Apparent-Source-IP: X.X.X.X1
X-IronPort-AV:

E=Sophos;i="4.64,365,1301893200";d="scan'208";a="24497322"

Received: from unknown (HELO sftmail01.X.X.net) ([1.1.1.1])by

smtp.X.net with ESMTP; 13 May 2011 13:44:22 -0500

X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: FW: UNDELIVERABLE MAIL
Date: Fri, 13 May 2011 13:44:21 -0500
X-ASG-Orig-Subj: FW: UNDELIVERABLE MAIL
Message-ID:

<CA21B5C82F5F634AAE49D7D8AC9CC14814445732@sftmail01.stfran.sclhs.
net>

X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: UNDELIVERABLE MAIL
Thread-Index: AcwRlhCpcXrJoh6nSo6F/+uPmmozdwAB6ilQ
From: "McKee, John" <John.McKee@xxxxx> [+]
To: <jmmckee@xxxxxxxxxxxxxx> [+]
X-Barracuda-Connect: smtp.X.net[1.1.1.1]
X-Barracuda-Start-Time: 1305312262
X-Barracuda-URL: http://24.249.116.47:8000/cgi-mod/mark.cgi
X-Virus-Scanned: by bsmtpd at wildflower.net
X-Barracuda-Bayes: INNOCENT GLOBAL 0.0060 1.0000 -1.9821
X-Barracuda-Spam-Score: -1.49
X-Barracuda-Spam-Status: No, SCORE=-1.49 using per-user scores of

TAG_LEVEL=2.0 QUARANTINE_LEVEL=1000.0 KILL_LEVEL=3.0
tests=UPPERCASE_50_75, UPPERCASE_50_75_2

X-Barracuda-Spam-Report: Code version 3.2, rules version

3.2.2.63638Rule breakdown below pts rule name description ---- --------
-------------- -------------------------------------------------- 0.00
UPPERCASE_50_75 message body is 50-75% uppercase 0.49 UPPERCASE_50_75_2
message body is 50-75% uppercase

-----Original message-----
From: "Rubens Lehmann" rubens@xxxxxxxxxxxxx
Date: Fri, 13 May 2011 13:24:35 -0500
To: "'Midrange Systems Technical Discussion'" midrange-l@xxxxxxxxxxxx
Subject: RES: RES: Email oddity

John,

I must agree with Dennis.

You state "Host Baxter not able to deliver mail to", we can't

figure out who

is "Baxter" neither to "whom" it is not able to deliver...

Full headers would be extremely helpful but still not enough,

probably we'll

need details on your topology and DNS.

Mail server oddities can be as complex as an SQL with many selects

and left

outer joins which misses some set of results without any probable

cause. If

show just the table names, nobody will find answers.

If you prefer, mail me privately.

Rubens

-----Mensagem original-----
De: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-

bounces@xxxxxxxxxxxx]

Em nome de Dennis
Enviada em: sexta-feira, 13 de maio de 2011 15:03
Para: Midrange Systems Technical Discussion
Assunto: Re: RES: Email oddity

Cannot tell from what you provided. Any chance of sharing the full

headers?

There's usually an attachment with those headers, or it's inline.

(Some

nice mail servers provide it both ways.)

"jmmckee" <jmmckee@xxxxxxxxxxxxxx> wrote:

Two hours after my last attempt, a message was sent to me (I had

put my

return address on the email). Message came from

QGATE@BAXTER.X.X.X -

the i. Stated Host Baxter not able to deliver mail to....

Does this still seem like a reverse DNS issue?

John McKee

-----Original message-----
From: Dennis iseries@xxxxxxxxxxxx
Date: Fri, 13 May 2011 12:05:24 -0500
To: Midrange Systems Technical Discussion midrange-l@xxxxxxxxxxxx
Subject: Re: RES: Email oddity

Ask the folks who made it possible to have this in DNS, to check

the

PTR record for that entry. This is, I believe, the final key to

making

it work.

"jmmckee" <jmmckee@xxxxxxxxxxxxxx> wrote:

I >thought< I had it fixed.

I used INav and looked at TCP/IP Configuration -> Properties.

Original value for host was the serial number (Sxxxxxxx). And

domain

looked OK for internal. However, I could not ping the machine.

The

computer does have an entry in the DNS s3rver, so I changed the

host

and domain name to what I was told by the network folks. That

name

can

be pinged.

Just tried SNDEMAIL to Cox, again. I was told it did not make

it.

I am referring to a line in the header which used to say:
Received: from S1015362.xxxxx.org ([x.x.x.x])

I'll need to try it again to my email account to see if that

changed.

-----Original message-----
From: "Rubens Lehmann" rubens@xxxxxxxxxxxxx
Date: Fri, 13 May 2011 10:40:50 -0500
To: "'Midrange Systems Technical Discussion'"

midrange-l@xxxxxxxxxxxx

Subject: RES: Email oddity

John,

Can't understand what you mean without looking at it... Can

you

post

both

headers here, perhaps changing important data with something

generic?

Something like:

From my Outlook, to my mail server, to Gmail:

Received: from mydomain.com ([My Mail Server IP Address])
by mx.google.com with ESMTP id "lots_of_numbers";
Fri, 13 May 2011 08:18:23 -0700 (PDT)
Received: from [My WS IP on Internal Network] (HELO

rubensmydep)

by mydomain.com (My_Mail_SW_Name)
with ESMTP id "lots_of_numbers" for XXXX@xxxxxxxxx; Fri, 13

May

2011

12:19:45 -0300

From my i, to my mail server, to Gmail:

Received: from mydomain.com ([My Mail Server IP Address])
by mx.google.com with ESMTP id "lots_of_numbers";
Fri, 13 May 2011 08:30:58 -0700 (PDT)
Received: from [My i IP Address] (HELO MY_I)
by mydomain.com (My_Mail_SW_Name)
with ESMTP id "lots_of_numbers" for rubensXXXX@xxxxxxxxx;

Fri,

13

May 2011

12:32:20 -0300

Thanks,

Rubens

-----Mensagem original-----
De: midrange-l-bounces@xxxxxxxxxxxx

[mailto:midrange-l-bounces@xxxxxxxxxxxx]

Em nome de jmmckee
Enviada em: sexta-feira, 13 de maio de 2011 11:23
Para: Midrange Systems Technical Discussion
Assunto: Re: Email oddity

I >think< I have the answer. I sent an email from Outlook

and

from

the i to

my personal email account and looked at the headers.

The issue is that "Received:" is bogus. That, to me, means

the

SMPT

attributes. It would be nice if I could see the original

value.

I

searched

MIDRANGE and saw something from 2002, but I thought this had

been

discussed

more recently, and that a method to see original values - in

some

PF,

for

example, existed.

Is there some way to see original values?

John McKee
-----Original message-----
From: jmmckee jmmckee@xxxxxxxxxxxxxx
Date: Thu, 12 May 2011 11:14:53 -0500
To: "Midrange Systems Technical Discussion"

midrange-l@xxxxxxxxxxxx

Subject: Re: Email oddity

Haven't had THAT thrill yet, but have had others.

Coworker

called

somebody years ago on another job. Was put on hold by the

system.

He

waited patiently. A little after 5PM, the system announced

that

the

business was closed for the day, call again tomorrow, and

hung up.

John McKee
-----Original message-----
From: "sjl" sjl_abc@xxxxxxxxxxx
Date: Thu, 12 May 2011 10:45:50 -0500
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Email oddity

John -
Not unlike having a support call with Dell technical

support

in

Bangalore...

- sjl

John wrote:
Thanks for the article.
Maybe, it >will< be resolved today.
Just (apparently)

<< have to supply the answers, as well as the questions

when

asking

some

support people for help. >>

--
This is the Midrange Systems Technical Discussion

(MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:

http://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the

archives

at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion

(MIDRANGE-L)

mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-

l

or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please

excuse my

brevity.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing

list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
Sent from my Galaxy tablet phone with with K-9 Mail. Please excuse

my

brevity.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)

mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.