Re: Managesieve stopped working - Undefined symbol "i_stream_read_memarea"
On 02-08-2018 15:29, Aki Tuomi wrote: On 02 August 2018 at 16:22 Henrik Larsson wrote: On 02-08-2018 15:16, Aki Tuomi wrote: >> On 02 August 2018 at 16:08 Henrik Larsson >> wrote: >> >> >> On 15-07-2018 11:42, Henrik Larsson wrote: >> > After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, >> > managesieve stopped working. >> > >> > I'm using FreeBSD ports tree, to build these. Only domains have been >> > modified in below output. >> > >> > A FreeBSD bug report have also been created. But I'm not sure if this >> > is FreeBSD ports related or Dovecot/Pigeonhole related: >> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228067 >> > >> >> [Removed output from "uname", "pkg version", "dmesg" and "dovecot -n" >> from my original post] >> >> Anyone able to give me some input how to solve this? >> >> Best regards >> Henrik Larsson >> > > Hi! > > i_stream_read_memarea was added in v2.3.0. > > Can you try uninstalling /usr/local/libexec/dovecot/managesieve, > recompiling pigeonhole 0.5.2 and reinstalling it? > > Aki Re-compiled today, same error. /usr/local/libexec/dovecot # ll managesieve -rwxr-xr-x 1 root wheel 64664 2 aug 14:50 managesieve* From Dovecot log: Aug 02 15:09:10 master: Info: Dovecot v2.3.2.1 (0719df592) starting up for imap, pop3, lmtp, sieve Aug 02 15:09:10 config: Error: /usr/local/libexec/dovecot/managesieve: Undefined symbol "i_stream_read_memarea" Aug 02 15:09:10 config: Error: managesieve-login: dump-capability process returned 1 /Henrik Can you do ldd /usr/local/libexec/dovecot/managesieve and make sure it points to correct libdovecot.so? Aki ldd showed that managesieve was linked to "libdovecot.so" in "/usr/local/lib/compat/pkg". /usr/local/lib/compat/pkg # ll -rwxr-xr-x 1 root wheel 164080 28 mar 14:50 libdovecot-fts.so.0* -rwxr-xr-x 1 root wheel46016 28 mar 14:50 libdovecot-lda.so.0* -rwxr-xr-x 1 root wheel 122808 28 mar 14:50 libdovecot-login.so.0* -rwxr-xr-x 1 root wheel45728 28 mar 14:50 libdovecot-sql.so.0* -rwxr-xr-x 1 root wheel 1282080 28 mar 14:50 libdovecot-storage.so.0* -rwxr-xr-x 1 root wheel 1203968 28 mar 14:50 libdovecot.so.0* I removed these and recompiled. Now it is indeed working again. I'm not sure how I ended up in this situation. Thank you for the help. /Henrik
Re: Managesieve stopped working - Undefined symbol "i_stream_read_memarea"
On 02-08-2018 15:16, Aki Tuomi wrote: On 02 August 2018 at 16:08 Henrik Larsson wrote: On 15-07-2018 11:42, Henrik Larsson wrote: > After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, > managesieve stopped working. > > I'm using FreeBSD ports tree, to build these. Only domains have been > modified in below output. > > A FreeBSD bug report have also been created. But I'm not sure if this > is FreeBSD ports related or Dovecot/Pigeonhole related: > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228067 > [Removed output from "uname", "pkg version", "dmesg" and "dovecot -n" from my original post] Anyone able to give me some input how to solve this? Best regards Henrik Larsson Hi! i_stream_read_memarea was added in v2.3.0. Can you try uninstalling /usr/local/libexec/dovecot/managesieve, recompiling pigeonhole 0.5.2 and reinstalling it? Aki Re-compiled today, same error. /usr/local/libexec/dovecot # ll managesieve -rwxr-xr-x 1 root wheel 64664 2 aug 14:50 managesieve* From Dovecot log: Aug 02 15:09:10 master: Info: Dovecot v2.3.2.1 (0719df592) starting up for imap, pop3, lmtp, sieve Aug 02 15:09:10 config: Error: /usr/local/libexec/dovecot/managesieve: Undefined symbol "i_stream_read_memarea" Aug 02 15:09:10 config: Error: managesieve-login: dump-capability process returned 1 /Henrik
Re: Managesieve stopped working - Undefined symbol "i_stream_read_memarea"
On 15-07-2018 11:42, Henrik Larsson wrote: After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, managesieve stopped working. I'm using FreeBSD ports tree, to build these. Only domains have been modified in below output. A FreeBSD bug report have also been created. But I'm not sure if this is FreeBSD ports related or Dovecot/Pigeonhole related: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228067 [Removed output from "uname", "pkg version", "dmesg" and "dovecot -n" from my original post] Anyone able to give me some input how to solve this? Best regards Henrik Larsson
Managesieve stopped working - Undefined symbol "i_stream_read_memarea"
After upgrading Dovecot to 2.3.2.1 and Pigeonhole to 0.5.2, managesieve
stopped working.
I'm using FreeBSD ports tree, to build these. Only domains have been
modified in below output.
A FreeBSD bug report have also been created. But I'm not sure if this is
FreeBSD ports related or Dovecot/Pigeonhole related:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228067
%uname -a
FreeBSD 10.4-RELEASE-p9 FreeBSD 10.4-RELEASE-p9 #0: Sat Jul 14 22:38:37
CEST 2018 /usr/obj/usr/src/sys/GENERIC amd64
%pkg version -v
dovecot-2.3.2.1= up-to-date with index
dovecot-pigeonhole-0.5.2_2 = up-to-date with index
%dmesg -a
/usr/local/libexec/dovecot/managesieve: Undefined symbol
"i_stream_read_memarea"
doveconf: Error: managesieve-login: dump-capability process returned 1
% dovecot -n
# 2.3.2.1 (0719df592): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.2 (7704de5e)
/usr/local/libexec/dovecot/managesieve: Undefined symbol
"i_stream_read_memarea"
doveconf: Error: managesieve-login: dump-capability process returned 1
# OS: FreeBSD 10.4-RELEASE-p9 amd64
# Hostname: mail.example.com
auth_mechanisms = plain login
first_valid_uid = 125
hostname = mail.example.com
listen = *
log_path = /var/log/dovecot
mail_plugins = zlib
mail_privileged_group = postfix
mail_temp_dir = /var/db/dovecot
namespace compat {
hidden = yes
inbox = no
list = no
location =
prefix = INBOX.
separator = .
type = private
}
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox "Sent Items" {
special_use = \Sent
}
mailbox Spam {
special_use = \Junk
}
mailbox Trash {
special_use = \Trash
}
prefix =
separator = .
type = private
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
postmaster_address = postmas...@example.com
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /home/mail/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
}
}
service lmtp {
executable = lmtp -L
unix_listener /home/mail/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert =
[Dovecot] Permissions for mail_temp_dir directory
I recently upgraded from 2.1.16 to 2.2.2 and started to receive the
following errors:
imap(hen...@example.com): Error:
stat(/var/db/dovecot/dovecot.imap.mail.example.com.16128.3209d13f842955c2)
failed: Permission denied
imap(hen...@example.com): Error: Temp file creation to
/var/db/dovecot/dovecot.imap.mail.example.com.16128. failed: Permission
denied
imap(hen...@example.com): Error:
stat(/var/db/dovecot/dovecot.imap.mail.example.com.16501.0ddff1dc93cdbe6a)
failed: Permission denied
imap(hen...@example.com): Error: Temp file creation to
/var/db/dovecot/dovecot.imap.mail.example.com.16501. failed: Permission
denied
I didn't have these before the upgrade. The current permissions for the
/var/db/dovecot directory is root:wheel 755.
What would be the correct permissions for the mail_temp_dir directory?
doveconf -n output
--cut--
# 2.2.2: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.3-RELEASE-p3 amd64
auth_mechanisms = plain login digest-md5 cram-md5
first_valid_uid = 125
hostname = mail.example.com
listen = *
log_path = /var/log/dovecot
mail_plugins = zlib
mail_privileged_group = postfix
mail_temp_dir = /var/db/dovecot
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 ihave
namespace {
inbox = yes
location =
prefix =
separator = .
type = private
}
namespace {
hidden = yes
inbox = no
list = no
location =
prefix = INBOX.
separator = .
type = private
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
postmaster_address = postmas...@example.com
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /home/mail/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
}
}
service lmtp {
executable = lmtp -L
unix_listener /home/mail/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert = /etc/ssl/mail.example.com-chained.crt
ssl_key = /etc/ssl/mail.example.com.key
userdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lmtp {
log_path = /var/log/dovecot-deliver
mail_plugins = zlib sieve
}
protocol lda {
mail_plugins = zlib sieve
}
protocol imap {
mail_plugins = zlib imap_zlib
}
--cut--
Best regards
Henrik Larsson
Re: [Dovecot] 2.1.4 Corrupted squat uidlist
Just to let you know, 2.1.4 didn't solve this either.
If you need any futher info to get this solved, please let me know.
Best regards
Henrik Larsson
This problem is still showing up every day in the logs.
I tried to delete the dovecot.index.search and
dovecot.index.search.uids files for all users, but the errors are
still there after a re-build of the search index with
/usr/local/bin/doveadm search -A TEXT xyzabczzz.
If you need any further details, please let me know.
Best regards
Henrik Larsson
On 15-04-2012 10:42, Henrik Larsson wrote:
On 27-03-2012 08:57, Luca Palazzo wrote:
Hi Timo and All,
after upgrading to 2.1.2 i'm getting a lot of these messages:
Error: Corrupted squat uidlist file XX wrong indexid
After an upgrade to 2.1.3 i see this as well. Any thoughts?
Apr 15 03:43:43 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
Apr 15 06:30:27 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
Apr 15 07:43:55 pop3(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
Apr 15 09:00:01 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
# doveconf -n
# 2.1.3: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.2-STABLE amd64
auth_mechanisms = plain login digest-md5 cram-md5
first_valid_uid = 125
listen = *
log_path = /var/log/dovecot
mail_plugins = fts fts_squat zlib
mail_privileged_group = postfix
mail_temp_dir = /var/db/dovecot
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 ihave
namespace {
inbox = yes
location =
prefix =
separator = .
type = private
}
namespace {
hidden = yes
inbox = no
list = no
location =
prefix = INBOX.
separator = .
type = private
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /home/mail/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
}
}
service lmtp {
executable = lmtp -L
unix_listener /home/mail/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert = /etc/ssl/mail-chained.crt
ssl_key = /etc/ssl/mail.key
userdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lmtp {
log_path = /var/log/dovecot-deliver
mail_plugins = fts fts_squat zlib sieve
}
protocol lda {
mail_plugins = fts fts_squat zlib sieve
}
protocol imap {
mail_plugins = fts fts_squat zlib imap_zlib
}
Best regards
Henrik Larsson
Re: [Dovecot] 2.1.3 Corrupted squat uidlist
So the doveadm search itself succeeds without errors, but if you immediately do another doveadm search it fails? Or do you need to do something else also in the middle? I couldn't reproduce this with a few tests. Is there any way to produce debug logs that will show what goes wrong. It is consistent in such a way that I will have several errors within a 24 hour period. I will be willing to add code and rebuild dovecot to produce the logs you need. Best regards Henrik Larsson
Re: [Dovecot] 2.1.3 Corrupted squat uidlist
This problem is still showing up every day in the logs.
I tried to delete the dovecot.index.search and
dovecot.index.search.uids files for all users, but the errors are still
there after a re-build of the search index with /usr/local/bin/doveadm
search -A TEXT xyzabczzz.
If you need any further details, please let me know.
Best regards
Henrik Larsson
On 15-04-2012 10:42, Henrik Larsson wrote:
On 27-03-2012 08:57, Luca Palazzo wrote:
Hi Timo and All,
after upgrading to 2.1.2 i'm getting a lot of these messages:
Error: Corrupted squat uidlist file XX wrong indexid
After an upgrade to 2.1.3 i see this as well. Any thoughts?
Apr 15 03:43:43 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
Apr 15 06:30:27 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
Apr 15 07:43:55 pop3(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
Apr 15 09:00:01 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong
indexid
# doveconf -n
# 2.1.3: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.2-STABLE amd64
auth_mechanisms = plain login digest-md5 cram-md5
first_valid_uid = 125
listen = *
log_path = /var/log/dovecot
mail_plugins = fts fts_squat zlib
mail_privileged_group = postfix
mail_temp_dir = /var/db/dovecot
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 ihave
namespace {
inbox = yes
location =
prefix =
separator = .
type = private
}
namespace {
hidden = yes
inbox = no
list = no
location =
prefix = INBOX.
separator = .
type = private
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /home/mail/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
}
}
service lmtp {
executable = lmtp -L
unix_listener /home/mail/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert = /etc/ssl/mail-chained.crt
ssl_key = /etc/ssl/mail.key
userdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lmtp {
log_path = /var/log/dovecot-deliver
mail_plugins = fts fts_squat zlib sieve
}
protocol lda {
mail_plugins = fts fts_squat zlib sieve
}
protocol imap {
mail_plugins = fts fts_squat zlib imap_zlib
}
Best regards
Henrik Larsson
Re: [Dovecot] 2.1.2 Corrupted squat uidlist
On 27-03-2012 08:57, Luca Palazzo wrote:
Hi Timo and All,
after upgrading to 2.1.2 i'm getting a lot of these messages:
Error: Corrupted squat uidlist file XX wrong indexid
After an upgrade to 2.1.3 i see this as well. Any thoughts?
Apr 15 03:43:43 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong indexid
Apr 15 06:30:27 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong indexid
Apr 15 07:43:55 pop3(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong indexid
Apr 15 09:00:01 imap(): Error: Corrupted squat uidlist file
/home/mail////Maildir/dovecot.index.search.uids: wrong indexid
# doveconf -n
# 2.1.3: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.2-STABLE amd64
auth_mechanisms = plain login digest-md5 cram-md5
first_valid_uid = 125
listen = *
log_path = /var/log/dovecot
mail_plugins = fts fts_squat zlib
mail_privileged_group = postfix
mail_temp_dir = /var/db/dovecot
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 ihave
namespace {
inbox = yes
location =
prefix =
separator = .
type = private
}
namespace {
hidden = yes
inbox = no
list = no
location =
prefix = INBOX.
separator = .
type = private
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /home/mail/postfix/private/dovecot-auth {
group = postfix
mode = 0660
user = postfix
}
}
service lmtp {
executable = lmtp -L
unix_listener /home/mail/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert = /etc/ssl/mail-chained.crt
ssl_key = /etc/ssl/mail.key
userdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lmtp {
log_path = /var/log/dovecot-deliver
mail_plugins = fts fts_squat zlib sieve
}
protocol lda {
mail_plugins = fts fts_squat zlib sieve
}
protocol imap {
mail_plugins = fts fts_squat zlib imap_zlib
}
Best regards
Henrik Larsson
Re: [Dovecot] doveadm log reopen don't reopen separate lmtp log
I still see the issue below. Is there anyone running separate LMTP
logging that could check if they experience the same issue?
Best regards
Henrik Larsson
Original Message
Subject: doveadm log reopen don't reopen separate lmtp log
Date: Sun, 25 Sep 2011 00:23:49 +0200
From: Henrik Larsson dovecot-u...@spambox.dk
To: dovecot@dovecot.org
Dear all
I have setup separate pop3/imap log /var/log/dovecot and lmtp
delivery log /var/log/dovecot-deliver.
After rotating logfiles, i run doveadm log reopen. I see that my
pop3/imap log /var/log/dovecot is used straight away, but my lmpt log
/var/log/dovecot-deliver isn't used at first. After some time, usually
a few minutes, logs are being written to this file anyway. But if I
compare this to my maillog, it misses some deliveries just after the log
rotation.
Is there any problems with this configuration that should be corrected?
--cut--
# doveconf -n
# 2.0.15: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.2-STABLE amd64
auth_mechanisms = plain login digest-md5 cram-md5
first_valid_uid = 125
hostname = mail.larsson.it
listen = *
log_path = /var/log/dovecot
mail_plugins = fts fts_squat zlib
mail_privileged_group = postfix
mail_temp_dir = /var/db/dovecot
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
namespace {
inbox = yes
location =
prefix =
separator = .
type = private
}
namespace {
hidden = yes
inbox = no
list = no
location =
prefix = INBOX.
separator = .
type = private
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /home/mail/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
}
}
service lmtp {
executable = lmtp -L
unix_listener /home/mail/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert = /etc/ssl/mail-chained.crt
ssl_key = /etc/ssl/mail.key
userdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lmtp {
log_path = /var/log/dovecot-deliver
mail_plugins = fts fts_squat zlib sieve
}
protocol lda {
mail_plugins = fts fts_squat zlib sieve
}
protocol imap {
mail_plugins = fts fts_squat zlib imap_zlib
}
--cut--
Best regards
Henrik Larsson
Re: [Dovecot] doveadm log reopen don't reopen separate lmtp log
The problem isn't lmtp itself, it's that you're using -L parameter, which causes LMTP processes to open the log files directly. Just to be sure, isn't this the only way to have a separate LMTP log files? The only way to reopen the log files is to restart those LMTP processes. doveadm reload should do it. Thanks, I will try this. Best regards Henrik Larsson
[Dovecot] doveadm log reopen don't reopen seperate lmtp log
Dear all
I have setup separate pop3/imap log /var/log/dovecot and lmtp delivery
log /var/log/dovecot-deliver.
After rotating logfiles, i run doveadm log reopen. I see that my
pop3/imap log /var/log/dovecot is used straight away, but my lmpt log
/var/log/dovecot-deliver isn't used at first. After some time, usually
a few minutes, logs are being written to this file anyway. But if I
compare this to my maillog, it misses some deliveries just after the log
rotation.
Is there any problems with this configuration that should be corrected?
--cut--
# doveconf -n
# 2.0.15: /usr/local/etc/dovecot/dovecot.conf
# OS: FreeBSD 8.2-STABLE amd64
auth_mechanisms = plain login digest-md5 cram-md5
first_valid_uid = 125
hostname = mail.larsson.it
listen = *
log_path = /var/log/dovecot
mail_plugins = fts fts_squat zlib
mail_privileged_group = postfix
mail_temp_dir = /var/db/dovecot
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
namespace {
inbox = yes
location =
prefix =
separator = .
type = private
}
namespace {
hidden = yes
inbox = no
list = no
location =
prefix = INBOX.
separator = .
type = private
}
passdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
fts = squat
fts_squat = partial=4 full=10
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp sieve
service auth-worker {
user = $default_internal_user
}
service auth {
unix_listener /home/mail/postfix/private/auth {
group = postfix
mode = 0666
user = postfix
}
}
service lmtp {
executable = lmtp -L
unix_listener /home/mail/postfix/private/dovecot-lmtp {
group = postfix
mode = 0660
user = postfix
}
}
ssl_cert = /etc/ssl/mail-chained.crt
ssl_key = /etc/ssl/mail.key
userdb {
args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lmtp {
log_path = /var/log/dovecot-deliver
mail_plugins = fts fts_squat zlib sieve
}
protocol lda {
mail_plugins = fts fts_squat zlib sieve
}
protocol imap {
mail_plugins = fts fts_squat zlib imap_zlib
}
--cut--
Best regards
Henrik Larsson
Re: [Dovecot] OT: DNS-Problem with Mailnglist-Server
which leads to postfix complaining: May 30 13:28:39 mail postfix/smtpd[25014]: NOQUEUE: reject_warning: RCPT from unknown[193.210.130.67]: 450 4.7.1 Client host rejected: cannot find your reverse hostname, [193.210.130.67]; from=dovecot-boun...@dovecot.org to=ha...@hannsmattes.de proto=ESMTP helo=dovecot.org If your are checking for reverse hostname and won't accept e-mails if this is not present you will reject a lot of legitimate mail.
Re: [Dovecot] Dovecot stops with Fatal: kevent(): Invalid argument
Is there a problem adding a patch like this to the stable code? Annoying to add ugly debug code for a problem that happens so rarely.. But what are the alternatives? Best regards Henrik Larsson
[Dovecot] IMAP COMPRESS not announced while using imap_zlib plugin
I'm trying to enable the IMAP COMPRESS plugin listed here:
http://wiki2.dovecot.org/Plugins/Compress
I have added zlib globally and imap_zlib to the imap protocol.
This is the output from doveconf -n with regards to mail_plugins:
--cut--
mail_plugins = zlib
protocol imap {
mail_plugins = zlib imap_zlib
}
--cut
But it seem like the feature is not announced when connecting to the
IMAP server:
* OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE
IDLE STARTTLS LOGINDISABLED AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready.
I would expect something like COMPRESS=DEFLATE.
I haven't enabled any compression for the Maildir files, zlib_save_level
and zlib_save is not set. Does IMAP COMPRESS only work if the mailbox is
compressed?
Best regards
Henrik Larsson
Re: [Dovecot] IMAP COMPRESS not announced while using imap_zlib plugin
But it seem like the feature is not announced when connecting to the IMAP server: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. Log in first. Thank you Timo, I see it is listed after login. The reason why I didn't check this was the explanation in the RFC. Here the feature is announced before logging in: --cut-- The following example illustrates how commands and responses are compressed during a simple login sequence: S: * OK [CAPABILITY IMAP4REV1 STARTTLS COMPRESS=DEFLATE] C: a starttls S: a OK TLS active --cut-- Is there any way I can see in the logs if IMAP COMPRESS is used? Best regards Henrik Larsson
Re: [Dovecot] Dovecot stops with Fatal: kevent(): Invalid argument
That patch doesn't fix anything. It only changes the error message to be more informative so I could figure out what is causing it. If you haven't seen any more errors, it's just a coincidence. I have for some reason not seen the error since applying the above patch. But wouldn't it make sense to include the patch in the stable release so others can give input in the rare case they experience the same issue? At least until the issue has been resolved. I don't say that this is a Dovecot issue, and I admit that it have to be a rare case, but when two independent people experience the same error, there have to be a problem somewhere. Is there a problem adding a patch like this to the stable code? Should I ask the FreeBSD dovecot2 port maintainer to add it to the FreeBSD port instead? Best regards Henrik Larsson
Re: [Dovecot] Dovecot stops with Fatal: kevent(): Invalid argument
Dovecot stops with the following logged: - master: Fatal: kevent(): Invalid argument I have found that a diff was created for src/lib/ioloop-kqueue.c for a similar issue: http://dovecot.org/pipermail/dovecot/2010-November/054855.html I have patched my system with this and haven't seen the problem since, but I don't know if this is a coincidence. Could you please explain if the diff should actually fix anything or just add some more logging in case it stops again? That patch doesn't fix anything. It only changes the error message to be more informative so I could figure out what is causing it. If you haven't seen any more errors, it's just a coincidence. I have for some reason not seen the error since applying the above patch. But wouldn't it make sense to include the patch in the stable release so others can give input in the rare case they experience the same issue? At least until the issue has been resolved. I don't say that this is a Dovecot issue, and I admit that it have to be a rare case, but when two independent people experience the same error, there have to be a problem somewhere. Best regards Henrik Larsson
Re: [Dovecot] Dovecot stops with Fatal: kevent(): Invalid argument
# 2.0.11: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-STABLE amd64 Dovecot stops with the following logged: - master: Fatal: kevent(): Invalid argument I have found that a diff was created for src/lib/ioloop-kqueue.c for a similar issue: http://dovecot.org/pipermail/dovecot/2010-November/054855.html I have patched my system with this and haven't seen the problem since, but I don't know if this is a coincidence. Could you please explain if the diff should actually fix anything or just add some more logging in case it stops again? And if this is a fix, why isn't it included in 2.0.11, I think it was created for 2.0.6. Best regards Henrik Larsson
[Dovecot] Dovecot stops with Fatal: kevent(): Invalid argument
# 2.0.11: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 8.2-STABLE amd64 Dovecot stops with the following logged: - master: Fatal: kevent(): Invalid argument I have found that a diff was created for src/lib/ioloop-kqueue.c for a similar issue: http://dovecot.org/pipermail/dovecot/2010-November/054855.html I have patched my system with this and haven't seen the problem since, but I don't know if this is a coincidence. Could you please explain if the diff should actually fix anything or just add some more logging in case it stops again? Best regards Henrik Larsson
