Displaying 20 results from an estimated 10000 matches similar to: "More and better logging"
2018 Jun 29
2
v2.3.2 released
On 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote:
>
> On 2018-06-29 14:51, Timo Sirainen wrote:
>
>> v2.3.2 is mainly a bugfix release. It contains all the changes in
>> v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only
>> bugs). Binary packages are already in https://repo.dovecot.org/
>
> A simple "yum update"
2018 Jun 29
1
v2.3.2 released
On 29 Jun 2018, at 15.28, Tom Sommer <mail at tomsommer.dk> wrote:
>
> On 2018-06-29 15:20, Timo Sirainen wrote:
>> On 29 Jun 2018, at 15.05, Tom Sommer <mail at tomsommer.dk> wrote:
>>> On 2018-06-29 14:51, Timo Sirainen wrote:
>>>> v2.3.2 is mainly a bugfix release. It contains all the changes in
>>>> v2.2.36, as well as a bunch of other
2018 Jul 10
1
v2.3.2.1 released
On 10 Jul 2018, at 10.40, Tom Sommer <mail at tomsommer.dk> wrote:
>
> On 2018-07-09 16:48, Timo Sirainen wrote:
>> https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz
>> https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig
>> v2.3.2 still had a few unexpected bugs:
>> - SSL/TLS servers may have crashed during client disconnection
>> - lmtp:
2018 Jul 09
2
v2.3.2.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig
v2.3.2 still had a few unexpected bugs:
- SSL/TLS servers may have crashed during client disconnection
- lmtp: With lmtp_rcpt_check_quota=yes mail deliveries may have
sometimes assert-crashed.
- v2.3.2: "make check" may have crashed with 32bit systems
2018 Jul 09
2
v2.3.2.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig
v2.3.2 still had a few unexpected bugs:
- SSL/TLS servers may have crashed during client disconnection
- lmtp: With lmtp_rcpt_check_quota=yes mail deliveries may have
sometimes assert-crashed.
- v2.3.2: "make check" may have crashed with 32bit systems
2018 Jun 29
9
v2.3.2 released
https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig
v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). Binary packages are already in https://repo.dovecot.org/
* old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while
opening
2018 Jun 29
9
v2.3.2 released
https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz
https://dovecot.org/releases/2.3/dovecot-2.3.2.tar.gz.sig
v2.3.2 is mainly a bugfix release. It contains all the changes in v2.2.36, as well as a bunch of other fixes (mainly for v2.3-only bugs). Binary packages are already in https://repo.dovecot.org/
* old-stats plugin: Don't temporarily enable PR_SET_DUMPABLE while
opening
2018 Oct 05
2
VOLATILEDIR not really used?
On 2018-10-05 11:35, Timo Sirainen wrote:
> On 4 Oct 2018, at 17.13, Tom Sommer <mail at tomsommer.dk> wrote:
>>
>>
>> On 2018-10-04 15:55, Timo Sirainen wrote:
>>> On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote:
>>
>>>> Is this correct, and if so are there any plans to move dotlocks etc.
>>>> to this
2016 Apr 07
2
Opportunistic quota recalc
On 07 Apr 2016, at 14:49, Tom Sommer <mail at tomsommer.dk> wrote:
>
> On 2016-04-06 21:09, Tom Sommer wrote:
>> On 2016-04-06 20:38, Timo Sirainen wrote:
>>> On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote:
>>>> I'm switching quota backend to redis (from maildir++), so all my current usages are reset.
>>>> I get that
2018 Oct 04
2
VOLATILEDIR not really used?
On 2018-10-04 15:55, Timo Sirainen wrote:
> On 4 Oct 2018, at 14.39, Tom Sommer <mail at tomsommer.dk> wrote:
>> Is this correct, and if so are there any plans to move dotlocks etc.
>> to this directory?
>
>
> What dotlocks? I guess mbox and Maildir have some locks that could be
> moved there, but a better performance optimization for those
> installations
2016 Apr 06
2
Opportunistic quota recalc
On 2016-04-06 20:38, Timo Sirainen wrote:
> On 06 Apr 2016, at 13:43, Tom Sommer <mail at tomsommer.dk> wrote:
>>
>> I'm switching quota backend to redis (from maildir++), so all my
>> current usages are reset.
>>
>> I get that I can do "doveadm quota recalc -A", but it takes forever
>> (and auth processes time out/crash).
>>
2016 Apr 05
2
New feature: HTTP API
On 2016-04-05 08:44, aki.tuomi at dovecot.fi wrote:
>> On April 5, 2016 at 9:27 AM Tom Sommer <mail at tomsommer.dk> wrote:
>>
>>
>> On 2016-04-04 20:22, aki.tuomi at 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
2018 Oct 22
2
Calendar function ?
On Mon, 22 Oct 2018 19:48:17 +0200
Tom Sommer <mail at tomsommer.dk> wrote:
> On 2018-10-22 12:56, Mar?a Arrea wrote:
>
> > We use sabredav for caldav+cardav and roundcube+agendav for nice
> > web ui :)
>
>
> Is Sabre still maintained?
http://sabre.io/ says 2018 is most recent version
--
In modern fantasy (literary or governmental), killing people is the
2016 May 04
2
more info about deleting users
> On May 2, 2016 at 9:56 AM Tom Sommer <mail at tomsommer.dk> wrote:
>
>
>
> On 2016-04-29 16:25, Matteo Gaito Test Account wrote:
>
> > i've search a lot in order to find a way to delete account by dovecot
> > but i
> > found only this way
> >
> > http://dovecot.org/list/dovecot/2011-November/079273.html
> >
> > It's
2006 Apr 27
4
auth-request.c: assertion failed: (*name != '\0')
I upgraded to beta7 from alpha4, and got this error during the auth process:
dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3
lip=0.0.0.0 rip=0.0.0.0 resp=<hidden>
dovecot: auth-worker(default): sql(webmaster at example.com,0.0.0.0): query:
SELECT username as user, NULL as password FROM users WHERE username =
'webmaster at example.com' AND
2017 May 18
2
lmtp segfault after upgrade
On 18.05.2017 10:55, Tom Sommer wrote:
> On 2017-05-18 09:36, Teemu Huovila wrote:
>> Hello Tom
>>
>> On 02.05.2017 11:19, Timo Sirainen wrote:
>>> On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote:
>>>>
>>>> (gdb) bt full
>>>> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298
>>>>
2017 May 01
2
lmtp segfault after upgrade
> On May 1, 2017 at 8:26 PM Aki Tuomi <aki.tuomi at dovecot.fi> wrote:
>
>
>
> > On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote:
> >
> >
> > I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg
> > and /var/log/messages are getting flooded by these errors:
> >
> > lmtp[45758]: segfault at
2017 May 02
4
lmtp segfault after upgrade
On 2017-05-02 09:35, Aki Tuomi wrote:
> On 2017-05-02 10:20, Tom Sommer wrote:
>> On 2017-05-01 19:26, Aki Tuomi wrote:
>>>> On May 1, 2017 at 8:21 PM Tom Sommer <mail at tomsommer.dk> wrote:
>>>>
>>>>
>>>> I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my
>>>> dmesg
>>>> and /var/log/messages
2017 May 18
3
lmtp segfault after upgrade
Hello Tom
On 02.05.2017 11:19, Timo Sirainen wrote:
> On 2 May 2017, at 10.41, Tom Sommer <mail at tomsommer.dk> wrote:
>>
>> (gdb) bt full
>> #0 i_stream_seek (stream=0x21, v_offset=0) at istream.c:298
>> _stream = <value optimized out>
>> #1 0x00007fe98391ff32 in i_stream_concat_read_next (stream=0x1efe6c0) at istream-concat.c:77
>>
2016 Apr 05
2
New feature: HTTP API
> On April 5, 2016 at 12:24 PM aki.tuomi at dovecot.fi wrote:
>
>
>
> > On April 5, 2016 at 9:57 AM Tom Sommer <mail at tomsommer.dk> wrote:
> >
> >
> > On 2016-04-05 08:44, aki.tuomi at dovecot.fi wrote:
> > >> On April 5, 2016 at 9:27 AM Tom Sommer <mail at tomsommer.dk> wrote:
> > >>
> > >>
> >