Gnus development mailing list
 help / color / mirror / Atom feed
From: Harry Putnam <reader@newsguy.com>
Subject: Gnus Access mail spool by ssh
Date: 08 Jul 2000 14:02:27 -0700	[thread overview]
Message-ID: <m2itugl4ik.fsf@reader.ptw.com> (raw)


[ also posted to freebsd-mobil list]

I have ssh-1.2.27 installed and use it extensively.  In fact I've set
my machines (personal at home machines) to only allow connections via
ssh.

Now I want to have a laptop running FreeBSD 4.0 networked to desktop
running Redhat linux, be able to  view/manipulate mail on the parent machine
but don't want to  setup pop, imap or  special sendmail stuff.  I
don't want more daemons running that can be exploited from the internet.
And haven't really looked into firewall technique.

I realize there are other ways via scp, rsync, mirror using ssh  but it seems
the most convient to have the laptop users inbox be a ssh connection
to the parent desktop at /var/spool/mail/$NAME

I'll  use procmail to send a copy of every mail to
/var/spool/mail/NAME, on the parent machine.  I know how to do that part.
Then both machines will have full access to the mail without screwing
up the others spool.

I would like to just have $MAIL on the laptop set to
`ssh PARENT:/var/spool/mail/$NAME' to access the procmail created 
spool on the parent machine.

I'm pretty lost how to script this so that when a mail client is
called, a ssh connection is initiated and /var/spool/mail/$NAME
becomes the inbox.

What would be nice is to just say `M-x gnus' and a ssh connection is
started and mail in PARENT:/var/spool/mail/$NAME is viewed, expired
saved etc.

I have `TRAMP' installed and can think of several ways that
application could be called in to do this job, but would rather find a
more general solution so that *any* mail client could use it.

I have ssh-agent setup and do understand how to avoid password
problems during connections. (Thanks Kai)




             reply	other threads:[~2000-07-08 21:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-07-08 21:02 Harry Putnam [this message]
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
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=m2itugl4ik.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).