From: Nuutti Kotivuori <nuutti.kotivuori@sonera.com>
Cc: ding@gnus.org
Subject: Re: Gnus Access mail spool by ssh
Date: 12 Jul 2000 17:54:01 +0300 [thread overview]
Message-ID: <87hf9vcsc6.fsf@sonera.com> (raw)
In-Reply-To: <m2d7kj4miv.fsf@reader.ptw.com> (Harry Putnam's message of "12 Jul 2000 04:26:48 -0700")
"Harry" == Harry Putnam <reader@newsguy.com> writes:
> Nuutti Kotivuori <nuutti.kotivuori@sonera.com> writes:
> [...]
>
>>
>> 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.
>
> This looks like an interesting approach.
> I'll have to get an imap program installed, but before I do:
>
> It isn't clear to me how fetchmail fits in here. Reading man
> fetchail, particularly the `--plugin <command>' section:
>
> " . . . . . . . Fetchmail will write to the
> plugin's stdin and read from the plugin's stdout.
>
> It appears that the fetchmail addressed here will be running on the
> parent desktop (in this case, $remote) or `mail.host.foo' so does it
> just put its standard out into the ssh tunnel in the same way as the
> mail-sources prescript `cat' command does, or is fetchmail asked to
> deliver to sendmail on the local machine?
>
> It sounds somewhat confusing. Can you describe the process in a bit
> more detail?
Local machine runs fetchmail, which runs ssh to connect to the remote
machine and run imapd, which the fetchmail will access. I will put a
few configuration scripts to demonstrate.
Local .fetchmailrc:
poll mail.host.foo with proto IMAP and options no dns
preauth ssh plugin /usr/home/xxx/bin/fetchmail-imap-wrapper
Local bin/fetchmail-imap-wrapper:
#!/bin/sh
exec ssh -i $HOME/.ssh/identity-imap -l xxx $1 /opt/net/etc/imapd
So, what nnimap should be able to do is to do exactly what --plugin
option in fetchmail does.
-- Naked
next prev parent reply other threads:[~2000-07-12 14:54 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
2000-07-12 11:26 ` Harry Putnam
2000-07-12 14:54 ` Nuutti Kotivuori [this message]
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=87hf9vcsc6.fsf@sonera.com \
--to=nuutti.kotivuori@sonera.com \
--cc=ding@gnus.org \
/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).