Re: New Dovecot release?
Hello, I had reported it a while back in April on this list and Aki is correct — it is due to recent kernels. The change that was committed to Git resolved the issue for me with kernel version 6.1.12 on Gentoo. For reference, Aki had stated it was fixed in main and provided this: https://github.com/dovecot/core/compare/f359c6ee179aad5e077711c188fc8422106cbead%5E..d93c31d51b05d43eaa6eeef9cdc0f7a4157f7d0e.patch Regards, Elisamuel Resto > On Sep 19, 2023, at 02:54, Aki Tuomi via dovecot wrote: > >> >> On 19/09/2023 10:33 EEST Taavi Ansper via dovecot >> wrote: >> >> >> Hi >> >> When will there be a new dovecot release. The 2.3.21 version borked our >> users with large amount of folders (i think over 255 folders) >> >> doveadm(REDACTED_USER): Error: /proc/self/status is larger than expected >> >> I can't find the debian bug report (or was it mentioned in this same mailing >> list), but somebody else has mentioned the same issue. >> >> I hope this gets fixed in the next version. >> >> -- >> Taavi Ansper >> taavi.ans...@cyber.ee > > Hi! > > This is actually caused by very recent kernels, if I remember correctly. Can > you let me known the distro & kernel you are using and source of your > packages? This is actually fixed for 2.4 already in > > https://github.com/dovecot/core/commit/218a79a48bb0e5d2be44bb46c51836fd406b0c50.patch > > Aki > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: Error: /proc/self/status is larger than expected
On 2023-03-30 5:27 am, Aki Tuomi wrote: Hi! This is now fixed in main, see https://github.com/dovecot/core/compare/f359c6ee179aad5e077711c188fc8422106cbead%5E..d93c31d51b05d43eaa6eeef9cdc0f7a4157f7d0e.patch Aki [..] Aki, Thank you! -- Elisamuel Resto signature.asc Description: OpenPGP digital signature
Re: Error: /proc/self/status is larger than expected
Aki, Thank you! Regards, -Sam > On Mar 26, 2023, at 04:00, Aki Tuomi wrote: > > Hi! > > This requires a code change, which is currently in progress. It does require > you to patch Dovecot yourself if you want to use it, once it's ready. > > Aki > >> On 26/03/2023 05:22 EEST Elisamuel Resto Donate wrote: >> >> >> Hi, >> >> At this point I have resorted to add the error message to be ignored by the >> syslog daemon to at least keep it out of sight. It really makes logs >> confusing. I'm paying attention of anyone has any suggestions to try. >> >> Thanks! >> -Sam >> >> >>> On 3/22/2023 10:39 AM, Elisamuel Resto wrote: >>> >>> Hello, >>> >>> gaia ~ # uname -a >>> Linux gaia 6.1.12-gentoo-x86_64 #1 SMP Thu Mar 9 19:57:24 CST 2023 x86_64 >>> Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz GenuineIntel GNU/Linux >>> gaia ~ # dovecot --version >>> 2.3.20 (80a5ac675d) >>> gaia ~ # cat /proc/self/status | wc --bytes >>> >>> See attached for example content of /proc/self/status and the dovecot.conf >>> through 'dovecot -n' >>> >>> >>> I am re-sending this message because there were a lot of DMARC reports due >>> to my reject policy and the Dovecot list settings. >>> >>> >>> >>> >>> >>> Regards, >>> -Sam >>> >>> >>> >>>> On Mar 21, 2023, at 02:38, Aki Tuomi wrote: >>>> >>>> >>>> >>>> >>>>> On 21/03/2023 05:29 EET Elisamuel Resto Donate wrote: >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> 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 >>>>> >>>>> >>>>> >>>> >>>> Hi! >>>> >>>> Which distro is this? >>>> >>>> Aki >>>> >> >>
Re: Error: /proc/self/status is larger than expected
Hi, At this point I have resorted to add the error message to be ignored by the syslog daemon to at least keep it out of sight. It really makes logs confusing. I'm paying attention of anyone has any suggestions to try. Thanks! -Sam On 3/22/2023 10:39 AM, Elisamuel Resto wrote: Hello, gaia ~ # uname -a Linux gaia 6.1.12-gentoo-x86_64 #1 SMP Thu Mar 9 19:57:24 CST 2023 x86_64 Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz GenuineIntel GNU/Linux gaia ~ # dovecot --version 2.3.20 (80a5ac675d) gaia ~ # cat /proc/self/status | wc --bytes See attached for example content of /proc/self/status and the dovecot.conf through 'dovecot -n' I am re-sending this message because there were a lot of DMARC reports due to my reject policy and the Dovecot list settings. Regards, -Sam On Mar 21, 2023, at 02:38, Aki Tuomi wrote: On 21/03/2023 05:29 EET Elisamuel Resto Donate wrote: 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 Hi! Which distro is this? Aki
Re: Error: /proc/self/status is larger than expected
-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 1
service_count = 1
}
service managesieve {
process_limit = 20
}
service pop3-login {
inet_listener pop3 {
port = 110
}
inet_listener pop3s {
port = 995
ssl = yes
}
}
service stats {
unix_listener stats-reader {
group = vmail
mode = 0664
user = vmail
}
unix_listener stats-writer {
group = vmail
mode = 0666
user = vmail
}
}
service submission-login {
inet_listener submission {
port = 587
}
}
ssl_cert = Regards,-SamOn Mar 21, 2023, at 02:38, Aki Tuomi wrote:On 21/03/2023 05:29 EET Elisamuel Resto Donate wrote: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: removedHi!Which distro is this?Aki
Re: Error: /proc/self/status is larger than expected
Hello,
gaia ~ # uname -a
Linux gaia 6.1.12-gentoo-x86_64 #1 SMP Thu Mar 9 19:57:24 CST 2023
x86_64 Intel(R) Core(TM) i5-3470S CPU @ 2.90GHz GenuineIntel GNU/Linux
gaia ~ # dovecot --version
2.3.20 (80a5ac675d)
gaia ~ # cat /proc/self/status | wc --bytes
See attached for example content of /proc/self/status and the
dovecot.conf through 'dovecot -n'
Regards,
-Sam
On 3/21/2023 2:32 AM, Aki Tuomi wrote:
On 21/03/2023 05:29 EET Elisamuel Resto Donate wrote:
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
Hi!
Which distro is this?
Aki
# 2.3.20 (80a5ac675d): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.20 (149edcf2)
# OS: Linux 6.1.12-gentoo-x86_64 x86_64 Gentoo Base System release 2.13 btrfs
# Hostname: wyvern.samresto.dev
auth_mechanisms = plain login
dict {
lastlogin = mysql:/etc/dovecot/dovecot-lastlogin-dict.conf.ext
metadata = mysql:/etc/dovecot/dovecot-metadata-dict.conf.ext
quota_clone = mysql:/etc/dovecot/dovecot-quota-dict.conf.ext
}
doveadm_worker_count = 5
first_valid_gid = 5000
first_valid_uid = 5000
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
last_valid_gid = 5000
last_valid_uid = 5000
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header = X-Original-To
lmtp_client_workarounds = whitespace-before-path
lmtp_rcpt_check_quota = yes
lmtp_save_to_detail_mailbox = yes
mail_attachment_detection_options = add-flags-on-save
mail_attribute_dict = file:%h/dovecot-attributes
mail_gid = 5000
mail_home = /var/mail/virtual/%Ld/%Ln
mail_location = maildir:/var/mail/virtual/%Ld/%Ln
mail_plugins = " quota quota_clone mailbox_alias trash fts fts_flatcurve"
mail_uid = 5000
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date index ihave duplicate
mime foreverypart extracttext spamtestplus virustest vnd.dovecot.pipe
vnd.dovecot.filter
namespace inbox {
inbox = yes
location =
mailbox Archive {
auto = subscribe
special_use = \Archive
}
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox "Sent Messages" {
auto = no
special_use = \Sent
}
mailbox Spam {
auto = subscribe
autoexpunge = 30 days
special_use = \Junk
}
mailbox Trash {
auto = subscribe
au
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: TLS renegotiation issue (CVE-2011-1473) in Dovecot
On 2022-05-13 5:02 pm, Greg Earle wrote: Hello, At work I'm running a Dovecot 2.3.15 server on a RHEL 7.9 system with OpenSSL 1.0.2k. Our IT Security people are threatening to shut it down because of this: We were notified of a possible TLS renegotiation vulnerability on [FQHN]. [Parent organization] ticket NNN is open to track efforts. We conducted a manual test on the site for TLS Renegotiation on IMAP port 993. We found that this was set to enabled. In order to remediate we will need to either: 1. Disable Renegotiation (preferred) 2. Set a max aggregated renegotiation Please remediate as soon as possible. References: https://support.f5.com/csp/article/K15278 https://nvd.nist.gov/vuln/detail/cve-2011-1473 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1473 I did some Googling and among the results, I found a few old posts from this mailing list among them, which to summarize basically seemed to say "Yeah, we could write some code ... " but that was about it. The IT Security rep sent me a reference to an ancient Red Hat article https://access.redhat.com/articles/23543 which is hysterical - ancient history, references NSS and Tomcat, suggests changes to an add-on product (Red Hat Certificate Server) that is EOL, etc. Is there any way to mitigate this issue? (The only thing I can think of is to upgrade the Dovecot server to RHEL 8 and restrict connections to only TLSv1.3, but that ain't gonna happen overnight.) Thanks, - Greg Greg, I believe this to be a configuration error, not a dovecot problem. The output of dovecot -n (as an attachment; look it over for any data you do not want publicized) would help to suggest changes to bring you back into compliance. Regards, Elisamuel Resto
Re: imap_metadata plugin panic
Hi,
So I have waited to see what comes in updates and while it hasn't been
fixed on my end, it at least doesn't panic anymore and properly errors
out. This error has only happened when deleting folders. No other action
I do from day to day has triggered this in the logs that I can see.
Mar 23 07:13:57 wyvern dovecot[148148]: dict(454663): Error: metadata:
dict_iterate() failed: sql dict iterate failed for
priv/90da1903dab0c2614f0d0100a07d9965/: Key continues past the matched
pattern priv/$
Mar 23 07:13:57 wyvern dovecot[148148]:
imap(s...@samresto.dev)<453545>: Error:
Mailbox Trash/2009: dict_iterate(priv/90da1903dab0c2614f0d0100a07d9965/)
failed: dict-server returned failure: sql dict iterate failed for
priv/90da1903dab0c2614f0d0100a07d9965/: Key continues past the matched
pattern priv/$ (reply took 0.035 secs (0.036 in dict wait, 0.000 in
other ioloops, 0.000 in locks, async-id reply 0.000 secs ago, started on
dict-server 0.009 secs ago, took 0.009 secs))
The configurations have not changed much (if at all), but I have
attached them for reference. I would love to be able to delete folders
again.
Regards,
Elisamuel Resto
On 11/15/2021 12:27 PM, Elisamuel Resto wrote:
Hello,
This may be covered somewhere but recently I enabled the metadata
plugin to work with sieve as part of some updates I did a while back
and I hadn't checked my logs for any issues with it and so far they're
not completely taking my system down.
Right now, upon trying to delete a folder I noticed the following in
my logs... what am I missing? I see the broken SQL query, but I don't
know enough about the dict system or the metadata plugin to know how
to add the missing information or fix it otherwise.
Regards,
Elisamuel Resto
Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too
many bind args (2) for statement: SELECT meta_key FROM metadata WHERE
meta_key LIKE AND username = ?
Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Error: Raw
backtrace: /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x43)
[0x7f449789d073] ->
/usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x20) [0x7f449789d190]
-> /usr/lib/dovecot/libdovecot.so.0(+0xfaf1f) [0x7f44978a9f1f] ->
/usr/lib/dovecot/libdovecot.so.0(+0xfafb1) [0x7f44978a9fb1] ->
/usr/lib/dovecot/libdovecot.so.0(+0x4cd20) [0x7f44977fbd20] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](+0x875a) [0x555e60d7775a] -> dovecot/dict [0 clients,
0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](sql_statement_query+0x42) [0x555e60d7f262] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](+0xd97f) [0x555e60d7c97f] ->
/usr/lib/dovecot/libdovecot.so.0(dict_iterate_values+0x25)
[0x7f4497868615] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](+0xa929) [0x555e60d79929] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](+0xb224) [0x555e60d7a224] -> dovecot/dict [0 clients,
0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0 commits:0/0/0/0](+0xb381)
[0x555e60d7a381] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](dict_command_input+0xd9)
[0x555e60d7a579] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](+0x95b8) [0x555e60d785b8] ->
/usr/lib/dovecot/libdovecot.so.0(connection_input_default+0x15e)
[0x7f44978a16ce] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6b)
[0x7f44978bfebb] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x13b)
[0x7f44978c15cb] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x51)
[0x7f44978bff61] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x41)
[0x7f44978c0131] ->
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x14)
[0x7f4497831f74] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](main+0x189) [0x555e60d78139] ->
/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f44972cfb25] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](_start+0x2e) [0x555e60d7819e]
Nov 15 12:19:19 wyvern dovecot[461]:
imap(s...@samresto.dev)<51449><+BGq2NfQM/7Pisr9>: Error: Mailbox
Trash/Processed: dict_iterate(priv/c841ad0291c27461ac670100a07d9965/)
failed: Connection closed (reply took 0.204 secs (0.204 in dict wait,
0.000 in other ioloops, 0.000 in locks))
Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Fatal: master:
service(dict): child 51438 killed with signal 6 (core dumped)
# 2.3.18 (9dd8408c18): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.18 (0bc28b32)
# OS: Linux 5.16.15-arch1-1 x86_64 ext4
# Hostname: wyvern.simplysam.us
auth_mechanisms = plain login
dict {
lastlogin = mysql:/etc/dovecot/dovecot-lastlogin-dict.conf.ext
metadata = mysql:/etc/dovecot/dovecot-metadata-dict.conf.ext
quota_clone = mys
Re: imap_metadata plugin panic
Any other suggestions? I’m stuck between a rock and a hard place. Had to enable
to get the fts module working and now I can’t get rid of this problem.
Just seems like the user is not being passed to the query builder at some
point. I’ve taken a look at code pertaining the metadata module and I can’t
quite tell where it would be, though my skills are limited.
Regards,
Elisamuel Resto
> On Dec 1, 2021, at 7:01 AM, Elisamuel Resto wrote:
>
> Aki,
>
> Since the original email, dicts are now on their own. For the metadata I have
> tried the two dicts (shared/$key, priv/$key), just the priv dict db schema
> with "pattern = $key" per one of your emails to the ML, and just the
> "priv/$key" pattern. All of those combinations produce the same issue. In
> summary, I've tried several things but result is still that I can create
> folders but deletion causes a panic.
>
> As of last email sending the dict, here is what dovecot knows about the dicts:
> dict {
> quota_clone = mysql:/etc/dovecot/dovecot-quota-dict.conf.ext
> lastlogin = mysql:/etc/dovecot/dovecot-lastlogin-dict.conf.ext
> metadata = mysql:/etc/dovecot/dovecot-metadata-dict.conf.ext
> }
>
> And the dovecot-metadata-dict.conf.ext:
> map {
> pattern = shared/$key
> table = metadata_shared
> username_field = username
> value_field = meta_value
>
> fields {
> meta_key = $key
> }
> }
>
> map {
> pattern = priv/$key
> table = metadata_priv
> username_field = username
> value_field = meta_value
>
> fields {
> meta_key = $key
> }
> }
>
> I've attached the current dovecot.conf.
>
>
> -Sam
>
> ----
> *From:* Aki Tuomi [mailto:aki.tu...@open-xchange.com]
> *Sent:* Wednesday, December 1, 2021, 2:23 AM
> *To:* Elisamuel Resto; dovecot@dovecot.org
> *Subject:* imap_metadata plugin panic
>
>> It's probably not a good idea to put all the patterns in same dict. I would
>> first try if it still happens if you make a dedicated mysql dict with only
>> the metadata patterns.
>>
>> Aki
>>
>>>> On 22/11/2021 18:52 Elisamuel Resto wrote:
>>>
>>> Aki,
>>>
>>> My apologies, I thought that it was included in the output of "dovecot
>>> -n". I don't have just one, but I concatenated them for ease. See attached.
>>>
>>> Thanks!
>>> -Sam
>>>
>>> *From:* Aki Tuomi [mailto:aki.tu...@open-xchange.com]
>>> *Sent:* Monday, November 22, 2021, 5:13 AM
>>> *To:* dovecot@dovecot.org, Elisamuel Resto
>>> *Cc:* dove...@ptld.com
>>> *Subject:* imap_metadata plugin panic
>>>
>>>> Hi, I wanted to see /etc/dovecot/dovecot-dict-sql.conf.ext
>>>>
>>>> Aki
>>>>
>>>> On 22 November 2021 11.08.01 UTC, Elisamuel Resto
>>>> wrote:
>>>>
>>>> Aki,
>>>>
>>>> # 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
>>>> # Pigeonhole version 0.5.16 (09c29328)
>>>> # OS: Linux 5.14.16-arch1-1 x86_64 ext4
>>>>
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.16 (09c29328)
# OS: Linux 5.15.4-arch1-1 x86_64 ext4
# Hostname: wyvern.simplysam.us
auth_mechanisms = plain login
dict {
lastlogin = mysql:/etc/dovecot/dovecot-lastlogin-dict.conf.ext
metadata = mysql:/etc/dovecot/dovecot-metadata-dict.conf.ext
quota_clone = mysql:/etc/dovecot/dovecot-quota-dict.conf.ext
}
doveadm_worker_count = 5
first_valid_gid = 5000
first_valid_uid = 5000
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
last_valid_gid = 5000
last_valid_uid = 5000
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header = X-Original-To
lmtp_client_workarounds = whitespace-before-path
lmtp_rcpt_check_quota = yes
lmtp_save_to_detail_mailbox = yes
mail_attachment_detection_options = add-flags-on-save
mail_attribute_dict = proxy::metadata
mail_gid = 5000
mail_home = /var/mail/virtual/%Ld/%Ln
mail_location = maildir:/var/mail/virtual/%Ld/%Ln
mail_plugins = " quota quota_clone mailbox_alias trash fts fts_flatcurve"
mail_uid = 5000
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date index ihave
Re: imap_metadata plugin panic
Aki,
Since the original email, dicts are now on their own. For the metadata I
have tried the two dicts (shared/$key, priv/$key), just the priv dict db
schema with "pattern = $key" per one of your emails to the ML, and just
the "priv/$key" pattern. All of those combinations produce the same
issue. In summary, I've tried several things but result is still that I
can create folders but deletion causes a panic.
As of last email sending the dict, here is what dovecot knows about the
dicts:
dict {
quota_clone = mysql:/etc/dovecot/dovecot-quota-dict.conf.ext
lastlogin = mysql:/etc/dovecot/dovecot-lastlogin-dict.conf.ext
metadata = mysql:/etc/dovecot/dovecot-metadata-dict.conf.ext
}
And the dovecot-metadata-dict.conf.ext:
map {
pattern = shared/$key
table = metadata_shared
username_field = username
value_field = meta_value
fields {
meta_key = $key
}
}
map {
pattern = priv/$key
table = metadata_priv
username_field = username
value_field = meta_value
fields {
meta_key = $key
}
}
I've attached the current dovecot.conf.
-Sam
*From:* Aki Tuomi [mailto:aki.tu...@open-xchange.com]
*Sent:* Wednesday, December 1, 2021, 2:23 AM
*To:* Elisamuel Resto; dovecot@dovecot.org
*Subject:* imap_metadata plugin panic
It's probably not a good idea to put all the patterns in same dict. I would
first try if it still happens if you make a dedicated mysql dict with only the
metadata patterns.
Aki
On 22/11/2021 18:52 Elisamuel Resto wrote:
Aki,
My apologies, I thought that it was included in the output of "dovecot
-n". I don't have just one, but I concatenated them for ease. See attached.
Thanks!
-Sam
*From:* Aki Tuomi [mailto:aki.tu...@open-xchange.com]
*Sent:* Monday, November 22, 2021, 5:13 AM
*To:* dovecot@dovecot.org, Elisamuel Resto
*Cc:* dove...@ptld.com
*Subject:* imap_metadata plugin panic
Hi, I wanted to see /etc/dovecot/dovecot-dict-sql.conf.ext
Aki
On 22 November 2021 11.08.01 UTC, Elisamuel Resto
wrote:
Aki,
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.16 (09c29328)
# OS: Linux 5.14.16-arch1-1 x86_64 ext4
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.16 (09c29328)
# OS: Linux 5.15.4-arch1-1 x86_64 ext4
# Hostname: wyvern.simplysam.us
auth_mechanisms = plain login
dict {
lastlogin = mysql:/etc/dovecot/dovecot-lastlogin-dict.conf.ext
metadata = mysql:/etc/dovecot/dovecot-metadata-dict.conf.ext
quota_clone = mysql:/etc/dovecot/dovecot-quota-dict.conf.ext
}
doveadm_worker_count = 5
first_valid_gid = 5000
first_valid_uid = 5000
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
last_valid_gid = 5000
last_valid_uid = 5000
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header = X-Original-To
lmtp_client_workarounds = whitespace-before-path
lmtp_rcpt_check_quota = yes
lmtp_save_to_detail_mailbox = yes
mail_attachment_detection_options = add-flags-on-save
mail_attribute_dict = proxy::metadata
mail_gid = 5000
mail_home = /var/mail/virtual/%Ld/%Ln
mail_location = maildir:/var/mail/virtual/%Ld/%Ln
mail_plugins = " quota quota_clone mailbox_alias trash fts fts_flatcurve"
mail_uid = 5000
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date index ihave duplicate
mime foreverypart extracttext spamtestplus virustest vnd.dovecot.pipe
vnd.dovecot.filter
namespace inbox {
inbox = yes
location =
mailbox Archive {
auto = subscribe
special_use = \Archive
}
mailbox Drafts {
auto = subscribe
special_use = \Drafts
}
mailbox Sent {
auto = subscribe
special_use = \Sent
}
mailbox "Sent Messages" {
auto = no
special_use = \Sent
}
mailbox Spam {
auto = subscribe
autoexpunge = 30 days
special_use = \Junk
}
mailbox Trash {
auto = subscribe
autoexpunge = 90 days
special_use = \Trash
}
prefix =
separator = /
type = private
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
antispam_backend = pipe
antispam_pipe_program = /usr/local/sbin/sa-learn-pipe
antispam_pipe_program_notspam_arg = --ham
antispam_pipe_program_spam_arg = --spam
antispam_pipe_tmpdir = /tmp
antispam_spam = Junk;Spam
antispam_trash = trash;Trash;Deleted Items;Deleted Messages
fts = flatcurve
fts_autoindex = yes
fts_autoindex_exclude = \Spam
fts_autoindex_exclude2 = \Trash
fts_enforced = yes
fts_flatcurve
Re: imap_metadata plugin panic
Aki,
My apologies, I thought that it was included in the output of "dovecot
-n". I don't have just one, but I concatenated them for ease. See attached.
Thanks!
-Sam
*From:* Aki Tuomi [mailto:aki.tu...@open-xchange.com]
*Sent:* Monday, November 22, 2021, 5:13 AM
*To:* dovecot@dovecot.org, Elisamuel Resto
*Cc:* dove...@ptld.com
*Subject:* imap_metadata plugin panic
Hi, I wanted to see /etc/dovecot/dovecot-dict-sql.conf.ext
Aki
On 22 November 2021 11.08.01 UTC, Elisamuel Resto
wrote:
Aki,
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.16 (09c29328)
# OS: Linux 5.14.16-arch1-1 x86_64 ext4
map {
pattern = shared/last-login/$user
table = lastlogin
value_field = last_login
value_type = uint
fields {
username = $user
}
}
map {
pattern = shared/$key
table = metadata
username_field = username
value_field = meta_value
fields {
meta_key = $key
}
}
map {
pattern = priv/$key
table = metadata
username_field = username
value_field = meta_value
fields {
meta_key = $key
}
}
map {
pattern = priv/quota/storage
table = quota2
username_field = username
value_field = bytes
}
map {
pattern = priv/quota/messages
table = quota2
username_field = username
value_field = messages
}
OpenPGP_0xD2D5FB6118615F19.asc
Description: OpenPGP public key
OpenPGP_signature
Description: OpenPGP digital signature
Re: imap_metadata plugin panic
0
user = postfix
}
unix_listener auth-userdb {
mode = 0666
}
}
service dict {
unix_listener dict {
group = vmail
mode = 0660
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
process_min_avail = 1
service_count = 1
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
unix_listener lmtp {
mode = 0666
}
}
service managesieve-login {
inet_listener sieve {
port = 4190
}
process_min_avail = 1
service_count = 1
}
service managesieve {
process_limit = 20
}
service pop3-login {
inet_listener pop3 {
port = 110
}
inet_listener pop3s {
port = 995
ssl = yes
}
}
service stats {
unix_listener stats-reader {
group = vmail
mode = 0664
user = vmail
}
unix_listener stats-writer {
group = vmail
mode = 0666
user = vmail
}
}
service submission-login {
inet_listener submission {
port = 587
}
}
ssl_cert =
Regards,
Elisamuel Resto
> On Nov 22, 2021, at 12:36 AM, Aki Tuomi wrote:
>
>
>>> On 21/11/2021 22:40 dove...@ptld.com wrote:
>>>
>>>
>>>> On 11-21-2021 1:15 pm, Elisamuel Resto wrote:
>>> I have gone through my configuration and even found a configuration example
>>> by Aki and that confirms how I configured it… still getting that
>>> error.
>>
>>> Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many
>>> bind args (2) for statement: SELECT meta_key FROM metadata WHERE meta_key
>>> LIKE AND username = ?
>>
>>
>> You fixed the query syntax to make sure that is not the issue?
>> "WHERE meta_key LIKE AND username = ?" is not valid syntax.
>
> It's not possible to fix the SQL syntax manually with dict driver. Sam, can
> you post your dict config, without passwords. Also which version of Dovecot &
> Pigeonhole is this?
>
> Aki
Re: imap_metadata plugin panic
I can’t fix a query that is built by dovecot. The code itself builds the query based on my dict configuration… so I can’t do that. I know the query is broken and why it’s failing, but I can’t fix it myself unless I find the code or what I did wrong in the configuration… but thanks for the reply anyway Regards, Elisamuel Resto > On Nov 21, 2021, at 2:41 PM, dove...@ptld.com wrote: > > >> >> On 11-21-2021 1:15 pm, Elisamuel Resto wrote: >> I have gone through my configuration and even found a configuration example >> by Aki and that confirms how I configured it… still getting that >> error. > >> Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many >> bind args (2) for statement: SELECT meta_key FROM metadata WHERE meta_key >> LIKE AND username = ? > > > You fixed the query syntax to make sure that is not the issue? > "WHERE meta_key LIKE AND username = ?" is not valid syntax.
Re: imap_metadata plugin panic
I have gone through my configuration and even found a configuration example by
Aki and that confirms how I configured it… still getting that error.
Possibly a issue with the code? Any suggestions as to how to enable debugging
to try and find the issue?
Regards,
Elisamuel Resto
> On Nov 15, 2021, at 12:37 PM, Elisamuel Resto wrote:
>
> Hello,
>
> This may be covered somewhere but recently I enabled the metadata plugin to
> work with sieve as part of some updates I did a while back and I hadn't
> checked my logs for any issues with it and so far they're not completely
> taking my system down.
>
> Right now, upon trying to delete a folder I noticed the following in my
> logs... what am I missing? I see the broken SQL query, but I don't know
> enough about the dict system or the metadata plugin to know how to add the
> missing information or fix it otherwise.
>
> Regards,
> Elisamuel Resto
>
>
> Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too many
> bind args (2) for statement: SELECT meta_key FROM metadata WHERE meta_key
> LIKE AND username = ?
> Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Error: Raw backtrace:
> /usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x43) [0x7f449789d073] ->
> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x20) [0x7f449789d190] ->
> /usr/lib/dovecot/libdovecot.so.0(+0xfaf1f) [0x7f44978a9f1f] ->
> /usr/lib/dovecot/libdovecot.so.0(+0xfafb1) [0x7f44978a9fb1] ->
> /usr/lib/dovecot/libdovecot.so.0(+0x4cd20) [0x7f44977fbd20] -> dovecot/dict
> [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0 commits:0/0/0/0](+0x875a)
> [0x555e60d7775a] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
> iters:0/0/0/0, 0 commits:0/0/0/0](sql_statement_query+0x42) [0x555e60d7f262]
> -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
> commits:0/0/0/0](+0xd97f) [0x555e60d7c97f] ->
> /usr/lib/dovecot/libdovecot.so.0(dict_iterate_values+0x25) [0x7f4497868615]
> -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
> commits:0/0/0/0](+0xa929) [0x555e60d79929] -> dovecot/dict [0 clients, 0
> lookups:0/0/0/0, 0 iters:0/0/0/0, 0 commits:0/0/0/0](+0xb224)
> [0x555e60d7a224] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
> iters:0/0/0/0, 0 commits:0/0/0/0](+0xb381) [0x555e60d7a381] -> dovecot/dict
> [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
> commits:0/0/0/0](dict_command_input+0xd9) [0x555e60d7a579] -> dovecot/dict [0
> clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0 commits:0/0/0/0](+0x95b8)
> [0x555e60d785b8] ->
> /usr/lib/dovecot/libdovecot.so.0(connection_input_default+0x15e)
> [0x7f44978a16ce] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6b)
> [0x7f44978bfebb] ->
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x13b)
> [0x7f44978c15cb] ->
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x51) [0x7f44978bff61]
> -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x41) [0x7f44978c0131] ->
> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x14) [0x7f4497831f74] ->
> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
> commits:0/0/0/0](main+0x189) [0x555e60d78139] ->
> /usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f44972cfb25] -> dovecot/dict
> [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
> commits:0/0/0/0](_start+0x2e) [0x555e60d7819e]
> Nov 15 12:19:19 wyvern dovecot[461]:
> imap(s...@samresto.dev)<51449><+BGq2NfQM/7Pisr9>: Error: Mailbox
> Trash/Processed: dict_iterate(priv/c841ad0291c27461ac670100a07d9965/) failed:
> Connection closed (reply took 0.204 secs (0.204 in dict wait, 0.000 in other
> ioloops, 0.000 in locks))
> Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Fatal: master:
> service(dict): child 51438 killed with signal 6 (core dumped)
>
[root@wyvern ~]# dovecot -n
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.16 (09c29328)
# OS: Linux 5.14.16-arch1-1 x86_64 ext4
# Hostname: wyvern.simplysam.us
auth_mechanisms = plain login
dict {
lastlogin = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
metadata = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
quota_clone = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
doveadm_worker_count = 5
first_valid_gid = 5000
first_valid_uid = 5000
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
last_valid_gid = 5000
last_valid_uid = 5000
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header = X-Original-To
lmtp_client_workarounds = whitespace-before-path
lmtp_rcpt_check_quota = yes
lmtp_save_to_detail_mailbox = yes
mail_attachment_detection_options = add-flags-on-save
mail_attribute_dict = proxy::metadata
mail_gid = 500
imap_metadata plugin panic
Hello,
This may be covered somewhere but recently I enabled the metadata plugin
to work with sieve as part of some updates I did a while back and I
hadn't checked my logs for any issues with it and so far they're not
completely taking my system down.
Right now, upon trying to delete a folder I noticed the following in my
logs... what am I missing? I see the broken SQL query, but I don't know
enough about the dict system or the metadata plugin to know how to add
the missing information or fix it otherwise.
Regards,
Elisamuel Resto
Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Panic: lib-sql: Too
many bind args (2) for statement: SELECT meta_key FROM metadata WHERE
meta_key LIKE AND username = ?
Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(backtrace_append+0x43) [0x7f449789d073]
-> /usr/lib/dovecot/libdovecot.so.0(backtrace_get+0x20) [0x7f449789d190]
-> /usr/lib/dovecot/libdovecot.so.0(+0xfaf1f) [0x7f44978a9f1f] ->
/usr/lib/dovecot/libdovecot.so.0(+0xfafb1) [0x7f44978a9fb1] ->
/usr/lib/dovecot/libdovecot.so.0(+0x4cd20) [0x7f44977fbd20] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](+0x875a) [0x555e60d7775a] -> dovecot/dict [0 clients, 0
lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](sql_statement_query+0x42) [0x555e60d7f262] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](+0xd97f) [0x555e60d7c97f] ->
/usr/lib/dovecot/libdovecot.so.0(dict_iterate_values+0x25)
[0x7f4497868615] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](+0xa929) [0x555e60d79929] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](+0xb224) [0x555e60d7a224] -> dovecot/dict [0 clients, 0
lookups:0/0/0/0, 0 iters:0/0/0/0, 0 commits:0/0/0/0](+0xb381)
[0x555e60d7a381] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](dict_command_input+0xd9)
[0x555e60d7a579] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](+0x95b8) [0x555e60d785b8] ->
/usr/lib/dovecot/libdovecot.so.0(connection_input_default+0x15e)
[0x7f44978a16ce] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6b) [0x7f44978bfebb]
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x13b)
[0x7f44978c15cb] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x51)
[0x7f44978bff61] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x41)
[0x7f44978c0131] ->
/usr/lib/dovecot/libdovecot.so.0(master_service_run+0x14)
[0x7f4497831f74] -> dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0
iters:0/0/0/0, 0 commits:0/0/0/0](main+0x189) [0x555e60d78139] ->
/usr/lib/libc.so.6(__libc_start_main+0xd5) [0x7f44972cfb25] ->
dovecot/dict [0 clients, 0 lookups:0/0/0/0, 0 iters:0/0/0/0, 0
commits:0/0/0/0](_start+0x2e) [0x555e60d7819e]
Nov 15 12:19:19 wyvern dovecot[461]:
imap(s...@samresto.dev)<51449><+BGq2NfQM/7Pisr9>: Error: Mailbox
Trash/Processed: dict_iterate(priv/c841ad0291c27461ac670100a07d9965/)
failed: Connection closed (reply took 0.204 secs (0.204 in dict wait,
0.000 in other ioloops, 0.000 in locks))
Nov 15 12:19:19 wyvern dovecot[461]: dict(51438): Fatal: master:
service(dict): child 51438 killed with signal 6 (core dumped)
[root@wyvern ~]# dovecot -n
# 2.3.16 (7e2e900c1a): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.16 (09c29328)
# OS: Linux 5.14.16-arch1-1 x86_64 ext4
# Hostname: wyvern.simplysam.us
auth_mechanisms = plain login
dict {
lastlogin = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
metadata = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
quota_clone = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
doveadm_worker_count = 5
first_valid_gid = 5000
first_valid_uid = 5000
imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags
last_valid_gid = 5000
last_valid_uid = 5000
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
lda_original_recipient_header = X-Original-To
lmtp_client_workarounds = whitespace-before-path
lmtp_rcpt_check_quota = yes
lmtp_save_to_detail_mailbox = yes
mail_attachment_detection_options = add-flags-on-save
mail_attribute_dict = proxy::metadata
mail_gid = 5000
mail_home = /var/mail/virtual/%Ld/%Ln
mail_location = maildir:/var/mail/virtual/%Ld/%Ln
mail_plugins = " quota quota_clone mailbox_alias trash fts fts_flatcurve"
mail_uid = 5000
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy
include variables body enotify environment mailbox date index ihave duplicate
mime foreverypart extracttext spamtestplus virustest vnd.dovecot.pipe
vnd.dovecot.filter
namespace inbox {
inbox = yes
location =
mailbox Archive {
auto = subscribe
special_
Re: reconsidering my (your?) current setup
Marc, Have you heard of Rocky Linux[1]? Started by Gregory Kurtzer, founder of the CentOS project. You should give it a look. [1] https://rockylinux.org/ Regards, Elisamuel Resto > On Oct 7, 2021, at 3:31 AM, Marc wrote: > > > With redhat 'dumping' the support for centos and the availability of > containers. I thought about reconsidering my default dovecot setup. > > Since the concept of having a lts distribution that is supported by > redhat/centos is more or less 'unavailable'. I thought about using the repo > of dovecot with centos8stream. > > os > == > For now I stick with centos8stream, just because the rest is still on centos7 > support and the ceph development team is using it as a default. (And can't > yet let go of the idea this closest to professional distro ;)) > > auth uid gid os > === > I am not really convinced that storing users in mysql/postgres is a better > alternative than having linux do auth. I also think it is good to have > mailbox files stored with different uid's (no idea if this is even the case > when dovecot is using mysql/maria/postgres) > > Normally I would use a synced ldap server on the vm for authentication. But I > was thinking of using now an external ldap task from the container > environment. To de-duplicate services/data and make the environment simple. > Since rh is moving to a different ldap server, it would be good to have this > seperated in the future. > > New to me is the sssd, used nscd/nslcd for decades without issues. > > I guess the best solution is to have the os uid/gid coming from sssd, > configure sssd to have a huge timeout if the backend ldap auth is not > available. What is your thought about this? > > auth uid gid dovecot > > I do not really have an idea if I should have dovecot use ldap directly or > use this sssd pam? The advantage of using ldap directly is you could maybe > skip identifying users in the os. But maybe then tools like dovadm that > require a user are not working anymore. > From the keep it simple perspective it is probably better to use sssd. > However centos8stream and sssd are not really known to me. So any > ideas/advice about this? > > > > > > > >
Re: namespace assertion failed
Here's a core dump from a login process: --- #0 0x7f8ac70cba10 raise (libc.so.6) #1 0x7f8ac70cd13a abort (libc.so.6) #2 0x7f8ac74d839a n/a (libdovecot.so.0) #3 0x7f8ac74d849d n/a (libdovecot.so.0) #4 0x7f8ac746ae41 i_panic (libdovecot.so.0) #5 0x7f8ac77a53a8 mail_namespace_find (libdovecot-storage.so.0) #6 0x7f8ac6879e56 n/a (lib11_trash_plugin.so) #7 0x7f8ac77b1feb hook_mail_user_created (libdovecot-storage.so.0) #8 0x7f8ac77b6fb6 mail_user_init (libdovecot-storage.so.0) #9 0x7f8ac77b50c8 mail_storage_service_next (libdovecot-storage.so.0) #10 0x7f8ac77b568c mail_storage_service_lookup_next (libdovecot-storage.so.0) #11 0x004263d6 client_create_from_input (imap) #12 0x004265df n/a (imap) #13 0x7f8ac7472c6e n/a (libdovecot.so.0) #14 0x7f8ac7472efd n/a (libdovecot.so.0) #15 0x7f8ac74738bf n/a (libdovecot.so.0) #16 0x7f8ac74ed152 io_loop_call_io (libdovecot.so.0) #17 0x7f8ac74ee779 io_loop_handler_run_internal (libdovecot.so.0) #18 0x7f8ac74ed1ec io_loop_handler_run (libdovecot.so.0) #19 0x7f8ac74ed398 io_loop_run (libdovecot.so.0) #20 0x7f8ac7475223 master_service_run (libdovecot.so.0) #21 0x0040c992 main (imap) On Thu, Apr 20, 2017 at 11:29 AM, Elisamuel Resto wrote: > Hello, > > I'm trying to figure out if this is a configuration issue or an actual > bug. Dovecot does start, but if anybody tries to log in or if you run > sievec you get an assertion fail and a coredump. > > --- > sievec(root): Panic: file mail-namespace.c: line 709 > (mail_namespace_find): assertion failed: (ns != NULL) > sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2) > [0x7ff70e2133a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c429) > [0x7ff70e213429] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) > [0x7ff70e1a5e41] -> /usr/lib/dovecot/libdovecot- > storage.so.0(mail_namespace_find+0xc8) [0x7ff70e4e03a8] -> > /usr/lib/dovecot/modules/lib11_trash_plugin.so(+0x1e56) [0x7ff70d5ace56] > -> /usr/lib/dovecot/libdovecot-storage.so.0(hook_mail_user_created+0x1eb) > [0x7ff70e4ecfeb] -> /usr/lib/dovecot/libdovecot- > storage.so.0(mail_user_init+0x206) [0x7ff70e4f1fb6] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_next+0x438) > [0x7ff70e4f00c8] -> > /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup_next+0x4c) > [0x7ff70e4f068c] -> sievec(sieve_tool_init_finish+0xc1) [0x403371] -> > sievec(main+0xd2) [0x402cb2] -> /usr/lib/libc.so.6(__libc_start_main+0xf1) > [0x7ff70ddf3511] -> sievec(_start+0x2a) [0x402f3a] > Aborted (core dumped) > --- > > Coredump as follows: > --- > #0 0x7ff70de06a10 in raise () from /usr/lib/libc.so.6 > #1 0x7ff70de0813a in abort () from /usr/lib/libc.so.6 > #2 0x7ff70e21339a in ?? () from /usr/lib/dovecot/libdovecot.so.0 > #3 0x7ff70e213429 in default_fatal_handler () from > /usr/lib/dovecot/libdovecot.so.0 > #4 0x7ff70e1a5e41 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 > #5 0x7ff70e4e03a8 in mail_namespace_find () from > /usr/lib/dovecot/libdovecot-storage.so.0 > #6 0x7ff70d5ace56 in ?? () from /usr/lib/dovecot/modules/ > lib11_trash_plugin.so > #7 0x7ff70e4ecfeb in hook_mail_user_created () from > /usr/lib/dovecot/libdovecot-storage.so.0 > #8 0x7ff70e4f1fb6 in mail_user_init () from > /usr/lib/dovecot/libdovecot-storage.so.0 > #9 0x7ff70e4f00c8 in mail_storage_service_next () from > /usr/lib/dovecot/libdovecot-storage.so.0 > #10 0x7ff70e4f068c in mail_storage_service_lookup_next () from > /usr/lib/dovecot/libdovecot-storage.so.0 > #11 0x00403371 in sieve_tool_init_finish () > #12 0x00402cb2 in main () > --- > > Any help appreciated! > > -Sam >
namespace assertion failed
Hello, I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump. --- sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2) [0x7ff70e2133a2] -> /usr/lib/dovecot/libdovecot.so.0(+0x9c429) [0x7ff70e213429] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ff70e1a5e41] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_namespace_find+0xc8) [0x7ff70e4e03a8] -> /usr/lib/dovecot/modules/lib11_trash_plugin.so(+0x1e56) [0x7ff70d5ace56] -> /usr/lib/dovecot/libdovecot-storage.so.0(hook_mail_user_created+0x1eb) [0x7ff70e4ecfeb] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_user_init+0x206) [0x7ff70e4f1fb6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_next+0x438) [0x7ff70e4f00c8] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_storage_service_lookup_next+0x4c) [0x7ff70e4f068c] -> sievec(sieve_tool_init_finish+0xc1) [0x403371] -> sievec(main+0xd2) [0x402cb2] -> /usr/lib/libc.so.6(__libc_start_main+0xf1) [0x7ff70ddf3511] -> sievec(_start+0x2a) [0x402f3a] Aborted (core dumped) --- Coredump as follows: --- #0 0x7ff70de06a10 in raise () from /usr/lib/libc.so.6 #1 0x7ff70de0813a in abort () from /usr/lib/libc.so.6 #2 0x7ff70e21339a in ?? () from /usr/lib/dovecot/libdovecot.so.0 #3 0x7ff70e213429 in default_fatal_handler () from /usr/lib/dovecot/libdovecot.so.0 #4 0x7ff70e1a5e41 in i_panic () from /usr/lib/dovecot/libdovecot.so.0 #5 0x7ff70e4e03a8 in mail_namespace_find () from /usr/lib/dovecot/libdovecot-storage.so.0 #6 0x7ff70d5ace56 in ?? () from /usr/lib/dovecot/modules/lib11_trash_plugin.so #7 0x7ff70e4ecfeb in hook_mail_user_created () from /usr/lib/dovecot/libdovecot-storage.so.0 #8 0x7ff70e4f1fb6 in mail_user_init () from /usr/lib/dovecot/libdovecot-storage.so.0 #9 0x7ff70e4f00c8 in mail_storage_service_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #10 0x7ff70e4f068c in mail_storage_service_lookup_next () from /usr/lib/dovecot/libdovecot-storage.so.0 #11 0x00403371 in sieve_tool_init_finish () #12 0x00402cb2 in main () --- Any help appreciated! -Sam
Re: [Dovecot] Build failure building dbox and gnutls
Figure that as-per the docs, it is now called "sdbox" -- well, that should be one issue down, I assume, but building specifically by sdbox (tried before) or dbox fails, so that means the call to build it also changed? both should work, in my opinion. Now its just the GnuTLS issue. -- Elisamuel Rest http://www.simplysam.us - Simply Sam Blog Elisamuel Resto wrote: G'Day: I actually did that to get it up and running (build without the "--with-storages" flag), and it did not build: [ere...@hanjin ~]$ dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: cydir maildir mbox mdbox raw sdbox shared SQL drivers: sqlite Passdb: checkpassword pam passwd passwd-file shadow sql Userdb: checkpassword nss passwd prefetch passwd-file sql
Re: [Dovecot] Build failure building dbox and gnutls
G'Day: I actually did that to get it up and running (build without the "--with-storages" flag), and it did not build: [ere...@hanjin ~]$ dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: cydir maildir mbox mdbox raw sdbox shared SQL drivers: sqlite Passdb: checkpassword pam passwd passwd-file shadow sql Userdb: checkpassword nss passwd prefetch passwd-file sql -- Elisamuel Resto http://www.simplysam.us - Simply Sam Blog Marcus Rueckert wrote: On 2010-08-22 16:17:01 -0400, Elisamuel Resto wrote: --with-storages=maildir,mbox,dbox,mdbox remove that, the default is to build all storage engines
[Dovecot] Build failure building dbox and gnutls
Hello! I'm having two issues building dovecot, one is with dbox storage, and another building gnutls as the SSL backend (builds fine with openssl). Software versions are Dovecot v2.0.0, GnuTLS 2.8.6 and OpenSSL 1.0.0a Configure: ./configure --prefix=/usr --sysconfdir=/etc/dovecot --localstatedir=/var --libexecdir=/usr/lib --with-moduledir=/usr/lib/dovecot/modules --with-zlib --with-sqlite --with-ssl=openssl --with-ssldir=/etc/ssl --with-gssapi --with-pam --with-bzlib --with-docs --without-mysql --without-vpopmail --without-sia --without-bsdauth --with-libcap --with-ioloop=epoll --with-storages=maildir,mbox,dbox,mdbox For the dbox build error, the log states: libdovecot-storage.so: undefined reference to `dbox_storage' Configure: http://pastie.org/1106301 - Make: http://pastie.org/private/qtt76kxomhmwqwii20oroq Configure: ./configure --prefix=/usr --sysconfdir=/etc/dovecot --localstatedir=/var --libexecdir=/usr/lib --with-moduledir=/usr/lib/dovecot/modules --with-zlib --with-sqlite --with-ssl=gnutls --with-ssldir=/etc/ssl --with-gssapi --with-pam --with-bzlib --with-docs --without-mysql --without-vpopmail --without-sia --without-bsdauth --with-libcap --with-ioloop=epoll For the gnutls build error, the log states quite a few errors, so see the linked logs. Configure: http://pastie.org/1108356 - Make: http://pastie.org/private/dxmmmopnodptut77o6fx2g -- Elisamuel Resto http://www.simplysam.us/ - Simply Sam Blog
Re: [Dovecot] antispam plugin claims "antispam signature not found"
On Sunday 09 November 2008, Jakob Curdes wrote:
> > plugins {
> > antispam_trash = trash;Trash;Deleted Items
> > antispam_spam = SPAM;Spam;Junk
> > antispam_dspam_args = --client;--deliver=;--user;%u
>
> I am using dspam in a different setup; I run it under amavis so the user
> is always the user amavis. I don't run a daemon so --client makes no
> sense. What does "deliver=" do? Is that the same as
> "deliver=innocent,spam" ?
>
> I think it must be related to permissions in some way but I do not see
> how. I would like to debug it further but am no C programmer. I cannot
> see why it is not able to extract the signature.
>
> JC
Yes, you are correct about not needing '--client' in your case. '--deliver='
means
deliver nothing, just process it. Since I don't use quarantine on my setup, and
the message is existent already in IMAP, there is no need to deliver anything.
--
Elisamuel Resto <[EMAIL PROTECTED]>
Source Mage General Guru / http://sourcemage.org
GPG ID: 18615F19/1024D / http://simplysam.us
Re: [Dovecot] antispam plugin claims "antispam signature not found"
On Sunday 09 November 2008, Jakob Curdes wrote:
> Some weeks ago I asked a question on the antispam plugin; obviously
> nobody could help me. I just worked on it again but made no progress.
> Is actually anybody out there running the antispam plugin with dspam?? I
> am willing to write a Wiki page for configuring this as soon as I get it
> to work.
>
> The problem still remains and the outlines are:
>
> - antispam plugin is compiled, configured for dspam and debug is
> switched on.
> - plugin starts with dovecot and throws debug info to /var/log/messages
> (debug logging activated via syslog)
> - as soon as I move a message into the spam folder it gives an error
> message saying "antispam signature not found"
>
> I checked that the given location for the dspam executable is correct,
> that the user executing it (dovecot?) is actually able to execute dspam
> and that dspam trusts this user. I triple-checked that the signature is
> configured correctly. I have lines like
>
> X-DSPAM-Signature: 1,49084a24139132188715614
>
> in all mails and my plugin conf says
>
> # mail signature (used with any backend requiring a signature)
>
> antispam_signature = X-DSPAM-Signature
>
> I do not get any error messages in the debug output, only dovecot says:
> dovecot: Nov 09 13:19:40 Error: IMAP(): Next message unexpectedly
> lost from 49
>
> Any ideas? How can I get a more specific debugging for the signature? Or
> might this still be a permission problem?
>
> Here is my plugin config:
>
> # antispam plugin - learn spam from folder
> antispam_signature = X-DSPAM-Signature
> antispam_spam = spam
> antispam_dspam_binary = /usr/local/bin/dspam
>
>
> Regards, Jakob
Personally, I don't set anything but the spam folder, trash folder names and
the
args to pass to the dspam executable. It works here flawlessly.
plugins {
antispam_trash = trash;Trash;Deleted Items
antispam_spam = SPAM;Spam;Junk
antispam_dspam_args = --client;--deliver=;--user;%u
}
--
Elisamuel Resto <[EMAIL PROTECTED]>
Source Mage Tome Lead / http://sourcemage.org
GPG ID: 18615F19/1024D / http://simplysam.us
Re: [Dovecot] Switching Servers now can't retrieve mail
On Fri, 10 Oct 2008 10:52:22 -0700, [EMAIL PROTECTED] wrote: > Started with a new conf file and now it's working. I guess there is a > configuration difference between 1.0.14 and 1.1.2 For future reference: http://wiki.dovecot.org/Upgrading/1.1 -- Elisamuel Resto | GPG: 18615F19 [EMAIL PROTECTED] | Source Mage GNU/Linux Tome Lead http://simplysam.us/ | http://www.sourcemage.org/ signature.asc Description: PGP signature
Re: [Dovecot] Something weird happening...
On Thu, 09 Oct 2008 11:30:43 -0400, Bill Cole wrote: > Timo Sirainen wrote: > > On Oct 9, 2008, at 12:43 AM, Bill Cole wrote: > > > >> Claudio Prono wrote: > >>> Very strange, i have tryied to chmod 666 all log files, like that: > >>> -rw-rw-rw- 1 root root 681 Oct 8 11:08 dovecot-err.log > >>> -rw-rw-rw- 1 root root 1039 Oct 8 11:02 dovecot-inf.log > >>> (Is terrible i know, but only a test) > >> > >> I think you should follow the suggestion already provided: > >> > >> >>> You should chown dovecot /var/log/dovecot-*.log > > > > dovecot? In the preferred configuration only login processes run using > > dovecot user, and the dovecot user has access to nothing. Login > > processes don't need to access log files. > > An excellent point! > > I guess the better alternatives to 666 logs would be > > 1. use syslog > 2. split deliver logs off to their own files > 3. Depending on how deliver is being run, chown the logs to the user that > runs deliver or put all of the uid's it might run as (i.e. all mail users) > into a group and chgrp the logs to that group with 660 permissions. I prefer syslog and then doing any particular routing of information by rsyslog (my syslog daemon), that solves any permission issues with the logs. -- Elisamuel Resto | GPG: 18615F19 [EMAIL PROTECTED] | Source Mage GNU/Linux Tome Lead http://simplysam.us/ | http://www.sourcemage.org/ signature.asc Description: PGP signature
Re: [Dovecot] Something weird happening...
On Wed, 08 Oct 2008 10:44:25 +0200, Claudio Prono wrote: > Hi to all, > > I use Dovecot dovecot11-1.1.3-5.1 from OpenSuSE 11, when i send a mail > from the logs i read: > > Oct 8 10:36:31 mail postfix/pipe[17934]: A360A851: > to=<[EMAIL PROTECTED]>, relay=dovecot, delay=0.22, > delays=0.18/0/0/0.04, dsn=4.3.0, status=deferred (temporary failure. > Command output: Can't open log file /var/log/dovecot-err.log: Permission > denied ) > > But, log files seems ok: > > -rw--- 1 777 root 56 Oct 8 10:35 dovecot-err.log > -rw--- 1 777 root 302 Oct 8 10:35 dovecot-inf.log According to the below output, the above output is wrong. User with UID 777 does not exist, hence, the Permission denied. You should chown dovecot /var/log/dovecot-*.log > Also processess seems right: > > root 17965 0.0 0.0 2052 584 ?Ss 10:35 0:00 > /usr/sbin/dovecot > root 17966 0.0 0.2 8564 2172 ?S10:35 0:00 > dovecot-auth > root 17967 0.0 0.2 8564 2356 ?S10:35 0:00 > dovecot-auth -w > dovecot 17969 0.0 0.1 3476 1572 ?S10:36 0:00 pop3-login > dovecot 17970 0.0 0.1 3476 1572 ?S10:36 0:00 pop3-login > dovecot 17971 0.0 0.1 3476 1572 ?S10:36 0:00 pop3-login > dovecot 17972 0.0 0.1 3484 1584 ?S10:36 0:00 imap-login > dovecot 17973 0.0 0.1 3484 1584 ?S10:36 0:00 imap-login > dovecot 17974 0.0 0.1 3484 1584 ?S10:36 0:00 imap-login > -- Elisamuel Resto | GPG: 18615F19 [EMAIL PROTECTED] | Source Mage GNU/Linux Tome Lead http://simplysam.us/ | http://www.sourcemage.org/ signature.asc Description: PGP signature
[Dovecot] Dovecot v1.0.3 -> Sieve "redirect" command returning Sendmail exit status 75
Hello! My local setup here is Exim 4.68, DSPAM 3.8.0 and Dovecot 1.0.5. Entirely on MySQL tables for virtual hosts and authentication. Dovecot does the authentication for Exim. What I am having problems with, is a simple sieve script to redirect a message that matches the "X-DSPAM-Result" header as "Spam" to another email address. When this rule matches, deliver returns in the log (which is attached) that "Sendmail process terminated abnormally, exit status: 75" What would cause this, and how can I resolve it? Thanks. -- Elisamuel Resto <[EMAIL PROTECTED]> ID: 0x18615F19 / FP: B66D 1C2A E8EE B922 1D9C D98F D2D5 FB61 1861 5F19 exim[30998]: 2007-10-18 22:26:44 1IihZU-00083y-90 <= [EMAIL PROTECTED] H=mx.isp.net [1.2.3.4] P=esmtp S=1658 [EMAIL PROTECTED] T="redirect me" exim[31003]: 2007-10-18 22:27:00 1IihZU-000843-Gb <= [EMAIL PROTECTED] U=exim P=spam-scanned S=2139 [EMAIL PROTECTED] T="redirect me" deliver([EMAIL PROTECTED]): Sendmail process terminated abnormally, exit status 75 deliver([EMAIL PROTECTED]): sieve runtime error: Redirect: Error sending mail deliver([EMAIL PROTECTED]): sieve_execute_bytecode(/srv/mail/local.net/me/.dovecot.sievec) failed deliver([EMAIL PROTECTED]): msgid=<[EMAIL PROTECTED]>: saved mail to INBOX exim[31013]: 2007-10-18 22:27:04 1IihZU-000843-Gb => /srv/mail/local.net/me <[EMAIL PROTECTED]> R=virtual_domains T=virtual_delivery exim[31013]: 2007-10-18 22:27:04 1IihZU-000843-Gb Completed exim[31000]: 2007-10-18 22:27:04 1IihZU-00083y-90 => me <[EMAIL PROTECTED]> R=dspam_router T=dspam_spamcheck exim[31000]: 2007-10-18 22:27:04 1IihZU-00083y-90 Completed pgpIhjqxIhAN1.pgp Description: PGP signature
