Forward entire gnupg $HOME

Brian Minton brian at minton.name
Wed Jan 8 14:54:31 CET 2020


On Mon, Sep 09, 2019 at 11:39:01PM +0200, Ángel wrote:
> On 2019-09-05 at 08:59 +0200, john doe wrote:
> > On 9/4/2019 10:41 PM, Andre Klärner wrote:
> > > I usually use my workstation to do everything, but since I can't
> > > access my mailbox via NFS anymore (different story), I resorted to
> > > sshing into my email server, and doing all the mailing needs right
> > > there, locally.
> (...)
> > 
> > The obvious solution would be to use mutt on your work station! :)
> 
> Using mutt locally seems much simpler than forcing gnupg to work that
> way.  You mention that you can no longer access your mailbox via nfs,
> but since you can ssh to the email server, maybe you could mount it
> with sshfs?

There are some problems with sshfs, however, such as slowness and
locking.  It would probably be better to run an imap daemon on your mail
server, and have mutt use imap to access the mailbox.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 390 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-users/attachments/20200108/6fa6f4a3/attachment-0001.sig>


More information about the Gnupg-users mailing list