Hey, Mr. Dunsmore, thanks for all the hard work! To Bill and the others who helped out as well. People in this list have been talking about fixing the server for what seems like years, you guys actually did something.
Don't curse the darkness - light a fart!
On Wed, 2004-08-25 at 23:46, Jonathan Hutchins wrote:
Hey, Mr. Dunsmore, thanks for all the hard work! To Bill and the others who helped out as well. People in this list have been talking about fixing the server for what seems like years, you guys actually did something.
You are most welcome. I do apologize for the duration, but I wanted to do things correctly. Also I want to thank Mike Neuliep for hosting the server for the past six (?) years. I'm open to trouble reports tomorrow, as I've got most of the issues I'm aware of dealt with.
-- Hal Duston <-- Note spelling please, Mr. Hutchins! :-)
On Wednesday 25 August 2004 11:55 pm, Hal Duston wrote:
On Wed, 2004-08-25 at 23:46, Jonathan Hutchins wrote:
Hey, Mr. Dunsmore, thanks for all the hard work! To Bill and the others who helped out as well. People in this list have been talking about fixing the server for what seems like years, you guys actually did something.
You are most welcome. I do apologize for the duration, but I wanted to do things correctly. Also I want to thank Mike Neuliep for hosting the server for the past six (?) years. I'm open to trouble reports tomorrow, as I've got most of the issues I'm aware of dealt with.
-- Hal Duston <-- Note spelling please, Mr. Hutchins! :-)
I just wanted to extend my thanks to Mr. Hal Duston as well. Thanks man!
Rich
Rich Edelman wrote:
On Wednesday 25 August 2004 11:55 pm, Hal Duston wrote:
On Wed, 2004-08-25 at 23:46, Jonathan Hutchins wrote:
Hey, Mr. Dunsmore, thanks for all the hard work! To Bill and the others who helped out as well. People in this list have been talking about fixing the server for what seems like years, you guys actually did something.
You are most welcome. I do apologize for the duration, but I wanted to do things correctly. Also I want to thank Mike Neuliep for hosting the server for the past six (?) years. I'm open to trouble reports tomorrow, as I've got most of the issues I'm aware of dealt with.
-- Hal Duston <-- Note spelling please, Mr. Hutchins! :-)
I just wanted to extend my thanks to Mr. Hal Duston as well. Thanks man!
Rich
Now that everybody has thanked _me_. I need to name the other people involved who actually _did_ most of the work. They include Chris Bier, Bill Cavalieri, and Jason Clinton. See? I'm learning to delegate!
-- Hal Duston
Hal Duston wrote:
I just wanted to extend my thanks to Mr. Hal Duston as well. Thanks man!
Rich
Now that everybody has thanked _me_. I need to name the other people involved who actually _did_ most of the work. They include Chris Bier, Bill Cavalieri, and Jason Clinton. See? I'm learning to delegate!
-- Hal Duston
Way to go guys! I went to the server install party and drank enough beer for everyone else. I can confirm that Jason Clinton and Chris Bier did the install, Bill Cavalieri donated and built the box. They wiped his Gentoo install. Bill and I drank beer and supervised while Jason and Chris got Debian installed, updated and tweaked. Hal did the mail and website migration.
Thanks again to Walt at Netstandard for the free hosting. I took the tour and it's a real class operation. I was amazed.
Thanks to Mike Neuliep for starting KCLUG long ago and hosting the LUG server for all these thankless years. He's been doing this since at least 1998, possibly 96. Thanks to Rich Minear, who is probably not around the mail list anymore, but he had a hand in the old LUG website and ran the meetings back when we still met at the Power and Light building. Rich also had a hand in teaching me about TCP/IP when I was still a newbie. Thanks for your patience.
---------------------------------------------- Somewhere there is a village missing an idiot.
Hmm...
bam:/home/gerald> host -t mx kclug.org kclug.org mail is handled by 20 marauder.illiana.net. kclug.org mail is handled by 10 kclug.org.
bam:/home/gerald> telnet kclug.org 25 Trying 139.146.133.42... Connected to kclug.org. Escape character is '^]'. 220 kclug.org ESMTP Postfix (Debian/GNU) quit 221 Bye Connection closed by foreign host.
We're now running on Postfix/Mailman. The delay between sending my last post and receiving it from the kclug server was less than two minutes. This is SO cool. Excellent work, gentlemen.
<scream style="like: howard-dean;"> YEEAAAAAAHHHHHH!!!!! </scream>
Gerald Combs wrote:
bam:/home/gerald> telnet kclug.org 25 Trying 139.146.133.42... Connected to kclug.org. Escape character is '^]'. 220 kclug.org ESMTP Postfix (Debian/GNU) quit 221 Bye Connection closed by foreign host.
Umm, why is telnet running/responding on the server?
---------------------------------------------- Somewhere there is a village missing an idiot.
Brian Kelsay wrote:
Gerald Combs wrote:
bam:/home/gerald> telnet kclug.org 25 Trying 139.146.133.42... Connected to kclug.org. Escape character is '^]'. 220 kclug.org ESMTP Postfix (Debian/GNU) quit 221 Bye Connection closed by foreign host.
Umm, why is telnet running/responding on the server?
I'm not sure if telnet is running on the server, but Postfix is responding on port 25. Most telnet clients allow you to specify a port number after the host name. If you specify a non-standard port from Telnet's perspective (not 23), the telnet client just opens a direct ("raw") connection (normally it tries to exchange environment information upon connecting). At this point you're just pushing bytes at the server, like any other TCP client. Since a bunch of popular TCP protocols are text-based, this means you can interact with the server manually.
This has several uses, including the ability to apply Occam's razor in a troubleshooting situation. If someone is having trouble connecting to a web server, you can run
---- bam:/home/gerald> telnet www.cnn.com 80 Trying 64.236.16.52... Connected to www.cnn.com. Escape character is '^]'. HEAD / HTTP/1.0 Host: www.cnn.com
HTTP/1.1 200 OK Server: Netscape-Enterprise/6.1 AOL Date: Fri, 27 Aug 2004 04:13:04 GMT Last-modified: Fri, 27 Aug 2004 04:13:05 GMT Expires: Fri, 27 Aug 2004 04:14:05 GMT Cache-control: private,max-age=60 Content-type: text/html Content-length: 0 Connection: close
Connection closed by foreign host. ----
In this case, we know that CNN is up, so we might want to start looking for problems on the browser end.
Other examples:
POP ---- xxxx:/home/gerald> telnet xxxxxxx 110 Trying xxxxxxxxxx... Connected to xxxxxxx. Escape character is '^]'. +OK POP3 xxxxxx 2003.85 server ready user xxxxxx +OK User name accepted, password please pass xxxxxx +OK Mailbox open, 1188 messages quit +OK Sayonara Connection closed by foreign host. ----
NNTP ---- bam:/home/gerald> telnet news-server.kc.rr.com 119 Trying 24.94.170.87... Connected to news-server.kc.rr.com. Escape character is '^]'. 200 Powered By Twister - Road Runner - Kansas City, MO (Twister v2.0.6.342) group rec.bicycles.tech 211 2322 335670 338086 rec.bicycles.tech quit 205 GoodBye Connection closed by foreign host. ----
Gerald Combs wrote:
Brian Kelsay wrote:
Gerald Combs wrote:
bam:/home/gerald> telnet kclug.org 25 Trying 139.146.133.42... Connected to kclug.org. Escape character is '^]'. 220 kclug.org ESMTP Postfix (Debian/GNU) quit 221 Bye Connection closed by foreign host.
Umm, why is telnet running/responding on the server?
I'm not sure if telnet is running on the server, but Postfix is responding on port 25. Most telnet clients allow you to specify a port number after the host name. If you specify a non-standard port from Telnet's perspective (not 23), the telnet client just opens a direct ("raw") connection (normally it tries to exchange environment information upon connecting). At this point you're just pushing bytes at the server, like any other TCP client. Since a bunch of popular TCP protocols are text-based, this means you can interact with the server manually.
This has several uses, including the ability to apply Occam's razor in a troubleshooting situation. If someone is having trouble connecting to a web server, you can run
Sorry, I didn't get a good look at the port.
because mail servers respond to telnet via thier port. So do other services. Try it on other mail servers. I wouldnt actually pass login information with it across an untrusted network but its great for a quick test to see if the mail server is responding.
dre
On Thu, 26 Aug 2004, Brian Kelsay wrote:
Gerald Combs wrote:
bam:/home/gerald> telnet kclug.org 25 Trying 139.146.133.42... Connected to kclug.org. Escape character is '^]'. 220 kclug.org ESMTP Postfix (Debian/GNU) quit 221 Bye Connection closed by foreign host.
Umm, why is telnet running/responding on the server?
Somewhere there is a village missing an idiot. _______________________________________________ Kclug mailing list [email protected] http://kclug.org/mailman/listinfo/kclug
On Thursday 26 August 2004 10:01 pm, Gerald Combs wrote:
We're now running on Postfix/Mailman. The delay between sending my last post and receiving it from the kclug server was less than two minutes. This is SO cool. Excellent work, gentlemen.
Wow, yeah, I posted to the list and by the time I read a handful of messages I had caught up with my own post! That is SO much better!
Quoting Jonathan Hutchins [email protected]:
On Thursday 26 August 2004 10:01 pm, Gerald Combs wrote:
We're now running on Postfix/Mailman. The delay between sending my last post and receiving it from the kclug server was less than two minutes. This is SO cool. Excellent work, gentlemen.
Wow, yeah, I posted to the list and by the time I read a handful of messages I had caught up with my own post! That is SO much better!
Yes, it is send...posted.
jonathan
-
Brian Kelsay -
Dre G. -
Gerald Combs -
Hal Duston -
Jonathan Hutchins -
Rich Edelman -
staff＠tektronic.org