Displaying 20 results from an estimated 20000 matches similar to: "Dovecot 2.0beta4: Managesieve example config"
2019 Jan 11
2
managesieve configuration
Hi Dominik,
I have set ssl = required in 10-ssl.conf globally but no ssl here:
service managesieve-login {
inet_listener sieve {
port = 4190
}
...
}
Nevertheless, STARTTLS is offered
"IMPLEMENTATION" "Dovecot Pigeonhole"
"SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
2015 Apr 17
1
ManageSieve Dovecot v2 listen on localhost only
Thanks. I tried that now and added the "address":
service managesieve-login {
inet_listener sieve {
port = 4190
address = 127.0.0.1
}
I restarted dovecot but:
tcp 0 0 0.0.0.0:4190 0.0.0.0:*
LISTEN 0 522413 22288/dovecot
Why is this not working?
Quoting Gedalya <gedalya at gedalya.net>:
>
2019 Feb 03
2
Managesieve problem
Hi John,
On Sun, Feb 03, 2019 at 09:56:38AM +0100, John Fawcett wrote:
> On 01/02/2019 13:39, Ervin Heged?s wrote:
> > I'ld try to set up the managesieve (for RoundCube) - the sieve is
> > works as well with dovecot (I mean my filters works perfectly).
> >
> > When I would try to connect to managesieve, I got an error, and
> > mail.err contains:
> >
>
2011 Mar 02
3
Segfault in managesieve with "sieve_extensions = -redirect"
Hi!
I've got a segfault in managesieve while using:
sieve_extensions = -vacation -reject -spamtest -virustest -enotify -redirect
The problem seems to lie in "-redirect".
Reason for excluding "redirect" from sieve is my users should not use
sieve to forward or redirect mails but use an external method
(web-script to set LDAP attribute) which checks several things like
2011 Dec 12
1
v2.1.rc1 managesieve TLS
Hi,
TLS on imap port 143 works.
But if I try TLS on managesieve port 4190, I get no connection.
Dec 12 21:16:10 managesieve-login: Info: Disconnected (no auth attempts in 5 secs): rip=192.168.10.117, lip=192.168.10.117, secured
Dec 12 21:16:20 managesieve-login: Info: Disconnected (no auth attempts in 5 secs): rip=192.168.10.117, lip=192.168.10.117, TLS handshaking: Disconnected
# gnutls-cli
2015 Apr 17
4
ManageSieve Dovecot v2 listen on localhost only
Hi,
How can I only listen on localhost for ManageSieve?
I tried:
port = localhost:4190
still listening *:
tcp 0 0 0.0.0.0:4190 0.0.0.0:*
LISTEN 0 515675 20540/dovecot
Would did I not get here?
Thanks,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-keys
Size: 1718
2019 Feb 01
3
Managesieve problem
Hi,
I'ld try to set up the managesieve (for RoundCube) - the sieve is
works as well with dovecot (I mean my filters works perfectly).
When I would try to connect to managesieve, I got an error, and
mail.err contains:
dovecot: managesieve(airween at mydomain.hu): Error: user airween at madomain.hu: Couldn't drop privileges: getgrnam(vmail) failed: Permission denied (in
2016 Oct 27
2
Bugreport: managesieve-login won't start without a ssl-key
Hello,
If you don?t have a ssl_key and ssl_cert configured in your dovecot config managesieve-login will fail to start with the following error message: dovecot: managesieve-login: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY, even if you haven?t enabled ssl for managesieve-login.
Infos according to
2012 Jan 11
3
proxy, managesieve and ssl?
Hello,
On a dovecot 2.0.14 proxy, I found that proxying managesieve works well
when using 'starttls' option in pass_attrs, but does not work when using
'ssl' option. The backend server is also dovecot 2.0.14; when using the
ssl option, it reports "no auth attempts" in the logs about
managesieve-login, and meanwhile the MUA, Thunderbird with sieve plugin,
reports
2015 Feb 12
2
Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive
Hello,
I've ran into problem with Dovecot and dsync replication. Everything
works perfectly, including replication of sieve scripts, except fact
that if user activates the 'managesieve' ruleset (I'm using currently
Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2"
host, by creating symlink ".dovecot.sieve ->
2018 Jun 07
2
dovecot-pigeonhole Missing sieve_imapsieve Plugin?
Hi Folks,
I am having a problem configuring imapsieve via dovecot-pidgeonhole on CentOS7.
After following the docs here:
https://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/IMAPSieve
I get:
dovecot[22026]: managesieve: Fatal: Plugin 'sieve_imapsieve' not found from directory /usr/lib64/dovecot/sieve
dovecot[22026]: doveconf: Error: managesieve-login: dump-capability process returned 89
2017 Jul 21
2
Core dumped when authenticating to managesieve
Hey,
I'm getting "Error in MANAGESIEVE command received by server." and
service(managesieve-login) killed with signal 11 (core dumped) when doing
two line autenticate(sogo) to managesieve().
# telnet localhost 4190
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
"IMPLEMENTATION" "Dovecot Pigeonhole"
"SIEVE"
2011 Dec 07
1
dovecot 2.0 sieve if working, managesieve not.
Hi,
this is my configuration
# OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.1 (Santiago) ext4
auth_debug = yes
auth_master_user_separator = *
auth_username_format = %Lu
auth_verbose = yes
disable_plaintext_auth = no
info_log_path = /var/log/dovecot-info.log
log_path = /var/log/dovecot.log
log_timestamp = "%Y-%m-%d %H:%M:%S "
login_greeting =
2010 Apr 24
1
Dovecot 2.0beta4 HG 11189: dovecot-uidvalidity warning with mdbox mailboxes
Hi,
the latest HG of Dovecot 2.0 throws a warning when creating a new mailbox inside an INBOX with 'mdbox' format. It does however create the mailbox correctly.
==> /var/log/dovecot.log <==
Apr 24 14:35:09 spectre dovecot: imap(tlx at leuxner.net): rename(/var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity, /var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity) failed: No such
2010 May 30
2
dovecot-2.0-pigeonhole/ManageSieve: wrong service name
Hi Stephan,
ManageSieve uses the wrong? service name for the authdb lookup.
With dovecot-1.2-managesieve the service name was changed from
'managesieve' to 'sieve'. So I altered my table layout in order to make
the query "SELECT userid AS "user", password FROM dovecotpassword('%Ln',
'%Ld') WHERE %Ls" work again.
When I try to login on the sieve
2016 Apr 06
2
[help]enotify "mail to" run fine edit via managesieve 0.4.4 complied failed
hi all
edit via vi editor to change dovecot.sieve and enotify works fine.but
when I telnet 4190 port via managesieve to edit it with the same code,the
managesieve said "NO "Error in MANAGESIEVE command CHECKSCRIPT: "", find
many topic in wiki and maillist but not solved.
need you help!thanks!!dovecot version 2.2.15,pigonhole version 0.4.4
here are more infos
2013 Sep 09
1
Ring SYNC appears to have got lost, resending after upgrade
Hi @all,
on Saturday I upgraded two dovecot servers from squeeze to wheezy and
dovecot from 2.1.x to 2.2.5 (compiled from sources). After the upgrade
everything worked fine at first.
On Sunday Morning I recognized these errors (they occured after a reload
for logging purpose on midnight) on one server:
director: Error: Ring SYNC appears to have got lost, resending
After reloading/restarting
2012 Feb 21
1
dovecot 2 doesn't start with managesieve
Hi
I build dovecot 2.0.16 and and dovecot-pigeonhole-0.2.5 on two machines with the same options. The config files are equivalent. On the first machine everything works fine - on the second dovecot with managesive won't start (without sieve protocol it does).
Error: socket() failed: Protocol not supported
Error: service(managesieve-login): listen(::, 4190) failed: Protocol not supported
2020 Mar 28
2
managesieve user
Hello,
I am updating dovecot, from Debian Stretch to Buster, and I have an
issue with the managesieve service:
> Mar 28 15:05:06 mail dovecot[2637]: managesieve-login: Error: auth:
> connect(login) in directory / failed: Permission denied
> (euid=120(<getpwuid() error>) egid=128(<getgrgid() error>) missing +x
> perm: /, we're not in group 127, dir owned by 0:127
2013 Oct 06
2
smartsieve managesieve-login failure with dovecot 2.1.7
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello,
I just subscribed to the mailing list because I am stuck trying to solve
a problem getting smartsieve to work with a new version of dovecot.
But let me first explain the situation shortly. I am running a mail
server at home for personal use, and for fun. At this moment this is an
old, slow machine running Debian Squeeze, Dovecot 1.2.15 and