From: Stainless Steel Rat <ratinox@peorth.gweep.net>
Subject: Re: Fully-qualifying Email addresses in outgoing mail
Date: 10 Dec 1999 17:17:05 -0500 [thread overview]
Message-ID: <m3ln72igpq.fsf@peorth.gweep.net> (raw)
In-Reply-To: patl@cag.lcs.mit.edu's message of "10 Dec 1999 16:36:06 -0500"
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
* patl@cag.lcs.mit.edu (Patrick J. LoPresti) on Fri, 10 Dec 1999
| Sure, having no control of your system's MX record *and* wanting to
| receive mail there is the NORM! No other configuration should even be
| supported. What was I thinking?
It is common practice to give contractors very limited system access, only
as much as they require to do their jobs, no more. When I had a ClearCase
contractor in a couple of months ago, I gave him root on the ClearCase view
server because he needed it, and that is where people could send him mail
while he was working for us. I sure as Hell did not give him access to my
name servers or mail hubs.
| It would be useful to 99.9% of all users, but not to you, so it should
| not be offered as an option. Very sensible. Thanks for your help.
I would like to know where you get your numbers. Where I work we have 300
employees, about 1/3 of which use local mail on our development systems. I
do not really consider my slice of the world to be statistically useful,
but 100 people is more than the "zero" you previously stated use local
mail. So I think I have good reason not to go breaking local mail delivery
simply because you think *all* mail must be Internet mail.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.0g (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE4UXvggl+vIlSVSNkRAuxnAJ9tYYmSeAdOCPCUjVipgyw/jjNGkwCgn/lr
JOIFyROJH0lFFGWVbza/H/4=
=6+F5
-----END PGP SIGNATURE-----
--
Rat <ratinox@peorth.gweep.net> \ Happy Fun Ball contains a liquid core,
Minion of Nathan - Nathan says Hi! \ which, if exposed due to rupture, should
PGP Key: at a key server near you! \ not be touched, inhaled, or looked at.
next prev parent reply other threads:[~1999-12-10 22:17 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 21:51 Patrick J. LoPresti
1999-12-10 9:32 ` Per Abrahamsen
1999-12-10 14:59 ` Patrick J. LoPresti
1999-12-10 15:41 ` Kai Großjohann
1999-12-10 15:51 ` Kai Großjohann
1999-12-10 16:02 ` Patrick J. LoPresti
1999-12-10 17:22 ` Stainless Steel Rat
1999-12-10 18:28 ` Patrick J. LoPresti
1999-12-10 18:32 ` Patrick J. LoPresti
1999-12-10 19:08 ` Stainless Steel Rat
1999-12-10 20:20 ` Patrick J. LoPresti
1999-12-10 20:48 ` Patrick J. LoPresti
1999-12-10 22:03 ` Stainless Steel Rat
1999-12-10 22:14 ` Russ Allbery
1999-12-10 22:24 ` Stainless Steel Rat
1999-12-10 22:41 ` Russ Allbery
1999-12-11 1:03 ` Patrick J. LoPresti
1999-12-10 22:15 ` Russ Allbery
1999-12-10 22:30 ` Stainless Steel Rat
1999-12-11 1:28 ` Patrick J. LoPresti
1999-12-11 3:09 ` Stainless Steel Rat
1999-12-11 3:14 ` Russ Allbery
1999-12-12 15:55 ` Stainless Steel Rat
1999-12-10 19:44 ` Kai Großjohann
1999-12-10 20:58 ` Stainless Steel Rat
1999-12-10 21:36 ` Patrick J. LoPresti
1999-12-10 22:17 ` Stainless Steel Rat [this message]
1999-12-11 0:55 ` Patrick J. LoPresti
1999-12-11 11:44 ` Per Abrahamsen
1999-12-11 16:58 ` Amos Gouaux
1999-12-10 20:25 ` Patrick J. LoPresti
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=m3ln72igpq.fsf@peorth.gweep.net \
--to=ratinox@peorth.gweep.net \
/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).