search for: mcdougal

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

I noticed this today, I had a user outside of our department test out dovecot. They were using squirrelmail and I noticed that dovecot thinks this user is subscribed to ALL public folders even though a dovecot ACL prevents all access. I'm pretty sure access is still denied. I was able to reproduce this with a guest account I added: l lsub "" "#shared/decs/%" * LSUB

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

I've been looking for a variable I can use in my dovecot.conf within the INDEX= setting so I can have one index dir per imap server on NFS. I've been looking at http://wiki.dovecot.org/Variables but no variable seems to contain something like server hostname, and I've been hunting for the variable expansion code in dovecot but haven't been able to find it. %l (local IP) won't

I have some public mailboxes setup in 1.0.0, location = maildir:/egr/mail/shared/org:CONTROL=%h/Maildir/dovecot/public/control/org:INDEX=%h/Maildir/dovecot/public/indexes/org I also have a dovecot-shared file in the maildir folders so messages that are added to the inbox get a decent set of default permissions. However, I think dovecot is also trying to fchown the index files (stored in a user

I noticed this in an earlier beta and took a note, and I still see it sometimes in 1.1b4, but it is only occasional so I have not tracked down yet what dovecot is doing. Just a FYI for the list incase others see it and to say that its an issue I tend to track down that I did not see in 1.0, and its been low on my list until now. Sometimes when I login to dovecot and read a message from an imap

I just started testing 1.2.3 then 1.2.4 this week, I was too busy earlier in the year to look at 1.2 at all. So far so good except I noticed newly granted permissions via ACL on some newly created public mailboxes were not visible by the client. It seemed to be a version thing because the same files work fine concurrently on a server running 1.1.x. I came across this in the ACLwiki which

I think today just due to increased use, my mail servers hit login_max_processes_count. It wasn't obvious what was happening, logins just weren't acting like they should and sometimes would get disconnected before given a prompt from the server. Something made me think to check if I had too many of certain dovecot processes and I found I had 128 imap-login processes on both servers,

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

Early next week I need to upload over 100,000 emails to an IMAP server as quickly as possible from an Outlook client. I am looking for any methods I can use to (temporarily?) speed up the rate at which dovecot can accept and store IMAP uploads, whether it be storing on local disk, ram disk, etc. I can setup a temporary server on a laptop for example and once the upload has finished I can use

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

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)

Can someone, more learned in the ways of dtrace point me at what to look at to help understand why the kernel on one machine is using tons of memory, while another machine doing the same task/same user load is not. swapinfo for the "afflicted" machine shows RAM _______Total 16384 Mb RAM Unusable 73 Mb RAM Kernel 9226 Mb RAM Locked 2 Mb RAM Used

My config has folders show up in the root namespace as well as hidden ones like mail/ for compat. In thunderbird when I set the namespace prefix to mail/, I effectively cannot subscribe to folders. You can pull up the folder list, select some folders to subscribe to, hit okay, and nothing changes in thunderbird: 3 subscribe "mail/Spam" 3 OK Subscribe completed. 4 lsub ""

A user alerted me to a problem when he renamed an upper level mail folder and lost access to a lower level folder under it. I tried with and without listescape, it didn't seem to make a difference, and I saw no errors in the dovecot log. Symptoms are if a client has a maildir folder tree .a and .a.b and renames a to c in their client, Thunderbird shows c/b but b is inaccessible since it

This happened from one user near noon on the 17th and 19th (today) of this month. From the backtrace it looks like they were searching, but I won't know for sure unless I need to ask them. Is this possibly fixed already? I just haven't upgraded dovecot in a while due to lack of problems. The sig11 happened a few dozen times, a few seconds apart each day. I have one coredump from

I am testing dovecot 1.1 betas on a testing system, hoping to take advantage of self repairing and NFS-capable indexes when 1.1 is sensible to put into production. I ran into a number of issues that I did not have with 1.0, and I think I'll just pick one or more at a time and report them rather than try to report every single issue at once, hoping that some of the fixes will solve more than

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

I noticed the following this week. No idea how long its been happening because I have not tested deleting folders hardly at all. Steps to reproduce: 1. Create a folder "NewFolder", click on it in thunderbird so an index dir is created: ls -ldi Maildir/.NewFolder/ 1504062 drwx------ 5 mcdouga9 egrstaff 4096 Nov 16 19:44 Maildir/.NewFolder/ ls -ldi

I haven't seen this before 1.1b16, it happened to two users today while they were searching using fts. Feb 18 16:41:36 hill dovecot: IMAP(username): file buffer.c: line 288 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) Feb 18 16:41:36 hill dovecot: child 53560 (imap) killed with signal 6 I can probably narrow it down to an example mail if needed. GNU gdb 6.1.1