Site Navigation

Welcome Page

Legacy Utilities Archive

Rant of the Month

We operate our network and mail server(s) for the benefit and convenience of OUR users only. Therefore, unsolicited commercial and/or bulk e-mail is NEVER welcome here.  As a means of enforcing this policy, connection control and spam rejection for our mail server(s) is handled primarily via public DNS-based blacklists, including (but not limited to) the following:

1.   SBL - The Spamhaus Block List.  This is a database of verified spam sources (including spammers, spam gangs and spam support services.  See: <http://www.spamhaus.org/sbl/>.

2.   PBL - The Spamhaus Policy Block List.  This is a database of IP address ranges which should never attempt "direct-to-MX" delivery of unauthenticated SMTP email traffic -- in other words, typical retail ISP end-user IP space. Such users should ALWAYS transmit their mail via their ISP's server(s) (or those of a third-party e-mail service provider with whom they have legitimate privileges).  See: <http://www.spamhaus.org/pbl/>.

3.   SORBS - Spam & Open Relay Blocking System.  See: <http://www.dnsbl.sorbs.net/>.

4.   CBL - Composite Blocking List.  This is a list of insecurely misconfigured hosts (mostly virus/trojan-infected "zombies") abusable by spammers -- much like open mail relays, only more dangerous due to their facilitating (usually anonymous) connections on virtually any port, using virtually any service, from virtually any source, to virtually any destination -- which are known to send mail to spamtrap addresses (i.e., those which should NEVER get any mail).  See: <http://cbl.abuseat.org/>..

5.   RFC-Ignorant - This is a database of domains and network operators who are too incompetent (and/or too arrogant) to follow the well-established fundamental "rules" of the internet, as codified by the relevant IETF (Internet Engineering Task Force) "Best Current Practices" and "Requests For Comments" documents.  See: <http://www.rfc-ignorant.org>.

6.   SpamCannibal - This is a database containing the IP addresses of confirmed spam or DoS-attack sources.  See: <http://www.spamcannibal.org>.

7.   UCEPROTECT Network -  This is an escalating multi-zone DNSbl system, based primarily on data from a large number of covert "spamtrap" systems.  We currently use Levels 1 & 2 only.  See: <http://www.uceprotect.net/en/index.php>.

8.   510 Software Group Blackholes List.  See: <http://www.five-ten-sg.com/blackhole.php>.

9.   Moensted.DK - Dr. Jørgen Mash's "no-more-funn" DNSbl; lists individual spam sources, dialup-equivalent IP addresses, spam-support networks, open relays, etc..;  See: <http://www.moensted.dk/spam/no-more-funn/>.

10.  NJABL - This is another general-purpose DNSbl, containing individual spam sources, dialup-equivalent IP addresses, spam-support networks, open relays, etc..;  See: <http://www.njabl.org/>.

11.  URIBL - This is a URI/URL-based DNSbl, primarily containing domain names belonging to and/or used by spammers.  See: <http://www.uribl.com/about.shtml>.

12.  Backscatterer.Org - This DNSbl primarily contains hosts which are so grossy misconfigured as to send NDRs ("Non-Delivery Reports") off-network to the forged "From:" addresses commonly used in spam, thus doing the spammers' work for them and amplifying the spam problem many-fold in the process.  Sadly, this idiotic behavior is still all too common.  See: <http://www.backscatterer.org/?target=backscatter>.

We would like to express our sincere appreciation to the operators of the above-noted services for their generous contribution to the health of the 'net as a whole, and that of our mail servers in particular.

If you are reading this because you received a non-delivery notice which directed you here, referring to one of the above blacklist services, be aware that we do NOT control those lists, nor can we influence in any way which IP addresses may exist on, be added to, or be removed from said lists.  If you believe your mail has been rejected in error, refer to the URLs cited above for further information.  In addition, ISPs, domains and networks who have spammed or attempted to spam our users may be listed in our privately maintained block lists.  There is NO process for removal from our block lists.  We do not want to exchange traffic with spammers, and we don't believe that spammers ever reform (at least, not unless there is a multi-million-dollar judgement hanging over their heads if they should ever spam again).  If you don't want to be included on the above-cited block lists, the procedure is very simple:

1. DON'T SPAM!

2. Don't allow your users to spam.  Not even once.

3. Don't ever ignore a spam complaint.

4. Don't allow open proxies, open relays, or "zombies" on your network.

5. Don't host "block-on-sight" spammers, such as ANY of the ones listed HERE

In addition to the above, all messages sent to or through our servers are subject to certain specific criteria with regard to their content and formatting.  Specifically:

1.  NO EXECUTABLE ATTACHMENTS!

Most attachments are perfectly innocuous and fully acceptable, and we encourage their use when appropriate.  Further, we currently do not impose any arbitrary limits on attachment size (but this is subject to change on a case-by-case basis as needed).  However, certain attachment types, primarily those comprising executable programs, are inherently dangerous, at least to some recipients.  Therefore, the following attachment types are currently forbidden on our servers & network (others may be added as the need arises):

If you attempt to send one of the above-cited attachment types, your message will be automatically discarded and you will receive a DSN (Delivery Status Notification) to that effect. If and when you feel you MUST send any of these file types, encase it inside a standard compressed archive file, such as .bz2/bzip2, .gzip, .lha, .rar, .zip, etc. (all of which are acceptable), then attach that to your message.

2.  NO HTML!

HTML-formatted e-mail is a plague upon the Internet.  While its use has become more and more common over time, this is nearly always for the wrong reasons (chiefly ignorance and carelessness), AND completely unnecessary.  HTML is not and never was designed for this application; nor does it serve the usual "intended" purpose of those who erroneously inflict this dreck on others (short version: no, it does NOT provide WYSIWYG control over how your "document" will appear to the reader), and it is grossly inefficient (a typical HTML-formatted message is 4-10 times as large as the exact same message in Plain Text format).

Further, and more to the immediate point here, HTML-formatted e-mail is inherently dangerous, especially to those ignorant and/or foolish enough to run certain "popular" mail clients or use so-called "webmail" services (often with inadequately secured web browsers).  Among other well-documented problems, it can carry hidden viruses, worms and trojan-horse programs which are capable of infecting your computer before you've even finished reading the message (in some cases, and with some particularly bad mail clients, before you have even opened the message!), and it can contain "web bugs" which can be used to track your usage habits and otherwise invade your privacy. It is beyond the scope of this article to go into much greater detail; but if any of the above comes as even the slightest news to you, we strongly recommend that you refer to any/all of the following off-site references for further confirmation and background information:

In short, there is virtually never a good reason to send HTML-formatted e-mail, yet there are a multitude of very good reasons to NOT do so.  Therefore, as a matter of policy, such messages are forbidden on our servers & network.  This includes so-called "multipart/alternative" messages which contain HTML-formatted "parts".  If you attempt to send an HTML-formatted message, it will be automatically discarded and you will receive a DSN (Delivery Status Notification) to that effect.

In the exceedingly rare case that you (think you) MUST send highly formatted text in order to get your point across, use a word processor (such as OpenOffice.Org "Writer") to create your opus, save it in whatever format you know to be mutually acceptable to your recipient(s) (such as .odt or .pdf or .rtf), then if necessary place the resulting file inside a standard compressed archive file (as described above) before attaching it to your (otherwise Plain Text) message.

All messages sent to our network, servers, or domain, regardless of source, character, or how they may be routed or addressed, become the property of Appropriate Technology, Inc.  We reserve the right to publish or republish said messages, in whole or in part, and in any form, manner or venue as we in our sole discretion deem fit.  Please also be aware that we routinely report instances of unsolicited commercial and/or bulk e-mail to all relevant parties and publish same to such public evidence archives/forums as the <news.admin.net-abuse*> hierarchy of Usenet newsgroups.  If you are a spammer and you do not wish your loathesome misbehavior to be held up for public scrutiny and/or ridicule, don't spam us -- it's that simple.

If you have any questions which are not covered by the above, feel free to contact us.