Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Philipp Haselwarter <philipp.haselwarter@gmx.de>
To: info-gnus-english@gnu.org
Subject: Re: my vs maildir
Date: Mon, 03 Jan 2011 03:54:59 +0100	[thread overview]
Message-ID: <87vd26d7cs.fsf@nzebook.haselwarter.org> (raw)
In-Reply-To: <ifqpk6$ba2$1@quimby.gnus.org>

On Sun, 02 Jan 2011 22:10:30 +0100, Richard Riley
<rileyrg@googlemail.com> said: 

---8<---[snipped 28 lines]---8<---

RR> other machines can talk to it (if you want) e.g your dev machine on
RR> the desk could have the router routing imap to it so you can read
RR> your email from anywhere in the word.

Just another open port, another socket you're blasting your passwords
through. If you set up dovecot properly to use imaps, I guess you should
be good. But I think the shell method is preferable to plain auth. For
you LAN: wrap ssh around the dovecot command.

That being said - I also still run dovecot as server: for
offlineimap. Dno if offlineimap could do without a server, guess I'll
have to take a look.

Anyone?


-- 
Philipp Haselwarter

  reply	other threads:[~2011-01-03  2:54 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 21:59 prad
2010-12-31  0:35 ` Brett Viren
2010-12-31  8:50 ` Tassilo Horn
2011-01-01  6:21 ` prad
2011-01-01  9:16 ` prad
2011-01-01 13:06   ` Philipp Haselwarter
2011-01-06 16:37     ` Eric S Fraga
     [not found]   ` <mailman.0.1293887230.28475.info-gnus-english@gnu.org>
2011-01-01 13:52     ` Richard Riley
2011-01-01 22:35       ` Philipp Haselwarter
2011-01-01 16:24   ` Brett Viren
2011-01-01 20:56     ` prad
     [not found]     ` <mailman.12.1293915387.32515.info-gnus-english@gnu.org>
2011-01-02  9:04       ` Richard Riley
2011-01-02 10:38         ` Philipp Haselwarter
2011-01-02 18:38         ` prad
     [not found]         ` <mailman.4.1293993514.23049.info-gnus-english@gnu.org>
2011-01-02 20:02           ` Richard Riley
2011-01-02 21:03             ` Brett Viren
     [not found]             ` <mailman.0.1294002284.29417.info-gnus-english@gnu.org>
2011-01-02 21:10               ` Richard Riley
2011-01-03  2:54                 ` Philipp Haselwarter [this message]
2011-01-03  3:12                   ` Brett Viren
     [not found]                   ` <mailman.29.1294024360.15403.info-gnus-english@gnu.org>
2011-01-03 13:50                     ` Richard Riley
2011-01-03 16:42                       ` David Brown
2011-01-03 17:42                         ` Richard Riley
2011-01-03 19:38                           ` Dan Christensen
2011-01-03 17:21                       ` Brett Viren
     [not found]                 ` <mailman.27.1294023329.15403.info-gnus-english@gnu.org>
2011-01-03 13:44                   ` Richard Riley
2011-01-03  3:02             ` prad
     [not found]             ` <mailman.28.1294023762.15403.info-gnus-english@gnu.org>
2011-01-03 13:48               ` Richard Riley
2011-01-03 20:28                 ` prad
2011-01-03 23:10                   ` Brett Viren
2011-01-03 23:31                     ` Yuri D'Elia
     [not found]                   ` <mailman.20.1294096220.614.info-gnus-english@gnu.org>
2011-01-03 23:57                     ` Richard Riley
2011-01-04 11:30                       ` Adam Sjøgren
     [not found] <mailman.0.1293746291.12460.info-gnus-english@gnu.org>
2010-12-31  2:33 ` Richard Riley

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=87vd26d7cs.fsf@nzebook.haselwarter.org \
    --to=philipp.haselwarter@gmx.de \
    --cc=info-gnus-english@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 NNTP newsgroup(s).