9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] forget authing the senders
Date: Mon, 29 Sep 2003 07:38:59 +0200	[thread overview]
Message-ID: <20030929073858.X27821@cackle.proxima.alt.za> (raw)
In-Reply-To: <7c31e1e429810c8df2a896d6b7bfdbb9@sdgm.net>; from boyd@sdgm.net on Sun, Sep 28, 2003 at 02:51:46PM -0400

On Sun, Sep 28, 2003 at 02:51:46PM -0400, boyd@sdgm.net wrote:
>
> you don't need a reverse lookup.  you never use domain name.
> getpeername(2) on lunix will hand up the address -- always
> use dotted quads.
>
Thing is, I can suppress SPAM to my own workstation, but not to my
client's users, on the off chance that something important arrives
unsolicited.

I can't afford to reply and request confirmation, because then I've
alerted the spammer that my address is in fact valid; something in
the current climate I'd rather avoid (our discussion has omitted
that fact, but I can see why).

I _could_ demand that the DNS for the connecting exchanger be set
up in both directions, preferably matched, as my mail exchanger
can validate such details.  But at the user level this is unacceptable:
too many exchangers are _not_ set up in such a fashion and many of
them are legitimate forwarders.

The same with relays, but more pervasive.  In case you wonder, my
own exchanger (cackle.proxima.alt.za [196.30.44.141]) will reject
mail from exchangers with unresolved IP addresses.  I keep stats
for that as well, but they are not as high, understandably, and
they are not web-accessible.

> anyway?  where is your face?

Rhetoric question?  It's in the Plan 9 distribution.

++L


  reply	other threads:[~2003-09-29  5:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28 18:01 boyd
2003-09-28 18:35 ` Lucio De Re
2003-09-28 18:51   ` boyd
2003-09-29  5:38     ` Lucio De Re [this message]
2003-09-29  9:22       ` boyd
2003-09-28 19:08   ` boyd

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=20030929073858.X27821@cackle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).