At 20:16 -0700 9/17/00, Dave Robbins wrote:
I got put on at least two lists on egroups.com without my approval
and certainly no action on my part. The list admin appears to funnell
his/her lists through a list at cuy.net as can be seen in either of
two headers included below. I have contacted the list manager at cuy.net
and notify(_at_)egroups(_dot_)com without any action or response on their part.
All my other recipes work yet I have tried redirecting the mail from
these two lists to /dev/null and back to the list admin without success.
The list is running on a majordomo server on a cuy.net machine. See
below for analysis.
Any suggestions on who to contact at egroups to get someone to act
against such abuse?
abuse(_at_)egroups(_dot_)com and abuse(_at_)yahoo(_dot_)com is a good start. Send a copy to
postmaster(_at_)cuy(_dot_)net, too. You may want to mention that cuy.net seems
to be running a majordomo reflector of eGroups mailing lists, which
they may not like. The subscribed address is dads(_at_)cuy(_dot_)net(_dot_) But it
isn't eGroups' problem; cuy.net is the culprit.
You may find your removal from these lists, ah, expedited if you're
willing to use one of several methods. The clean one is to generate
bounces for majordomo to deal with:
:0
^(From|Received).*tom\.cuy\.net
{
LOG="$DT Rejected mail: tom.cuy.net
"
EXITCODE=67
:0:
$MAILDATA/cuynet-f
}
Unless it's severely malconfigured, majordomo will give up on you
eventually. Note that my recipe doesn't auto-trash the messages (who
knows, maybe the postmaster will eventually respond).
You could also set up your sendmail to deny tom.cuy.net; this would
make that problem go away until either they give up or change machine
names and IP addresses. But that's not a procmail solution, and it
presumes you're the admin of the machine.
The dirty way is to use your procmail skills for evil and not good. I
won't go into details -- it's a last-resort kind of thing (hint: lots
of forwarding). I don't advise it unless you have a pitch-black
heart. :-)
Regards,
Scott
From dads-owner(_at_)tom(_dot_)cuy(_dot_)net Sun Sep 17 18:10:52 2000
Received: from tom.cuy.net (tom.cuy.net [207.246.237.133])
by geosci.geol.ucsb.edu (8.9.3+Sun/8.9.3) with ESMTP id SAA26004
for <dave(_at_)geosci(_dot_)geol(_dot_)ucsb(_dot_)edu>; Sun, 17 Sep
2000 18:10:51 -0700 (PDT)
Your machine got it from tom.cuy.net.
Received: (from majordom(_at_)localhost)
by tom.cuy.net (8.8.7/8.8.7) id VAA04070
for dads-outgoing; Sun, 17 Sep 2000 21:17:19 -0400
Majordomo got it from the queue locally.
X-Authentication-Warning: tom.cuy.net: majordom set sender to
owner-dads(_at_)cuy(_dot_)net using -f
Received: from f19.egroups.com (f19.egroups.com [208.50.99.238])
by tom.cuy.net (8.8.7/8.8.7) with SMTP id VAA04066
for <dads(_at_)cuy(_dot_)net>; Sun, 17 Sep 2000 21:17:09 -0400
cuy.net got it from egroups. The address it was sent to is
dads(_at_)cuy(_dot_)net(_dot_)
The rest is unimportant, and mostly similar. tom.cuy.net is your target.
Scott
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail