I got solr working. I'll post more info later.
On Wed, Nov 2, 2016 at 3:37 PM, Larry Rosenman wrote:
>
> On Wed, Nov 2, 2016 at 3:15 PM, Larry Rosenman wrote:
>
>> ah. Looking into Solr. Is the wiki out of date with regard to
>> solr 6.2.0? there
On 02 Nov 2016, at 22:02, Larry Rosenman wrote:
>
> why wouldn't it be able to use the ~/MAILARCHIVE/ filesystem space?
>
> The other indexes etc seem to get built there.
It's not about adding an index there, but about trying to open "MAILARCHIVE"
itself as a folder.
Am 2016-11-02 um 13:16 schrieb Konstantin Khomoutov:
On Tue, 1 Nov 2016 18:20:14 -0500
Bryan Holloway wrote:
The new (2.2) server had "auth_mechanisms" of "digest-md5" enabled
along with "plain". This is what was causing the four-second delay,
but only with Outlook clients.
On Wed, Nov 2, 2016 at 3:15 PM, Larry Rosenman wrote:
> ah. Looking into Solr. Is the wiki out of date with regard to
> solr 6.2.0? there doesn't seem to be a conf/schmea.xml file any more.
I started the default solr from FreeBSD ports, and there is no update URL.
I'll
On Wed, Nov 2, 2016 at 3:02 PM, Larry Rosenman wrote:
> why wouldn't it be able to use the ~/MAILARCHIVE/ filesystem space?
>
> The other indexes etc seem to get built there.
>
> I'll see if the current FreeBSD solr port is easier to set up than the
> last time I tried.
>
Is there anything else I can provide?
On Wed, Nov 2, 2016 at 1:30 PM, Larry Rosenman wrote:
> nope -- No difference
>
> thebighonker.lerctr.org ~ $ ls -l ~/MAILARCHIVE/
> total 176
> drwx-- 6 ler ler 7 May 25 2014 2004
> drwx-- 8 ler ler 8 Mar 3 2013
Thnx Larry,
Thats was it!
Ruud
> On 2 Nov 2016, at 18:52, Larry Rosenman wrote:
>
> I added the following to 90-plugin.conf:
>
> service stats {
> chroot = empty
> client_limit = 0
> drop_priv_before_exec = no
> executable = stats
> extra_groups =
>
I updated dovecot-ldap.conf.ext so that it now reads as below:
#Custom Settings
hosts = 192.168.153.143
dn = u...@domain.com
dnpass = password
auth_bind = yes
auth_bind_userdn = %u...@domain.com
ldap_version = 3
base = dc=rpservices,dc=com
#user_filter = (&(objectclass=person)(mail=%u))
On Wed, Nov 02, 2016 at 07:15:17PM +0200, Timo Sirainen wrote:
> On 01 Nov 2016, at 18:26, The Doctor wrote:
> >
> > Getting complaints from people about pop/imap
> >
> > issues.
> >
> > some people are getting repaeted e-mail.
> >
> > Other are not able to delete
nope -- No difference
thebighonker.lerctr.org ~ $ ls -l ~/MAILARCHIVE/
total 176
drwx-- 6 ler ler 7 May 25 2014 2004
drwx-- 8 ler ler 8 Mar 3 2013 2005
drwx-- 11 ler ler 11 Mar 3 2013 2006
drwx-- 11 ler ler 11 May 3 2013 2007
drwx-- 14 ler ler 14 Mar
It looks like fts-lucene wants to write some information into INBOX's index
files. But your archive namespace doesn't have a working INBOX. Maybe it would
work if you create "#ARCHIVE/inbox"?
> On 02 Nov 2016, at 20:13, Larry Rosenman wrote:
>
> one other thing,
one other thing, fts_autoindex does NOT appear to be working on the
#ARCHIVE/ NAMESPACE.
I wonder if these are all interrelated?
On Wed, Nov 2, 2016 at 1:10 PM, Larry Rosenman wrote:
> FWIW it DOES work on my default NAMESPACE, just not the #ARCHIVE/
> NAMESPACE.
>
>
> On
FWIW it DOES work on my default NAMESPACE, just not the #ARCHIVE/ NAMESPACE.
On Wed, Nov 2, 2016 at 12:32 PM, Larry Rosenman wrote:
> It's ALWAYS failed on the other NAMESPACE.
>
> Some of the logging looks weird as well for the 2nd namespace:
>
> Nov 2 12:32:03
On 02.11.2016 19:54, Stuart Henderson wrote:
On 2016-11-02, Aki Tuomi wrote:
If the standard way works, I am happy to include the original patch I
sent, amended so that it checks for presence of LIBRESSL_VERSION_NUMBER.
If they keep this promise, then we should have no
On 2016-11-02, Aki Tuomi wrote:
> If the standard way works, I am happy to include the original patch I
> sent, amended so that it checks for presence of LIBRESSL_VERSION_NUMBER.
> If they keep this promise, then we should have no worries about things
> breaking up.
Diff
I added the following to 90-plugin.conf:
service stats {
chroot = empty
client_limit = 0
drop_priv_before_exec = no
executable = stats
extra_groups =
fifo_listener stats-mail {
group =
mode = 0666
user =
}
fifo_listener stats-user {
group =
mode = 0666
It's ALWAYS failed on the other NAMESPACE.
Some of the logging looks weird as well for the 2nd namespace:
Nov 2 12:32:03 thebighonker dovecot: imap-login: Login: user=,
method=PLAIN, rip=207.231.91.36, lip=192.147.25.65, mpid=76712, TLS,
session=
Nov 2 12:32:03 thebighonker
It's getting a bit strange. You were running 2.2.25 previously and it was
working then? Does the doveadm index always fail with the same errors?
Also I just noticed that it's saying INBOX isn't selectable: "lucene: Failed to
sync mailbox INBOX: Mailbox isn't selectable". Which I guess isn't
is there something more i need to be doing my end?
On 25/10/2016 09:11, Matthew Broadhead wrote:
are there any instructions or tests i can make to check the sieve
configuration? or does the magic all happen internally and there are
no settings to change?
On 21/10/2016 10:22, Matthew
thebighonker.lerctr.org ~ $ doveadm mailbox status -u l...@lerctr.org vsize
\#ARCHIVE/2016/10/clamav-rules
#ARCHIVE/2016/10/clamav-rules vsize=3840752
thebighonker.lerctr.org ~ $
On Wed, Nov 2, 2016 at 12:22 PM, Timo Sirainen wrote:
> On 02 Nov 2016, at 19:19, Larry Rosenman
On 02 Nov 2016, at 19:19, Larry Rosenman wrote:
>
> clamav-rules is NOT a directory, nor are any of the others:
Can you access these mboxes at all with Dovecot? e.g.
doveadm mailbox status -u user@domain clamav-rules
> thebighonker.lerctr.org ~/MAILARCHIVE $ cd 2016/10
>
clamav-rules is NOT a directory, nor are any of the others:
thebighonker.lerctr.org ~/MAILARCHIVE $ cd 2016/10
thebighonker.lerctr.org ~/MAILARCHIVE/2016/10 $ ls -l
total 72106
-rw-r--r-- 1 ler ler 440461 Nov 1 00:05 Amplify_Mail
-rw-r--r-- 1 ler ler 104102478 Nov 1 14:53 INBOX
prw-rw-rw- 1 root wheel 0 Nov 1 13:09 stats-mail
prw--- 1 root wheel 0 Nov 1 13:09 stats-user
drwxr-x--- 2 root dovenull 4 Nov 1 13:09 token-login
If something other than root is trying to write to stats-user, we found the
issue.
this is on 10.3-STABLE
On Wed,
On 01 Nov 2016, at 20:30, Larry Rosenman wrote:
>
> doveadm -D -vv index \#ARCHIVE/\* garners the below for ALL mailboxes
> in the
> namespace:
> doveadm(ler): Error: Mailbox #ARCHIVE/2013/04/clamav-rules: Status lookup
> failed: Internal error occurred. Refer to server
On 01 Nov 2016, at 18:26, The Doctor wrote:
>
> Getting complaints from people about pop/imap
>
> issues.
>
> some people are getting repaeted e-mail.
>
> Other are not able to delete their e-mails from an IMAP lcient.
Anything in error logs? POP3 duplicates sound
On 01 Nov 2016, at 22:31, Ruud Boon wrote:
>
> HI,
>
> I’m currently testing the stats module of Dovecot (2.2.26.0 (23d1de6))
> Looks like there no statistics under FreeBSD.
> Server isn’t busy yet but got at least a few connection open.
See if there are any errors
Hello everyone.
I see we are having issues with dovecot 2.226.0 in the FreeBSD world.
I did run dovecot-2.2.26.rc1 myself and did not see repeat problem
in POP3 or IMAP issue customers were reporting.
I see this repeat issue in dovecot 2.26.0 either port or compiled similarly.
So the question
Anything else I can provide ?
Sent from my Sprint Samsung Galaxy S7.
Original message From: Larry Rosenman
Date: 11/1/16 1:37 PM (GMT-06:00) To: Aki Tuomi Cc:
Dovecot Mailing List Subject: Re: doveadm index:
Thank you.
Sent from ProtonMail Mobile
On Wed, Nov 2, 2016 at 12:22 PM, Michael A. Peters <'mpet...@domblogger.net'>
wrote:
Standard way to fix it (on the LibreSSL page) is to check for
LIBRESSL_VERSION_NUMBER - e.g. the patch attached which I think catches
them all where needed. Note the word
If the standard way works, I am happy to include the original patch I
sent, amended so that it checks for presence of LIBRESSL_VERSION_NUMBER.
If they keep this promise, then we should have no worries about things
breaking up.
Aki
On 02.11.2016 14:24, Michael A. Peters wrote:
Indeed, which
Indeed, which is why I use it.
But it also is in the minority which is why I find it acceptable for
FLOSS projects like dovecot to elect to only un-officially support
LibreSSL via a community maintained patch.
One of the reasons why OpenSSL was forked is because they were trying to
support
On Tue, 1 Nov 2016 18:20:14 -0500
Bryan Holloway wrote:
> In case anyone is interested, we finally found the problem:
>
> The new (2.2) server had "auth_mechanisms" of "digest-md5" enabled
> along with "plain". This is what was causing the four-second delay,
> but only with
libressl is a leaner and safer openssl
Sent from ProtonMail Mobile
On Wed, Nov 2, 2016 at 12:39 PM, Michael A. Peters <'mpet...@domblogger.net'>
wrote:
IMHO it would be acceptable to have a LibreSSL patch that is maintained
by the people who want it.
It's free software, and that kind of is
IMHO it would be acceptable to have a LibreSSL patch that is maintained
by the people who want it.
It's free software, and that kind of is the point of Open Source.
On 11/02/2016 04:36 AM, Michael A. Peters wrote:
They have stated they are going to remain API compatible with 1.0.1h (or
g,
They have stated they are going to remain API compatible with 1.0.1h (or
g, forget which they forked) - their new stuff is outside of libcrypto.
On 11/02/2016 04:25 AM, Aki Tuomi wrote:
It does work today, I am just bit worried that it will keep on breaking
with libressl as they evolve their
On 02.11.2016 13:30, Limperis Antonis wrote:
Hello,
I tried to compile Dovecot 2.2.26.0 with Sun Studio 12.0 on a Sun Solaris 10
x86 machine, but an error occurred related to src/lib-ldap/ldap-compare.c.
"ldap-compare.c", line 112: void function cannot return value
cc: acomp failed for
Hello,
I tried to compile Dovecot 2.2.26.0 with Sun Studio 12.0 on a Sun Solaris 10
x86 machine, but an error occurred related to src/lib-ldap/ldap-compare.c.
"ldap-compare.c", line 112: void function cannot return value
cc: acomp failed for ldap-compare.c
*** Error code 1
make: Fatal
It does work today, I am just bit worried that it will keep on breaking
with libressl as they evolve their API. I would personally like to avoid
more ifdef hell if possible...
Aki
On 02.11.2016 13:22, Michael A. Peters wrote:
Standard way to fix it (on the LibreSSL page) is to check for
Standard way to fix it (on the LibreSSL page) is to check for
LIBRESSL_VERSION_NUMBER - e.g. the patch attached which I think catches
them all where needed. Note the word think.
It certainly appears to be working anyway with it.
On 11/02/2016 04:07 AM, Aki Tuomi wrote:
After doing some
After doing some testing by myself, I noticed that libressl, for some
unknown reason, defines
#define OPENSSL_VERSION_NUMBER0x2000L
No idea why they decided to advertise that they are OpenSSL v2.0.0. A
local fix, if you need one, is to use
#if OPENSSL_VERSION_NUMBER == 0x2000L
Hi!
Those are used if
#if OPENSSL_VERSION_NUMBER >= 0x1010L
So (your) libressl is providing this define. We compile our code using
GCC and CLANG regularly, with OpenSSL v1.0.x which is the currently
officially supported one.
Aki
On 02.11.2016 12:34, Ruga wrote:
dovecot 2.2.26.0 uses
dovecot 2.2.26.0 uses the following functions, which are not available on
libressl 2.4.3:
HMAC_CTX_new
HMAC_CTX_free
EVP_PKEY_get0_EC_KEY
EVP_PKEY_get0_RSA
OBJ_length
EVP_MD_CTX_new
EVP_MD_CTX_free
The result of calling a non-existent function is a runtime error,
and we do not want that on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tue, 1 Nov 2016, Peter Fraser wrote:
root@BSD-11:/usr/local/etc/dovecot # doveadm auth test username
Password:
passdb: user auth succeeded
extra fields:
user=username
root@BSD-11:/usr/local/etc/dovecot #
But when I run telnet 127.0.0.1 110 and
43 matches
Mail list logo