Re: Good Day
> What bothers me in all of this is that Debian lists are managed so
> to let this happen. I subscribed to 6 debian mailing lists recently,
> dropped two right away because there was so much spam I've never seen
> before. Today I received 8 messages related to that f*ng crap from
> or whatever place out there through deb mailing lists. I haven't seen
> much spam on any other mailing list in over a year.
I believe that it's an intentional policy not to reject anything on the
grounds that it _may_ be a valid poster, and guilty because of some minor
configuration error should not mean automated lockout.
> Email should never be accepted from poorly (or intensionaly baddly)
> servers that do not follow RFCs.
> Received: (qmail 17581 invoked by uid 38); 1 Jul 2002 11:54:29 -0000
> X-Envelope-Sender: email@example.com
> Received: (qmail 14664 invoked from network); 1 Jul 2002 11:52:03 -0000
> Received: from master.debian.org (22.214.171.124)
> by murphy.debian.org with SMTP; 1 Jul 2002 11:52:03 -0000
> Received: from (ok62977.com) [126.96.36.199]
> by master.debian.org with smtp (Exim 3.12 1 (Debian))
> id 17Ozil-0003W2-00; Mon, 01 Jul 2002 06:51:58 -0500
> From: "Mr.Muyiwa Ige" <firstname.lastname@example.org>
> Reply-To: email@example.com
> Assuming the spam came from 188.8.131.52 it would be very easy to
> it based on the fact that there is no RR in DNS for that IP.
I have a /28 at work, small enough that I don't get the run reverse DNS
myself, the ISP provides it. If I want to make changes, I fax them a
list of hostnames and IPs, and they update it. Sometimes they even
remember to increment the serial number. Occasionally they decide to
blow away a section of the zone file because someone made a mistake.
Should all my email be refused by offsite servers while my ISP is
being stupid? Even though it's otherwise correctly formed? I don't
think so. Liberal in what you accept is the catch phrase here.
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com