Since there is no active list god, it continues like this.
Now, what mailer are you using? It generates invalid date headers (they
violate the applicable RFC). A date header must have an offset or zone
indication. Many provide both the offset and a comment with the zone
indication, but this is not required. Many take it to be an indication
of that class of spam which has spammer generated (defective) date
headers.
I am using the usa.net service: (www.usa.net). The service provides
a web-page based service that enables you to have a email address
where you can set up filters and forward the mail to your real address.
Frequently, instead of posting using the buggy web-page interface,
I simply fake my address to be my usa.net address when I post on
public lists. (I don't know if that is what gave you the fake
header because I'm pretty sure I used the interface yesterday).
(Note this post isn't using the interface)
This way, I can subscribe to lists or post on usenet and my usa.net
service forwards to me only mail directly addressed to my usa.net
address. (Most spammers address their messages to a list instead
of you directly).
NOTE:
Also my usa.net is now deleting the spam that
comes from the procmail-request address.
In absence of a moderator it may be a good
solution for members.
:0:^TO: *my(_dot_)address(_at_)my(_dot_)provider(_dot_)com
/dev/null
I wonder if this recipe is case sensitive ?
Ei if I address it in upper case letters.
Will it still work ?
----------------------------------------------------------------------
Ken Thompson has an automobile which he helped design. Unlike most
automobiles, it has neither speedometer, nor gas gage, nor any of the
numerous idiot lights which plague the modern driver. Rather, if the
driver makes any mistake, a giant "?" lights up in the center of the
dashboard. "The experienced driver", he says, "will usually know
what's wrong."