Displaying 20 results from an estimated 500 matches similar to: "unlink_directory(....Trash.NewFolder) failed: Directory not empty"
2007 Nov 06
3
Various uidlist and index errors with 1.1 on NFS
Two nights ago I took a leap and extended my testing of dovecot 1.1 by
replacing 1.0 for the approx 15 users I had on 1.0. At that time I also
for the first time tried dovecot 1.1 in a load balanced 2 server configuration
with indexes on NFS. I was hoping I did this right, using the mail_nfs params
and 1.1 so fchown etc would flush the access cache, but I am getting a number
of messages and
2007 Oct 21
3
assertion failed: (mailbox_list_is_valid_existing_name(_list, name))
When I was initially testing dovecot 1.1b2,3 I had ACLs turned on and encountered
this problem below. I had them turned off until now, I'll need to have ACLs working
before I can widen testing. I'm not sure how to make "env MAIL=maildir:~/Maildir gdb
/tmp/imap" load the ACL plugin so I assume that is why it does not crash; not getting
any log either from that, maybe I made a
2007 May 25
2
Quick question on multiple access to dovecot indexes
I have up to 4 servers that will run dovecot behind a load balancer, which means
the same user might be accessing the same mailbox from multiple servers, and it
seems like dovecot doesn't like multiple access to the dovecot indexes for the
one user since I currently have them stored in a nfs home directory. Is this
a bad thing? Must I keep a seperate index location per server?
Just today
2007 Nov 17
1
crash with fts_squat on an identified email
I have some folders with a good amount of spam. While demonstrating full text search to a user,
we found a folder that would crash dovecot while doing a fts. While splitting up the mailbox to
narrow it down, I found there are a good number of messages in that folder that all made it crash
in the same manner. I figured I'd narrow down a single one, get that fixed, then retest the rest.
I
2007 May 07
6
Dovecot not handling r/o mailboxes completely, and problem with ACL as a workaround
First of all, I think dovecot is really fantastic and I have thanks for all
the hard work. I think it will be the best fit for my ~5000 users when I
have it setup completely. We normally have approx 500 concurrent IMAP
connections during the day.
I am trying to convert from courier-imap to dovecot, but I have an issue with
public namespace folders that are not writable by certain users.
2008 Feb 06
1
imap fs quota (rpc) won't work?
In the past I dabbled with the imap quota plugin with the fs backend
because I wanted
to report usage to my users (not limit them). At the time, the quota
plugin would make
dovecot crash when trying to write to a folder (I can bring up this
report if needed).
However, in a later beta of dovecot 1.1 I tried quota again but I cannot
get it to report
any results. I've been wanting to use
2007 Oct 27
4
do 1.1b4 assertion failed: (mailbox_list_is_valid_existing_name
I think this is where I left off last weekend. Instead of this happening at the base
of one of my shared mail namespaces, it happens when I try to select a top level folder
inside the namespace, or try to directly select an entire path to a folder. This only
happens when ACL is enabled. Let me know if I need to provide more. Thanks.
Oct 27 16:03:27 gribble dovecot: IMAP(mcdouga9): file
2008 Feb 06
2
(message_parse_header_next): assertion failed:, +(IS_LWSP(line->value[0])) 1.1beta14
I noticed these happen when one of my users searches his Trash folder
which he doesn't empty.
He uses thunderbird and it is reproducable.
Feb 5 22:47:39 boomhauer dovecot: IMAP(username): file
message-header-parser.c: line 350 (message_parse_header_next): assertion
failed:
+(IS_LWSP(line->value[0]))
Feb 5 22:47:41 boomhauer dovecot: child 8022 (imap) killed with signal 6
Feb 5
2007 Oct 27
2
Segfault when opening a public folder, dovecot 1.1 beta4
I was trying to debug this with gdb, but I'm not sure how to make
env MAIL=maildir:~/Maildir MAIL_PLUGINS=acl ACL=vfile gdb /tmp/imap
understand the #shared/decs namespace from below so I can SELECT it.
I have a number of maildirs under #ahared/decs, I tried opening at least
2 of them but dovecot gives sig 11 without a direct error about the problem.
I don't think this was exactly the
2007 Oct 27
2
dovecot 1.1b4 not listing public folder children
ACL plugin still disabled. The folders listed below definitely do have Children.
telnet session problem example in 1.1b4:
* OK Dovecot ready.
? login mcdouga9 password
? OK Logged in.
9 LIST "" "#shared/decs/%"
* LIST (\HasNoChildren) "/" "#shared/decs/support"
* LIST (\HasNoChildren) "/" "#shared/decs/receipts"
* LIST (\HasNoChildren)
2008 Mar 09
2
1.1r1: auth-worker(default): BUG: PASSV had missing parameters, sig11
I don't know how this happened. I'm not sure if there is a coredump
somewhere because
I don't know what user, and I have nothing for 'root' or 'dovecot'. Any
advice, or should
I make all my coredumps go to a central writable directory so I have
better chance of
catching it if it happens again? Is it maybe from someone connecting to
postfix and causing
a SMTP-AUTH
2008 May 06
1
FETCH for mailbox INBOX UID 5003 got too little data: 5369 vs 38919
This happened a while back, I was running 1.1rc3 up until today so I have no idea
if it would have an effect. Sorry if its something that has been fixed. The
error below was repeated many many times, I deleted the index so the user would
stop getting disconnected (although I didn't hear any complaints). I have not
seen this happen repeatedly in this manner to any other user yet.
Apr 15
2007 Oct 21
2
two small low importance issues in 1.1b
Item 1:
I store the indexes and control in their own directory.
I noticed in 1.1:
1192 ./private/indexes/.INBOX
32 ./private/indexes/.Trash
1228 ./private/indexes
4 ./private/control/.INBOX/.INBOX
84 ./private/control/.INBOX
4 ./private/control/.Trash/.Trash
12 ./private/control/.Trash
100 ./private/control
1332 ./private
.INBOX/.INBOX and .Trash/.Trash
2011 Aug 24
1
unlink_directory failed with 'Device or resource busy' on NFS
Hi,
I'm getting some errors while I'm trying to move mailboxes from IMAP server to Outlook client. The error message is "IMAP command is failed" and I think it is useless.
Here are the error messages written to server's syslog.
imap(name at domain.com<mailto:name at domain.com>): Error: unlink_directory(/data/domain.com/name/INBOX/direct/.nfs00000000000033fd000000cd)
2012 Dec 05
1
Error: unlink_directory(.../lucene-indexes) with doveadm index
Hi,
Per discussion on this previous thread:
http://dovecot.org/pipermail/dovecot/2012-October/068849.html
I am updating search indexes on all my mailboxes via a nightly cronjob that
runs: doveadm index -A '*'
The problem we're running into is that random mailboxes will throw the
following error during the update (sanitized to conceal actual domain name):
doveadm(user at
2008 Jul 16
2
1.1.1 (maildir_uidlist_sync_update): assertion failed: (uidlist->initial_hdr_read)
Version: 1.1.1
OS: FreeBSD 7.0-STABLE amd64
I have only seen this happen twice so far. I do not know what the two
users were doing to cause it.
Jun 26 17:23:26 hill dovecot: IMAP(userA): Invalid transaction log size
(32812 vs 32920): /home/userA/Maildir/dovecot/private/indexes/.Deleted
Messages/dovecot.index.log
Jun 26 17:23:26 hill dovecot: IMAP(userA): Invalid transaction log size
(32812
2019 Mar 08
2
Writing unit tests - how to test re-orderable blocks...
I’m not sure if it’s truly deterministic. It always gives the same results (so far) on my machine but I’m not sure that’s enough.
My guess is it’s probably going to be deterministic on one machine but might well not be deterministic across environments. Like it might give varying results if cross compiled on different hosts, macOS vs intel Linux vs arm vs s390. (Obviously AVR is always a cross
2019 Mar 07
5
Writing unit tests - how to test re-orderable blocks...
We have a test that looks like this…
define void @array16_store() {
; CHECK-LABEL: array16_store:
; CHECK: ldi [[REG1:r[0-9]+]], 204
; CHECK: ldi [[REG2:r[0-9]+]], 170
; CHECK: sts int.array+3, [[REG2]]
; CHECK: sts int.array+2, [[REG1]]
; CHECK: ldi [[REG1:r[0-9]+]], 187
; CHECK: ldi [[REG2:r[0-9]+]], 170
; CHECK: sts int.array+1, [[REG2]]
; CHECK: sts int.array, [[REG1]]
; CHECK: ldi
2016 Mar 15
2
static vs shared modules build
> it may make sense to build others which you really use on every
> machine statically to not need to add them in your smb.conf
That's what I expected, too. Since then I made some experiences. I built
samba 4.3.6 with a static vfs_acl_xattr module. It is builtin alright,
it is listed under "Builtin modules" at the output of "smbd -b".
Then:
-- Comment"vfs
2016 Mar 15
0
static vs shared modules build
Am 15.03.2016 um 21:07 schrieb Miguel Medalha:
>
>> it may make sense to build others which you really use on every
>> machine statically to not need to add them in your smb.conf
>
> That's what I expected, too. Since then I made some experiences. I built
> samba 4.3.6 with a static vfs_acl_xattr module. It is builtin alright,
> it is listed under "Builtin