similar to: Doveadm error since 2.3.11.3 when run as unprivileged user

On 13. Aug 2020, at 11.29, Timo Sirainen <timo at sirainen.com> wrote: > > On 13. Aug 2020, at 11.00, Arjen de Korte <build+dovecot at de-korte.org> wrote: >> >> I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: >>

On Thu, Aug 13, 2020 at 21:16:42 +0200, Arjen de Korte wrote: > Citeren Timo Sirainen <timo at sirainen.com>: > > !include_try ssl-keys.conf > > That will only work to include an optional configuration file and > suppress errors if it doesn't exist. I put > > ssl_key = </etc/ssl/private/de-korte.org.key > > in a separate configuration file and it

Citeren Timo Sirainen <timo at sirainen.com>: > On 13. Aug 2020, at 11.29, Timo Sirainen <timo at sirainen.com> wrote: >> >> On 13. Aug 2020, at 11.00, Arjen de Korte >> <build+dovecot at de-korte.org> wrote: >>> >>> I allow users to run 'doveadm' for mailbox maintenance (to expunge >>> mail for instance). Since the

On Thu, Aug 13, 2020, Arjen de Korte wrote: > include optional config file and suppress errors if it doesn't exist I followed this workaround, which is nicely summarized at https://github.com/postfixadmin/postfixadmin/issues/381#issuecomment-678269198 Yet, not all errors are suppressed this way: $ doveadm pw doveadm(olav): Error: net_connect_unix(/run/dovecot/stats-writer) failed:

On 13. Aug 2020, at 11.00, Arjen de Korte <build+dovecot at de-korte.org> wrote: > > I allow users to run 'doveadm' for mailbox maintenance (to expunge mail for instance). Since the upgrade to 2.3.11.3, this no longer works and results in the following error message: > > doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 13: ssl_key:

> On 11/09/2020 01:40 Olav Seyfarth <olav at seyfarth.de> wrote: > > > On Thu, Aug 13, 2020, Arjen de Korte wrote: > > include optional config file and suppress errors if it doesn't exist > > I followed this workaround, which is nicely summarized at > https://github.com/postfixadmin/postfixadmin/issues/381#issuecomment-678269198 > > Yet, not all

Distro: OpenSuSE Tumbleweed for x86_64 Failing version: dovecot23-2.3.11.3-1.1.x86_64 Install Date: 2020-08-18 Reverting to previous version works: dovecot23-2.3.10.1-2.3.x86_64 (Packages downgraded coordinately: dovecot23 dovecot23-backend-sqlite) How to make it fail: As the user, execute doveadm expunge mailbox Spam37 savedbefore 3day #User's actual cmd doveadm who #The simplest

With a recent update, I started seeing this: doveconf: Fatal: Error in configuration file /etc/dovecot/conf.d/10-ssl.conf line 14: ssl_cert: Can't open file /etc/letsencrypt/live/SERVER/fullchain.pem: Permission denied 1 4 * * * vmail /usr/bin/doveadm expunge -A mailbox MAILBOXINQUESTION savedbefore 1w is one of the crontab entries I am seeing this for. Is there an option to keep doveadm

On 18/01/2023 22:01, Bert Van de Poel wrote: > I was quite surprised to find that doveadm requires > quite broad privileges (in my case root privileges) to function > properly. This is, I think, a "feature" that was introduced in 2.3. It can make life difficult. There's a message somewhere on the mailing list describing this, but I can't currently find it. The OP

> On 27/03/2023 16:42 EEST Jesper Dybdal <jd-dovecot at dybdal.dk> wrote: > > > I have just upgraded my Debian Buster (Dovecot 2.3.4, I think it was) to > Bullseye (Dovecot 2.3.13). > > The Dovecot server works fine, which of course is the really important > thing. > > But I have a cron job that cleans up all old mail from the mailbox that > I use for

ok, I did install zstd (zstd command line interface 64-bits v1.4.4, by Yann Collet) reconfigured & compiled dovecot 2.3.10.1 again with option : with-zstd changed the configuration file to : zlib_save = zstd and restarted dovecot - now I have following log file errors : Aug 28 16:17:39 lxc-imap dovecot: imap(rnowotny)<237930><H1kft/CtENRUclcc>: Error: zlib_save: Unknown

I have just upgraded my Debian Buster (Dovecot 2.3.4, I think it was) to Bullseye (Dovecot 2.3.13). The Dovecot server works fine, which of course is the really important thing. But I have a cron job that cleans up all old mail from the mailbox that I use for my mobile phone by running "doveadm expunge" every night. That worked fine in 2.3.4, but now it fails: > jdmobile at

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Sun Nov 16 13:00:30 2008 > New Revision: 1560 > > Log: > Generated by libtool and should not be versioned. > > Modified: > trunk/ (props changed) Right, that didn't work out quite the way I intended. Can someone please set the svn:ignore property on

THANKS, but the 'megatec' driver only works whith windows OS via USB, and i need it for red hat OS with USB-serial connection... Please, anybody can help me.... nut-upsuser-request@lists.alioth.debian.org escribi?: Send Nut-upsuser mailing list submissions to nut-upsuser@lists.alioth.debian.org To subscribe or unsubscribe via the World Wide Web, visit

Citeren Arjen de Korte <adkorte-guest op alioth.debian.org>: > Log: > Use the 'nss_compat_ossl' compatibility layer to use the Mozilla NSS > library instead of OpenSSL (we might want to include native support > in the future, but this will at least allow a quick migration for > testing purposes) I don't recall that we ever discussed the possibility of

Hello! I've started seeing intermittent dsync failures since upgrading Dovecot to 2.3.11.3-3 (CentOS 8 using the official Dovecot repo). Sep 27 17:49:04 host dovecot[130]: dsync-local(user at host)<5GWFD2CmcF+TJwAAsNnMGQ>: Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 66543 no longer in transaction log (highest=66547,

Citeren Arjen de Korte <adkorte-guest at alioth.debian.org>: > Author: adkorte-guest > Date: Thu Jan 15 11:54:05 2009 > New Revision: 1728 > > Log: > Another stab at this. > > Modified: > trunk/tools/Makefile.am And failing miserably... :-( Can someone more fluent in 'autotoolish' fix this problem? Currently the BuildBot is broken by update r1718

Dear Sirs, First of all I would like to thank you for support PCM product in your project. Kindly please be informed that POWERCOM launch new USB-controller with productID 0X04. Updated USB-controller compatible with previous version which supported by your usbhid-ups driver. There is added some command and changed idProduct. Vendor ID stay the same 0X0d9f without changes. Detailed information

Dear Sirs, We appreciate your support and cooperation. Can you please kindly add our new USB-controller with productID 0X04 to NUT compatible list. Updated USB-controller compatible with previous version which is supported by your usbhid-ups driver. Detailed information regarding new POWERCOM communication protocol you could download via link

Hi, Sorry for the forwarding. I sent this with the wrong "from" address and got rejected by the list. ---------- Forwarded message ---------- From: Carlos Rodrigues <cefrodrigues at mail.telepac.pt> Date: Jun 18, 2007 9:34 PM Subject: Re: Megatec - modem control lines [impact to megatec_usb] To: Arjen de Korte <nut+devel at de-korte.org> Cc: ups-dev-list <nut-upsdev at