similar to: Dovecot antispam plugin for 2.2

hello all, y a use dovecot 1.2.5, compiled with : ./configure --prefix=/opt/dovecot125 --enable-header-install --with-mysql --with-ssl=openssl my error is : make install : cc -DHAVE_CONFIG_H -I/opt/dovecot125/include/dovecot/ -I/opt/dovecot125/include/dovecot/src/ -I/opt/dovecot125/include/dovecot/src/lib/ -I/opt/dovecot125/include/dovecot/src/lib-storage/

Hi Timo, Hi list, I finally got along to test the current dovecot 1.2 with our Kolab Server. And I'm very excited to see all the cool ACL and shared name spaces stuff upstream, thanks a lot Timo! Anyway I just stumbled across a new bug using our metadata-plugin (which in turn uses the dict back end): Making a few annotations requests after another it stops working. dovecot.log sais

$ hg --cwd ./work/dovecot-antispam-plugin-50 glog -l3 --style compact @ 50[tip] 0319240072d8 2012-12-20 03:56 +0200 Eugene Paskevich <eugene at raptor.kiev.ua> | Made use of new DOVECOT_ABI_VERSION macro. ... $ configure; make Compiling signature-log.c (plugin)... signature-log.c:122: error: too many arguments to function ?dict_init? ... Reverting src/signature-log.c from r49 to

I try to create a patch to allow (proxy-)dict to use tcp connections instead of a unix domain socket. I'm replacing connection_init_client_unix with connection_init_client_ip: --- ./src/lib-dict/dict-client.c.orig +++ ./src/lib-dict/dict-client.c @@ -721,6 +721,10 @@ client_dict_init(struct dict *driver, const char *uri, struct ioloop *old_ioloop = current_ioloop; struct

> On August 3, 2017 at 2:10 PM Ralf Becker <rb at egroupware.org> wrote: > > > I try to create a patch to allow (proxy-)dict to use tcp connections > instead of a unix domain socket. > > I'm replacing connection_init_client_unix with connection_init_client_ip: > > --- ./src/lib-dict/dict-client.c.orig > +++ ./src/lib-dict/dict-client.c > @@ -721,6

Hello, Is the signature-log backend of the antispam plugin broken when compiling with dovecot version 1.1.2? I'm using version 1.0 of the antispam plugin. It looks like there isn't anything more recent. cc -c -DCONFIG_DEBUG -DDEBUG_SYSLOG -fPIC -shared -Wall -Wextra -DPLUGINNAME=antispam -DHAVE_CONFIG_H -I../dovecot-1.1.2/ -I../dovecot-1.1.2/src/ -I../dovecot-1.1.2/src/lib/

Dovecot 2.1.12 and antispam-plugin 0319240072d8 bash-# make Entering directory src. signature-log.c: In function 'signature_log_transaction_begin': signature-log.c:122: error: too many arguments to function 'dict_init' Failed to compile signature-log.c (plugin)! make[3]: *** [signature-log.plugin.o] Error 1 make[2]: *** [all] Error 2 make[1]: *** [src] Error 2 make: *** [all]

While trying to isolate properly and reproduce, I was able to trigger the same bug with the following code: struct dict *dict; char* dict_uri = "proxy::sieve"; char* key = "priv/key"; char* username = "admin at domain.tld"; char* value, error; dict_drivers_register_builtin(); dict_init(dict_uri, DICT_DATA_TYPE_STRING, username,

Hello (Stephan?), is this planned? Have to abandon dovecot 2.3.2 if extdata not available. > thanks you AKi for alway responding! > >>> Pigeonhole download page has links for extdata plugin up to v0.4 but >>> nothing more and no link to the master repository >>> >>> https://pigeonhole.dovecot.org/download.html >>> >>> I want to use

thanks you AKi for alway responding! >> Pigeonhole download page has links for extdata plugin up to v0.4 but >> nothing more and no link to the master repository >> >> https://pigeonhole.dovecot.org/download.html >> >> I want to use with dovecot 2.3.2rc1 but v0.4 won't compile with it. > > Seems to need v0.5 for it. What are you using it for? For a

Hi! Looking at the code, I think the bug is that it just copies pointer to the value, it should, instead, duplicate the value to some memory region. Can you see if this following patch fixes it? Aki > On October 17, 2016 at 4:14 PM Pierre Jaury <pierre at jaury.eu> wrote: > > > Okay, it seems to me that the bug is due to "t_str_tabunescape" using > the unsafe

The problem we are facing is incorrect authentications being caught by firewall rules and IP?s getting blocked. We would like to be able to identify the problem account to help the domain admin track down the issue. Does anyone have another idea? We use sql user db so I thought of logging all login attempts to a table with timestamps and lookup the failed logins by timestamp. Regards, Bradley

Oh duh, it used datastack pool. Try again with the attached patch? Please remember to clear the previous one out before trying. Aki > > The trace is missing some symbols, I will debug tomorrow and see where > the call comes from exactly. > > Regards, > > > On 10/17/2016 06:23 PM, Aki Tuomi wrote: > > Hi! > > > > Looking at the code, I think the bug

dovecot 2.2.22 postfix 3.1.1 I?m seeing "SASL NTLM authentication failed: {long_hash}? in mail.log. Is there a way to log the SASL username? I think postfix is logging what Dovecot SASL is returning so I hope I am asking on the right list. Regards, Bradley Giesbrecht (pixilla)

On 19/05/2019 22:45, John Fawcett via dovecot wrote: > On 19/05/2019 22:37, John Fawcett via dovecot wrote: >> On 19/05/2019 20:31, mabi via dovecot wrote: >>> >>> ??????? Original Message ??????? >>> On Sunday, May 19, 2019 7:36 PM, John Fawcett via dovecot >>> <dovecot at dovecot.org> wrote: >>>> >>>> Attached is a

The code that I have written to get the function type is: const std::vector<Type *> ParamTys; ParamTys.push_back(IntegerType::getInt32Ty(Context)); ParamTys.push_back(IntegerType::getInt32Ty(Context)); ParamTys.push_back(IntegerType::getInt32Ty(Context)); ParamTys.push_back(PointerType::get(Type::getVoidTy(Context), 0)); ParamTys.push_back(PointerType::get(Type::getVoidTy(Context), 0));

In fact, looking again, dovecot should log the failure with username, if available. Aki On 24.05.2017 09:22, Aki Tuomi wrote: > As band-aid you could try looking at the SASL message, if you decode64 > it might contain the username in plain text. > > Aki > > > On 23.05.2017 17:44, Bradley Giesbrecht wrote: >> The problem we are facing is incorrect authentications being

After a recent upgrade to dovecot 2.2.9 (caused by an ubuntu upgrade to 14.04), the antispam plugin has stopped recognizing my spam folders as spam. I see the plugin initializes properly, but when moving a message, the mailbox_is_spam() function always returns 0. The version of dovecot-antispam that ships with ubuntu is 2.0+20130822-2build1. I also compiled the latest version in the git

On 2009-05-15, at 07:26, David Greene wrote: > On Friday 15 May 2009 05:50, Jay Foad wrote: >> > >>> The one major thing to be aware of is that it isn't safe to use >>> &V[0] when V is an empty std::vector >> >> Oh dear. That's a bit of a flaw in the plan. I suppose the solution >> is to switch to SmallVector whenever this might be a

Hi list! Recently I noticed that dovecot-lda throws segfault when resolver is unavailable and with imapc configured. $ cat /etc/resolv.conf search . nameserver 127.0.0.1 backtrace: # gdb -q /usr/libexec/dovecot/dovecot-lda 'core-1398282784-8-11-!usr!libexec!dovecot!dovecot-lda-8805' [...] Core was generated by `/usr/libexec/dovecot/deliver -d marcin at mejor.pl'. Program terminated