Displaying 20 results from an estimated 200 matches similar to: "v2.2.36 to v2.3.8 maildirlock bug"
2019 Dec 06
2
v2.2.36 to v2.3.8 maildirlock bug
Hello,
Aki created this patch a while ago: http://files1.directadmin.com/services/custombuild/patches/maildirlock-crash.patch
It works perfectly to fix the issue :) Regarding dsync - I don't think it's a good replacement in all the cases, is it? We use maildirlock extensively for compression of email folders (when zlib compression is enabled in dovecot, old emails remain untouched).
--
2019 Dec 06
0
v2.2.36 to v2.3.8 maildirlock bug
On 22/10/2019 05:44, lty--- via dovecot wrote:
> Dear all,
> ? Dovecot upgraded from v2.2.36 to v2.3.8?There is no problem with the
> configuration, but the lock directory seems to have an error.
>
> [root at spam dovecot]# /usr/libexec/dovecot/maildirlock /path/to/maildir 1
> Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
> 19276[root at spam dovecot]# Error:
2019 Dec 08
1
v2.2.36 to v2.3.8 maildirlock bug
On 08 Dec 2019, at 05:58, @lbutlr <kremels at kreme.com> wrote:
> On 06 Dec 2019, at 16:28, Martynas Bendorius <martynas at martynas.it> wrote:
>> when zlib compression is enabled in dovecot, old emails remain untouched
>
> I?ve been considering doing this, or at least looking into how much space we?d save (answer so far, less than you might think), but I am hesitant to
2019 Apr 11
3
maildirlock fails
Hello,
Maildirlock seems to panic on locking:
[root at centos7 home]# /usr/libexec/dovecot/maildirlock "/home/user/imap/domain.com/email/Maildir" 10
Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xd90ee) [0x7f5bf02f10ee] -> /usr/lib/dovecot/libdovecot.so.0(+0xd9131) [0x7f5bf02f1131] ->
2018 Oct 27
2
maildirlock time unit?
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 27 October 2018 at 21:32 Kris von Mach <
<a href="mailto:mach@swishmail.com">mach@swishmail.com</a>> wrote:
</div>
<div>
2018 Oct 15
4
maildirlock time unit?
What is the time unit maildirlock will accept?
I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in:
Fatal: Invalid timeout value: 20s
And if you don't specify time unit you just get:
Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
This is on 2.3.3. 2.2 worked fine without needing time unit specified.
-------------- next part --------------
A non-text attachment
2019 Dec 08
0
v2.2.36 to v2.3.8 maildirlock bug
On 06 Dec 2019, at 16:28, Martynas Bendorius <martynas at martynas.it> wrote:
> when zlib compression is enabled in dovecot, old emails remain untouched
I?ve been considering doing this, or at least looking into how much space we?d save (answer so far, less than you might think), but I am hesitant to ?alter? the user?s mail stores without a bit more guidance.
Has anyone found a good
2019 Apr 15
0
maildirlock fails
It seems something like this has been reported already, however, I was unable to find any changelog entries or patches: http://dovecot.2317879.n4.nabble.com/maildirlock-time-unit-td65122.html
--
Best regards,
Martynas Bendorius
> On 12 Apr 2019, at 01:08, Martynas Bendorius <martynas at martynas.it> wrote:
>
> Hello,
>
> Maildirlock seems to panic on locking:
> [root
2018 Oct 27
0
maildirlock time unit?
Don't think maildirlock uses dovecot config, but sure. maildirlock is a
utility that comes with dovecot...
#? /usr/local/libexec/dovecot/maildirlock -h
Usage: maildirlock <path> <timeout>
?- SIGTERM will release the lock.
# /usr/local/libexec/dovecot/maildirlock
/home2/vpopmail/domains/swishmail.com/mach/Maildir 20s
Fatal: Invalid timeout value: 20s
#
2018 Oct 27
0
maildirlock time unit?
This appears to be a bug.
On 10/15/2018 9:46 PM, Kris von Mach wrote:
> What is the time unit maildirlock will accept?
>
> I've tried 20s, 20 sec, 20 secs, 20 seconds, all results in:
> Fatal: Invalid timeout value: 20s
>
> And if you don't specify time unit you just get:
> Panic: BUG: No IOs or timeouts set. Not waiting for infinity.
>
> This is on 2.3.3. 2.2
2020 Feb 09
5
Email Server Backup Strategy
Hello,
Was thinking it would be wise to backup my server, in case anything
"bad" ever happened, so that I could quickly get up to speed.
1. clone the whole drive -- which might be the best to ensure I keep the
whole system working.
2. But, what about, if I just wanted to backup my Email server
components? Postfix - which I think is just config files, and Dovecot -
I think there is a
2009 Oct 06
10
Binary locations
Where do you think the following binaries should be installed to? The
possible locations are:
- bin/
- sbin/
- libexec/dovecot/ (or lib/dovecot/ in most Linux distros)
So the binaries are:
1) These probably belong to bin/ or sbin/ or both:
- authtest
- dovecotpw
- doveadm
2) Binaries that you might want to call from mail_executable setting:
- rawlog
- gdbhelper
3) Index file dumping
2020 Feb 09
4
Email Server Backup Strategy
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi,
On 10/2/20 4:59 am, Francis Augusto Medeiros-Logeay wrote:
> What I do:
>
> 1 - I ran a maildirlock command to my mail folder 2 - I then rsync
> the folder where my maildirs are, as well as the indexes, to a
> remote location
If rsync is not fast... then how about doing a snapshot and then rsync
off the snapshot? (I do rsync
2009 Sep 08
1
compression script for use with zlib module
Hi,
I'm wondering if someone already implemented a compression script
(and would like to share it) based on the step-by-step provided on wiki
page of Zlib module.
I can already do some find|xargs gzip .... but couldnt implement it
completly as described on the wiki page. I know the suggested
step-by-step is very detailed and probably a must simplier will be
enough for almost
2008 Jul 24
4
v1.1.2 released
http://dovecot.org/releases/1.1/dovecot-1.1.2.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.2.tar.gz.sig
Development of new features in this release and the upcoming
multi-master replication are sponsored by Directi (www.directi.com).
Lucene indexing is currently deprecated in favor of the new Solr
indexing. I'm even considering removing the Lucene C++ library support,
so if you're
2008 Jul 24
4
v1.1.2 released
http://dovecot.org/releases/1.1/dovecot-1.1.2.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.2.tar.gz.sig
Development of new features in this release and the upcoming
multi-master replication are sponsored by Directi (www.directi.com).
Lucene indexing is currently deprecated in favor of the new Solr
indexing. I'm even considering removing the Lucene C++ library support,
so if you're
2011 Dec 24
3
Compressing existing maildirs
I've just enabled zlib for our users, and am looking at how to compress
the existing files. The routine for doing this at
http://wiki2.dovecot.org/Plugins/Zlib seems a bit complicated. What do
you think about simply doing:
find /var/vmail -type f -name "*,S=*" -mtime +1 -exec gzip -S Z -6 '{}' +
I.e. find all maildir-files:
- with size in the name ("*,S=*")
-
2016 May 18
2
mailbox.auto ignores dovecot-uidlist.lock
On 2016-05-18 11:52, Aki Tuomi wrote:
> On 18.05.2016 12:44, Tom Sommer wrote:
>> I'm trying to lock down a maildir from modifications using
>> dovecot-uidlist.lock, but when a user with mailbox.auto = create logs
>> in, then the folder is created regardless of dovecot-uidlist.lock
>> existing or not.
>>
>> Is there no way to prevent dovecot from
2020 May 29
3
Simple backup of maildir folder
Hi,
I want to do a simple backup of my maildir. I read here that maildirlock
is not to count on in the future and the recommended option was to use
doveadm backup. However, it seems that this requires to setup another
dovecot server.
My questions are:
- How much to I need to configure this new server? Do I need to setup
user by user, or even install postfix (that's where my users are
2009 Nov 12
2
Turning off "Fixed Duplicates" feature
Is there a way to disable this feature? Seems to be causing more harm then
good right now. Without getting into too much details it is fixing the
duplcates but it does not remove the old file, and the new file it creates
is not marked as read like the old one was. I understand that this problem
can be created by multiple rsyncs and files changing in between, but is
there any way that I can