Adland Tips

<HTML>
<HEAD>

<TITLE>place a couple keyword phrases here</TITLE>
<META NAME="description"content=" place your description here made up of short descripive sentences using your keyword phrases">
<META NAME="keywords" content="place your keywords and keyword phrases here separated with comma's ">

<META NAME="resource type" content= "document">
<META NAME="distribution" content="global">
<META NAME="revisit-after" content="7 days">
<META NAME="robots" content="index,follow">
<META NAME="robots"content="index,all">
</HEAD>
<BODY BGCOLOR="#FFFFFF">

<BR>

<TABLE BORDER=0 WIDTH=600 CELLPADDING=5>
<TR>
<TD>
<H1 align="center"> the headline for your page goes here made up of one or two of your keyword phrases</H1>

<P>If you are looking for any of the following items:
<UL>
<LI><A HREF="http:// place url here"> place a keyword phrase here</A></LI>
<LI><A HREF="http://place url here"> place another keyword phrase here</A></LI>
<LI><A HREF="http://place url here"> place a descriptive sentence with keyword phrase here</A></LI>
<LI><A HREF="http://place url here"> place another descriptive sentence with keywords here </A></LI>
<LI><A HREF="http://place url here"> place one last descriptive sentence with keyword phrases here</A></LI>
</UL>
<P>Search no more. You'll find it at <A HREF="http://place url here"> place your webpage name here</A>
<P>place a short descriptive paragraph with a keyword phrase ... should be a benefit someone gets when they visit your site</P>
<P>place another descriptive paragraph here </P>
<P>place another descriptive paragraph here</P>

FreeWebPromote - Place free ads to over 3380 High Traffic Websites with one
click. Get Free Software - Remembers passwords/all personal data and fills
out internet forms for you! Plus subscribe to FreeWebPromote a great
Tutorial Newsletter.
http://freeyellow.com/members8/freewebpromote/index.html *

In #135, we were asked for tips on downloading larger
messages in AOL.

AOL will truncate all long messages. In answer to Bogdan's
question about optimal size, it's too small. I tested issue 135
and it truncated at the bottom of the Power Tip at the top - it
didn't even make it to the topic list.

Luckily there are two ways to read the whole message, even
though you can't read them in the AOL email program.

AOL creates an attachment that you can download and read
by opening the file. There is a download icon at the bottom of
the email message. This is a little annoying to have to do with
any frequency and this isn't the preferred method.

Here is the easiest way around it:
1. In AOL or in your favorite web browser type in this URL:
     http://aolmail.aol.com/
     (I'd save it to your favorite places or bookmark it)
2. Sign-on with your AOL membername and password
     You can do this whether or not you already signed on
      to your AOL program.
3. Click on the "click to complete sign-in" box
4. Click the message or if you don't see it on the new
     messages page, click on the old message tab, then
     click on the message to open.
5. The message will appear truncated but right under the
     header (to/from/subject) section you will see an icon and
     a link "AdlandDi.txt"
6. Click on the "AdlandDi.txt"
7. It will open the full message.

AOLMail works just like your regular online email, but you
can pick up your email without signing on to your account.
Plus, since it's done on the web, you don't have to deal with
the size limits.

I pick up all of my AOL mail using AOLMail on the web
because it is a lot easier to use.

Melody
------------------------------------------------------------------
Melody Treece Vargas, melodyt@success-solution.com
http://www.success-solution.com/workathome.html
Resources, tips & solutions for home businesses
Melody is now your Retail Industry Guide at About.com
http://retailindustry.about.com/
------------------------------------------------------------------

Hi Bogdan and readers,
Been following the messages about spam and peoples problems with it. There
are of course two issues here, that people need to actually address at an
international level .
I'd like to offer this [Tutorial on Tracking Smappers to the Source].

There are two 'classes' of people using the popular internet.
a) Those of us trying to make an honest living by promoting a
product/service to the international community. My multilingual-domain
registration site, http://www.inexpensivewebsites.com falls into this, and
probably most of the readers of this newsletter as well. I've been a member
of this list almost from its inception, and rarely have I seen anyone
operating out of pure skullduggery!
b) Those other types who will try any rip-off, get rich quick, blast the
internet with junk, steal your kids, thieving sod, sell a billion email
address for $5 fools that you find anywhere where the rules and regulations
are at best 'murky' and in anycase don't apply across state boundaries, let
alone in Turkmenistan! and who all operate on the gullability of others -
Give us your money, and we assure that you will be rich overnight, if you
can catch us!

It's the type B's that cause the problems, and unfortuantly because of the
traffic volume they generate the operators of major servers have tried to
block them out.
See a few positng of mine some time last year where I did some research on
the traffic generated over a server by repeaded requests to add links to
that Links.cgi/html program thats about (Add your site to 5,842,641.5 search
engines thing.. I forget what its called) Unbelievably, after nearly 12
months of the link not being there - there are STILL requests coming in to
add links!!!

HOWEVER. Major server operators who adopt a 'we'll cut you off if you spam'
policy are actually reacting to the wrong people - in the main.

The Problem lies in these facts.
1. Far too many servers have NO PROTECTION in their mail servers to deny
Mail Relaying.
2. Most SPAM is seen to originate through valid addresses, often places like
hotmail.com because they are easy to remember by the spammers when they type
in their setups. They tend to lend a small degree of spurious validity to
the email. But they are not in fact the true source.

Let me show you an example:
This is is the header of just one of many SPAM mails I received today..
Nothing special, but it servers to use as an example.
See just below it for the explaination of what is happening here.
========================================================
1   Return-Path: <westonls@yahoo.com>
2   Received: from wamego.net (216096074012.midusa.net [216.96.74.12])
3   by nanguo.chalmers.com.au (8.11.0/8.11.0) with ESMTP id eAGLXRH25251
4   for <robert@chalmers.com.au>; Fri, 17 Nov 2000 07:33:29 +1000 (EST)
5   Received: from dsl [216.96.44.97] by wamego.net
6   (SMTPD32-6.04) id A1834B5B0074; Thu, 16 Nov 2000 15:28:35 -0600
7   From: Weston Sulsar <westonls@yahoo.com>
8   To: <rnemanja@serbiancafe.com>
9   Message-Id: <18161.236846.64186794 robinton@GMX.de>
10 Subject: Earn $50,000.00 dollars in 90 days out of your own home. Must
read to believe.
11 Mime-Version: 1.0
12 Content-Type: text/plain; charset="us-ascii"
13 Content-Transfer-Encoding: 7bit
14 Date: Thu, 16 Nov 2000 15:30:08 -0600
15 X-UIDL: 3de4f91ed18d12bbe4e21081a9e2e347
=========================================================
Line:
1    The supposed return address. It's false, although it may well be an
actual user on yahoo. Poor him if it is.
2 3 4   The address it is being sent to, and who the email is _supposedly_
from

***** This next bit is the IMPORTANT bit - who the mail is _Really From - :
5 Where the email actually originated. In this case;
    $ nslookup 216.96.44.97
      Name:    216096044097.midusa.net
      Address: 216.96.44.97
That IP address [216.96.44.97] tells you who the spammer really is. No
matter how they try - it's not possible to truly hide.
The part just after the ip 'by wamego.net' is who actually took the mail,
and relayed it on.!!! More on that baby later...

6 7 8 9 10 11 12 13 14
15 More envelope stuff - irrelevant to what you are looking for.
=========================================================

The first bit of sluting we do is to find the actual source. midusa.net.
So, lets look up that network . midusa.net. and we find it's this company:
----------------------------------------------------------------------------
-------------------------------
Registrant:
RevRon of Salina, Inc (MIDUSA-DOM)
   127 N. 7th St.
   Salina, KS 67401 US

   Domain Name: MIDUSA.NET

   Administrative Contact, Technical Contact, Billing Contact:
      hostmaster (HOS202-ORG) hostmaster@MIDUSA.NET
      NetSpace Internet Services
      127 North 7th
      Salina, KS 67401
      US
      (913) 823-3565 Fax- (913) 825-5873

   Record last updated on 01-Nov-2000.
   Record expires on 14-Oct-2000.
   Record created on 13-Oct-1995.
   Database last updated on 16-Nov-2000 16:58:56 EST.

   Domain servers in listed order:

   NS.MIDUSA.NET                206.28.168.20
   NS2.MIDUSA.NET               206.28.168.19
======================================================

This tells me that the HOST (216096044097) is actually alive at the moment.
So it's probably a user-account.
Doesn't that host name look like a local phone number !!!!! (Go look at
www.midusa.net, just to get the picture, and make sure who they are.)

Then,
PING 216096044097.midusa.net (216.96.44.97): 56 data bytes
64 bytes from 216.96.44.97: icmp_seq=3 ttl=102 time=3350.561 ms
64 bytes from 216.96.44.97: icmp_seq=5 ttl=102 time=1350.538 ms
64 bytes from 216.96.44.97: icmp_seq=4 ttl=102 time=2370.398 ms
64 bytes from 216.96.44.97: icmp_seq=6 ttl=102 time=1250.386 ms
=======================================================

So the ip/name resolves to a live host. Looks like an account on the
midusa.net service.
So you finally know who the spammer really is.
Here you have a few choices.

Contact the spammer directly on that HOST.DOMAIN - send them your spam,
phone them, whatever. (postmaster@216096044097.midusa.net) would probably
get them, or some variation of that.
Contact Midusa.net and ask them politely to deal with the culprit.
That's the usual course of action. and not a bad one. However, you could
also take one more step. The most important step. Close off another hole.
Do nothing - and delete the message. The easiest course.

The BETTER course of action is to contact THESE people, and inform them that
it looks like the spammers are using their server as an unauthorised mail
relay!
=================================
$ ./whois wamego.net
Wamego Telecommunications Company, (WAMEGO-NET-DOM)
   529 Lincoln
   Wamego, Ks 66547
   US

   Domain Name: WAMEGO.NET

   Administrative Contact:
         Michael Rice (MR43-BR) mrice@midusa.net
        -
        529 Lincoln
        Wamego, Ks 66547
        US
        Phone- 785-456-1029
        Fax- 785-456-9903
   Technical Contact:
        Internet Planners (IP4-BR) hosting@internetplanners.com
        Internet Planners LLC
        PO Box 601
        Kensington, MD 20895
        US
        Phone- 301-933-2431
        Fax- 301-933-2431

   Record updated on 2000-01-15.
   Record created on 2000-01-15.
   Record expires on 2002-01-15.
   Database last updated on 2000-11-14 03:42:18 EST.

   Domain servers in listed order:

   GAILLAND.OCT.NET              64.39.195.10
   KONZA.FLINTHILLS.COM          64.39.200.1
$
==========================================

And there you have it. From source to receipt.
Now you can see why a lot of companies will simply ban _anyone_ reported to
be spamming. Even when they haven't. It's way easier than actually finding
the TRUE culprit. The sysadmin may not know how to find the culprit. The
sysadmin doesn't care/doesn't get paid enough. But more often, they just
dont have the time to follow up the volume of spammers.

Hope that helps clear up some of the mystery.
Regards
Robert, robert@chalmers.com.au &
info@inexpensivewebsites.com
=================================