Displaying 8 results from an estimated 8 matches for "listscript".
Did you mean:
listscripts
2016 Apr 06
2
[help]enotify "mail to" run fine edit via managesieve 0.4.4 complied failed
...comparator-i;ascii-numeric relational regex imap4flags copy include
variables body enotify environment mailbox date ihave duplicate
vacation-seconds"
"NOTIFY" "mailto"
"SASL" "PLAIN LOGIN"
"VERSION" "1.0"
OK "Dovecot ready."
listscripts
NO "Error in MANAGESIEVE command received by server."
AUTHENTICATE "PLAIN" "AGFuZ196aGFAdG9tLmNvbQAxMTExMTE="
OK "Logged in."
listscripts
"blackwhitelist"
"rulefilter" ACTIVE
OK "Listscripts completed."
getscript "rulefilte...
2008 Apr 07
2
A little assistance with Sieve
...e to try
to make use of Sieve, but I'm having quite the time finding out how to
make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to
be compiled with it. I can access managesieve, and I have set up
dovecot.conf with lda. I do not get a NO response when I PUTSCRIPI, but
LISTSCRIPTS produces no result, so I assume it's not working properly,
though if I try with a non-existent script I get an error message.
Questions:
1. Is anyone else seeing this, or am I doing something wrong?
2. I have seen through Googling some dovecot.conf examples that suggest I
should be using mana...
2012 Jun 01
1
Exposing global (default) sieve script through Managesieve
...nageSieve protocol doesn't seem to support any way to flag
this situation, it would be fooling the clients a bit, but I'm not sure
if that's really a problem.
While the user has not script named "default" in his sieve_dir:
- include a script called "default" in the LISTSCRIPTS output.
- return the contents of the sieve_global_path in the GETSCRIPT
"default" command.
- remove any sieve symlink after a SETACTIVE "default" command (as if
SETACTIVE "" was given). This causes dovecot to fall back to the
sieve_global_path script.
- th...
2017 Feb 10
3
Managesieve cannot access script store
...a bit of a bug:
I'm glad to h've been able to help with this beta-test ;-)
> About the cause of this error: keep in mind that the whole directory
> path needs read/execute permission, not only the leaf directory.
Have checked. They are...
> You could try a command other than LISTSCRIPTS in your manual debugging
> efforts. That should take a different code path that provides a more
> detailed error.
I tried:
PUTSCRIPT "hutsefluts" {6+}
keep;
Gives the same result:
Feb 10 15:43:26 p150 dovecot[2042]: managesieve(rogier): Error: sieve:
file storage: save:
open(...
2008 Nov 28
2
ManageSieve and invalid scriptname
Hello there,
I have been using pysieved and avelsieve and it has been working
great. I decided to do test with the ManageSieve patch and got this
problem:
Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage:
using active sieve script path: ~/.dovecot.sieve
Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage:
using sieve script storage directory: ~/.sieve
Nov 27
2017 Feb 08
0
Managesieve cannot access script store
...rror message in itself is a bit of a bug:
https://github.com/dovecot/pigeonhole/commit/51e4ff296987781e1ce93cb1c0ccc14e863bf8d6
About the cause of this error: keep in mind that the whole directory
path needs read/execute permission, not only the leaf directory.
You could try a command other than LISTSCRIPTS in your manual debugging
efforts. That should take a different code path that provides a more
detailed error.
Regards,
Stephan.
2017 Feb 05
5
Managesieve cannot access script store
Hi,
I am trying to get sieve working on a new OpenSuse leap 42.2 install. On
my 'old' OpenSuse 13.2 machine it worked fine.
The problem is that Managesieve can't access the script store and won't
let me create any script. It says permission denied on ~/sieve
directory. See log below. I 've activated debug logging, but that
doesn't give any clues to me. Also, I've
2009 Jul 30
1
Managesieve configuration problem
Hello!
I'm trying for a lot of time to make managesieve working with dovecot 1.1.17 and virtual users on openSuSE 11.1. I think I'm doing some misconfiguration, but I can't figure it out. Perhaps it's something with the paths to the sieve scripts?
In dovecot.conf I find in the comments:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
protocol