Error: /proc/self/status is larger than expected
Hello, Writing to get some insight as to how I might rid myself of a the pesky error message on the subject. Every binary throws out that error, every LMTP delivery... basically every time any dovecot binary is executed. I am unsure if this is configuration related or not, but intuition says it is an issue with a kernel feature or compiler issue. I saw the error message in the source code (file ), but I don't understand enough of the dovecot architecture or what the code itself is doing in this case. Below and excerpt of a few lines of logs. Since I don't know what specifically this would relate to (and I don't quite remember the command to send the "safe" version of the configuration), I am sending this message in hopes that whatever is needed can be asked and I will provide it. Regards, -Sam [... postfix and rspamd output...] Mar 20 22:17:02 gaia postfix/qmgr[21403]: 4PgcGQ33LfzdT4h: from=, size=12064, nrcpt=1 (queue active) Mar 20 22:17:02 gaia postfix/smtpd[18941]: disconnect from some.list.server[1.2.3.4] ehlo=2 starttls=1 mail=1 rcpt=1 data=1 quit=1 commands=7 Mar 20 22:17:02 gaia dovecot: lmtp(18954): Error: /proc/self/status is larger than expected Mar 20 22:17:02 gaia dovecot: lmtp(18954): Connect from local Mar 20 22:17:02 gaia dovecot: lmtp(s...@samresto.dev)<18954>: Error: /proc/self/status is larger than expected Mar 20 22:17:02 gaia dovecot: message repeated 2 times: [ lmtp(s...@samresto.dev)<18954>: Error: /proc/self/status is larger than expected] Mar 20 22:17:02 gaia dovecot: lmtp(s...@samresto.dev)<18954>: sieve: msgid=<84cf4a75-db54-f33c-cea2-f4772cd18...@samresto.dev>: fileinto action: stored mail into mailbox 'Lists/Folder' Mar 20 22:17:02 gaia dovecot: lmtp(s...@samresto.dev)<18954>: Error: /proc/self/status is larger than expected Mar 20 22:17:02 gaia dovecot: indexer-worker(s...@samresto.dev)<18956>: Error: /proc/self/status is larger than expected Mar 20 22:17:02 gaia postfix/lmtp[18943]: 4PgcGQ33LfzdT4h: to=, relay=wyvern.samresto.dev[private/dovecot-lmtp], delay=0.4, delays=0.31/0/0.01/0.07, dsn=2.0.0, status=sent (250 2.0.0 vbRKLa4hGWQKSgAAw1YR2w Saved) Mar 20 22:17:02 gaia dovecot: lmtp(18954): Disconnect from local: Logged out (state=READY) Mar 20 22:17:02 gaia dovecot: lmtp(18954): Error: /proc/self/status is larger than expected Mar 20 22:17:02 gaia postfix/qmgr[21403]: 4PgcGQ33LfzdT4h: removed
Re: "doveadm altmove -r" not working ?
Hi, Sorry, just read your email again and I realize your problem is different to mine. - Yours is that everything should be moved back to the default storage but nothing - Mine is that some of them should be moved back but everything Does "-Dv" give you any hint? On Tue, 21 Mar 2023 at 08:45, Duc Anh Do wrote: > Hi, > > Your problem might be similar to mine a long time ago. IMO behavior of > "doveadm altmove -r" command with mdbox format is different to sdbox format: > >- With sdbox format, when you move back a message to primary storage >(aka default storage), only the message and the file containing it are >affected. There is nothing impacted. >- With mdbox format, a file in storage contains multiple messages. >When a message is moved back to primary storage, other messages in the same >file storage will go with it. The whole file is moved as well. > > My workaround for this case is: In the mdbox_altmove_add_files function, > after defining action for the message which is marked as MOVE_FROM_ALT, we > will continue checking other messages in the file storage. If they are not > listed in altmoves (they stay in alternate storage), their action will be > MDBOX_MSG_ACTION_MOVE_TO_ALT. That means they will be moved 2 times: to > primary storage as usual then to alternate storage again to ensure finally > they are in alternate storage. > >- Pros: > - Simple > - Do not impact other parts > - Do not require to update other processes to perform MOVE_FROM_ALT > messages >- Cons: > - Reduce performance when number of messages is big > - Increase file storage counter > - If you don't mind building Dovecot from source, give my patch a > look. > > If you don't mind building Dovecot from source, give my patch a look. > > > On Tue, 21 Mar 2023 at 05:26, Benoit Branciard < > benoit.branci...@univ-paris1.fr> wrote: > >> Hello, >> >> I have some trouble using "doveadm altmove -r". >> >> Regular "doveadm altmove" is OK, selected mails were moved to alternate >> storage as expected. But I can't manage to get them back to original >> location, "doveadm altmove -r" has no effect. >> >> We are using Dovecot 2.3.4 (Debian Buster package). >> >> mail_location = mdbox:~/mdbox:DIRNAME=_@@_dbox-Mails_@ >> @_:ALT=/slow%h/mdbox >> >> doveadm altmove -u myuser since 90d >> >> -> some message files are created under /slow/my/homedir/mdbox/storage >> >> doveadm altmove -r -u myuser all >> >> -> message files are still sitting under /slow/my/homedir/mdbox/storage, >> none were created into /my/homedir/mdbox/storage. >> >> Is there some known issues with doveadm altmove in this version ? Or am >> I missing something ? >> >> I can share more config details if needed. >> >> -- >> Benoit BRANCIARD >> Université Paris 1 Panthéon-Sorbonne - DSIUN-SIS >> B405 - Centre PMF - 90 rue de Tolbiac - 75013 Paris >> Tel. 01 44 07 89 68 >> http://dsiun.univ-paris1.fr >> >
Re: "doveadm altmove -r" not working ?
Hi, Your problem might be similar to mine a long time ago. IMO behavior of "doveadm altmove -r" command with mdbox format is different to sdbox format: - With sdbox format, when you move back a message to primary storage (aka default storage), only the message and the file containing it are affected. There is nothing impacted. - With mdbox format, a file in storage contains multiple messages. When a message is moved back to primary storage, other messages in the same file storage will go with it. The whole file is moved as well. My workaround for this case is: In the mdbox_altmove_add_files function, after defining action for the message which is marked as MOVE_FROM_ALT, we will continue checking other messages in the file storage. If they are not listed in altmoves (they stay in alternate storage), their action will be MDBOX_MSG_ACTION_MOVE_TO_ALT. That means they will be moved 2 times: to primary storage as usual then to alternate storage again to ensure finally they are in alternate storage. - Pros: - Simple - Do not impact other parts - Do not require to update other processes to perform MOVE_FROM_ALT messages - Cons: - Reduce performance when number of messages is big - Increase file storage counter - If you don't mind building Dovecot from source, give my patch a look. If you don't mind building Dovecot from source, give my patch a look. On Tue, 21 Mar 2023 at 05:26, Benoit Branciard < benoit.branci...@univ-paris1.fr> wrote: > Hello, > > I have some trouble using "doveadm altmove -r". > > Regular "doveadm altmove" is OK, selected mails were moved to alternate > storage as expected. But I can't manage to get them back to original > location, "doveadm altmove -r" has no effect. > > We are using Dovecot 2.3.4 (Debian Buster package). > > mail_location = mdbox:~/mdbox:DIRNAME=_@@_dbox-Mails_@@_:ALT=/slow%h/mdbox > > doveadm altmove -u myuser since 90d > > -> some message files are created under /slow/my/homedir/mdbox/storage > > doveadm altmove -r -u myuser all > > -> message files are still sitting under /slow/my/homedir/mdbox/storage, > none were created into /my/homedir/mdbox/storage. > > Is there some known issues with doveadm altmove in this version ? Or am > I missing something ? > > I can share more config details if needed. > > -- > Benoit BRANCIARD > Université Paris 1 Panthéon-Sorbonne - DSIUN-SIS > B405 - Centre PMF - 90 rue de Tolbiac - 75013 Paris > Tel. 01 44 07 89 68 > http://dsiun.univ-paris1.fr > doveadm_altmove_r.patch Description: Binary data
"doveadm altmove -r" not working ?
Hello, I have some trouble using "doveadm altmove -r". Regular "doveadm altmove" is OK, selected mails were moved to alternate storage as expected. But I can't manage to get them back to original location, "doveadm altmove -r" has no effect. We are using Dovecot 2.3.4 (Debian Buster package). mail_location = mdbox:~/mdbox:DIRNAME=_@@_dbox-Mails_@@_:ALT=/slow%h/mdbox doveadm altmove -u myuser since 90d -> some message files are created under /slow/my/homedir/mdbox/storage doveadm altmove -r -u myuser all -> message files are still sitting under /slow/my/homedir/mdbox/storage, none were created into /my/homedir/mdbox/storage. Is there some known issues with doveadm altmove in this version ? Or am I missing something ? I can share more config details if needed. -- Benoit BRANCIARD Université Paris 1 Panthéon-Sorbonne - DSIUN-SIS B405 - Centre PMF - 90 rue de Tolbiac - 75013 Paris Tel. 01 44 07 89 68 http://dsiun.univ-paris1.fr
Re: Read-only / archive mode for IMAP mailboxes?
On mars 20, 2023 at 2002 +0100, Robert Schetterer appeared and said: > Am 20.03.23 um 18:26 schrieb Brendan Braybrook: > > check out the imap acl support: > > https://doc.dovecot.org/configuration_manual/acl/ > > > > On 2023-03-20 10:12, Rᴇɴᴇ́ Pꜰᴇɪꜰꜰᴇʀ wrote: > > > > > > We are currently exploring email archiving solutions. Is there a way > > > to use an > > > IMAP mailbox in read-only / archive mode? The requirement is that > > > delibveries of > > > new emails should be possible (via SMTP/LMTP), but no messages > > > should be deleted > > > via IMAP access. … > > years ago i created a archive concept > > https://blog.sys4.de/mailarchiv-mit-dovecot-und-postfix-sortiert-nach-datum-mailadressen-und-ein-ausgehend-unterordnern-de.html > read only via imap acl should also be addable Thanks for the hints. I'll have a look. > but however read > > https://en.wikipedia.org/wiki/Email_archiving > > when it comes to i.e > > Regulatory compliance etc In the use case we have in mind the mailboxes belong to their respective users. It's just an extension of their normal mailbox, because they use a mail client that cannot handle large mailboxes (due to inadequate IMAP support). Also the usual retention polices apply, but the mail client in question can't handle even "normal" retention periods. Best regards, René. -- )\._.,--,'``. fL Let GNU/Linux work for you while you take a nap. /, _.. \ _\ (`._ ,. R. Pfeiffer + https://web.luchs.at/ `._.-(,_..'--(,_..'`-.;.' - System administration + Consulting + Teaching - Got mail delivery problems? https://web.luchs.at/information/blockedmail.php Complete contact information: https://web.luchs.at/kontakt/ Download latest GPG/PGP keys: https://web.luchs.at/kontakt/gpg.asc ⛔ W͇A͇R͇N͇I͇N͇G͇:͇ ͇D͇O͇ ͇_͇N͇O͇T͇_͇ ͇S͇E͇N͇D͇ ͇E͇M͇A͇I͇L͇S͇ ͇W͇I͇T͇H͇ ͇H͇T͇M͇L͇ ͇C͇O͇N͇T͇E͇N͇T͇ ͇T͇O͇ ͇M͇Y͇ ͇E͇M͇A͇I͇L͇ ͇A͇D͇D͇R͇E͇S͇S͇!͇ ⛔ signature.asc Description: PGP signature
Remote backup of IMAP user fails with dsync_remote epoll_ctl error
I’m trying backup a user’s IMAP folders from a system running dovecot 2.1.7. to a system running dovecot 2.3.19.1. After much perusing of the web and Dovecot documentation I tried this: 1) On the 2.1.7 host set up the doveadm server to listen on TCP port 2425 and defined a doveadm_password value 2) Issued the following command on the 2.13.19.1 system: doveadm -o doveadm_password= backup -R -u -S :2425 tcp: 3) The command returned the following errors: Error: doveadm server disconnected before handshake: EOF Error: Command backup failed for : EOF 4) In the Dovecot log on the 2.1.7 system I found the following error message: dsync(): Error: user : Initialization failed: Namespace '': Unknown mail storage driver tcp dovecot: dsync(): Fatal: User init failed A couple of questions: 1) I thought that setting up doveadm-server as an inet_listener (with a password) meant that all communications (including the backup) occurred over that link - is that not correct? Or does SSH also need to be enabled as well? 2) Am I specifying the arguments correctly? The definition of the destination argument is confusing in the documentation - if doveadm is trying to backup a user’s IMAP mailboxes from a remote source, and you’ve already specified the information needed to connect to the remote sources doveadm-server why would the source need to be specified again via the TCP: argument?
Re: Read-only / archive mode for IMAP mailboxes?
Am 20.03.23 um 18:26 schrieb Brendan Braybrook: check out the imap acl support: https://doc.dovecot.org/configuration_manual/acl/ On 2023-03-20 10:12, Rᴇɴᴇ́ Pꜰᴇɪꜰꜰᴇʀ wrote: Hello! We are currently exploring email archiving solutions. Is there a way to use an IMAP mailbox in read-only / archive mode? The requirement is that delibveries of new emails should be possible (via SMTP/LMTP), but no messages should be deleted via IMAP access. Frankly I don't think this works, but maybe some of you have tried this already. Regards, René. years ago i created a archive concept https://blog.sys4.de/mailarchiv-mit-dovecot-und-postfix-sortiert-nach-datum-mailadressen-und-ein-ausgehend-unterordnern-de.html read only via imap acl should also be addable but however read https://en.wikipedia.org/wiki/Email_archiving when it comes to i.e Regulatory compliance etc -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG, 80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein
Re: Read-only / archive mode for IMAP mailboxes?
check out the imap acl support: https://doc.dovecot.org/configuration_manual/acl/ On 2023-03-20 10:12, Rᴇɴᴇ́ Pꜰᴇɪꜰꜰᴇʀ wrote: Hello! We are currently exploring email archiving solutions. Is there a way to use an IMAP mailbox in read-only / archive mode? The requirement is that delibveries of new emails should be possible (via SMTP/LMTP), but no messages should be deleted via IMAP access. Frankly I don't think this works, but maybe some of you have tried this already. Regards, René.
Read-only / archive mode for IMAP mailboxes?
Hello! We are currently exploring email archiving solutions. Is there a way to use an IMAP mailbox in read-only / archive mode? The requirement is that delibveries of new emails should be possible (via SMTP/LMTP), but no messages should be deleted via IMAP access. Frankly I don't think this works, but maybe some of you have tried this already. Regards, René. -- )\._.,--,'``. fL Let GNU/Linux work for you while you take a nap. /, _.. \ _\ (`._ ,. R. Pfeiffer + https://web.luchs.at/ `._.-(,_..'--(,_..'`-.;.' - System administration + Consulting + Teaching - Got mail delivery problems? https://web.luchs.at/information/blockedmail.php Complete contact information: https://web.luchs.at/kontakt/ Download latest GPG/PGP keys: https://web.luchs.at/kontakt/gpg.asc ⛔ W͇A͇R͇N͇I͇N͇G͇:͇ ͇D͇O͇ ͇_͇N͇O͇T͇_͇ ͇S͇E͇N͇D͇ ͇E͇M͇A͇I͇L͇S͇ ͇W͇I͇T͇H͇ ͇H͇T͇M͇L͇ ͇C͇O͇N͇T͇E͇N͇T͇ ͇T͇O͇ ͇M͇Y͇ ͇E͇M͇A͇I͇L͇ ͇A͇D͇D͇R͇E͇S͇S͇!͇ ⛔ signature.asc Description: PGP signature
iPhone Mail clients generate high Solr I/O
Hi,
I'm running a mail server with Dovecot 2.3.20 and Apache Solr as FTS
backend.
It seems that iPhone/iPad Mail clients are generating some IMAP
searches, especially on header Message-ID, that are increasing our Solr
I/O load, especially during the night.
Are these kind of queries normal? What are they?
You can find some logs below.
Dovecot logs:
Mar 13 21:06:14 dovecot: imap-login: Login: user=,
method=PLAIN, rip=x.x.x.x, lip=z.z.z.z, mpid=11263, secured,
session=
Mar 13 21:06:14 dovecot: imap(user@domain) session=:
ID sent: name=iPhone Mail, version=20D67, os=iOS, os-version=16.3.1 (20D67)
Mar 13 21:06:14 dovecot: imap(user@domain) session=:
Disconnected: Logged out in=207 out=1128 deleted=0 expunged=0
autoexpunged=0 trashed=0 appended=0 hdr_count=0 hdr_bytes=0 body_count=0
body_bytes=0
Solr logs:
2023-03-13 21:06:14.411 INFO (qtp1671846437-1652) [ x:dovecot]
o.a.s.c.S.Request [dovecot] webapp=/solr path=/select
params={q={!lucene+q.op%3DAND}hdr:+OR+hdr:<\!\%26\!AAAYAI\/Oo\%2bconzzmkcvmey7ywqjcgaaaep968yud4n1lmhwjxwgturqbaa%3d...@domain5.tld>+OR+hdr:+OR+hdr:+OR+hdr:<24e36a6e5bb2410c8090482b3e1eb...@domain8.tld>=uid,score=uid+asc=%2Bbox:d0f433254ee1b161c82c2e1056c4+%2Buser:user@domain=88=xml}
hits=0 status=0 QTime=275
2023-03-13 21:06:14.511 INFO (qtp1671846437-1628) [ x:dovecot]
o.a.s.c.S.Request [dovecot] webapp=/solr path=/select
params={q={!lucene+q.op%3DAND}hdr:+OR+hdr:+OR+hdr:<00eb01d8c8dc$caa8a580$5ff9f080$@domain1.tld>+OR+hdr:+OR+hdr:<00c701d8bb83$f307bc70$d9173550$@domain1.tld>=uid,score=uid+asc=%2Bbox:d0f433254ee1b161c82c2e1056c4+%2Buser:user@domain=88=xml}
hits=0 status=0 QTime=59
2023-03-13 21:06:14.714 INFO (qtp1671846437-1652) [ x:dovecot]
o.a.s.c.S.Request [dovecot] webapp=/solr path=/select
params={q={!lucene+q.op%3DAND}hdr:+OR+hdr:+OR+hdr:+OR+hdr:<\!\%26\!AAAYAI\/Oo\%2BConZZMkCvmEY7yWqjCgAAAEDl2MLfkWRxJjQW\%2b3dohzn0baa%3d...@domain5.tld>+OR+hdr:=uid,score=uid+asc=%2Bbox:d0f433254ee1b161c82c2e1056c4+%2Buser:user@domain=88=xml}
hits=0 status=0 QTime=178
2023-03-13 21:06:14.771 INFO (qtp1671846437-1628) [ x:dovecot]
o.a.s.c.S.Request [dovecot] webapp=/solr path=/select
params={q={!lucene+q.op%3DAND}hdr:+OR+hdr:+OR+hdr:=uid,score=uid+asc=%2Bbox:d0f433254ee1b161c82c2e1056c4+%2Buser:user@domain=88=xml}
hits=0 status=0 QTime=34
2023-03-13 21:06:14.899 INFO (qtp1671846437-1652) [ x:dovecot]
o.a.s.c.S.Request [dovecot] webapp=/solr path=/select
params={q={!lucene+q.op%3DAND}hdr:+OR+hdr:<02e5e16df27945b6a764f49a5d9e0...@domain8.tld>+OR+hdr:+OR+hdr:<4edb1720076ab71575067b0fc2b5d...@domain2.tld>+OR+hdr:<1657012847.68884...@domain6.tld>=uid,score=uid+asc=%2Bbox:4830f5144ee1b161c82c2e1056c4+%2Buser:user@domain=1=xml}
hits=0 status=0 QTime=46
Thanks
--
Alessio Cecchi
Postmaster @http://www.qboxmail.it
https://www.linkedin.com/in/alessice
Re: Disable folder creation for details username
On 3/17/23 14:55, Gedalya wrote:
That's the setting you want. In IMAP / dovecot context, "mailbox" means
"folder".
The basic directory structure for an account, with INBOX and the various mailboxes
("folders") as defined in your namespace / mailbox configuration where auto =
[create|subscribe], will still be created automatically as soon as the first message
arrives.
Got that, but if the actual INBOX does not exist, will that raise and
exception and not deliver?
We want INBOX to be created and delivered to as well as special use
folders (which I believe there are seperate options for on create/subscribe)
We just don't want the details (users+something) folders to be
automatically created. We find this as a possible DOS vector...
--
inoc.net!rblayzor
XMPP: rblayzor.AT.inoc.net
PGP: https://pgp.inoc.net/rblayzor/
Re: Error: Can't load SSL certificate
The others are on openSUSE 15.4 and macOS, all are binary installs Entware build options Build options: ioloop=epoll openssl io_block_size=8192 SQL drivers: mysql Passdb: checkpassword ldap passwd passwd-file shadow sql Userdb: checkpassword ldap passwd prefetch passwd-file sql macOS build options Build options: ioloop=kqueue notify=kqueue openssl io_block_size=8192 SQL drivers: mysql Passdb: checkpassword pam passwd passwd-file sql Userdb: checkpassword passwd prefetch passwd-file sql openSUSE build options Build options: ioloop=epoll notify=inotify openssl io_block_size=8192 SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) passwd prefetch passwd-file sql The libz.so are for OpenSUSE and the QNap in the same directories withe the same permissions The macOS does not have a libz.so, this dovecot was build by macports. All servers are running dovecot with the same user accounts. At the moment I will look into this issue later and will try to authenticate without using SSL. On the MACs and openSUSE I authenticate using pam, the QNAP does not use pam so I want to authenticate using a local password file, but I have problems to set it up correctly I have changed it 10-auth.conf to use auth-passwdfile.conf.ext and created a password file called userdb. I don’t know what else to change and what exactly should be in the userdb file. The log only shows Mar 20 23:52:45 auth: Debug: auth client connected (pid=6966) Mar 20 23:52:45 imap-login: Info: Disconnected: Aborted login by logging out (no auth attempts in 0 secs): user=<>, rip=192.168.117.5, lip=192.168.117.2, session= I need to fix this first before I can enable SSL again. Maybe I should open a new threat Horst > > My suggests to look for: > > 1. Are your other servers setups installed from "Entware for QNAP" too? > 2. Do your other servers have libz.so* located under /opt/lib/ too? > 3. Did you compare owner and permissions of every libz.so* file between > servers too? > 4. Are other servers running Dovecot with same user account? > > > El 20/3/23 a les 4:01, Horst Simon ha escrit: >> I try to logon to map using dovecot with SSL required. I get following >> entries in the log:Mar 20 13:49:30 auth: Debug: Loading modules from >> directory: /opt/lib/dovecot/modules/auth >> Mar 20 13:49:30 auth: Debug: Module loaded: >> /opt/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so >> Mar 20 13:49:30 auth: Debug: Read auth token secret from >> /opt/var/run/dovecot/auth-token-secret.dat >> Mar 20 13:49:30 auth: Debug: passwd-file /opt/etc/dovecot/userdb:Read 1 >> users in 0 secs >> Mar 20 13:49:30 auth: Debug: auth client connected (pid=26120) >> Mar 20 13:49:30 imap-login: Error: Failed to initialize SSL server >> context: Can't load SSL certificate (ssl_cert setting): >> error:12800067:DSO support routines::could not load the shared library: >> filename(libz.so): libz.so: cannot open shared object file: No such file >> or directory, error:12800067:DSO support routines::could not load the >> shared library: user=<>, rip=192.168.117.5, lip=192.168.117.2, >> session= >> Mar 20 13:49:30 imap-login: Info: Disconnected: TLS initialization >> failed. (no auth attempts in 0 secs): user=<>, rip=192.168.117.5, >> lip=192.168.117.2, session=> >> The library files exist in the include directory >> [/opt] # find . -name libz* -print >> >> ./lib/opkg/info/libzstd.control >> >> ./lib/opkg/info/libzstd.list >> >> ./lib/libz.so >> >> ./lib/libz.so.1 >> >> ./lib/libz.so.1.2.13 >> >> ./lib/libzstd.so >> >> ./lib/libzstd.so.1 >> >> ./lib/libzstd.so.1.5.2 >> >> ./lib/libz.a >> >> >> Have the dovecot settings the same on other servers and it works, >> Dovecot is v2.3.18, installed from Entware for QNAP. Any help?appreciated. >> >> Horst >> >> >> > > -- > > Narcis Garcia >
Re: Dovecot unified event filtering
> On 20/03/2023 13:21 EET Felix Auringer wrote:
>
>
> Hello,
>
> I have an issue with debug logging when using a custom plugin for Dovecot. In
> my plugin, I create a child event of the session's user event:
>
> ```c
> struct event *plugin_event = event_create(list->ns->user->event);
> event_set_name(plugin_event, "oidc_shared_mailboxes_plugin");
> event_set_min_log_level(plugin_event, LOG_TYPE_WARNING);
> event_set_append_log_prefix(plugin_event, "oidc-shared-mailboxes-plugin: ");
> ```
>
> I then use passthrough events like the following:
>
> ```
> e_debug(event_create_passthrough(data->event)->event(), "Modified
> mailbox_list_iter_init was called.");
> e_warning(event_create_passthrough(event)->event(), "Did not find required
> key 'roles' in the JWT body.");
> ```
>
> `e_warning` and `e_error` work fine.
> If I understand the documentation for the unified event filtering
> (https://doc.dovecot.org/configuration_manual/event_filter/#unified-filter-language)
> correctly, I should be able to enable debug logging for with `log_debug =
> event="oidc_shared_mailboxes_plugin"`. However, this setting has no influence
> on the logging behavior. The setting I have to set for the debug logging to
> work is `mail_debug = yes` (I do not have to set `log_debug` at all).
>
> Is this intended behavior or am I doing something wrong?
>
> Best regards,
> Felix Auringer
>
>
> Here is the output of `dovecot -n` (I removed the passdb, userdb, namespace,
> service, and managesieve settings as they cluttered the output):
>
> Felix Auringer
> IT
Hi!
Usually this is used like this:
const struct event_category cat_oidc = {
.name = "oidc"
};
struct event *plugin_event = event_create(list->ns->user->event);
event_add_category(plugin_event, _oid);
event_set_append_log_prefix(plugin_event, "oidc-shared-mailboxes-plugin: ")
...
e_debug(plugin_event, "foo");
e_warning(plugin_event, "bar");
now you can do
log_debug = category=oidc
Aki
Dovecot unified event filtering
Hello,
I have an issue with debug logging when using a custom plugin for Dovecot. In
my plugin, I create a child event of the session's user event:
```c
struct event *plugin_event = event_create(list->ns->user->event);
event_set_name(plugin_event, "oidc_shared_mailboxes_plugin");
event_set_min_log_level(plugin_event, LOG_TYPE_WARNING);
event_set_append_log_prefix(plugin_event, "oidc-shared-mailboxes-plugin: ");
```
I then use passthrough events like the following:
```
e_debug(event_create_passthrough(data->event)->event(), "Modified
mailbox_list_iter_init was called.");
e_warning(event_create_passthrough(event)->event(), "Did not find required key
'roles' in the JWT body.");
```
`e_warning` and `e_error` work fine.
If I understand the documentation for the unified event filtering
(https://doc.dovecot.org/configuration_manual/event_filter/#unified-filter-language)
correctly, I should be able to enable debug logging for with `log_debug =
event="oidc_shared_mailboxes_plugin"`. However, this setting has no influence
on the logging behavior. The setting I have to set for the debug logging to
work is `mail_debug = yes` (I do not have to set `log_debug` at all).
Is this intended behavior or am I doing something wrong?
Best regards,
Felix Auringer
Here is the output of `dovecot -n` (I removed the passdb, userdb, namespace,
service, and managesieve settings as they cluttered the output):
```
# 2.3.19 (b3ad6004dc): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.19 (4eae2f79)
# OS: Linux 5.10.0-15-amd64 x86_64 Debian 11.6
# Hostname: c3dd5b346d22
auth_mechanisms = plain login xoauth2 oauthbearer
debug_log_path = /dev/stdout
disable_plaintext_auth = no
first_valid_uid = 1000
info_log_path = /dev/stdout
last_valid_uid = 1000
log_debug = event="oidc_shared_mailboxes_plugin"
log_path = /dev/stdout
login_greeting = Hello there! GIZ Mail!
mail_location = maildir:~/mail
mail_plugins = " oidc_shared_mailboxes"
plugin {
oidc_shared_mailboxes_client_id = dovecot-test
}
protocols = imap lmtp
```
---
Gesellschaft für interkulturelles
Zusammenleben gGmbH (GIZ)
Felix Auringer
IT
Reformationsplatz 2
13597 Berlin
Tel: 030/513 0100 00; Fax: 030/513 0100 09
www.giz.berlin; felix.auringer@giz.berlin
Amtsgericht Charlottenburg HRB 200872 B
Geschäftsführerin: Dr. Britta Marschke
Re: Error: Can't load SSL certificate
My suggests to look for: 1. Are your other servers setups installed from "Entware for QNAP" too? 2. Do your other servers have libz.so* located under /opt/lib/ too? 3. Did you compare owner and permissions of every libz.so* file between servers too? 4. Are other servers running Dovecot with same user account? El 20/3/23 a les 4:01, Horst Simon ha escrit: I try to logon to map using dovecot with SSL required. I get following entries in the log:Mar 20 13:49:30 auth: Debug: Loading modules from directory: /opt/lib/dovecot/modules/auth Mar 20 13:49:30 auth: Debug: Module loaded: /opt/lib/dovecot/modules/auth/lib20_auth_var_expand_crypt.so Mar 20 13:49:30 auth: Debug: Read auth token secret from /opt/var/run/dovecot/auth-token-secret.dat Mar 20 13:49:30 auth: Debug: passwd-file /opt/etc/dovecot/userdb:Read 1 users in 0 secs Mar 20 13:49:30 auth: Debug: auth client connected (pid=26120) Mar 20 13:49:30 imap-login: Error: Failed to initialize SSL server context: Can't load SSL certificate (ssl_cert setting): error:12800067:DSO support routines::could not load the shared library: filename(libz.so): libz.so: cannot open shared object file: No such file or directory, error:12800067:DSO support routines::could not load the shared library: user=<>, rip=192.168.117.5, lip=192.168.117.2, session= Mar 20 13:49:30 imap-login: Info: Disconnected: TLS initialization failed. (no auth attempts in 0 secs): user=<>, rip=192.168.117.5, lip=192.168.117.2, session= The library files exist in the include directory [/opt] # find . -name libz* -print ./lib/opkg/info/libzstd.control ./lib/opkg/info/libzstd.list ./lib/libz.so ./lib/libz.so.1 ./lib/libz.so.1.2.13 ./lib/libzstd.so ./lib/libzstd.so.1 ./lib/libzstd.so.1.5.2 ./lib/libz.a Have the dovecot settings the same on other servers and it works, Dovecot is v2.3.18, installed from Entware for QNAP. Any help appreciated. Horst -- Narcis Garcia __ I'm using this dedicated address because personal addresses aren't masked enough at this mail public archive. Public archive administrator should fix this against automated addresses collectors.
