From: Harry Putnam <reader@newsguy.com>
Subject: Re: Gnus Access mail spool by ssh
Date: 12 Jul 2000 12:22:39 -0700 [thread overview]
Message-ID: <m2wvircfwg.fsf@reader.ptw.com> (raw)
In-Reply-To: Nuutti Kotivuori's message of "12 Jul 2000 17:54:01 +0300"
Sorry, I'm still confused here.... Your description stops right at the
punch line.
Nuutti Kotivuori <nuutti.kotivuori@sonera.com> writes:
> Local machine runs fetchmail, which runs ssh to connect to the remote
> machine and run imapd, which the fetchmail will access. . . .
What does fetchmail do with it. Deliver to /var/mail/$USER or put it
on standard out of ssh command or what?
> Local .fetchmailrc:
>
> poll mail.host.foo with proto IMAP and options no dns
> preauth ssh plugin /usr/home/xxx/bin/fetchmail-imap-wrapper
OK .. I follow the .fetchmailrc recipe.
Is this wrapper necessary if ssh-agent is engaged?
> Local bin/fetchmail-imap-wrapper:
>
> #!/bin/sh
> exec ssh -i $HOME/.ssh/identity-imap -l xxx $1 /opt/net/etc/imapd
You aim ssh at a specific id in ~/.ssh -- login as xxx.... what does
$1 do? First argument to what... ssh? --- imapd gets invoked and
passes new mail to fetchmail? Which then does what?
I've tried this with the following scripts:
.fetchmailrc:
poll reader.local.lan with proto IMAP and options no dns
preauth ssh plugin /home/reader/scripts/ssh-fetch.sh
ssh-fetch.sh
#!/bin/sh
exec ssh reader@reader /usr/sbin/imapd
I can't tell if its going to work because some other mess with my
FreeBSD install crops up to wreck it.
$ fetchmail
/usr/libexec/ld-elf.so.1: Shared object "libssl.so.1" not found
Fetchmail installed from FreeBSD install with no complaints.
This is starting to look like too much pain in the ass for such a
simple chore.
Running just the shell script (ssh-fetch.sh) gives:
bsd > scripts/ssh-fetch.sh
* PREAUTH reader.ptw.com IMAP4rev1 v12.264 server ready
whoopee .... now what?
`man imapd' you say... Well the one I have is just one tiny cut above
useless, lacking descriptive information.
I think I like the straight forward approach laid out by Kai and Lars.
What are the chances on a local network that the `cat' command in the
mail-sources prescript will die an ugly death? I'm beginning to think
what ever risk, it is much less problem than sorting out a bunch of
complicated soft ware for this one task.
Plus, it seems one could insert some kind of `trap' that would make it
safer.
Especially since I have an overall backup of all incoming mail that
keeps the latest 1000 messages.
next prev parent reply other threads:[~2000-07-12 19:22 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
2000-07-12 15:10 ` Harry Putnam
2000-07-12 17:07 ` Kai Großjohann
2000-07-12 19:22 ` Harry Putnam [this message]
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=m2wvircfwg.fsf@reader.ptw.com \
--to=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).