From: pete@dunnington.u-net.com (Peter Turnbull)
Subject: [pups] Totally off topic question
Date: Sat, 22 Mar 2003 09:20:15 GMT [thread overview]
Message-ID: <10303220920.ZM25308@mindy.dunnington.u-net.com> (raw)
In-Reply-To: "Ian King" <iking@killthewabbit.org> "Re: [pups] Totally off topic question" (Mar 21, 19:31)
On Mar 21, 19:31, Ian King wrote:
> Yup. I used to do that, but had an older version of sendmail and got
> 'co-opted' as a relay host for a spammer. :-(
I've seen a few attempts to do that. I should point out that even if
you only run sendmail for the benefit of machines on your own network,
and even if you use a dialup (rather than always-on) connection, you
want the ant-relay stuff. I see regular attempts to connect to port 25
on my hub, even though it's behind a dynamic IP address on an ISDN
dialup (I also see regular attempts to connect to the telnet, ssh, and
ftp ports, and others, maybe 2-3 times a week. If you run a common
operating system, don't assume that a dynamic IP address, or NAT, or
using a dialup, gives any worthwhile protection).
> FWIW: rather than update sendmail and hack another .cf, I bought a
> Windows-based mail server
Nowadays, it's easy to use m4 to set up sendmail.cf for the common
sorts of home use -- just define the settings for masquerading and
smarthost, and press go (more or less). The only time you need to hack
it a bit is if you want something unusual, like some mail going to the
local machine and some forwarded to other machines on your network, or
using UUCP.
> Instead, I use my free time to hack 2.11BSD and UNIX v6! :-)
I have to admit that sounds like a better use of the time :-)
--
Pete Peter Turnbull
Network Manager
University of York
prev parent reply other threads:[~2003-03-22 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 23:04 Robin Birch
[not found] ` <robinb@ruffnready.co.uk>
2003-03-22 0:31 ` Peter Turnbull
2003-03-22 3:31 ` Ian King
[not found] ` <iking@killthewabbit.org>
2003-03-22 9:20 ` Peter Turnbull [this message]
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=10303220920.ZM25308@mindy.dunnington.u-net.com \
--to=pete@dunnington.u-net.com \
/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).