9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] IMAP clients and plan9 imap server
Date: Sun,  5 Oct 2003 12:54:46 -0400	[thread overview]
Message-ID: <200310051654.h95Gslj18325@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Sun, 05 Oct 2003 15:37:43 +0200." <86r81rdcuw.fsf@gic.mteege.de>

Matthias Teege <matthias-9fans@mteege.de> writes:
>
> boyd@sdgm.net writes:
>
> > pop - highway to hell
> > imap - superhighway to hell
>
> mut% nmap www.sdgm.net
>
> Starting nmap 3.27 ( www.insecure.org/nmap/ ) at 2003-10-05 15:34 CEST
> Interesting ports on brahma.sdgm.net (64.32.179.49):
> (The 1613 ports scanned but not shown below are in state: closed)
> Port       State       Service
> 22/tcp     open        ssh
> 25/tcp     open        smtp
> 53/tcp     open        domain
> 80/tcp     open        http
> 110/tcp    open        pop-3
> 113/tcp    open        auth
> 443/tcp    open        https
> 567/tcp    open        banyan-rpc
> 993/tcp    open        imaps
> 17007/tcp  open        isode-dua
>
> I'm with you ... ;-)

Umm, I own sdgm.net (the hardware, domain, etc), so it's configured the
way *I* like it.  Boyd just uses it.  He's entitled to his opinions, but
if you're making a judgement on those based on what services run on
sdgm.net, you're doing so under false pretenses; it's really my opinions
you're judging.  :-)

	- Dan C.

(Which, for the record, in this case are: Hey, a POP and IMAP server
would be useful for the mostly non-Plan 9 types who use the system....)


  parent reply	other threads:[~2003-10-05 16:54 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-05 12:37 Matthias Teege
2003-10-05 13:04 ` boyd
2003-10-05 13:40   ` Matthias Teege
2003-10-05 13:52     ` boyd
2003-10-05 13:06 ` boyd
2003-10-05 13:37   ` Matthias Teege
2003-10-05 13:49     ` boyd
2003-10-05 15:21     ` matt
2003-10-05 15:59       ` Matthias Teege
2003-10-05 16:03         ` David Presotto
2003-10-05 17:56           ` Dan Cross
2003-10-05 19:54             ` Christopher Nielsen
2003-10-05 21:51             ` Charles Forsyth
2003-10-05 16:54     ` Dan Cross [this message]
2003-10-05 17:04       ` matt
2003-10-05 17:47       ` Matthias Teege
2003-10-06  9:58       ` boyd
2003-10-05 15:14 ` David Presotto
2003-10-05 16:06   ` Matthias Teege
2003-10-05 16:14     ` David Presotto
2003-10-05 16:55       ` matt
2003-10-06  9:11       ` boyd
2003-10-05 16:23     ` Eric Grosse
2003-10-05 17:50       ` Matthias Teege
2003-10-05 16:29     ` Jim Choate
2003-10-06  9:30   ` Matthias Teege
2003-10-06 12:25     ` David Presotto
2003-10-10 18:30     ` David Presotto
2003-10-10 20:58     ` David Presotto
2003-10-11  5:09       ` Matthias Teege
2003-10-11  0:53     ` David Presotto
2003-10-05 13:16 Tiit Lankots
2003-10-05 13:43 ` Matthias Teege
2003-10-05 16:29 andrey mirtchovski
2003-10-10 17:12 David Presotto
     [not found] <9cee3c08f48b79252e3e53aa59d488c0@plan9.bell-labs.com>
2003-10-11  5:03 ` Matthias Teege

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=200310051654.h95Gslj18325@augusta.math.psu.edu \
    --to=cross@math.psu.edu \
    --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).