[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[OT] mail filtering (Re: [cobalt-users] Co-Lo Suggestions)
- Subject: [OT] mail filtering (Re: [cobalt-users] Co-Lo Suggestions)
- From: "E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>
- Date: Sun Apr 21 13:32:13 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
JL> Date: Sun, 21 Apr 2002 11:39:12 -0700
JL> From: Jeff Lasman <jblists@xxxxxxxxxxxxx>
[ snipped a bit... and let's fork the thread, folks! ]
JL> Anyone who chooses to block on the originating IP# to the
JL> machine, knowing that it's in an aDSL block with DHCP
JL> allocation, is just being foolish.
I disagree. Once spammers learned that using an MX left a log
trail, they began spamming direct-to-MX from dialups, DSL, and
cable. Few people have a valid reason for not using their
provider's MX.
It would be interesting to see whether more direct-to-MX senders
are spammers or clued people running Unix at home. I've noted
far more of the former than the latter.
Why do you not wish to use your provider's MX? Security is not a
valid reason. Reliability might be an issue, but the fact is
that you're lumped in with SMTP abusers; the filters that people
run hurt reliability.
You can always use authenticated relaying, or SSH in to your MX
and run Pine...
--
Eddy
Brotsman & Dreger, Inc. - EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.
These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.