On Wed, 6 Aug 1997 00:39:08 -0400, J Hulley-Miller <jhm(_at_)pobox(_dot_)com>
wrote:
On %M %N, Professional Software Engineering - Lists account wrote
^^^^^
(Say "ooops" :-)
apparently it ended up there because (among many possibilities) it didn't
have a valid Message-Id (absence of which qualifies as a highly
questionable message).
What recipe are you using to detect non-conforment Message-Ids ? Tnx.
Here's what I currently use:
:0
* ^\/Message-Id:[ ]*([^< ]|<>|<<).*
{
LOG="spamreject: $MATCH
"
:0:
$SPAMFOLDER
}
Technically, I guess the following recipe would be more on par with
what RFC822 specifies.
:0
* ! ^Message-Id:[ ]*<[^ <>]+>[ ]*$
{
LOG="spamreject: No valid Message-Id
"
:0:
$SPAMFOLDER
}
(In fact, I think I'll change mine to this, too.)
I don't know if this would match the most recent spam that hit the
list. I had it filtered out already because it was in HTML.
/* era */
The \/ and the trailing wildcard are of course unnecessary if you
don't want to log what happened.
The whitespace in the brackets consists of a tab and a space, in any
order, as usual.
--
Defin-i-t-e-ly. Sep-a-r-a-te. Gram-m-a-r. <http://www.iki.fi/~era/>
* Enjoy receiving spam? Register at <http://www.iki.fi/~era/spam.html>