From: geoff@collyer.net
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Lowlifes who have NAT routers
Date: Wed, 16 Jan 2002 15:33:34 -0800 [thread overview]
Message-ID: <20020116233344.1005519A71@mail.cse.psu.edu> (raw)
You could set
site = 9fs.org
in termrc and cpurc. I do something similar.
cse.psu.edu is getting to be a pain. It started checking reverse maps
against HELO domains or sender addresses or something a while ago, so
I initially routed mail to cse.psu.edu via my ISP's smtp server, then
got control of my reverse map from my ISP and implemented RFC 2317 in
my copy of DNS (Dave has those changes now). Now I can send directly
to cse.psu.edu again.
next reply other threads:[~2002-01-16 23:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 23:33 geoff [this message]
2002-01-16 23:49 ` Scott Schwartz
-- strict thread matches above, loose matches on Subject: below --
2002-01-16 20:21 bwc
2002-01-16 18:53 nigel
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=20020116233344.1005519A71@mail.cse.psu.edu \
--to=geoff@collyer.net \
--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).