Channel 1 Spam Policies

Customers sending unsolicited bulk email or spamming Usenet will be subject to the anti-spam provisions of our Term of Service.

Channel 1 Relay Policies

In order to stop the theft of system resources by spammers and maintain our reputation and connectivity in the Internet community, Channel 1 has closed its mail servers to foreign networks. If you are a Channel 1 customer accessing the net through another network, please use that system's SMTP (outgoing) mail server. In most cases it is faster and more efficient. Channel 1's POP servers (your mailboxes) are available from anywhere.

If you are not able to use a SMTP server on the network you are connected to, you may use our POP authorization option: simply check your mail first (and wait a maximum of 30 seconds) before sending outgoing mail via Channel 1's SMTP servers. If this solution is not available to you, contact Channel 1 support.

Channel 1 Spam Filtering

In addition to not serving as a spam-station for outside abusers, Channel 1 filters both e-mail and Usenet news for spam, and our news servers are open to spam-cancels. If you would like to be removed from e-mail spam filtering, contact Channel 1 support.

Spammer Tactics: What You See is Not What You Got

When reporting spam it is imperative to include the FULL headers of the spam. Many email programs hide this information from you by default. In Eudora, for instance, it is necessary to click on the "BLAH" button to see the full routing information in the email message.

See the links below for information on de-ciphering email headers. Basically, most of the information in the visible (and often full) headers is forged/false. Spammers try to cover their tracks.

Often, the spam is being "relayed" (reflected) from an innocent, clueless or careless third party, while the account being used to generate the spam is a "throwaway" account provided as a "trial period" (a la AOL). The spammer knows he/she will be backtracked and the account canceled.

Channel 1 can block the innocent relayer, but the spammer just moves on and finds a new victim. The originating throw-away account may be blocked, but do you really want to stop getting your mail from your Mother's AOL account?

Sample Header Analysis

Here is a typical spam mail header:

>>Return-Path: <564d@james.dse.de> >>Received: from james.dse.de (james.dse.de [194.25.156.131])

A careless/clueless mail server in Germany

>> by user1.channel1.com (8.9.1/8.9.1) with ESMTP id MAA17091 >> for ; Wed, 20 Jan 2000 12:43:39 -0500 (EST) >>From: 564d@james.dse.de >>Message-Id: <200001201743.MAA17091@user1.channel1.com> >>Received: by james.dse.de >> (1.39.111.2/16.2) id AA198803935; Wed, 20 Jan 2000 18:38:55 +0100 >>Received: from 1cust132.tnt2.ontario.ca.da.uu.net(208.254.109.132) by

The "throw-away" account used by the spammer

>james.dse.de via smap (V1.3) >> id smaza7352; Wed Jan 20 18:11:56 2000 >>To: user@the_internet.com

Don't be fooled. This is a fake To: address. Your real email address is hidden in a huge bcc: (blind-carbon-copy) field in the "envelope" of the message.

>>Date: Wed, 20 Jan 99 08:59:43 EST >>Subject: CALL 1-800-HOT-XXXXX....CALL NOW!! >>X-Mozilla-Status2: 00000000
and the spammer moves on ... write your congresspeople and demand strong anti-spammer legislation.

Spamming Defense Information






All Content and Design
· © Copyright 1996-2000, Channel 1 Communications® ·
· Channel 1® is a Service of Cybergate, Inc. ·