----- Original Message -----
From: Bob Miller <[EMAIL PROTECTED]>
Sent: Tuesday, March 27, 2001 10:26 AM
Subject: [[EMAIL PROTECTED]: Returned mail: Service unavailable]


> Hi, Seth and Mike.
>
> I can't send any mail to efn.org.  I can't even send mail to
> Pat Wade asking why I can't send mail.
>
> Could you, assuming you can get through, forward this to Pat or
> somebody at EFN and find out why my mail is being rejected, and what I
> can do about it?
>
> Thanks.
>
> K<bob>
>
> ----- Forwarded message from Mail Delivery Subsystem
<[EMAIL PROTECTED]> -----
>
> Date: Tue, 27 Mar 2001 09:47:31 -0800
> From: Mail Delivery Subsystem <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Returned mail: Service unavailable
> Auto-Submitted: auto-generated (failure)
>
> The original message was received at Tue, 27 Mar 2001 09:47:29 -0800
> from kbob@localhost
>
>    ----- The following addresses had permanent fatal errors -----
> [EMAIL PROTECTED]
>
>    ----- Transcript of session follows -----
> ... while talking to mailhost.efn.org.:
> >>> MAIL From:<[EMAIL PROTECTED]>
> <<< 550 5.0.0 Access denied
> 554 [EMAIL PROTECTED] Service unavailable
>
> Reporting-MTA: dns; jogger-egg.com
> Arrival-Date: Tue, 27 Mar 2001 09:47:29 -0800
>
> Final-Recipient: RFC822; [EMAIL PROTECTED]
> Action: failed
> Status: 5.0.0
> Remote-MTA: DNS; mailhost.efn.org
> Diagnostic-Code: SMTP; 550 5.0.0 Access denied
> Last-Attempt-Date: Tue, 27 Mar 2001 09:47:30 -0800
>
> From: Bob Miller <[EMAIL PROTECTED]>
> Date: Tue, 27 Mar 2001 09:47:29 -0800
> Subject: Re: [EUG-LUG:475] Coyote Linux, a report
> To: [EMAIL PROTECTED]
> Mail-Followup-To: [EMAIL PROTECTED]
> Organization: Unlikely
> X-Quote-Of-The: Charisse: It sounds like it's a bitch to get mail through
>                           your gateways.
>                 DEC FE:   We like it that way.  Keeps the Morris worms
out.
>                 Charisse: Hey, he's a good guy. I used to rent my house to
him.
>                 DEC FE:   (speechless)
>
> Bob Miller wrote:
>
> > This is a bit long, so here are the main points.
> >
> >     * Coyote Linux makes setting up a firewall way too easy.
> >     * The Linuxcare Bootable Business Card rocks.
> >     * My firewall uses 32 watts.
> >     * Yet another failed tech startup.
> >     * Diverse tales of hardware acquisition and assembly.
>
> Here's an update.
>
> I spent the weekend trying to make Coyote do things it doesn't
> do.  Specifically, I wanted to:
>
> Put an sshd on it so I don't have to use telnet.
>
> Give home machines static IP addresses via DHCPD
>
> Put a DNS cache on it
>
> Put a DNS server on it to give names to the machines
> on the LAN
>
> Hang a whiteboard in my office.  (Oops, sorry, not Linux
> content. (-: )
>
> Anyway, I messed around for quite a while, and learned that LRP
> packages do not plug in to Coyote.  The startup scripts for Coyote are
> completely different.  I got sshd working, and started reading about
> djbdns (Bind is 400K, djbdns is 28K, and we're limited to a single
> floppy).
>
> I also learned about superformat, which will make a floppy hold 1680K
> instead of 1440K.
>
> Then I noticed that the Unix version of Coyote is 1.27, while the
> Windows version is 1.20.  I built a 1.27 disk, and it came with two
> new features:
>
> ability to format disk to 1680K size
>
> sshd
>
> Oops, I'd wasted all that time. (-:
>
> So I built a brand new 1.27 disk and threw away the disk I'd
> painstakingly customized, then edited /etc/dhcpd.conf to give several
> machines static private IP addresses, then I put up djbdns on one of
> the machines with static IP.  Is anybody here using djbdns?  Wow, it's
> as idiosyncratic as its creator!
>
> So, once again, the lesson I failed to learn is, don't tinker. (-:
>
> On Friday, my cubemate had warned me that LRP systems are nothing
> but time sinks.  I'd said, "Yeah, but I only spent five minutes
> configuring the software."  Well, he was right.  I've now spent
> a whole weekend on it.
>
> Other "upgrading pays off" news: I bought a copy of MacOS 9.1 on
> Friday, the last day before OS X was available.  That allowed me to
> run the AirPort Setup Utility on my Mac, and the latest AirPort
> Setup Utility includes a firmware upgrade for the AirPort that
> fixed most of its buggy behavior.  So my AirPort is happier now.
>
> And the whiteboard is up.  Covered with router setup notes.
>
> --
> Bob Miller                              K<bob>
> kbobsoft, LLC, software consulting
> http://kbobsoft.com                     [EMAIL PROTECTED]
>
>
> ----- End forwarded message -----
>
> --
> Bob Miller                              K<bob>
> kbobsoft, LLC, software consulting
> http://kbobsoft.com                     [EMAIL PROTECTED]
>

Reply via email to