Displaying 20 results from an estimated 5000 matches similar to: "Plugin architecture"
2014 Feb 11
1
Order of istream and ostream chains
Hi,
I'm creating a scrambler plugin, that adds an istream and an ostream to
the stream-chain for the mail input/output. It works well until the zlib
plugin is added to the configuration. The scrambler should run before
the zlib and encrypt the mail before it's compressed. Since, the plugin
is named lib18_scrambler_... (and the other lib20_zlib....), that works
well when a mail is
2013 Dec 11
1
Plugin development - ostream and index cache size
Hi,
I'm new to this list, so first thanks for the dovecot tool! So far, it
has been great to work with.
Currently, I'm developing a scrambler plugin for dovecot, that should
stores the mails encrypted. To do that, I've created the
scrambler_ostream and scrambler_istream that does the encryption and
that I hook in the mail storage process.
The scrambler_ostream is stacked on top
2014 Dec 11
2
stacking istreams and ostreams
Hello,
I'm developing an encryption plugin for dovecot and ran into a problem
with the stacking of i/o-streams.
The encryption i/o-streams are working fine on any kind of mail the test
suite is passing through them. But as soon as the zlib plugin is enabled
the logs show an cache error:
failed: Cached message size larger than expected (214 > 206, box=INBOX,
UID=1)
I've already
2018 Dec 04
0
Compilation error
Did you run ./autogen.sh first?
Aki
> On 04 December 2018 at 17:20 Joan Moreau via dovecot <dovecot at dovecot.org> wrote:
>
>
> Hi
>
> USing git, I reach the following error (below).
>
> Here is my configure parameters :
>
> CPPFLAGS="-I/include -I/usr/include/tirpc/" LDFLAGS="-L/lib -ltirpc"
> ./configure --prefix=/usr
2016 Oct 09
6
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
Hi.
I finally decided it was really time to stop being lazy and really move
away from gmail. After I have a server in my basement using power, etc.
So I turned on the imap provided - and did not quite cry - it will have
to do for now, but imap2 is wanting.
A real server yes, but not Linux. (Using linux would require another
server AND I would feel I am being lazy again).
So, I downloaded
2018 Dec 04
2
Compilation error
Hi
USing git, I reach the following error (below).
Here is my configure parameters :
CPPFLAGS="-I/include -I/usr/include/tirpc/" LDFLAGS="-L/lib -ltirpc"
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--libexec=/usr/libexec --with-sql=yes --without-sqlite --with-mysql
--with-ssl --without-shadow --without-nss --without-pam --without-ldap
--with-zlib
2014 Dec 12
0
stacking istreams and ostreams
Well, I've found the bug. I've got confused with the stream-stacking
function pointers. The encryption istream was stacked on top of the
parent and the ostream below the parent. That caused this very confusing
bug.
Best,
Philipp
Am 11.12.2014 um 12:16 schrieb Philipp Br?ll:
> Hello,
>
> I'm developing an encryption plugin for dovecot and ran into a problem
> with the
2013 Apr 23
1
imap Panic: file istream-seekable.c: line 253 (i_stream_seekable_read): assertion failed: (stream->istream.v_offset + stream->pos <= sstream->write_peak)
Hi Timo,
just another crash - using 2.2.1 (c95cea6e1389).
Regards,
Pascal
-------------- next part --------------
Reading symbols from /usr/local/libexec/dovecot/imap...done.
[New LWP 15198]
warning: Can't read pathname for load map: Input/output error.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core
2006 Dec 07
7
[LLVMdev] #include <iostream>
Hi all,
With the newest patches to LLVM, there should be no reason for having
"#include <iostream>" in any library source code file, except for lib/
Support/Streams.cpp. Please use the following instead:
OLD NEW
--- ---
std::ostream llvm::OStream
std::istream llvm::IStream
std::cerr llvm::cerr
std::cerr llvm::cout
2012 Nov 13
0
older gcc don't know --as-needed
Hi,
I have to build dovecot-2.1.10 for SuSE SLES9.
/bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -no-undefined -Wl,--as-needed -o test-lib test_lib-test-lib.o test_lib-test-array.o test_lib-test-aqueue.o test_lib-test-base64.o
2006 Dec 08
0
[LLVMdev] #include <iostream>
Bill Wendling wrote:
> Hi all,
>
> With the newest patches to LLVM, there should be no reason for having
> "#include <iostream>" in any library source code file, except for lib/
> Support/Streams.cpp. Please use the following instead:
>
> OLD NEW
> --- ---
> std::ostream llvm::OStream
> std::istream
2006 Dec 11
0
[LLVMdev] #include <iostream>
Bill Wendling wrote:
It seems that when compiling Debug versions of LLVM, we use stream
manipulators (like std::hex) on the new LLVM streams, and doing so
causes a compiler error when compiling LLVM with GCC 3.4.0.
I commited a fix to work around the problem, but it seems to me it would
be better if LLVM streams could support common stream manipulators.
First, has anyone else experienced the
2006 Sep 25
2
Errors while doing make on Solaris 9 for dovecot-1.0.rc7
Hi,
I have Solaris 9 and I am getting the following errors for dovecot-1.0.rc7 after running
1.configure - No errors see output as attached
2. /usr/ccs/bin/make -- partial output below, complete attached
Thanks,
Lalit
.....
DEPDIR=.deps depmode=none /bin/bash ../../depcomp \
gcc -DHAVE_CONFIG_H -I. -I. -I../.. -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations
2006 Dec 08
0
[LLVMdev] #include <iostream>
On Thu, 7 Dec 2006, Bill Wendling wrote:
> With the newest patches to LLVM, there should be no reason for having
> "#include <iostream>" in any library source code file, except for lib/
> Support/Streams.cpp. Please use the following instead:
>
> OLD NEW
> --- ---
> std::ostream llvm::OStream
> std::istream
2005 Sep 06
0
Dovecot-LDA & OpenBSD
I?m having a bit of a problem with compiling dovecot-lda on OpenBSD. I
used information from wiki.dovecot.org but this, unfortunately, resulted
in some errors.
Am I missing something?
make all-recursive
Making all in src
Making all in libsieve
if gcc -DHAVE_CONFIG_H -I. -I. -I..
-I/mnt/files/dovecot-1.0-test80/src/lib
-I/mnt/files/dovecot-1.0-test80/src/lib-mail
2011 Oct 31
1
Rewrite the ostream output method, to save messages in another directory.
Hi Timo,
I Trying to integrate my antispam with dovecot, using the imap folder to do
certain actions. I Do almost every thing, but i have some problems saving
the message.
Explaining this function, i try to use a imap folder like a "collector
folder", the user append a message from outside (ie another imap or pop
message) to this folder, and i don't want to copy this message, i
2017 May 02
4
lmtp segfault after upgrade
On 2017-05-02 09:35, Aki Tuomi wrote:
> On 2017-05-02 10:20, Tom Sommer wrote:
>> On 2017-05-01 19:26, Aki Tuomi wrote:
>>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote:
>>>>
>>>>
>>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my
>>>> dmesg
>>>> and /var/log/messages
2010 Apr 20
3
zlib Plugin Dovecot 2.0 - ostream
Hello Everyone...
In zlib save mail have it:
struct ostream *output;
There is a way to get the file descriptor from output used in ostream zlib
plugin ?
to get in istream is i_stream_get_fd, but don't have o_stream_get_fd......
2008 Sep 16
2
assertion failure in current hg, file istream.c: line 303 (i_stream_read_data): assertion failed: (stream->stream_errno != 0) (1.1.3 was working fine)
Today I updated to current dovecot-1.1 hg tree and I got many of these
assertion failures:
file istream.c: line 303 (i_stream_read_data): assertion failed:
(stream->stream_errno != 0)
(gdb) bt full
#0 0x00352402 in __kernel_vsyscall ()
No symbol table info available.
#1 0x0043ed20 in raise () from /lib/libc.so.6
No symbol table info available.
#2 0x00440631 in abort () from /lib/libc.so.6
2008 Oct 16
2
dovecot 1.1.4 maildir imap segfault in message_parse_header_next
I've tried to stress test dovecot 1.1.4 with imaptest for days without
any assertion failure or crash.
Just some "got too little data" messages.
So far it's the most stable 1.1.x version.
Today a user got this imap segfault with vanilla 1.1.4 (I don't know
if it's something you have already fixed in current tree).
The user didn't complain of anything, I've just