a workaround you can create a directory named /srv/mail/c and make 16
symbolic links to it: /srv/mail/c0, /srv/mail/c1, /srv/mail/c2, up to /srv/
mail/cf.
In that way you can use truncate=8.
--
Simone Lazzaris
QCom SpA
#x27;m trying to fool him expanding the '%' into '%%' on the password
query, but without luck... I can also contact the user and make him choose a
different password, without '%'.
Anyway, I feel that this behaviour should be seen as a bug. Am I missing
something?
--
Simone Lazzaris
QCom SpA
hich backend?
Right now the "quota" subcommands are not recognised.
Thanks--
*Simone Lazzaris*
*Qcom S.p.A. a Socio Unico*
Via Roggia Vignola, 9 | 24047 Treviglio (BG)T +39 0363 47905 | D +39 0363
1970352
simone.lazza...@qcom.it[1] | www.qcom.it[2]
* LinkedIn[3]* | *Facebook*[4]
--
that iterates over the users, asks to
the frontend (via
doveadm http) which is the current backend, and then connect (again, doveadm
http) to
that to perform the recalculation.
A bit slow but working.
--
*Simone Lazzaris*
*Qcom S.p.A. a Socio Unico*
Via Roggia Vignola, 9 | 24047 Trevi
doveadm quota recalc -A" on the directors, because the quota
plugin is
enabled only on the backends.
I can parse the user mapping on the directors and split the calculation, one
user a time, on
the backends, but I feel I'm choosing a overly complicated path.
So.... which is the
Hi all;
I've just compiled version 2.2.36.1 on a new debian buster (debian 10) and it
seems that
this patch
https://github.com/dovecot/core/commit/
63a74b9e8e0604486a15a879e7f1a27257322400.patch
is needed to make it work.
Without the patch, the authentication segfaults.
*Simone Laz
gt; <https://github.com/dovecot/core/commit/c0583917fe760b2d901acf83387cc8edb6f
> 99550>
You nailed it!
I've applied the fix from commit c058 and that solved the issue. I'm no longer
able to crash
the director by stopping/starting a backend.
*Simone Lazzaris*
*Qcom S.p.A.*
In data mercoledì 19 settembre 2018 09:30:47 CEST, Timo Sirainen ha scritto:
> On 18 Sep 2018, at 15.15, Simone Lazzaris wrote:
> > I've got a core dump, and here is the backtrace. Let me know if you want
> > the core file.
> It would be useful if we're able to u
;
libdovecot-ssl.so.0.0.0
-rwxr-xr-x 1 root staff 1284527 Jun 17 2016
/usr/local/lib/dovecot/libdovecot-ssl.so.0.0.0
Can that be the ultimate cause?
*Simone Lazzaris*
*Qcom S.p.A.*
simone.lazza...@qcom.it[1] | www.qcom.it[2]
* LinkedIn[3]* | *Facebook[4]*
[5]
[1] mailto:sim
:223
#10 0xb7661496 in io_loop_handler_run (ioloop=ioloop@entry=0x82bd648) at
ioloop.c:649
#11 0xb7661658 in io_loop_run (ioloop=0x82bd648) at ioloop.c:624
#12 0xb75da45e in master_service_run (service=0x82bd578,
callback=callback@entry=0x804d360 ) at master-service.c:719
#13 0x0804cf5e in main (argc=1,
bytes out=56, 2940+0 USERs received,
last input
0.000 s ago, last output 0.006 s ago, connected 0.006 s ago, 0 peak output
buffer size,
0.004 CPU secs since connected)
I can confirm that I can trigger the issue having one of the backends flapping
down/up.
*Simone Lazzaris*
*Qcom S
> Hi all, again;
>
> I've enabled the core dumps and let it go for some day waiting for the issue
> to reoccur.
>
> Meantime I've also upgraded the poolmon script, as Sami suggested.
>
> It seems that the upgrade has scared the issue away, because it no longer
> occurred.
>
> Maybe the problem
In data martedì 11 settembre 2018 10:46:30 CEST, Timo Sirainen ha scritto:
> On 11 Sep 2018, at 10.57, Simone Lazzaris wrote:
> > Sep 11 03:25:55 imap-front4 dovecot: director: Panic: file
> > doveadm-connection.c: line 1097 (doveadm_connection_deinit): assertion
&g
In data martedì 11 settembre 2018 10:46:30 CEST, Timo Sirainen ha scritto:
> On 11 Sep 2018, at 10.57, Simone Lazzaris wrote:
> > Sep 11 03:25:55 imap-front4 dovecot: director: Panic: file
> > doveadm-connection.c: line 1097 (doveadm_connection_deinit): assertion
&g
In data lunedì 10 settembre 2018 09:58:50 CEST, Timo Sirainen ha scritto:
> On 8 Sep 2018, at 15.18, Simone Lazzaris wrote:
> > Timo, unfortunately the patch doesn't compile; I've moved the declaration
> > of "conn" one line up to make it work.
>
> O
In data lunedì 10 settembre 2018 09:58:50 CEST, Timo Sirainen ha scritto:
> On 8 Sep 2018, at 15.18, Simone Lazzaris wrote:
> > Timo, unfortunately the patch doesn't compile; I've moved the declaration
> > of "conn" one line up to make it work.
>
> O
In data venerdì 7 settembre 2018 19:11:24 CEST, Timo Sirainen ha scritto:
> On 7 Sep 2018, at 19.43, Timo Sirainen wrote:
> > On 7 Sep 2018, at 16.50, Simone Lazzaris mailto:s.lazza...@interactive.eu>> wrote:
> >> Some more information: the issue has just occurr
In data venerdì 7 settembre 2018 18:43:36 CEST, Timo Sirainen ha scritto:
Hi Timo;
it happened again, this time on a "high-performance" instance (e.g., WITH
service_count=0)
> On 7 Sep 2018, at 16.50, Simone Lazzaris wrote:
> > Some more information: the issue has just oc
service, restores
the correct behaviour.
*Simone Lazzaris*
*Qcom S.p.A.*
simone.lazza...@qcom.it[1] | www.qcom.it[2]
* LinkedIn[3]* | *Facebook[4]*
[5]
[1] mailto:simone.lazza...@qcom.it
[2] https://www.qcom.it
[3] https://www.linkedin.com/company/qcom-spa
[4] http://www.
In data venerdì 7 settembre 2018 11:20:49 CEST, Sami Ketola ha scritto:
> > On 7 Sep 2018, at 11.25, Simone Lazzaris wrote:
> > Actually, I have a poolmon script running that should drop vhost count for
> > unresponsive backends; the strage thing is, the backends are NOT
>
In data venerdì 7 settembre 2018 10:06:00 CEST, Sami Ketola ha scritto:
> > On 7 Sep 2018, at 11.00, Simone Lazzaris
> > wrote:
> >
> >
> > The only suspect thing is this:
> >
> > Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> >
In data venerdì 7 settembre 2018 10:06:00 CEST, Sami Ketola ha scritto:
> > On 7 Sep 2018, at 11.00, Simone Lazzaris
> > wrote:
> >
> >
> > The only suspect thing is this:
> >
> > Sep 6 14:45:41 imap-front13 dovecot: director: doveadm: Host
> >
rector: doveadm: Host 192.168.1.219
vhost count changed from 100 to 0
Nothing on the other system logs (e.g. kernel, daemon, syslog, messages ).
--
*Simone Lazzaris*
*Qcom S.p.A.*
Hi all;
I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the
upgrade I've got some instability: a few time per day per server, seemly at
random, the auth process stop responding and the clients cannot authenticate
any more:
Sep 6 14:45:51 imap-front13 dovecot: pop3-login:
Hi all;
I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the
upgrade I've got
some instability: a few time per day per server, seemly at random, the auth
process stop
responding and the clients cannot authenticate any more:
Sep 6 14:45:51 imap-front13 dovecot: pop3-login
postfix, you can check out my simple
daemon:
https://github.com/SimoneLazzaris/polka
It's written in go, very simple, efficient but effective. We're using in
production with zero
issues.
*Simone Lazzaris*
*Qcom S.p.A.*
simone.lazza...@qcom.it[1] | www.qcom.it[2]
* LinkedIn[3]* | *F
In data martedì 16 ottobre 2012 03:41:14, Timo Sirainen ha scritto:
> On 15.10.2012, at 16.13, Simone Lazzaris wrote:
> > Problem is, if I execute the update on the backend, I miss the information
> > regarding the original IP, as I only see the IP of the proxies.
>
> This
.
But I'd really prefer to create a plugin, that I'd be willing to share.
I attach the configuration of the servers (front and back) generated via
postfix -n.
Thanks in advance for any help.
--
Simone Lazzaris | Responsabile aree datacenter e VoIP Interactive Network srl
| via Rog
28 matches
Mail list logo
