search for: stephanbosch

...o end in '0'). > > > > Tracking internally as DOP-1470. > > > > I think this may also explain some of the weird reports about invalid > > UIDs that we've seen in recent history on this mailing list. > > Preliminary fix is here: > https://github.com/stephanbosch/dovecot-core/commits/fix-solr-xml-parser > > It's big due to some code restructuring for making a proper unit test. I > am not sure when this will be in a release. > > Regards, > > Stephan. > > -- Larry Rosenman http://www.lerctr.org/~ler Phone:...

...news on this getting into a release? On Sun, Oct 13, 2019 at 2:24 AM Stephan Bosch <stephan at rename-it.nl> wrote: > > > On 10/10/2019 04:05, Larry Rosenman via dovecot wrote: > > Is there a way to get this as a patchset against 2.3.8? > > > > https://github.com/stephanbosch/dovecot-core/tree/fix-solr-xml-parser-2.3.8 > > This hasn't seen any QA yet, so handle with care. > > Regards, > > Stephan. > > > > > On Tue, Oct 8, 2019 at 12:03 PM Stephan Bosch via dovecot > > <dovecot at dovecot.org <mailto:dovecot at dovecot.org...

...logs/ >> sieve_trace_dir = ~/mails/sieve/logs/ >> sieve_trace_level = commands >> sieve_trace_debug = yes >> sieve_trace_addresses = yes >> >> Did I a misconfigured something? > > This should fix the trace directory problem: > https://github.com/stephanbosch/pigeonhole-core/commit/ee0d15407d231198519b4f87a0fc533b941765a2 > I still need to create some CI tests for this and it needs some internal > review before it will be merged in Pigeonhole core. > > Also, I notice that your sieve_user_log setting points to a directory. > That needs to...

...? I looked >> through the GitHub commits, but it?s not clear to me which commit >> fixes this issue. I?d like to apply the patch and re-compile dovecot >> for my machines instead of having to downgrade to 2.2.35. > > This fix is currently pending: > https://github.com/stephanbosch/dovecot-core/commits/lmtp-fix-msg-size-limit > > I'm seeing some CI issues still and I am waiting on some input from > someone else. > > Regards, > > Stephan. Any news on when this fix might turn up in a release? Thanks, Reio

Hi, I wonder if someone could give me a little help bringing the sieve-extdata plugin up to date to be usable with latest Dovecot/pigeonhole Trying to use both together at present I get an error: ? managesieve: Fatal: Couldn't load required plugin /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: dlopen() failed: /usr/lib/dovecot/sieve/lib90_sieve_extdata_plugin.so: undefined symbol:

On 10/10/2019 04:05, Larry Rosenman via dovecot wrote: > Is there a way to get this as a patchset against 2.3.8? > https://github.com/stephanbosch/dovecot-core/tree/fix-solr-xml-parser-2.3.8 This hasn't seen any QA yet, so handle with care. Regards, Stephan. > > On Tue, Oct 8, 2019 at 12:03 PM Stephan Bosch via dovecot > <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: > > > > On 08...

> >> Messages are being sent to dovecot LMTP by postfix. If I change this email > >> to another server with dovecot 2.2.x the same message are delivered > >> immediately. > > Confirmed. Starts to fail here around 30Mb. Tested with Swaks. > > > > Working on a fix... > > Problem found. It is an explicit limit of 40Mb (for the 30Mb I saw in my >

...ure of a plain password, which could than easily used abusively. > > I just hope for better security in the future. I looked a this a bit and since it is basically only a matter of replacing the hash algorithm, I created a quick implementation (after some refactoring): https://github.com/stephanbosch/dovecot-core/commits/auth-scram-sha-256 However, since there is no client that actually supports this, I cannot test this myself. I've briefly tested that the old SHA-1 still works (using mpop) and that the server properly announces the new mechanism when enabled, but that is it. It is base...

Hello, I am using a custom directory for sieve logs and trace and it apparently generate an error, in some corner case. - I have an IMAP global sieve script, that is run when appending emails into the "Archives" folder. - I have Thunderbird configured to archive emails by year When archiving an email, for instance in "Archives/2018", I often have an error message like this:

On 07/10/2019 15:13, Fabian Kuran via dovecot wrote: > Hi, > >> Am 23.09.2019 um 09:36 schrieb Filip Hanes <filip.hanes at ringier.sk >> <mailto:filip.hanes at ringier.sk>>: >> >> >> ?t 19. 9. 2019 o?15:30 Fabian via dovecot <dovecot at dovecot.org >> <mailto:dovecot at dovecot.org>> nap?sal(a): >> >> Are there any

Hi, Since updating to 2.3.1 on my FreeBSD mailserver mail delivery using lda is broken if I have sieve enabled. (Before updating this was 2.2 and pigeonhole 0.4) FreeBSD 11.1-p8 amd64 Dovecot 2.3.1 Pigeonhole 0.5.1 Mailflow is OpenSMTPd as MTA, using mda delivery to rspamc which utlimately delivers using dovecot-lda. smtpd.conf deliver to mda "rspamc -h scan --mime -e

Hi again, On 24/12/2017 7:11 am, Stephan Bosch wrote: > Op 12/23/2017 om 7:18 AM schreef Reuben Farrelly: >> Hi, >> >> With latest 2.3 -git (and 2.3.0 release), I'm running into this error >> with Thunderbird: >> >> "An error occurred while sending mail. The mail server responded: >> 5.5.4 Unsupported mail BODY type. Please verify that your

...262144 >>> bytes >> >> I cannot reproduce this behavior so far. > >> I will continue experimenting a bit. I still have to actually try this >> with Thunderbird. Any other configuration I should know about (`dovecot >> -n`)? Fix pending: https://github.com/stephanbosch/dovecot-core/commits/fix-submission-thunderbird Regards, Stephan.

...> sieve_user_log = ~/mails/sieve/logs/ > sieve_trace_dir = ~/mails/sieve/logs/ > sieve_trace_level = commands > sieve_trace_debug = yes > sieve_trace_addresses = yes > > Did I a misconfigured something? This should fix the trace directory problem: https://github.com/stephanbosch/pigeonhole-core/commit/ee0d15407d231198519b4f87a0fc533b941765a2 I still need to create some CI tests for this and it needs some internal review before it will be merged in Pigeonhole core. Also, I notice that your sieve_user_log setting points to a directory. That needs to be a file, otherwise it...

...ace_dir = ~/mails/sieve/logs/ >>> sieve_trace_level = commands >>> sieve_trace_debug = yes >>> sieve_trace_addresses = yes >>> >>> Did I a misconfigured something? >> This should fix the trace directory problem: >> https://github.com/stephanbosch/pigeonhole-core/commit/ee0d15407d231198519b4f87a0fc533b941765a2 >> I still need to create some CI tests for this and it needs some internal >> review before it will be merged in Pigeonhole core. >> >> Also, I notice that your sieve_user_log setting points to a directory. &gt...

...an you tell me which commit fixes this issue? I looked through the GitHub commits, but it?s not clear to me which commit fixes this issue. I?d like to apply the patch and re-compile dovecot for my machines instead of having to downgrade to 2.2.35. This fix is currently pending: https://github.com/stephanbosch/dovecot-core/commits/lmtp-fix-msg-size-limit I'm seeing some CI issues still and I am waiting on some input from someone else. Regards, Stephan.

...le of a numeric value (that happens to end in '0'). > > Tracking internally as DOP-1470. > > I think this may also explain some of the weird reports about invalid > UIDs that we've seen in recent history on this mailing list. Preliminary fix is here: https://github.com/stephanbosch/dovecot-core/commits/fix-solr-xml-parser It's big due to some code restructuring for making a proper unit test. I am not sure when this will be in a release. Regards, Stephan.

...quot; and > "sieve_sys_warning()" functions > > I'm unclear how this code should be change (I've commented it out for > now - eek). You're not alone, I ran into the same problem a couple of days ago. Applying the patch from my pull request at https://github.com/stephanbosch/sieve-extdata-plugin/pull/1 will probably fix this problem. Kind regards, -- Sebastiaan Hoogeveen NederHost https://www.nederhost.nl KvK: 34099781

Hi all. My dovecot setup: pf at vulcan:~ ? dovecot --version 2.3.0 (c8b89eb) on Arch Linux, x86_64 (full config here: [0]) uses sieve plugin to train rspamd system as described in the wiki [1]. It used to work fine prior to 2.3.0/0.5.0 update, but now "imap" process crashes when I move spam letters from the inbox to the junk folder. I've recompiled both dovecot and pigeonhole

Hi all, Hey all, I upgraded to dovecot 2.3.1 (from 2.2.34) and noticed that the behavior for dovecot-lda changed. Apparently it no longer accepts -f "" or -f "<>? With 2.2.34, both were accepted now I get: root at mail:~# /usr/local/libexec/dovecot/dovecot-lda -f "<>" lda(root): Fatal: Invalid -f parameter: Null path not allowed or root at mail:~#