similar to: Which is the imap root directory? Conflicting documentation...

I have dovecot-0.99.10.5 on Fedora Core 2 installed and otherwise operating using Maildir format for the folders, Kmail as the email client. Got through all the ssl and other security configuration fine, but have one last problem: I can't read the incoming mail from /var/spool/mail/%u. Tried several 'default_mail_env' settings, including none at all, to no avail. When I try to

I get the following error message in my syslog frequently when a user accesses the dovecot (IMAP) server from his OS X AppleMail client: Nov 24 09:45:42 myhost imap(someuser): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) Nov 24 09:45:42 myhost dovecot: child 23277 (imap) killed with signal 6 Usually each message appears 5-6

https://bugzilla.mindrot.org/show_bug.cgi?id=2542 Bug ID: 2542 Summary: Conflicting usernames by -l, -o user, user@ - it's not clear which one is used Product: Portable OpenSSH Version: 6.7p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5

Hi sambalist, I set up a new test environment to test the problem. still the same result. It seems that if I didn't give administrator a uidNumber in unix attributes and only map this user to root. it can manage the share folder in fsmgmt.msc, but after I remove everyone's share permission and add share permissions to domain admins full control domain users RW then, the administrator

Hi Rowland , I have followed the wiki's step, the DNS works OK and I have use the fileserver for 2 years. here's a share folder "IT"'s acl getfacl IT/ # file: IT/ # owner: root # group: domain\040admins user::rwx user:root:rwx group::rwx group:domain\040admins:rwx group:it:rwx mask::rwx other::--- default:user::rwx default:user:root:rwx default:group::---

Greetings, Is there a mechanism (or relatively small source-code change) which would cause Dovecot to evaluate IMAP prefixes relative to $HOME rather than the configured IMAP root? * * * Background: We're currently migrating from a WU-IMAP mailserver configuration which stores user mail in a global NFS-exported $HOME, and we've run into well-known issues handling client-specified IMAP

I'm trying to set up dovecot to use /home/username as IMAP root, but it keeps creating /home/username/mail. I need /home/username in order to migrate with the least changes from uw-imap, just by copying .mailboxlist without the INBOX line in it into .subscriptions I tried each of these, one at a time: default_mail_env = mbox:~/:INBOX=/var/mail/%u default_mail_env =

Dear reader, Please help me find a way through this problem, I have CentOS 4.2, dovecot-0.99.11-4.EL4, squirrelmail-1.4.8, While I try to log in as Root (username: root; password: password) I get the error that says, > ERROR: Connection dropped by IMAP server. > Query: CAPABILITY > Content of the file /var/log/maillog is as follows > Jun 7 12:56:59 PBX sendmail[5170]:

Dear Dovecot experts, I'm in the process of setting up dovecot with mbsync as a local cache for remote IMAP servers. One recipe that I found involves using the /usr/lib/dovecot/imap (This is with Debian's dovecot package). For example, in .mbsyncrc I have IMAPAccount cwg-wf-local RequireSSL no Tunnel "/usr/lib/dovecot/imap -o mail_location=maildir:/home/cwg/.mail/cwg-wf"

Hi, I thought I had this problem licked but there still is a rights problem with ARI and Asterisk when using a non-root user (Following the wiki at http://www.voip-info.org/tiki-pagehistory.php?page=Asterisk+non-root&diff2=25). When I issue the following: chmod --recursive u=rwX,g=rX,o= /var/spool/asterisk The above command results in the following rights on messages: msg0000.gsm

Hi, I hope someone can point me in the right direction here. I am migrating a mailbox from a non cPanel server, and the mailboxes have folders which seem to be at the same level as the Inbox. The users access these mailboxes using IMAP. The new server configuration is Exim > Dovecot 1.2.17 > Maildir with the standard cPanel install settings. dovecot -n output below I have created the new

I just noticed these messages in my logs : modprobe:1998 conflicting memory types e8000000-e8010000 uncached-minus<->write-combining reserve_memtype failed 0xe8000000-0xe8010000, track uncached-minus, req uncached-minus ioremap reserve_memtype failed -16 Xorg:5078 conflicting memory types e8000000-e8010000 uncached-minus<->write-combining reserve_memtype failed 0xe8000000-0xe8010000,

Hello, I want to test Shorewall''s IPsec feature. It requires patched netfilter (and kernel but that''s another story). I didn''t want to replace my distribution''s iptables package with my own compilation so I installed it to another prefix. Now Shoreall uses the iptables command found first in $PATH. I don''t think this is the most elegant way. I

http://bugzilla.mindrot.org/show_bug.cgi?id=532 Summary: Conflicting basename and dirname on solaris Product: Portable OpenSSH Version: 3.6p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: openssh-unix-dev at mindrot.org

Hi all, Why are these two passes conflicting: UnifyFunctionExitNodes and LowerSwitch? AU.addRequired(LowerSwitchID) works, so does AU.addRequired<unifyFunctionExitNodes>(), but the two together don't... opt: PassManagerT.h:387: void llvm::PassManagerT<Trait>::markPassUsed(const llvm::PassInfo*, llvm::Pass*) [with Trait = llvm::MTraits]: Assertion `getAnalysisOrNullUp(P)

Duncan, Is there a long term plan for handling the conflicting c++ libraries in building dragonegg? In particular, as vendors switch their clang++ system compilers to default to -stdlib=libc++, the resulting builds of llvm against those compilers will be using the libc++ ABI but the dragonegg plugin will still need to be built against the libstdc++ ABI. For now, the only work-around appears to

Hello, I get this error building ash (with gcc 3.4.2): trap.c:398: error: conflicting types for 'onsig' trap.h:43: error: previous declaration of 'onsig' was here trap.c:398: error: conflicting types for 'onsig' trap.h:43: error: previous declaration of 'onsig' was here trap.c: In function `onsig': trap.c:399: warning: passing arg 2 of `bsd_signal' from

Hi I am trying to build the llvm tools following the instructions here: http://llvm.cs.uiuc.edu/docs/CFEBuildInstrs.html But I get this error: /zalloc.c:9: error: conflicting types for 'malloc' I am using gcc 3.4.1 What can be the problem? __________________________________ Do you Yahoo!? Yahoo! Sports - Sign up for Fantasy Baseball. http://baseball.fantasysports.yahoo.com/

Hi Andrew, > This should really be in the FAQ. But sufice to say if you make > your pass a function pass, you will be fine. > Andrew Thx for you reply. I think I can squeeze everything into a function pass, but I'd like to run this by you, just in the case I mixed-up something: (Chris, I'd also appreciate you wise thoughts on this. I'm sure that other users are banging

Hi Jack, On 29/08/13 18:35, Jack Howarth wrote: > Duncan, > Is there a long term plan for handling the conflicting c++ libraries in building > dragonegg? In particular, as vendors switch their clang++ system compilers to default > to -stdlib=libc++, the resulting builds of llvm against those compilers will be using > the libc++ ABI but the dragonegg plugin will still need to be