From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: George Hartzell <hartzell@alerce.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Two problems with sieve-manage
Date: Thu, 13 Jun 2019 19:40:48 -0700 [thread overview]
Message-ID: <87o930ga8f.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <23811.1714.61640.418431@alice.local> (George Hartzell's message of "Thu, 13 Jun 2019 19:30:10 -0700")
George Hartzell <hartzell@alerce.com> writes:
> Eric Abrahamsen writes:
> > George Hartzell <hartzell@alerce.com> writes:
> >
> > > I've been trying to use sieve-manage in GNU Emacs 26.1 on a Mac with
> > > dovecot-pigeonhole-0.5.6 on a FreeBSD 12 system.
> > >
> > > I've run into a few problems:
> >
> > I would use report-emacs-bugs to report these properly. It's possible
> > that I'll have time to look at this in the next week or so, but I don't
> > have time right now, and having a bug report makes it more likely people
> > will notice. I can't test at the moment since sieve-manage won't even
> > log in to the two mail servers that I use :(
> >
> > As to your last point, you might find it simpler to create a ~/.authinfo
> > file containing a line like:
> >
> > machine <server> login <user> port sieve password <password>
> >
> > You can also pgp-encrypt that file and it will work transparently.
>
> Thanks. I will do so.
>
> I'm not entirely sure that I'm using it properly though, so I thought
> I'd ask for "help" before I cried wol^H^H^Hbug!.
>
> Looking at the code, I can't see why it would ever (have ever) do
> anything differently, but....
I don't think anyone's given any love to the sieve functions for quite a
while, so it's safe to assume bugs. I do hope to have some time for this
in the next few weeks...
next prev parent reply other threads:[~2019-06-14 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 15:11 Two problems with sieve-manage George Hartzell
2019-06-13 22:35 ` Eric Abrahamsen
2019-06-14 2:30 ` George Hartzell
2019-06-14 2:40 ` Eric Abrahamsen [this message]
2019-06-17 17:08 ` George Hartzell
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=87o930ga8f.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=hartzell@alerce.com \
--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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.