Displaying 20 results from an estimated 2000 matches similar to: "Managesieve Build failure"
2009 Jul 15
2
sieve / managesieve: unknown Sieve capability 'imapflags'
$HOME/.dovecot.sieve.log reports:
main_script: line 8: error: require command: unknown Sieve capability 'imapflags'.
main_script: line 8: error: require command: unknown Sieve capability 'notify'.
main_script: error: validation failed.
I'm using sieve (not cmusieve) and managesieve with dovecot-1.2.
SquirrelMail 1.4 is using the avelsieve plugin to created/edit the
sieve
2007 Jul 13
2
Today's hg pull doesn't compile
I get:
Making all in auth
make[3]: Entering directory /usr/src/dovecot/src/auth'
rm -f libpassword.a
ar cru libpassword.a mycrypt.o password-scheme.o
password-scheme-md5crypt.o password-scheme-otp.o password-scheme-rpa.o
ranlib libpassword.a
gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-sql
-I../../src/lib-settings -I../../src/lib-ntlm -I../../src/lib-otp
2014 Sep 27
0
ALT storage question
I want to migrate from a non-hashed storage to a hashed storage.
So I set this up:
mail_location = mdbox:/srv/vmail/%2.256Hu/%Lu/mdbox:ALT=/srv/vmail/%Ld/%Ln/mdbox
I rsynced the "old" mdbox-style mailbox from another machine to to /srv/vmail/%Ld/%Ln/mdbox
(/srv/vmail/charite.de/ralf.hildebrandt/mdbox in my case)
The mail_location /srv/vmail/c5/ralf.hildebrandt at charite.de was
2009 Jul 25
0
dovecot-1.2 with managesieve patch: imap crash with backtrace
Log:
Jul 25 10:18:18 postamt dovecot: IMAP(virus-al):
/home/v/i/virus-al/Maildir/dovecot-uidlist: next_uid was lowered (216
-> 2)
Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Panic: file
index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion
failed: (seq_range_exists(&ibox->recent_flags, uid))
Jul 25 10:18:18 postamt dovecot: IMAP(virus-al): Raw backtrace: imap
[0x80efdb1]
2014 Feb 12
1
Crash in recent dovecot, different line (with Backtrace:dovecot/pop3)
Reading symbols from /usr/local/dovecot-2.2/libexec/dovecot/pop3...done.
[New LWP 17294]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
Core was generated by `dovecot/pop3'.
Program terminated with signal 11, Segmentation fault.
#0 0x0804eb6a in client_update_mails (client=client at entry=0x82017a0)
2014 Jun 16
1
SIGSEGV in 2.2.13 with IMAP Proxying to an Exchange Server
100% reproducible. User is using alpine to write an email.
Continue postponed composition (answering "No" won't erase it)?
y -> [>Empty folder! No messages really postponed!<]
Can't delete {mproxy.charite.de/ssl/novalidate-cert/user=theusername}postponed-msgs
Setup:
======
http://wiki2.dovecot.org/HowTo/ImapcProxy
coredump available for further inspection
Full
2014 Sep 24
2
LMTP proxying
How exactly is LMTP proxying supposed to work?
According to the example on
http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy
I'm only seeing "proxy" in the password_query statements.
But LMTP never sends a password.
IMAP Proxying is working OK:
Sep 24 12:51:09 imap-login: Info: proxy(ralf.hildebrandt at charite.de): started proxying to dovecot.charite.de:993:
2017 May 31
2
Bug with 2.2.29-1~auto+25 back to haunt me
> On May 31, 2017 at 6:10 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote:
>
>
> * Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:
>
> > So I added
> > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt
> >
> > But alas:
> > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in
2007 May 16
2
Login with firstname.lastname instead of loginname
Some of our users use to login as
firstname.lastname
or
firstname.lastname at charite.de
instead of using the "correct"
"flastname" login name.
In order to get this behaviour a long-gone co-worker wrote an
authdaemon.pl, which speaks the courier-authdaemon protocol.
How can I emulate this behaviour with dovecot?
Basically, all I need is a usernamen mapping ala:
2016 Oct 17
2
Massive LMTP Problems with dovecot
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:
> I attached gdb top a long running LMTP process:
>
> #0 sha1_loop (ctxt=0x7f3b1a4d7fa0, input=0x7f3b1a524860, len=0) at sha1.c:216
> input_c = 0x7f3b1a524860 "\211PNG\r\n\032\n"
> gaplen = <optimized out>
> gapstart = <optimized out>
> off = 0
> copysiz =
2016 Oct 17
2
Massive LMTP Problems with dovecot
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:
> > It seems to loop in sha1_loop & hash_format_loop
>
> The problem occurs in both 2.3 and 2.2 (I just updated to 2.3 to check).
I'm seeing the first occurence of that problem on the 10th of october!
I was using (prior to the 10th) : 2.3.0~alpha0-1~auto+371
On the 10th I upgraded (16:04) to:
2016 Apr 29
4
Recent update causes segfault in proxy mode
I'm using the auto builds (2:2.2.24-1~auto+3) for Ubuntu/Debian.
The recent upgrade to 2.2.24 cause the follwoing error to appear:
I can log in to a mailbox via dovecot
I can delete emails
Upon expunge, dovecot crashes:
Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX, uid=142514, msgid=, size=10086
Apr 29 11:05:30 mproxy dovecot: imap(hildeb): expunge: box=INBOX,
2016 Apr 29
2
Backtrace:dovecot/imap
Config:
# 2.2.devel (2dc8e2d): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.devel (850d80b)
# OS: Linux 3.13.0-77-generic x86_64 Ubuntu 16.04 LTS
auth_mechanisms = plain login
default_vsz_limit = 1 G
imapc_host = email.charite.de
imapc_port = 993
imapc_ssl = imaps
imapc_ssl_verify = no
listen = *,::
mail_gid = imapproxy
mail_home = /home/imapproxy/%u
mail_location = imapc:~/imapc
2017 Jun 02
2
Bug with 2.2.29-1~auto+25 back to haunt me
> On June 1, 2017 at 1:42 PM Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote:
>
>
> * Aki Tuomi <aki.tuomi at dovecot.fi>:
>
> > > > So I added
> > > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt
> > > >
> > > > But alas:
> > > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting
2018 Mar 05
1
[ext] Re: Panic: file smtp-address.c: line 530 (smtp_address_write): assertion failed: (smtp_char_is_qpair(*p))
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:
> > From the code in lib-smtp/smtp-address.c function smtp_address_write, it
> > looks as though the assertion will happen whenever there is a non ascii
> > char that is also non qpair in the local part, ie
> > !smtp_char_is_atext(*p) and !smtp_char_is_qpair(*p).
>
> Could somebody please point me in the
2014 Feb 12
0
Crash in pop3 with recent dovecot, backtrace
Core was generated by `dovecot/pop3'.
Program terminated with signal 11, Segmentation fault.
#0 0x0804eb6a in client_update_mails (client=client at entry=0x8afd7a8)
at pop3-commands.c:256
256 seq_range_array_add(&deleted_msgs, client->msgnum_to_seq_map[msgnum]);
#0 0x0804eb6a in client_update_mails (client=client at entry=0x8afd7a8)
at pop3-commands.c:256
2017 Jun 01
0
Bug with 2.2.29-1~auto+25 back to haunt me
* Aki Tuomi <aki.tuomi at dovecot.fi>:
> > > So I added
> > > ssl_ca_file = /etc/ssl/certs/ca-certificates.crt
> > >
> > > But alas:
> > > May 31 16:50:24 mproxy dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/10-ssl.conf:36: ssl_ca_file has been replaced by ssl_ca = <file
> > >
> > > Gnarf! As you can
2017 Mar 23
2
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt <r at sys4.de>:
> Mar 20 16:10:17 mproxy dovecot: master: Dovecot v2.2.devel (a39b5b2) starting up for imap
> Mar 20 16:10:26 mproxy dovecot: auth: Error: imapc(exchange-imap.charite.de:993): Couldn't initialize SSL context: Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
> Mar 20 16:10:26 mproxy dovecot: auth: Error:
2007 Dec 18
1
sieve & vacation question
We have a setup where a Postfix gateway does virtual_alias rewriting
of the envelope sender:
ralf.hildebrandt at charite.de get rewritten to hildeb at postamt.charite.de
The mail is then sent on to postamt.charite.de, the Mailbox server.
There we use deliver & doecot. The sieve vacation recipient says it won't answer if:
"The envelope recipient is not found in the message To:, Cc:
2017 Mar 20
0
Can't verify remote server certs without trusted CAs (ssl_client_ca_* settings)
* Ralf Hildebrandt <Ralf.Hildebrandt at charite.de>:
> Hi!
>
> I upgraded the 2.2 packages today (from 2:2.2.28-1~auto+5 to 2:2.2.28-1~auto+8) I now I'm getting an error:
I was able to determine the last working version: 2:2.2.28-1~auto+6
and the first "broken" version: 2:2.2.28-1~auto+7
--
Ralf Hildebrandt
Gesch?ftsbereich IT | Abteilung