On Wed, 15 Aug 2007, Guy Hulbert wrote:
On Wed, 2007-08-15 at 00:35 +0200, [EMAIL PROTECTED] wrote:
Ok, so maybe blacklisting countries isn't the best way to deal with spam,
but if you're going to do it, then why not block all services but VPN and
the non-admin areas of your website at the same time as you're blocking
SMTP from that "dangerous" country?!
Because the CEO visits that country and can't send mail ...
Well, like I said, I didn't want to focus on the problems themselves; I
used a simple enough scenario that everyone on this list should be tech/
google savvy enough to set it up in minutes. Making it CEO-proof was left
as an exercise for the reader, just as figuring out how to actually set it
up on whatever system they might be using was... It sort of makes sense to
not have to include a wikipedia-sized "How to read this e-mail for
dummies"-attachment every time you write an e-mail, right?!
Oh, BTW, you forgot to complain about how I only used one example instead
of writing an exhaustive list with everything from blacklisting to grey-
listing to tarpitting to whatever which one might do with something like
netfilter instead of qpsmtpd plugins...
/Tony
PS IMNSHO people still using that old "because the CEO [...]"-line should
go on a date with a clue-by-four; I mean, if you don't consider removing
the security to the serverroom on the off chance that the CEO might want
to store his Coca-cola at a perfect 18C, then why the heck would you want
to allow access to [something] from places like Kyrgyzstan based only on
the off chance that maybe the CEO might try to access [something] while on
vacation there 3 years from now while not knowing enough and/or without
having his computer/smartphone set up to use the VPN?
