Two problems with sieve-manage

Two problems with sieve-manage

[George Hartzell]

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:

1. I can start sieve-manage, use the `f` key with the `<new script>`
   line highlighted, edit a script, and use `C-c C-l` to upload it to
   the server.

   The problem is that the script, on the server, is named `<new
   script>.sieve`, which is awkward.

   But worse, if/when I restart sieve-manage it offers me two choices,
   one labeled `<new script>` (which is the button to create a new
   script) and one which is the existing script which was saved under
   that same name.

   I've tried renaming the buffer, but the code has a preference for
   `sieve-buffer-script-name`.

   Is there some way to rename the buffer?

2. If I create a script directly on the server (e.g. `ape.sieve`) then
   start sieve-manage, I'm offered the chance to edit it.  If I move
   the highlighting to `ape.sieve` then use `f` to edit it, emacs
   becomes unresponsive.  I can break out of it with C-g.

   But, I've had it work once or twice.  I haven't figure out how to
   repeat it.

   If I look in `*sieve-manage-log*`, I can see that emacs has sent
   `GETSCRIPT "ape"` and I can see the text of the script in the
   response.

   I'm not sure what it's waiting for.

3. If I mess up my authentication info, I'm never given a chance to
   re-enter it.  When I enter the server name, it goes ahead and
   re-uses the bad info and fails.  The only way I've been able to
   figure out to be reprompted is to restart emacs.

I'd appreciate any feedback from folks who are using sieve-mode and
sieve-manage.

Thanks,

g.

Re: Two problems with sieve-manage

[Eric Abrahamsen]

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.

Eric

Re: Two problems with sieve-manage

[George Hartzell]

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....

Thanks (again)!

g.

Re: Two problems with sieve-manage

[Eric Abrahamsen]

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...

Re: Two problems with sieve-manage

[George Hartzell]

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. [...]

Done.

g.