8:43 a.m.
APPROVE COMMIT web
Fixes my(?) old typo in the list-manager URLs (was incorrectly spelled
"listmaster"), and updates spam filter policy.
Index: Lists/ChangeLog
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Lists/ChangeLog,v
retrieving revision 1.25
diff -u -U0 -r1.25 ChangeLog
--- Lists/ChangeLog 5 Jul 2004 10:46:49 -0000 1.25
+++ Lists/ChangeLog 30 Dec 2004 08:40:11 -0000
＠＠ -0,0 +1,4 ＠＠
+2004-12-30 Stephen J. Turnbull <stephen(a)xemacs.org>
+
+ * index.content: Update #spam, listmaster->list-manager.
+
Index: Lists/index.content
===================================================================
RCS file: /pack/xemacscvs/XEmacs/xemacsweb/Lists/index.content,v
retrieving revision 1.25
diff -u -r1.25 index.content
--- Lists/index.content 5 Jul 2004 10:46:49 -0000 1.25
+++ Lists/index.content 30 Dec 2004 08:40:19 -0000
＠＠ -420,21 +420,6 ＠＠
state, and change it, from your personal options page.</p>
<p>
- <strong>Note to AOL users:</strong> Because XEmacs lists are
- public, the addresses are known to many viruses and spammers, and
- therefore are likely to be used to conceal real sources of
- undesired mail. AOL's filter is quite stupid about this. Several
- AOL users are bouncing mail, and we have turned off delivery to
- their subscriptions, because the bounce messages annoy the XEmacs
- list managers and AOL's Postmaster does not respond to inquiries
- (we usually can't reach you!). You will have to both fix your
- filter and restore your subscription to delivery status using the
- Mailman interfaces. (The XEmacs policy is not going to change. If
- your ISP is unwilling to provide resources to ensure that mail you
- have requested is delivered to you, XEmacs volunteers are not
- going to make up for that lack.)</p>
-
- <p>
If you lose your password, you can have it emailed to you from
this page. You can also change your password, which is especially
useful if you subscribe to several lists.</p>
＠＠ -449,6 +434,24 ＠＠
<a href="mailto:list-manager＠xemacs.org">XEmacs Mailing List
Manager &lt;list-manager(a)xemacs.org&gt;</a>.</p>
+ <p>
+ <strong>Note to AOL users:</strong> Because XEmacs lists are
+ public, the addresses are known to many viruses and spammers, and
+ therefore are likely to be used to conceal real sources of
+ undesired mail. AOL's filter is quite stupid about this. Several
+ AOL users are bouncing mail, and we have turned off delivery to
+ their subscriptions, because the bounce messages annoy the XEmacs
+ list managers and AOL's Postmaster does not respond to inquiries
+ (we usually can't reach you!). You will have to both fix your
+ filter and restore your subscription to delivery status using the
+ Mailman interfaces. (The XEmacs policy is not going to change.
+ If your ISP is unwilling to provide resources to ensure that mail
+ you have requested is delivered to you, XEmacs volunteers are not
+ going to make up for that lack. <strong>Note:</strong> It is now
+ over a year since the above was written; if AOL's service has
+ improved, we'd like to know at <a
+
href="mailto:list-manager＠xemacs.org">list-manager＠xemacs.org</a>)</p>
+
<h2><a id="spam" name="spam">Anti-Spam
Measures</a></h2>
<p>
＠＠ -482,7 +485,8 ＠＠
Due to a dramatic increase in the amount of spam and a near
perfect record of like 0.05% false positives, we are discarding
near-certain spam without checking as of 2004-04-27. We have
- added two more categories as of 2004-05-25. Here are the
+ added two more categories as of 2004-05-25. We've added several
+ more categories as of 2004-12-30. Here are the
criteria, any of which qualifies your post for automatic discard:
</p>
＠＠ -490,26 +494,30 ＠＠
<li>Have a known abusive from address (eg, daemon addresses at
Microsoft.com, used by the MS-Blaster/Nachi viruses)</li>
<li>Send posts with unencoded 8-bit characters in the headers</li>
- <li>Send posts in unwanted MIME charsets</li>
+ <li>Send posts in unwanted MIME charsets; except for
+ xemacs-patches (non-ISO-8859 charsets are held for moderation),
+ the xemacs-users-ja (Japanese is permitted) and xemacs-users-ru
+ (Cyrillic is permitted), only ISO-8859 charsets and Windows-1252
+ are permitted.</li>
<li>Convince SpamAssassin your post is spam (5 points, vanilla
config)</li>
- <li>Include an attachment with an extension that IE thinks is
- executable (practically everything but .txt and .tar.gz)</li>
<li>Send mail to majordomo＠xemacs (we're a Mailman site now)</li>
<li>
Use implicit addresses (ie, not addressed to the list) or too
many addresses (over 10).
</li>
<li>
+ Include any of several drug names in the headers, including
+ obfuscated versions like "V1agdra" and "c.i.a.l.i.s".
+ </li>
+ <li>
+ Include the word "rolex" or an apparent attempt to sell watches
+ in the headers.
+ </li>
+ <li>
Have a From or Sender address that procmail thinks is a daemon.
Basically that means sendmail and other MTAs, mailing list
managers, and root.
</li>
- <li>
- Include an invitation to click on a link. Links are OK, but
- don't include any text that would convince SpamAssassin you
- suggested clicking on it. XEmacs users are smart enough to
- figure that out for themselves.
- </li>
</ol>
<p>
＠＠ -518,13 +526,13 ＠＠
we throw it away, we can no longer check for false positives. If
you think your post may have been mistakenly filtered, feel free
to write to
- <a
href="mailto:listmaster＠xemacs.org">listmaster＠xemacs.org</a>.
+ <a
href="mailto:list-manager＠xemacs.org">list-manager＠xemacs.org</a>.
</p>
<p>
Please do not write to the list. Even resending is a bad idea
unless you think <em>you</em> made a mistake. Also, we request
- that you allow 24 hours for delivery before reporting a loss;
+ that you allow 4 hours for delivery before reporting a loss;
changes in DNS configuration, server outages, and the like can
cause delays of several hours even if other list traffic seems to
be arriving normally.
＠＠ -535,7 +543,7 ＠＠
documentation contains the phrase "click on the link", you would
run afoul of the "no soliciting clicks" clause---this is just an
example, patches already have an exception for that), write to
- <a
href="mailto:listmaster＠xemacs.org">listmaster＠xemacs.org</a>. See
+ <a
href="mailto:list-manager＠xemacs.org">list-manager＠xemacs.org</a>.
See
<a href="http://spamassassin.org/">SpamAssassin's site</a>
for more
information about SpamAssassin and what it is likely to block.
</p>
＠＠ -548,7 +556,36 ＠＠
<ol>
<li>
- Posts that contain only HTML.
+ Broken headers, including addresses or message IDs apparently
+ munged or added by relays.
+ </li>
+ <li>
+ Null subjects and certain single-word subjects.
+ </li>
+ <li>
+ Implicit addresses (ie, bcc'ing a list).
+ </li>
+ <li>Include an attachment with an extension that IE thinks is
+ executable (practically everything but .txt and .tar.gz).
+ </li>
+ <li>
+ A large number of phrases commonly used in spamvertisements,
+ including phrases referring to stocks, mortgages, diets,
+ well-known proprietary software, etc.
+ </li>
+ <li>
+ A variety of sexual or scatological terms that in my experience
+ are more likely to be used literally in spamverts than
+ figuratively in flames.
+ </li>
+ <li>
+ Invitations to click on a link. Links are OK, but
+ don't include any text that would convince SpamAssassin you
+ suggested clicking on it. XEmacs users are smart enough to
+ figure that out for themselves.
+ </li>
+ <li>
+ Posts that contain <em>any</em> HTML.
</li>
<li>
There are also certain restrictions on content. Try to avoid
--
Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.