news reader

  • Thread starter Thread starter cajun_mike
  • Start date Start date
Some IPs will ALWAYS return a Kansas location... that's where the IP
is registered, not where the post originated from.  It's apparently an
"ISP thing".

I did not know that. Thank you. :)
 
Silly boy. Working with a separate news and email client does not mean "more
clicks". Whether you use an "all-in-one" application, or separate
applications, going from news to mail will take the same effort in clicks
expnded.


Thank you for saying what I didn't want to say, because I expected it
to start an argument.

Actually in my case, since I keep both applications open and have two
monitors, going from either one to the other takes me *no* clicks.
 
Sorry, Ken... you're the one who is not correct. Here's a quote from a
recent post (Oct. 24, 2008) in the Outlook group:



Well, if Brian Tillman says that, I'll take his word for it. He's much
more of an Outlook expert than I am.

I apologize to you for my error, and I also thank you for pointing out
what I didn't know. That's apparently a new feature of Outlook 2007,
since it didn't work that way in prior versions.

However, typing a message in Outlook 2007 doesn't feel to me at all
like using Word as a word processor, especially since I don't send
HTML messages, and everything is in unformatted courier text. So I
really don't mind it.
 
Wow! I am duly impressed by your knowledge, Norman! :)

I don't know what else to say right now - but thanks for posting!

Dave


N. Miller said:
I often wonder if it is always the same persona that posts under the
name of PA Bear - but whenever I check an IP address it seems
consistently confusing (to me!) 24.152.248.232 relates to
Pennsylvania
yet 71.173.71.14 resolves to Dodge City, Kansas - a long way apart I
believe. Instead of simply explaining why this may be so, I am
stone-walled. That, in turn, makes me suspicious.

[24.152.248.232] resolves to:

| 01/04/09 11:07:44 dns 24.152.248.232
| nslookup 24.152.248.232
| Canonical name: 24.152.248.232.res-cmts.tvh.ptd.net
| Addresses:
| 24.152.248.232

In that host name, 'cmts' is likely a reference to the "Cable Modem
Termination System", indicating that 'ptd.net' is a cable service. For
that
matter, 'ptd.net' WHOIS shows this:

| 01/04/09 11:08:45 whois (e-mail address removed)
|
| whois -h whois.geektools.com ptd.net ...
| GeekTools Whois Proxy v5.0.4 Ready.
| Checking access for 68.127.104.88... ok.
|
| Checking server [whois.crsnic.net]
|
| Checking server [whois.tucows.com]
| Results:
| Registrant:
| PenTeleData Inc
| 471 Delaware Ave
| Palmerton, Pa 18071
| US

A trace route to that IP address, from San José, California is
consistent
with an East Coast (USA) location. Now [71.173.71.14] resolves to:

| 01/04/09 11:08:01 dns 71.173.71.14
| nslookup 71.173.71.14
| Canonical name: pool-71-173-71-14.ptldme.east.verizon.net
| Addresses:
| 71.173.71.14

Trace route, from San José, California is still consistent with an
East
Coast (USA) location. Different ISP, though: Verizon, as contrasted
with
PenTelData, Inc. The Verizon IP address could be DSL, could be FiOS.
Could
be serving the exact same community as the PenTelData IP address.

This much I can tell you about [71.173.71.14]: No way is it in Dodge
City,
Kansas! The host name appears to use a common Bell* practice of city
code.
I'd take 'ptldme' to likely be Portland, Maine.

NOTE* "Bell" is a brand name not used much by U.S. telephone
companies, any
more. When the Federal Government broke up AT&T in 1984, it forbade
the use
of the "Bell" brand by AT&T, reserving its use to the ILEC businesses
spun
off from AT&T. Some (Bell Atlantic, Bellsouth, and Southwestern Bell
Telephone) kept the brand in the corporate names. Others (Ameritech,
The
Pacific Telesis Group) kept the brand only in the local service
companies
(Wisconsin Bell, Indiana Bell, Illinois Bell, etc., for Ameritech, and
Nevada Bell and Pacific Bell for The Pacific Telesis group). Yet
others
(NYNEX, USWest) dropped the "Bell" brand altogether. But they all,
apparently, carried the practice of city/state naming in the pattern
of
'ctcdst', where 'ctcd' is a four-letter city code, and 'st' is the
U.S.
Postal two-letter state code. Verizon, formed from the merger of Bell
Atlantic, NYNEX, and General Telephone and Electronics, has some of
that old
"Bell" culture, as does AT&T formed from the merger of Ameritech, The
Pacific Telesis Group, and some none Bell companies, when Southwestern
Bell
Teleophone (as, "SBC") bought them. SBC also bought AT&T, renaming
themselves from, "SBC", to "AT&T" in the process. Then they bought
Bellsouth. So the "Bell Force" is strong with this new "Deathstar" (a
reference to the AT&T logo; designed for the stripped down AT&T of
1984, and
redesigned for the "new" AT&T after it fell to SBC.

BTW, even knowing the city and state codes for an AT&T (or Verizon)
host
name, you won't, necessarily, have the city of residence of the
subscriber.
My own ISP hostname incorporates 'pltnca' in the name: "Pleasanton,
California", which is a good 26 miles from San José, California.

Don't set too much stock by resolved hostnames for U.S. IP addresses.
Different corporate cultures result in different naming conventions;
and,
when they do use a geographic locator in the name, more often it
refers to
the location of some switching center, or transit hub, than the end
user's
location.

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.
 
(e-mail address removed) said this on 1/4/2009 3:14 PM:
I did not know that. Thank you. :)

I'd also speculate too that some larger ISPs have multiple farms to
provide backup/power failure security, whatever you want to call it.
And one time you hit machine A and another time you hit machine B.
I know I get two IPs when pinging Verizon. (or did).
 
BillW50 said:
In Ken Blake, MVP typed on Sat, 03 Jan 2009 08:04:11 -0700:

I too like newsreader and email rolled into one application. As they both
need servers, they both need readers, they both need editors, they both
for some of us need spell checkers, they both need a header list, they
both need to be sortable, they both use threads, etc. So since you need
the very same between them, why use something differently for both? So you
only have one program to master and not more. ;)

The only drawback I noticed in my OE is that source edit isn't available
when composing an e-mail from the newsreader. Going to the Inbox
to get the source edit to work, closes the newsreader. No big deal at
all - just something I noticed. The similarities between these applications
just scream for integration.
 
In FromTheRafters typed on Sun, 4 Jan 2009 18:01:15 -0500:
The only drawback I noticed in my OE is that source edit isn't
available when composing an e-mail from the newsreader. Going to the
Inbox to get the source edit to work, closes the newsreader. No big deal
at all - just something I noticed. The similarities between these
applications just scream for integration.

Source edit? Oh I see it now! I never used that under OE before. And it is
grayed out under newsgroups. How interesting.

--
Bill
2 Gateway MX6124 - Windows XP SP2
3 Asus EEE PC 701G4 ~ 2GB RAM ~ 16GB-SDHC
2 Asus EEE PC 702G8 ~ 1GB RAM ~ 16GB-SDHC
Windows XP SP2 ~ Xandros Linux - Puppy - Ubuntu
 
BillW50 said:
In FromTheRafters typed on Sun, 4 Jan 2009 18:01:15 -0500:

Source edit? Oh I see it now! I never used that under OE before. And it is
grayed out under newsgroups. How interesting.

--
Bill
2 Gateway MX6124 - Windows XP SP2
3 Asus EEE PC 701G4 ~ 2GB RAM ~ 16GB-SDHC
2 Asus EEE PC 702G8 ~ 1GB RAM ~ 16GB-SDHC
Windows XP SP2 ~ Xandros Linux - Puppy - Ubuntu
Source Edit is never available for text messages.
Are you composing a HTML message for the newsgroup?
 
In Ron Sommer typed on Sun, 4 Jan 2009 17:51:25 -0600:
Source Edit is never available for text messages.
Are you composing a HTML message for the newsgroup?

Look at my headers Ronald! No!

--
Bill
2 Gateway MX6124 - Windows XP SP2
3 Asus EEE PC 701G4 ~ 2GB RAM ~ 16GB-SDHC
2 Asus EEE PC 702G8 ~ 1GB RAM ~ 16GB-SDHC
Windows XP SP2 ~ Xandros Linux - Puppy - Ubuntu
 
He /despises/ Robear, (my mentor), with a passion.
--

Bruce Hagen
MS-MVP Outlook Express
Imperial Beach, CA


That's the first incorrect statement I have ever seen you make, Bruce.

I am simply troubled by many less-than-straight-forward answers which PA
Bear (Robear Dyer) has given to me from time to time.

I do not, though, check the Properties of every message. Even if I did,
I now know that Header Information can be forged so one cannot be
absolutely certain of the origin of any post in a newsgroup (nor, I
believe, in an email message!).

I'm fairly certain that if I met the real Robear Dyer face-to-face we
would have much in common! <beg> (I had no idea what <beg> meant 3
years ago!)

HTH

Dave

PS Interested to note your thread, here!!
http://forum.aumha.org/viewtopic.ph...&sid=993c7200a1cedbd7b3d8e28a73376535#p196979
 
I will let Robear speak for himself regarding how you two get along. That
was simply the impression I have.

Why are you interested in my thread in AUMHA?
 
Big_Al said:
(e-mail address removed) said this on 1/4/2009 3:14 PM:

I'd also speculate too that some larger ISPs have multiple farms to
provide backup/power failure security, whatever you want to call it.
And one time you hit machine A and another time you hit machine B.
I know I get two IPs when pinging Verizon. (or did).

Thanks for that info, 'Big_Al' :)
 
Don't set too much stock by resolved hostnames for U.S. IP addresses.
Different corporate cultures result in different naming conventions;
and,
when they do use a geographic locator in the name, more often it
refers to
the location of some switching center, or transit hub, than the end
user's
location.

To add a bit more confusion to Normans highly informative (and accurate,
from the portions of the history that I am personally familiar with)
post:

With the advent of "local number portability" some years ago, and now
that being extended to cell phones ... city codes no longer mean
anything at all with respect to location. An "area code - exchange" that
used to resolve to a specific telco (telophone company) physical
location now could be anywhere in the continental US.
 
[Please don't feed the trolls, especially /that/ troll...who knows full well
how to "spoof" someone else in these newsgroups because he's done so.]

Bruce said:
I will let Robear speak for himself regarding how you two get along. That
was simply the impression I have.

Why are you interested in my thread in AUMHA?
<snip>
 
To add a bit more confusion to Normans highly informative (and accurate,
from the portions of the history that I am personally familiar with)
post:

With the advent of "local number portability" some years ago, and now
that being extended to cell phones ... city codes no longer mean
anything at all with respect to location. An "area code - exchange" that
used to resolve to a specific telco (telophone company) physical
location now could be anywhere in the continental US.

Actually, router naming is as accurate as the network engineering department
of the ISP makes it. I am currently seeing a transit router hostname on the
ATTIS transit network, which looks to be a residential IP connection, not a
proper transit router. However, local number portability should not affect
the city codes used in naming transit routers. The names are only a network
convention, and need not be as informative as to include geolocations. There
are transit networks which only use generic host names on transit routers.

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.
 
Hi Norman! You must have an interesting résumé. ;)

Not at all. Any blank book matches my CV perfectly!

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.
 
I now know that Header Information can be forged so one cannot be
absolutely certain of the origin of any post in a newsgroup (nor, I
believe, in an email message!).

I can accurately identify the SMTP agent which connected to my gateway (MX)
SMTP server to leave an email. What I can't reliably do is trace the source
beyond that SMTP agent.

--
Norman
~Shine, bright morning light,
~now in the air the spring is coming.
~Sweet, blowing wind,
~singing down the hills and valleys.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top