Gnus development mailing list
 help / color / mirror / Atom feed
From: Norbert Koch <n.koch@delta-ii.de>
Subject: Re: pop server access?
Date: 25 Oct 1998 12:54:24 +0100	[thread overview]
Message-ID: <vo90i4n9fz.fsf@apollonius.delta-ii.de> (raw)
In-Reply-To: Stainless Steel Rat's message of "23 Oct 1998 20:16:19 -400"

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> "viteno" == Norbert Koch <n.koch@delta-ii.de> writes:
> 
> >> What happens when, from a shell on the same machine as you are running
> >> Emacs, you type 'telnet mail.delta-ii.de 110'?
> 
> viteno> Hi,
> 
> viteno> odd enough this works like a charm.
> 
> I need to know what happens when you telnet to your pop server directly,
> from the machine that is having problems, or I am never going to be able to
> figure out what is failing.

Hi ratinox,

first of all, thanks for the time you spend on helping me solving this 
problem (it still exists on 0.39)

So, here we go. I've written a simple test mail and retrieved it by
telnet.

(apollonius 3:3)$ telnet mail 110
Trying 192.9.200.11...
Connected to mail.delta-ii.de.
Escape character is '^]'.
+OK QPOP (version 2.2) at apollonius.delta-ii.de starting.  
user nok_mail
+OK Password required for nok_mail.
pass <you don't need to know my password, do you :-)>
+OK nok_mail has 1 message (415 octets).
list
+OK 1 messages (415 octets)
1 415
.
retr 1
+OK 415 octets
Return-Path: <norbert>
Received: by mail.delta-ii.de (Smail3.2.0.101/lists.delta-ii.de)
        via Delta-II
        id m0zXOcX-000AAcC; Sun, 25 Oct 1998 12:46:05 +0100 (MET)
Message-Id: <m0zXOcX-000AAcC@mail.delta-ii.de>
Date: Sun, 25 Oct 1998 12:46:05 +0100 (MET)
From: norbert (Norbert Koch)
To: nok_mail@delta-ii.de
subject: pop access test
X-UIDL: a734e2360b4080d73ed014c285d1c5a4

simple mail for pop access.

.
dele 1
+OK Message 1 has been deleted.
quit
+OK Pop server at apollonius.delta-ii.de signing off.
Connection closed by foreign host.
(apollonius 3:4)$ 


All in all, this looks just fine to me. 

Tia, norbert.

-- 
DELTA Industrie Informatik GmbH, Fellbach, Germany (+49.711.5715137)
A rattlesnake that doesn't bite teaches you nothing!


  parent reply	other threads:[~1998-10-25 11:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-20 10:53 Norbert Koch
1998-10-20 17:57 ` Lars Magne Ingebrigtsen
1998-10-22  5:21   ` Norbert Koch
     [not found]     ` <x7yaq8gpp8.fsf@peorth.gweep.net>
1998-10-23  4:39       ` Norbert Koch
     [not found]         ` <x7emry3jcc.fsf@peorth.gweep.net>
1998-10-25 11:54           ` Norbert Koch [this message]
     [not found]             ` <x7zpak5fgp.fsf@peorth.gweep.net>
1998-10-26  6:02               ` Norbert Koch
     [not found]                 ` <x7btmyyk3x.fsf@peorth.gweep.net>
1998-10-27 13:18                   ` Norbert Koch
1998-11-04  7:47                   ` Shenghuo ZHU
     [not found]                     ` <x7u30fpi7v.fsf@peorth.gweep.net>
1998-11-04 18:00                       ` Jan Vroonhof
     [not found]   ` <x790ia3thq.fsf@peorth.gweep.net>
1998-10-22  7:14     ` Urban Engberg
1998-10-22  7:22   ` Urban Engberg

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=vo90i4n9fz.fsf@apollonius.delta-ii.de \
    --to=n.koch@delta-ii.de \
    /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).