From: Lindsay Haisley <fmouse@fmp.com>
To: linux-hotplug@vger.kernel.org
Subject: Problems with the Sourceforge list server at 66.35.250.220
Date: Mon, 13 Dec 2004 17:50:39 +0000 [thread overview]
Message-ID: <20041213175039.GE1777@fmp.com> (raw)
It looks as though one of the Sourceforge list/mail servers has been, or was
compromised. My mail server uses advisory blocking lists, including one
from SpamCop, and the IP addres 66.35.250.220
(sc8-sf-sshgate.sourceforge.net) was listed (and blocked by my mail server)
starting last week. This is the server used by the linux-hotplug-devel
list. I disputed the listing and received the following in response to my
post.
--- FORWARDED MESSAGE ---
Date: Sat, 11 Dec 2004 00:40:20 -0600
From: SpamCop/Richard <deputies@admin.spamcop.net>
Subject: Re: BL dispute: IP:66.35.250.220
To: Lindsay Haisley <fmouse@fmp.com>
Hi Lindsay,
There isn't much we can do with this listing -- the listing is proper
and legit.
There is a copy of PHPNuke on that server that the good old 419 and
lottery scammers have discovered and are pumping their spam through it.
I trust as a member of sourceforge you are aware of the PHPNuke exploit,
so I don't have to explain it.
http://www.spamcop.net/sc?id=z700826632z7006e145b61d0b6c6dac99e6152c98cez
http://www.spamcop.net/sc?id=z700822535z21f624aad7ce275b8094b16a4af8c99ez
Richard
Please include all previous correspondence with replies
-------
----- Original Message -----
From: "Lindsay Haisley" <fmouse@fmp.com>
To: <deputies@admin.spamcop.net>
Sent: Friday, December 10, 2004 10:16 AM
Subject: BL dispute: IP:66.35.250.220
>GOOD GOD, PEOPLE!!! You're listing SOURCEFORGE!!
>
>Please STOP!!!!!
>
>$ dig -x 66.35.250.220;; ANSWER SECTION:
>220.250.35.66.in-addr.arpa. 1339 IN CNAME
>220.0/24.250.35.66.in-addr.arpa.
>220.0/24.250.35.66.in-addr.arpa. 1339 IN PTR
>sc8-sf-sshgate.sourceforge.net.
>
>There are other IPs belonging to developer lists that are also
>blocked.
>
>I'm on a number of developer mailing lists and can't get ANY email
>from them. I'm going to have to remove spamcop from the mix of
>advisory blocking lists on my mailserver.
>
>
>
>--
>This email generated by SpamCop web support form
>Referer: http://www.spamcop.net/w3m?action=blcheck&ipf.35.250.220
>Details:
>http://www.spamcop.net/admin?action=runquery;query=ipstats;paramf.35.250.220
>
--- END FORWARDED MESSAGE ---
--
Lindsay Haisley | "Fighting against human | PGP public key
FMP Computer Services | creativity is like | available at
512-259-1190 | trying to eradicate | <http://pubkeys.fmp.com>
http://www.fmp.com | dandelions" |
| (Pamela Jones) |
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2004-12-13 17:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 17:50 Lindsay Haisley [this message]
2004-12-13 17:54 ` Problems with the Sourceforge list server at 66.35.250.220 Lindsay Haisley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041213175039.GE1777@fmp.com \
--to=fmouse@fmp.com \
--cc=linux-hotplug@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.