RES: RES: Email oddity -- MIDRANGE-L

John,

Your host (your i) serial number and IP can be anything, it works as a
client the same way Outlook do to your PC with its own serial number and IP.

On Outlook, you have to authenticate (user password) and/or set your network
(ex: 10.10.10.1-255) to relay through it (your mail server).

Your mail server configuration is set, so your i can act about the same as
an Outlook client?

If your mails are sent without authentication, some receiving servers could
drop them.

Does that explanation help or still I didn't get the full idea?

Regards,

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 13:09
Para: Midrange Systems Technical Discussion
Assunto: Re: RES: Email oddity

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

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.