From: bobf@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] norelay option in /mail/lib/smtpd.conf
Date: Tue, 4 Jul 2000 11:05:34 -0400 [thread overview]
Message-ID: <200007041505.LAA25021@cse.psu.edu> (raw)
> If we are allowed to write:
> relay off # disallow relaying
> it will be more clear for everyone.
that's reasonable. you can change the code in
/sys/src/cmd/upas/smtp/spam.c to reverse the
sense of the parse.
> By the way, smtpd can controll incomming mails
> using sender-receiver address pair.
> Therefore relay filter using the pair will be more powerful.
no, the sender domain is easily forged. almost all relay
probes that we see claim to be from our domain. the peer ip
address is more difficult to forge, so we use it.
next reply other threads:[~2000-07-04 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-04 15:05 bobf [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-07-04 13:52 arisawa
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=200007041505.LAA25021@cse.psu.edu \
--to=bobf@plan9.bell-labs.com \
--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).