similar to: director service and managesieve

Hi, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] ->

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically

Hi, We get intermitend deliver-errors when we have activated the mail_log plugin. The installed version is dovecot-2.0-beta5. Below, the error we get: Jun 02 21:58:11 lda(xxx at uib.es): Panic: file mail-log-plugin.c: line 364 (mail_log_mail_transaction_commit): assertion failed: (ret) Jun 02 21:58:11 lda(xxx at uib.es): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x31c4a35dd0]

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

Hi, with the version 2.0.rc3, when I try to remove a mail server from director list, get this error: doveadm director remove 10.180.188.21 (null): doesn't exist but the other commands are working without problem ... doveadm director status mail server ip vhosts users 10.180.188.21 100 2 10.180.188.22

Hello, i have a problem with the managesieve plugin and a virtual namespace in v2.0. The managesieve plugin complains about an unknown storage driver virtual when i try to log intot the managesieve. I don't know if this is quite a recent problem or if it exists for a while, as i configured the virtual namspace from scratch. (The virtual namespace itself is working.) Jun 28 13:55:54

Hi, now, I'm working with the last version of dovecot and pigeonhole sieve, and when apply a sieve filter on a new message, and it try to move this mail to a folder with special character like accent give me the error 'mailbox name not utf-8: ...' >Aug 17 09:22:40 imap1 dovecot: lmtp(19629,miel): Error: kea6K484akytTAAAJBW4rA: sieve: msgid=

Hi, I've just tried to add managesieve to our director server, and when I try to connect they fail with Jun 26 12:28:13 director2 dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=sieve#011secured#011session=5LNQjl3DjQAKAAsR#011lip=10.0.100.75#011rip=10.0.11.17#011lport=4190#011rport=39309#011resp=<hidden> Jun 26 12:28:13 director2 dovecot: managesieve-login: Error:

I do have two questions related to the managesieve setup in dovecot 1) I did setup a global sieve filter, that is invoked if a user has no other sieve filter. If a user installs a sieve filter and activates it (PUTSCRIPT, SETACTIVE) then the sieve filter gets compiled (.sievec) and deliver does use it. If I want to deactivate the filter (SETACTIVE "") only the symlink (to the .sieve

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

Hi, the 'example-config' holds an incorrect value for the listener socket: $ head -10 20-managesieve.conf ## ## ManageSieve specific settings ## # Service definitions service managesieve-login { #inet_listener sieve { # port = 4190 #} inet_listener sieve <> inet_listener managesieve Regards Thomas

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

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

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

Hi, list. In dovecot-1.2, managesieve is identified as 'sieve' service while use '%s'[1] in dovecot. Is it possible to change it? Because we store it in SQL/LDAP as 'managesieve' service name, we don't want to change this. Thanks [1] http://wiki.dovecot.org/Variables -- Best Regards. Zhang Huangbin - Open Source Mail Server Solution for Red Hat(R) Enterprise

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

Hello, I'm using dovecot 1.2.11 with virtual folders. I'd like to replace my real INBOX by a virtual one but I have several questions : * will my mail still be delivered to my real INBOX? * will I be able to access my real INBOX, for example using a virtual folder reliyng on INBOX * and, how to do it. Here's my problem, if I look to the wiki page [1], I don't really

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

Hello, has anyone a running setup for LMTP proxy and the director service ? pop3/imap/managesieve is properly working, but i have problems with LMTP. I set it up as described in the conf.d/10-director.conf From the user_db i get proxy=y and no proxyhost as described for imap/pop3 But lmtp is complaining about the missing host: Jul 07 15:00:48 auth: Debug: master in: PASS 1 user56

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