Replication warnings
Hi list,
I get these warnings quite frequently.
Warning: Failed to do incremental sync for mailbox INBOX, retry with a
full sync
Is this something to worry about? Otherwise the replication works
perfectly.
Cheers Jan
--
MAX-PLANCK-INSTITUT fuer Radioastronomie
Jan Behrend - Rechenzentrum
Auf dem Huegel 69, D-53121 Bonn
Tel: +49 (228) 525 359, Fax: +49 (228) 525 229
jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de
# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.7 xfs
auth_gssapi_hostname = imap.mpifr-bonn.mpg.de
auth_krb5_keytab = /etc/krb5-ha.keytab
auth_mechanisms = plain login gssapi
auth_verbose = yes
default_process_limit = 1024
default_vsz_limit = 512 M
dict {
acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
doveadm_password = xxx
doveadm_port = 50222
listen = 134.104.18.77
lmtp_save_to_detail_mailbox = yes
mail_location = mdbox:/var/mail/%Ln/maildrop
mail_plugins = acl zlib notify replication
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 imapflags notify
mdbox_rotate_size = 10 M
namespace mpifr_private {
inbox = yes
location =
prefix =
separator = .
}
namespace mpifr_shared {
inbox = no
list = children
location = mdbox:/var/mail/%%n/maildrop
prefix = shared.%%n.
separator = .
subscriptions = no
type = shared
}
passdb {
args = /etc/dovecot/dovecot-ldap-passdb.conf.ext
driver = ldap
}
plugin {
acl = vfile
acl_defaults_from_inbox = yes
acl_shared_dict = proxy::acl
mail_replica = tcp:192.168.42.173:50222
sieve = ~/.dovecot.sieve
sieve_after = /var/mail/global-after.sieve
sieve_dir = ~/sieve
sieve_extensions = +notify +imapflags
sieve_global_dir = /var/mail
zlib_save = gz
zlib_save_level = 6
}
protocols = imap lmtp sieve pop3
replication_dsync_parameters = -d -l 30 -U -n mpifr_private -n mpifr_shared
replication_max_conns = 6
service aggregator {
fifo_listener replication-notify-fifo {
user = vmail
}
unix_listener replication-notify {
user = vmail
}
}
service anvil {
client_limit = 8192
}
service auth {
client_limit = 8192
unix_listener auth-userdb {
group = vmail
user = vmail
}
}
service dict {
unix_listener dict {
group = vmail
user = vmail
}
}
service doveadm {
inet_listener {
address = 192.168.42.105
port = 50222
}
}
service imap-login {
process_min_avail = 5
service_count = 1
}
service imap {
vsz_limit = 512 M
}
service indexer-worker {
client_limit = 1
process_limit = 10
user = root
}
service lmtp {
inet_listener lmtp {
address = 134.104.18.105
port = 24
}
}
service managesieve-login {
inet_listener sieve {
address = 134.104.18.77
port = 4190
}
service_count = 1
}
service pop3-login {
process_min_avail = 5
}
service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
mode = 0666
}
}
ssl = required
ssl_cert = /etc/dovecot/imap.pem
ssl_cipher_list = ALL:HIGH:!SSLv2:!LOW:!EXP:!RC4:!MD5:!aNULL
ssl_key = /etc/dovecot/private/imap.key
ssl_protocols = !SSLv2 !SSLv3
userdb {
args = /etc/dovecot/dovecot-ldap-userdb.conf.ext
driver = ldap
}
verbose_proctitle = yes
protocol lmtp {
mail_plugins = acl zlib notify replication sieve
}
protocol imap {
imap_client_workarounds = tb-lsub-flags
mail_max_userip_connections = 20
mail_plugins = acl zlib notify replication imap_acl imap_zlib
ssl_cert = /etc/dovecot/imap.pem
ssl_key = /etc/dovecot/private/imap.key
}
protocol pop3 {
ssl_cert = /etc/dovecot/pop3.pem
ssl_key = /etc/dovecot/private/imap.key
}
smime.p7s
Description: S/MIME cryptographic signature
Re: gssapi considered as PLAIN?
On Wed, 2014-11-05 at 16:52 +0100, Harry Schmalzbauer wrote:
Bezüglich Hans Morten Kind's Nachricht vom 05.11.2014 16:48 (localtime):
On Wed, Nov 05, 2014 at 04:22:12PM +0100, Harry Schmalzbauer wrote:
as soon as I set disable_plaintext_auth = yes, AUTH=GSSAPI vanishes
from capabilities.
Try setting login_trusted_networks to something you trust.
root@mailbox1:/etc/dovecot/conf.d# doveconf auth_mechanisms
auth_mechanisms = plain login gssapi
root@mailbox1:/etc/dovecot/conf.d# doveconf disable_plaintext_auth
disable_plaintext_auth = yes
root@mailbox1:/etc/dovecot/conf.d# doveconf login_trusted_networks
login_trusted_networks =
a CAPABILITY
* CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE
AUTH=PLAIN AUTH=LOGIN AUTH=GSSAPI
Must be something else ...
Check my attached config for differences.
Cheer Jan
--
MAX-PLANCK-INSTITUT fuer Radioastronomie
Jan Behrend - Rechenzentrum
Auf dem Huegel 69, D-53121 Bonn
Tel: +49 (228) 525 359, Fax: +49 (228) 525 229
jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de
# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.7 xfs
auth_gssapi_hostname = imap.mpifr-bonn.mpg.de
auth_krb5_keytab = /etc/krb5-ha.keytab
auth_mechanisms = plain login gssapi
auth_verbose = yes
default_process_limit = 1024
default_vsz_limit = 512 M
dict {
acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
doveadm_password = xxx
doveadm_port = 50222
listen = 134.104.18.77
lmtp_save_to_detail_mailbox = yes
mail_location = mdbox:/var/mail/%Ln/maildrop
mail_plugins = acl zlib notify replication
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 imapflags notify
mdbox_rotate_size = 10 M
namespace mpifr_private {
inbox = yes
location =
prefix =
separator = .
}
namespace mpifr_shared {
inbox = no
list = children
location = mdbox:/var/mail/%%n/maildrop
prefix = shared.%%n.
separator = .
subscriptions = no
type = shared
}
passdb {
args = /etc/dovecot/dovecot-ldap-passdb.conf.ext
driver = ldap
}
plugin {
acl = vfile
acl_defaults_from_inbox = yes
acl_shared_dict = proxy::acl
mail_replica = tcp:192.168.42.173:50222
sieve = ~/.dovecot.sieve
sieve_after = /var/mail/global-after.sieve
sieve_dir = ~/sieve
sieve_extensions = +notify +imapflags
sieve_global_dir = /var/mail
zlib_save = gz
zlib_save_level = 6
}
protocols = imap lmtp sieve pop3
replication_dsync_parameters = -d -l 30 -U -n mpifr_private -n mpifr_shared
replication_max_conns = 6
service aggregator {
fifo_listener replication-notify-fifo {
user = vmail
}
unix_listener replication-notify {
user = vmail
}
}
service anvil {
client_limit = 8192
}
service auth {
client_limit = 8192
unix_listener auth-userdb {
group = vmail
user = vmail
}
}
service dict {
unix_listener dict {
group = vmail
user = vmail
}
}
service doveadm {
inet_listener {
address = 192.168.42.105
port = 50222
}
}
service imap-login {
process_min_avail = 5
service_count = 1
}
service imap {
vsz_limit = 512 M
}
service indexer-worker {
client_limit = 1
process_limit = 10
user = root
}
service lmtp {
inet_listener lmtp {
address = 134.104.18.105
port = 24
}
}
service managesieve-login {
inet_listener sieve {
address = 134.104.18.77
port = 4190
}
service_count = 1
}
service pop3-login {
process_min_avail = 5
}
service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
mode = 0666
}
}
ssl = required
ssl_cert = /etc/dovecot/imap.pem
ssl_cipher_list = ALL:HIGH:!SSLv2:!LOW:!EXP:!RC4:!MD5:!aNULL
ssl_key = /etc/dovecot/private/imap.key
ssl_protocols = !SSLv2 !SSLv3
userdb {
args = /etc/dovecot/dovecot-ldap-userdb.conf.ext
driver = ldap
}
verbose_proctitle = yes
protocol lmtp {
mail_plugins = acl zlib notify replication sieve
}
protocol imap {
imap_client_workarounds = tb-lsub-flags
mail_max_userip_connections = 20
mail_plugins = acl zlib notify replication imap_acl imap_zlib
ssl_cert = /etc/dovecot/imap.pem
ssl_key = /etc/dovecot/private/imap.key
}
protocol pop3 {
ssl_cert = /etc/dovecot/pop3.pem
ssl_key = /etc/dovecot/private/imap.key
}
smime.p7s
Description: S/MIME cryptographic signature
Re: gssapi considered as PLAIN?
On Wed, 2014-11-05 at 17:04 +0100, Harry Schmalzbauer wrote: Bezüglich Jan Behrend's Nachricht vom 05.11.2014 17:01 (localtime): On Wed, 2014-11-05 at 16:52 +0100, Harry Schmalzbauer wrote: Bezüglich Hans Morten Kind's Nachricht vom 05.11.2014 16:48 (localtime): On Wed, Nov 05, 2014 at 04:22:12PM +0100, Harry Schmalzbauer wrote: as soon as I set disable_plaintext_auth = yes, AUTH=GSSAPI vanishes from capabilities. Try setting login_trusted_networks to something you trust. root@mailbox1:/etc/dovecot/conf.d# doveconf auth_mechanisms auth_mechanisms = plain login gssapi root@mailbox1:/etc/dovecot/conf.d# doveconf disable_plaintext_auth disable_plaintext_auth = yes root@mailbox1:/etc/dovecot/conf.d# doveconf login_trusted_networks login_trusted_networks = a CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=GSSAPI You don't see LOGINDISABLED, so I guess rip==lip (you tested @localhost), right? No, but I didn't show all of it ;-). Here it is: jbehrend@jb1:~$ gnutls-cli --starttls --x509cafile /etc/ssl/certs/Max-Planck-Gesellschaft.pem -p 143 imap.mpifr-bonn.mpg.de Processed 1 CA certificate(s). Resolving 'imap.mpifr-bonn.mpg.de'... Connecting to '134.104.18.77:143'... - Simple Client Mode: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS LOGINDISABLED] Dovecot ready. a starttls a OK Begin TLS negotiation now. *** Starting TLS handshake - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1023 bits - Peer's public key: 1023 bits - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `C=DE,ST=Nordrhein-Westfalen,L=Bonn,O=Max-Planck-Gesellschaft,OU=Max-Planck-Institut fuer Radioastronomie,CN=imap.mpifr-bonn.mpg.de', issuer `C=DE,O=Max-Planck-Gesellschaft,CN=MPG CA,EMAIL=mpg...@mpg.de', RSA key 4096 bits, signed using RSA-SHA1, activated `2014-05-06 11:17:21 UTC', expires `2019-05-05 11:17:21 UTC', SHA-1 fingerprint `c0b4fb497ac212f0e05de24f2c097a0b712435cc' - The hostname in the certificate matches 'imap.mpifr-bonn.mpg.de'. - Peer's certificate is trusted - Version: TLS1.2 - Key Exchange: DHE-RSA - Cipher: AES-128-CBC - MAC: SHA1 - Compression: NULL a CAPABILITY * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN AUTH=GSSAPI a OK Pre-login capabilities listed, post-login capabilities have more. Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de smime.p7s Description: S/MIME cryptographic signature
sieve replication and .dovecot.lda-dupes
Hello list,
I have a replicated dovecot with two servers.
People seem to get vacation responses more often then it is specified in
days: XX, depending on which dovecot instance they receive the
incoming mail. Is .dovecot.lda-dupes replicated?
The other problem is that the vacation response is coming from the wrong
address depending on which field the recipient was listed: to: or
cc:
Here is my test example:
g9-rz has the vacation rule set up:
date | mail -s test -r jbehr...@mpifr-bonn.mpg.de -c
g9...@mpifr-bonn.mpg.de j...@flatpick.de
and this returns this vacation response:
### snip ###
Return-Path:
Delivered-To: jbehr...@mpifr-bonn.mpg.de
Received: from mail2.mpifr-bonn.mpg.de ([134.104.18.60]) by
mailbox2.mpifr-bonn.mpg.de (Dovecot) with LMTP id
+pgPDzm1WFSn9wAAvl5QjA
for jbehr...@mpifr-bonn.mpg.de; Tue, 04 Nov 2014 12:16:13 +0100
X-Sieve: Pigeonhole Sieve 0.4.2
Message-ID:
dovecot-sieve-1415099773-54151...@mailbox1.mpifr-bonn.mpg.de
Date: Tue, 04 Nov 2014 12:16:13 +0100
From: j...@flatpick.de
To: jbehr...@mpifr-bonn.mpg.de
Subject: Vacation
In-Reply-To: e1xlc5t-0001lt...@jb1.mpifr-bonn.mpg.de
References: e1xlc5t-0001lt...@jb1.mpifr-bonn.mpg.de
Auto-Submitted: auto-replied (vacation)
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Evolution-Source: 1385020682.6450.3@jb1
Ain't here! Go away or something ...
Cheers
### snip ###
I would expect g9...@mpifr-bonn.mpg.de in the from: field. Is this
correct?
Cheers Jan
--
MAX-PLANCK-INSTITUT fuer Radioastronomie
Jan Behrend - Rechenzentrum
Auf dem Huegel 69, D-53121 Bonn
Tel: +49 (228) 525 359, Fax: +49 (228) 525 229
jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de
# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.7 xfs
auth_gssapi_hostname = imap.mpifr-bonn.mpg.de
auth_krb5_keytab = /etc/krb5-ha.keytab
auth_mechanisms = plain login gssapi
auth_verbose = yes
default_process_limit = 1024
default_vsz_limit = 512 M
dict {
acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
}
doveadm_password = xxx
doveadm_port = 50222
listen = 134.104.18.77
lmtp_save_to_detail_mailbox = yes
mail_location = mdbox:/var/mail/%Ln/maildrop
mail_plugins = acl zlib notify replication
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 imapflags notify
mdbox_rotate_size = 10 M
namespace mpifr_private {
inbox = yes
location =
prefix =
separator = .
}
namespace mpifr_shared {
inbox = no
list = children
location = mdbox:/var/mail/%%n/maildrop
prefix = shared.%%n.
separator = .
subscriptions = no
type = shared
}
passdb {
args = /etc/dovecot/dovecot-ldap-passdb.conf.ext
driver = ldap
}
plugin {
acl = vfile
acl_defaults_from_inbox = yes
acl_shared_dict = proxy::acl
mail_replica = tcp:192.168.42.173:50222
sieve = ~/.dovecot.sieve
sieve_after = /var/mail/global-after.sieve
sieve_dir = ~/sieve
sieve_extensions = +notify +imapflags
sieve_global_dir = /var/mail
zlib_save = gz
zlib_save_level = 6
}
protocols = imap lmtp sieve pop3
replication_dsync_parameters = -d -l 30 -U -n mpifr_private -n mpifr_shared
replication_max_conns = 6
service aggregator {
fifo_listener replication-notify-fifo {
user = vmail
}
unix_listener replication-notify {
user = vmail
}
}
service anvil {
client_limit = 8192
}
service auth {
client_limit = 8192
unix_listener auth-userdb {
group = vmail
user = vmail
}
}
service dict {
unix_listener dict {
group = vmail
user = vmail
}
}
service doveadm {
inet_listener {
address = 192.168.42.105
port = 50222
}
}
service imap-login {
process_min_avail = 5
service_count = 1
}
service imap {
vsz_limit = 512 M
}
service indexer-worker {
client_limit = 1
process_limit = 10
user = root
}
service lmtp {
inet_listener lmtp {
address = 134.104.18.105
port = 24
}
}
service managesieve-login {
inet_listener sieve {
address = 134.104.18.77
port = 4190
}
service_count = 1
}
service pop3-login {
process_min_avail = 5
}
service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
mode = 0666
}
}
ssl = required
ssl_cert = /etc/dovecot/imap.pem
ssl_cipher_list = ALL:HIGH:!SSLv2:!LOW:!EXP:!RC4:!MD5:!aNULL
ssl_key = /etc/dovecot/private/imap.key
ssl_protocols = !SSLv2 !SSLv3
userdb {
args = /etc/dovecot/dovecot-ldap-userdb.conf.ext
driver = ldap
}
verbose_proctitle = yes
protocol lmtp {
mail_plugins = acl zlib notify replication sieve
}
protocol imap {
imap_client_workarounds = tb-lsub-flags
mail_max_userip_connections = 20
mail_plugins = acl zlib notify replication imap_acl imap_zlib
ssl_cert = /etc/dovecot/imap.pem
ssl_key
Re: Question wrt. dovecot replicator
On Fri, 2014-10-10 at 14:45 +0200, Jan Behrend wrote: On Fri, 2014-10-03 at 23:37 +0200, Remko Lodder wrote: How can I determine why there are duplicated emails? Same problem here! What kind of messages should I specifically look for? Look for any errors and warnings in the Dovecot log. You could also enable mail_debug (ref. Can I set this up for a few selected accounts instead of all accounts like it was currently? To make sure I do not make things worse for others then needs to be :-) The service had been disabled for the time being to prevent the other users from getting duplicated emails. I do not know what kind of userdb you are running, but there is a newish patch that enables per user replication via the mail_replica setting. It is not yet included in the newest (2.2.13) release of Dovecot, but is available via the enterprise version. There are no FreeBSD builds for that, though. ref: http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 my userdb consists of local users (Which are fed through LDAP at the backend). perhaps I can setup a mailAttributes setting or something so that the replica can be set, although I prefer that I have control over that in the config itself :-) With the latest Debian jessie version 1:2.2.13-5 you can actually have a per user mail_replica setting taken from a (LDAP) directory. This keeps the duplicate mail issue away from other users but a few willing to test ... For what it’s worth: replication_dsync_parameters = -f -d -N -l 30 -U I read in Peer Heinlein's Dovecot book http://www.opensourcepress.de/de/produkte/Dovecot/13560/978-3-95539-074-7 that replicating a public namespace gives you trouble :-(. So keep the -N option away for now. However I would like examples for the -n and -x options, which are neither given in the wiki nor in the nonexistant man page. I think the replication feature is very, very cool, but right now it gives me a hard time to implement flawlessly ;-) Thanks for any help or light shed on this issue ... Found it ;-) http://wiki2.dovecot.org/Tools/Doveadm/Sync All working beautifully now! Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de smime.p7s Description: S/MIME cryptographic signature
Re: Question wrt. dovecot replicator
On Fri, 2014-10-03 at 23:37 +0200, Remko Lodder wrote: How can I determine why there are duplicated emails? Same problem here! What kind of messages should I specifically look for? Look for any errors and warnings in the Dovecot log. You could also enable mail_debug (ref. Can I set this up for a few selected accounts instead of all accounts like it was currently? To make sure I do not make things worse for others then needs to be :-) The service had been disabled for the time being to prevent the other users from getting duplicated emails. I do not know what kind of userdb you are running, but there is a newish patch that enables per user replication via the mail_replica setting. It is not yet included in the newest (2.2.13) release of Dovecot, but is available via the enterprise version. There are no FreeBSD builds for that, though. ref: http://hg.dovecot.org/dovecot-2.2/rev/c1c67bdc8752 my userdb consists of local users (Which are fed through LDAP at the backend). perhaps I can setup a mailAttributes setting or something so that the replica can be set, although I prefer that I have control over that in the config itself :-) With the latest Debian jessie version 1:2.2.13-5 you can actually have a per user mail_replica setting taken from a (LDAP) directory. This keeps the duplicate mail issue away from other users but a few willing to test ... For what it’s worth: replication_dsync_parameters = -f -d -N -l 30 -U I read in Peer Heinlein's Dovecot book http://www.opensourcepress.de/de/produkte/Dovecot/13560/978-3-95539-074-7 that replicating a public namespace gives you trouble :-(. So keep the -N option away for now. However I would like examples for the -n and -x options, which are neither given in the wiki nor in the nonexistant man page. I think the replication feature is very, very cool, but right now it gives me a hard time to implement flawlessly ;-) Thanks for any help or light shed on this issue ... Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de signature.asc Description: This is a digitally signed message part smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] LDA vs. LMTP
On 07/26/2013 05:45 PM, Martin Burgraf wrote: Hi there, I'm using Dovecot together with Postfix; as I understand it, there are two ways to transfer the mail from Postfix to Dovecot. 1.) by using LDA with mailbox_command = /usr/libexec/dovecot/dovecot-lda -f $SENDER -a $RECIPIENT 2.) by using LMTP with mailbox_transport = lmtp:unix:private/dovecot-lmtp (currently using number 1) I'm interessted in the differences and the advantages/disadvantages of each of those solutions. You cannot use the LDA method if SMTP and IMAP services reside on different machines, which would be the case in larger scale mail system setups. My advice is to go with LMTP anyway! Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de Die digitale Unterschrift dieser Mail kann durch das Zertifikat der DFN Global Hierarchie überprüft werden: https://ca.mpg.de/certs/root-DGP/deutsche-telekom-ca2-root-cert.der Weitere Informationen zur CA der MPG finden Sie unter: https://ca.mpg.de smime.p7s Description: S/MIME Cryptographic Signature
Re: [Dovecot] Automatic Debian Dovecot repository now also includes amd64 binary packages.
On 02/07/10 23:51, Stephan Bosch wrote: Hi, I've recently significantly improved the automated Dovecot Debian package builder. At the beginning it only produced i386 binaries for Debian testing. A few weeks back I added a slave builder that builds packages for Debian stable. Today I have extended the slave builder with support for multiple architectures and I've added amd64 binaries to the repository. Hello Stephan, has the amd64 build process stopped recently? I noticed no more updates in the amd64 repository while the i386 repository has plenty. Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de smime.p7s Description: S/MIME Cryptographic Signature
[Dovecot] Debian package init scripts
Dearest list, I am using dovecot with heartbeat-2 and I noticed that the init scripts in the Debian packages from http://xi.rename-it.nl/debian/ do not conform to the LSB standard: http://refspecs.freestandards.org/LSB_3.1.1/LSB-Core-generic/LSB-Core-generic/iniscrptact.html E.g. the return code for program is not running is not 3. Is there is special reason for this? Cheers Jan -- MAX-PLANCK-INSTITUT fuer Radioastronomie Jan Behrend - Rechenzentrum Auf dem Huegel 69, D-53121 Bonn Tel: +49 (228) 525 359, Fax: +49 (228) 525 229 jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de
[Dovecot] child 23925 killed with signal 6
Dearest list,
just now I migrated a pine user to dovecot. Nothing special so far, but
then I saw this in my syslog and the user reported, that he got this
error message:
MAIL FOLDER INBOX CLOSED DUE TO ACCESS ERROR
Obviously this problem is related to his local filter rules:
If commented out everything works like a charm. The corresponding
filter rule looks for a From-Line in the email header but the filter
string itself is empty. I know this filter rule does not make a lot of
sense, but nevertheless it shouldn't crash the imap process. If there
is any additional information you need please ask.
--- snip ---
Nov 16 11:25:07 imap-mgt dovecot: imap(username): Panic: file
istream-header-filter.c: line 520 (i_stream_create_header_filter):
assertion failed: (ret 0)
Nov 16 11:25:07 imap-mgt dovecot: imap(username): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x3e81b) [0x7f82a3bc381b] -
/usr/lib/dovecot/libdovecot.so.0(+0x3e876) [0x7f82a3bc3876] -
/usr/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f82a3b9dacf] - /usr/lib/do
vecot/libdovecot.so.0(i_stream_create_header_filter+0x27b)
[0x7f82a3babf9b] -
/usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x154)
[0x7f82a3e4cf04] -
/usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x530)
[0x7f82a3e4e7
e0] -
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x20)
[0x7f82a3e36630] - dovecot/imap() [0x416284] -
dovecot/imap(imap_search_start+0x106) [0x4166f6] -
dovecot/imap(cmd_search+0xc5) [0x40d535] - dovecot/imap() [0x41032d] -
dovecot/imap()
[0x41040d] - dovecot/imap(client_handle_input+0x135) [0x410635] -
dovecot/imap(client_input+0x5f) [0x410f5f] -
/usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xb5)
[0x7f82a3bcf205] - /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x18)
[0x7f82a3bce338] - /usr/lib
/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f82a3bbd0e3] -
dovecot/imap(main+0x2d1) [0x418f91] -
/lib/libc.so.6(__libc_start_main+0xfd) [0x7f82a3436c4d] -
dovecot/imap() [0x408c39]
Nov 16 11:25:07 imap-mgt dovecot: master: Error: service(imap): child
23925 killed with signal 6 (core not dumped)
--- snip ---
doveconf -n:
# 2.0.7 (3aced5ececd7): /etc/dovecot/dovecot.conf
# OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.6 xfs
auth_gssapi_hostname = imap.mpifr-bonn.mpg.de
auth_mechanisms = plain login gssapi
auth_verbose = yes
listen = 134.104.18.77
mail_gid = 4
mail_location = mdbox:/var/mail/%Ln
mail_uid = 4
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 = .
}
passdb {
args = /etc/dovecot/dovecot-ldap-passdb.conf.ext
driver = ldap
}
plugin {
sieve = ~/.dovecot.sieve
sieve_after = /home/global-after.sieve
sieve_dir = ~/sieve
}
protocols = imap pop3 lmtp sieve
service auth {
unix_listener auth-userdb {
group = vmail
}
}
service lmtp {
inet_listener lmtp {
address = 134.104.18.77
port = 24
}
}
service managesieve-login {
inet_listener sieve {
address = 134.104.18.77
port = 4190
}
}
ssl = required
ssl_cert = /etc/ssl/certs/imap-server.pem
ssl_key = /etc/ssl/private/imap-server.key
userdb {
args = /etc/dovecot/dovecot-ldap-userdb.conf.ext
driver = ldap
}
protocol lmtp {
mail_plugins = sieve
}
protocol imap {
ssl_cert = /etc/ssl/certs/imap-server.pem
ssl_key = /etc/ssl/private/imap-server.key
}
protocol pop3 {
ssl_cert = /etc/ssl/certs/pop3-server.pem
ssl_key = /etc/ssl/private/imap-server.key
}
--
MAX-PLANCK-INSTITUT fuer Radioastronomie
Jan Behrend - Rechenzentrum
Auf dem Huegel 69, D-53121 Bonn
Tel: +49 (228) 525 359, Fax: +49 (228) 525 229
jbehr...@mpifr-bonn.mpg.de http://www.mpifr-bonn.mpg.de
smime.p7s
Description: S/MIME Cryptographic Signature
