Gnus development mailing list
 help / color / mirror / Atom feed
From: Nuutti Kotivuori <nuutti.kotivuori@sonera.com>
Cc: Alexandre Oliva <oliva@lsd.ic.unicamp.br>,
	Harry Putnam <reader@newsguy.com>,
	ding@gnus.org
Subject: Re: Gnus Access mail spool by ssh
Date: 12 Jul 2000 11:52:06 +0300	[thread overview]
Message-ID: <87lmz7d93d.fsf@sonera.com> (raw)
In-Reply-To: <vafhf9vwz58.fsf@lucy.cs.uni-dortmund.de> (Kai =?ISO-8859-1?Q?Gro=DFjohann=27s?= message of "Wed, 12 Jul 2000 10:06:43 +0200")

"Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:
> On 11 Jul 2000, Alexandre Oliva wrote:
>> On Jul 11, 2000, Harry Putnam <reader@newsguy.com> wrote:
>> 
>>> But can fetchmail be used to fetch a spool
>>> file from a remote machine not running a special server?
>> 
>> Yup, as long as you can run the imapd program on the other end.
>> Then, you write a script that `ssh' to the other end and runs imapd
>> and tells fetchmail to use it as a plugin with preauth ssh.
> 
> I think Harry does not want to run a food on the other end, not even
> an imapd :-)
> 
> But of course it would be the best situation.  Setting up a POP server
> ought to be simple enough, for example.

Err. He won't be forced to run imapd as a daemon listening to an imap
port. Just as a program to access mail. To clear things up:

_Not_:
$ telnet mail.host.foo imap2
Trying 127.0.0.1...
Connected to oro.
Escape character is '^]'.
* OK mail.host.foo IMAP4rev1 v12.264 server ready

_But_:
$ ssh mail.host.foo
mail$ /usr/sbin/imapd
* PREAUTH mail.host.foo IMAP4rev1 v12.264 server ready

Most imap servers are able to run from the command line and notice the
situation and start up preauthenticated. And this is what can be used
by fetchmail and the plugin option - and if nnimap does not support
this, it would be nice.

-- Naked



  reply	other threads:[~2000-07-12  8:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-08 21:02 Harry Putnam
2000-07-08 23:08 ` Kai Großjohann
2000-07-09  2:03 ` Alan Shutko
2000-07-10  4:56   ` Harry Putnam
2000-07-10 11:48     ` Kai Großjohann
     [not found]     ` <lfllmzam504.fsf@rupert.informatik.uni-stuttgart.de>
2000-07-11 12:39       ` Harry Putnam
2000-07-11 22:28         ` Alexandre Oliva
2000-07-12  0:01           ` Harry Putnam
2000-07-12  2:31             ` Alexandre Oliva
2000-07-12  8:06               ` Kai Großjohann
2000-07-12  8:52                 ` Nuutti Kotivuori [this message]
2000-07-12 11:26                   ` Harry Putnam
2000-07-12 14:54                     ` Nuutti Kotivuori
2000-07-12 15:10                       ` Harry Putnam
2000-07-12 17:07                         ` Kai Großjohann
2000-07-12 19:22                       ` Harry Putnam
2000-07-12 19:42                         ` Alan Shutko
2000-07-12 21:28                           ` Harry Putnam
2000-07-13  3:50                             ` Nuutti Kotivuori
2000-07-13  3:46                         ` Nuutti Kotivuori
2000-07-14 11:02                           ` Harry Putnam
2000-07-16 15:11                             ` Nuutti Kotivuori
2000-07-15  0:29                   ` Simon Josefsson
2000-07-10 12:00 ` Nuutti Kotivuori

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=87lmz7d93d.fsf@sonera.com \
    --to=nuutti.kotivuori@sonera.com \
    --cc=ding@gnus.org \
    --cc=oliva@lsd.ic.unicamp.br \
    --cc=reader@newsguy.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).