Re: E-mail abuse report (was: Stuff Your Mailbox With $600 Checks...)
With the exception of xemacs-announce, all other XEmacs mailing lists
are open to submissions from non-subscribers. Occasionally, an idiot
will send SPAM to them. Please check the headers very carefully
before complaining to tux.org.
I would strongly suggest using a procmail recipe along the lines of
(using xemacs-beta as an example).
:0 w:
* ^Return-Path:.*xemacs-beta(-request)?＠
* ^TOxemacs-(announce|beta)＠
xemacs-beta.spool
This has all filtered all SPAM sent to xemacs-beta for me. It drops
Bcc'ed mail, but it is very rude to send Bcc'ed mail to mailing lists
anyway.
Followups to me or Jason or xemacs-beta, please.
TUX ORG Abuse Tracing <abuse(a)tux.org> writes:
This message was sent via an open relay in Korea by its original
sender,
whose traces do not remain in this message. It is unlikely that zzn.com
had anything to do with this message. TUX.ORG's only involvement is that
we host the xemacs-beta mailing list, which was spammed, and to which you
were presumably a subscriber. We have anti-spam countermeasures in place,
but there is no reliable defense against spams that are sent via
third-party relays.
I would suggest you complain to the operator of the Korean host about
their
open relay, and see if they can find out from their logs who actually sent
the message:
ns.hanyon.co.kr [203.231.147.1]
Jason and Steve, could you send out another reminder to your
subscribers
that they have subscribed to open-post mailing lists and that they should
not blame TUX.ORG when these lists get spammed?
Thanks,
David C Niemi
abuse(a)tux.org