Re: fts_solr: Lookup failed: 400 Bad Request / GET null null
On Sun, Apr 3, 2016 at 4:19 PM, Stephan Bosch wrote:
>> Unfortunately I do not know (yet) which client action produces these
>> log lines. "GET null null" seems not to be a sensible request in any
>> case.
>>
>> Anyone seeing the same effect?
>
>
> Did this happen only after upgrade to 2.2.23 or is this a fresh install?
>
This effect has been observed with 2.2.18 (initial install) and after
upgrading to 2.2.23 as well.
> Can you make a dump of what messages are exchanged on 10.0.0.123:8080 using
> ngrep or wireshark?
>
I've captured some requests and they look like this (some parts
changed due to privacy concerns):
GET
/solr/select?fl=uid,score&rows=439&sort=uid+asc&q={!lucene+q.op%3dAND}hdr:%3c56f3a6.7080...@domain.de%3e+OR+hdr:%3c664dcdx1a4facd8b7922c495...@czchows1356.prg%5c-domain.com%3e+OR+hdr:%3c00cxde3$70ad7880$52
... (many many more OR hdrs)
&fq=%2Bbox:f696f93xx6e+%2Buser:u...@domain.de HTTP/1.1
The total request size is 31708 bytes and it contains many (hundreds?)
of 'OR hdrs' (side note: I wonder which client action triggers these
kind of requests, maybe the user selected hundreds of mails for
search?)
I _think_ this is a problem of the URL length / max http header size.
(Debian Jessie) Tomcat7 very likely does not accept more than 32kb
data in a request.
I wonder if Dovecot should limit SOLR requests to a specific size and
deny long requests with an imap error (?)
Chris
Re: New feature: HTTP API
> On April 5, 2016 at 9:57 AM Tom Sommer wrote: > > > On 2016-04-05 08:44, aki.tu...@dovecot.fi wrote: > >> On April 5, 2016 at 9:27 AM Tom Sommer wrote: > >> > >> > >> On 2016-04-04 20:22, aki.tu...@dovecot.fi wrote: > >> > >> > Since the API is still a little beta, it will not return anything in > >> > case > >> > doveadm does not like the arguments (that is, calls i_fatal). Also, > >> > success is > >> > often indicated with 200 OK along with [["doveadmResponse",[],"c01"]]. > >> > >> I don't see the "doveadm proxy kick" command in the list? > > > > Not all commands are included, unfortunately. Also, the list only > > shows commands that are available with doveadm as per configuration. > > Hrmm, is it possible to add a non-http inet_listener to doveadm? And > feed it commands directly? > > I really need a remote proxy kick for my director. Unfortunately it's not possible with 2.2.23. It has been fixed internally and will eventually pop out to public repo and into some release. Aki
doveadm sync -1 -R
Hi, I’m migrating an old Zarafa-installation to a dovecot using mdbox and sis on Debian Jessie. To copy over the emails, I use doveadm backup on the new box - or more precisely: vmail# doveadm -v -o imapc_user=$user -o imapc_password=$pass -o imapc_host=$host -o imapc_features=rfc822.size -o imapc_port=993 -o mailbox_list_index=no -o imapc_ssl_verify=no backup -R -x "Public folders*" -x "Public folders/*" -u $user imapc: For each invoke of doveadm backup -R, the local (new) mailbox gets wiped and all mails are retransferred - so far, so good. I’d like to use "doveadm sync -1“ as per the manpage to keep the downtime short, however sync doesn’t like the -R option: sync: invalid option -- 'R' doveadm sync [-u |-A] [-S ] [-1fPU] [-l ] [-r ] [-m ] [-g ] [-n | -N] [-x ] [-s ] -d| If I understand it correctly, without -R it would mean that doveadm sync would incorporate the changes from the local dovecot-mailbox into the remote imapc:-Mailbox, which is the opposite of what I want. Dovecot version is current head as of yesterday. Is what I’m trying to do even possible with doveadm sync? Kind regards, Lukas
Re: v2.2.23 released
On Mon, 4 Apr 2016 11:02:46 +0300, Teemu Huovila wrote: >> >> ... the build breaks on NetBSD with [...] > > The build should work with > https://github.com/dovecot/core/commit/4adefdb40c7ffcac3d8f8279cdf52d9f72d39636. > Please report back, if it does not. It works indeed. Thanks for the fix! Cheerio, hauke -- The ASCII Ribbon CampaignHauke Fath () No HTML/RTF in emailInstitut für Nachrichtentechnik /\ No Word docs in email TU Darmstadt Respect for open standards Ruf +49-6151-16-21344
Re: How to delete Dovecot users when using Single Instance Storage
On 19.03.2016 18:56, Jesus Cea wrote: In case somebody find this useful: https://blog.jcea.es/posts/20160211-delete_users_dovecot.html "The expunge step" didn't work because "all" parameter was broken in 2.2.21. It's fixed now: https://github.com/dovecot/core/commit/6971937a6f3e93844dbd43bdbe903628e21a9422 Also as workaround you can replace 'all' with '1:*'. Here is a script that automates the procedure: https://github.com/moisseev/doveadm-tools/blob/master/bin/doveadm-mdboxrm
Re: New feature: HTTP API
> On April 5, 2016 at 12:24 PM aki.tu...@dovecot.fi wrote: > > > > > On April 5, 2016 at 9:57 AM Tom Sommer wrote: > > > > > > On 2016-04-05 08:44, aki.tu...@dovecot.fi wrote: > > >> On April 5, 2016 at 9:27 AM Tom Sommer wrote: > > >> > > >> > > >> On 2016-04-04 20:22, aki.tu...@dovecot.fi wrote: > > >> > > >> > Since the API is still a little beta, it will not return anything in > > >> > case > > >> > doveadm does not like the arguments (that is, calls i_fatal). Also, > > >> > success is > > >> > often indicated with 200 OK along with [["doveadmResponse",[],"c01"]]. > > >> > > >> I don't see the "doveadm proxy kick" command in the list? > > > > > > Not all commands are included, unfortunately. Also, the list only > > > shows commands that are available with doveadm as per configuration. > > > > Hrmm, is it possible to add a non-http inet_listener to doveadm? And > > feed it commands directly? > > > > I really need a remote proxy kick for my director. > > Unfortunately it's not possible with 2.2.23. It has been fixed internally and > will eventually pop out to public repo and into some release. > > Aki Fixed hopefully in https://github.com/dovecot/core/commit/76537b1991e7815c7a867a997f7fa2b3c17412d4 Aki
dovecot squatter
Hi, on cyrus installations we have the squatter utility that can index full message bodies and headers incrementally, allowing to run the squatter from time to time to arrange for index changes. Is there anything similar in Dovecot? This is expecially useful for full searches in body message. Thanks for any help Gabriele Sonicle S.r.l. : http://www.sonicle.com Music: http://www.gabrielebulfon.com Quantum Mechanics : http://www.cdbaby.com/cd/gabrielebulfon
Re: dovecot squatter
Am 05.04.2016 um 18:12 schrieb Gabriele Bulfon: > Hi, > on cyrus installations we have the squatter utility that can index full > message bodies and headers incrementally, allowing to run > the squatter from time to time to arrange for index changes. > Is there anything similar in Dovecot? > This is expecially useful for full searches in body message. > Thanks for any help > Gabriele > > Sonicle S.r.l. > : > http://www.sonicle.com > Music: > http://www.gabrielebulfon.com > Quantum Mechanics : > http://www.cdbaby.com/cd/gabrielebulfon > Hi Gabriele, something like this? http://wiki2.dovecot.org/Plugins/FTS/Lucene
Session ID separator change
LMTP is a but troublesome in that a single LMTP session can do multiple RCPT
TOs, so the same session will end up delivering mails to multiple different
users. This is causing trouble with stats process, because each delivery is
using the same session ID for multiple different users, which causes errors
about session ID duplication in stats process. So we'll need to make the
session IDs unique, while still keeping it clear enough that they're part of
the same original LMTP session (which is also visible in th Received: headers).
I'm now thinking that the first recipient's delivery will have the original
normal session ID (e.g. "ME3ZHCi+A1dUDQAAvAUe3g"), while the following
recipients will have :2, :3, etc suffix (e.g. "ME3ZHCi+A1dUDQAAvAUe3g:2"). If
somebody cares about parsing the original session ID from logs, they can just
cut off the session ID from the first ':' character (because indexer-worker
also adds its own :suffix).
So now I'm mainly wondering if ':' is a good character? Has somebody already
changed mail_log_prefix in a way that these additional ':' chars might break
their log parsers (e.g. mail_log_prefix=%u:%s%{session}:%r).
Re: namespace...mailbox doesn't exist
I tried that and am sad to say it did not work. Hmmm...
On 4/5/2016 12:43 AM, Steffen Kaiser wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Mon, 4 Apr 2016, Eric wrote:
Date: Mon, 4 Apr 2016 20:23:34 -0600
From: Eric
To: dovecot@dovecot.org
Subject: namespace...mailbox doesn't exist
Hello list,
I have a namespace called 'projects' which when clicked in
Thunderbird (nonexistent in eM Client) yields the following error:
"The current operation on 'projects' did not succeed. The mail server
for account
u...@domain.tld responded: mailbox doesn't exist: projects.projects
(0.00 + 0.00 secs)."
The namespace is configure as follows:
# Shared namespace 'projects'
namespace {
^^ IMHO first try to give that namespace a name, e.g.
namespace projects {
location = maildir:/home/vpopmail/domains/domain.tld/shared/projects
prefix = projects.
separator = .
type = public
}
This is the log:
1: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: Effective
uid=89, gid=89, home=/home/vpopmail/domains/domain.tld/postmaster
2: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: Quota root:
name=ignore=Trash backend=maildir args=
3: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: Quota rule:
root=ignore=Trash mailbox=? bytes=0 messages=0
4: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: Quota grace:
root=ignore=Trash bytes=0 (10%)
5: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: Namespace :
type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes,
subscriptions=yes location=
6: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: mdbox:
access(/home/vpopmail/domains/domain.tld/postmaster/mdbox, rwx):
failed: No such file or directory
7: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: mdbox:
couldn't find root dir
8: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: sdbox:
access(/home/vpopmail/domains/domain.tld/postmaster/sdbox, rwx):
failed: No such file or directory
9: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: sdbox:
couldn't find root dir
10: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: maildir: root
exists (/home/vpopmail/domains/domain.tld/postmaster/Maildir)
11: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: maildir++:
root=/home/vpopmail/domains/domain.tld/postmaster/Maildir, index=,
indexpvt=, control=,
inbox=/home/vpopmail/domains/domain.tld/postmaster/Maildir, alt=
12: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: Namespace :
type=public, prefix=projects., sep=., inbox=no, hidden=no, list=yes,
subscriptions=yes
location=maildir:/home/vpopmail/domains/domain.tld/shared/projects
13: Apr 04 20:00:30 imap(postmas...@domain.tld): Debug: maildir++:
root=/home/vpopmail/domains/domain.tld/shared/projects, index=,
indexpvt=, control=, inbox=, alt=
This did not happen with other versions of dovecot (I think) but just
started happening with the upgrade. While it is not
a serious problem and I can live with it, what would be causing it in
the new dovecot iteration (2.2.23) ? And, could it be
that I'm missing the necessary setting to mitigate this? Please let
me know if any additional information is necessary.
I'm thinking that the problem lies in lines 6/7 and 8/9 where Dovecot
is looking for mdbox/sdbox.
Eric
- -- Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEVAwUBVwNejHz1H7kL/d9rAQJMKgf7B0B4mqfXCxYPx1mgimXgUZxUh1+OfMKs
SFE2oKnpsg5lFsqeYXNHKVBToOaOEQCHVvcNg7iEe009X7CFTbzoOWm1PaX1ue+N
LsPzPhSmoqU74D8+3OMK4noiFdWz3vZMPI2vt181q2HzQSHPdI8T73AVOhROQ/62
k2mIX9OxCH+wU9ZsLD6uUrG9jsNPIwdmLdSbDjTWgmyoZWRlL9rxYVcrU+laPu0F
U0P29Vx9DmlEFdu42cua2BkCRKsFDg2BajF6UiCqyeKN3V8ZUJH8jVI2WFZ2jF6/
bytKdnFVTIDKbt/dkwWJjTDH1LMI8BpCFh/AGrJeoC9IfKMSs5F61Q==
=XSh1
-END PGP SIGNATURE-
Re: Session ID separator change
* Timo Sirainen schrieb am 05.04.16 um 19:29 Uhr:
[…]
> So now I'm mainly wondering if ':' is a good character? Has somebody
> already changed mail_log_prefix in a way that these additional ':'
> chars might break their log parsers (e.g.
> mail_log_prefix=%u:%s%{session}:%r).
Why not use another '+'?
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
Re: Session ID separator change
Op 4/6/2016 om 12:14 AM schreef Marc Schiffbauer:
> * Timo Sirainen schrieb am 05.04.16 um 19:29 Uhr:
> […]
>> So now I'm mainly wondering if ':' is a good character? Has somebody
>> already changed mail_log_prefix in a way that these additional ':'
>> chars might break their log parsers (e.g.
>> mail_log_prefix=%u:%s%{session}:%r).
> Why not use another '+'?
>
That '+' in the example is just part of the Base64 encoding, so it is
not a separator.
Regards,
Stephan.
Unable to login with iPhone?
Hey Everyone,
So I have my dovecot install up and running! I can receive mail from the
outside, still dealing with a small issue with sending email, but I think
that's an issue off needing to setup a relay...
Right now though... My biggest issue is it won't connect to my iPhone... I
can login with mail on my computer, and through round cube for webmail...
But it gets stuck on "verifying"... I tried addingcram-md5 and digest-md5
to the auth_mechanisms but that didn't work... Any idea what I'm missing?
Here is my doveconf -n:
[ec2-user@ip-172-31-28-46 postfix]$ doveconf -n
# 2.2.10: /etc/dovecot/dovecot.conf
# OS: Linux 4.4.5-15.26.amzn1.x86_64 x86_64 ext4
auth_mechanisms = plain login cram-md5 digest-md5
mail_location = maildir:/var/vmail/%d/%n/Maildir
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
mbox_write_locks = fcntl
namespace inbox {
inbox = yes
location =
prefix =
separator = .
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0666
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
}
ssl = required
ssl_cert =
Re: Unable to login with iPhone?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 5 Apr 2016, Jason Pruim wrote:
Right now though... My biggest issue is it won't connect to my iPhone... I
can login with mail on my computer, and through round cube for webmail...
But it gets stuck on "verifying"... I tried addingcram-md5 and digest-md5
to the auth_mechanisms but that didn't work... Any idea what I'm missing?
did you verified that the connection from the iPhone arrives at Dovecot at
all? Then: http://wiki2.dovecot.org/Debugging/Authentication and visit the
log files.
Here is my doveconf -n:
[ec2-user@ip-172-31-28-46 postfix]$ doveconf -n
# 2.2.10: /etc/dovecot/dovecot.conf
# OS: Linux 4.4.5-15.26.amzn1.x86_64 x86_64 ext4
auth_mechanisms = plain login cram-md5 digest-md5
mail_location = maildir:/var/vmail/%d/%n/Maildir
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
mbox_write_locks = fcntl
namespace inbox {
inbox = yes
location =
prefix =
separator = .
}
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0666
user = vmail
}
}
service imap-login {
inet_listener imap {
port = 143
}
inet_listener imaps {
port = 993
ssl = yes
}
}
ssl = required
ssl_cert =
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
iQEVAwUBVwShXnz1H7kL/d9rAQIBjAgAj3eonk5bthDHFLDh/+VfdpqGMJ4+32Ch
kd5zueur30hMOJH379efDs/bSERRsgrC4T8GPlLYaKYzg1+OPVE11Jaz85LJ7K7r
CtaujA9wIkLdnKm91jKZ5jtvlZ6awVKYI7422LBOB1TkYEYfUvWIaEhrjTZvKiGT
WcbyUS0FqJrAZu/T5wwfBoZbNHukiZEonai77/yQzIPhzKnOTFav/goid9NjfBSC
RkL83yZ7lahDAh0hu8KkH+tfg2nGJhhpZzlwHZAbmypmVjB73Dwa5vnkqc+ah+BJ
YJSEfUI/nd7if9HQIoAyW6f57ljF0Cj91fG9e0bD22C0ZK1lLMK7UQ==
=Zvca
-END PGP SIGNATURE-
