unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: <tomas@tuxteam.de>
To: help-gnu-emacs@gnu.org
Subject: Re: Reading remote emails in gnus
Date: Fri, 4 Mar 2016 11:15:00 +0100	[thread overview]
Message-ID: <20160304101500.GA30077@tuxteam.de> (raw)
In-Reply-To: <87ziueil9o.fsf@skimble.plus.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Mar 04, 2016 at 10:34:59AM +0000, Sharon Kimble wrote:
> 
> 
> My main machine is called "london" and gets its system emails from
> '(setq mail-sources '((file :path "/var/mail/boudiccas")'.
> 
> I have a second machine functioning as a fileserver called "norwich". It
> is generating system emails, but how do I access them using gnus please?
> I've looked at the gnus manual and this seemed to fit -
> 
> --8<---------------cut here---------------start------------->8---
> (setq mail-sources '((pop :server "norwich" :user "boztu")))
> --8<---------------cut here---------------end--------------->8---
> 
> except its not a pop server.
> 
> So I've tried this -
> 
> --8<---------------cut here---------------start------------->8---
> (setq mail-sources '((file :server "norwich" :path "/var/mail/boztu")))
> --8<---------------cut here---------------end--------------->8---

I'd guess that gnus doesn't "understand" file servers directly (how
should it), but if norwich is a file server chances are that it is
exporting (parts of) its file system somehow and london is possibly
mounting some of those exports anyway.

If norwich's /var/mail/boztu is one of those lucky locations which
end up mounted in london, say under /net/norwich/var/mail/boztu (this
is just an example!), then it should be visible as

 ╭────
 │(setq mail-sources '((file :path "/net/norwich/var/mail/boztu")
 ╰────

i.e. as seen from gnus it's just a regular file; the fact that it's
mounted from norwich should be irrelevant.

If that's not the case yet, you can arrange norwich's exports to
include the relevant mailboxes and london's mounts to mount them
somewhere.

Alternatively, you can set up a server (IMAP or POP) on norwich
in a way that it's accessible from london.

Even more alternatively, you can configure norwich's SMTP server
(which most probably is there) to forward its mails to london,
and london's SMTP server to drop those mails into a convenient
mailbox.

I think it's a matter of taste which flavour you choose. I'd tend
to the third one, on the principle that all admin related mails
from your network end up in one place (mailbox or set of mailboxes),
independently of your mail user agent.

regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAlbZYCQACgkQBcgs9XrR2kbX+ACfY29W5+3m1WhqTa87eIOErDsm
brwAn14sDDDK55rMSQdaTgZL3kQsRywh
=PG8r
-----END PGP SIGNATURE-----



      reply	other threads:[~2016-03-04 10:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-04 10:34 Reading remote emails in gnus Sharon Kimble
2016-03-04 10:15 ` tomas [this message]

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160304101500.GA30077@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).