similar to: Inbox weirdness

Hi I am trying to install 1.0 stable from source on a test server running 0.99 on FC3. i did basic ./configure etc and get this result Jul 13 17:24:26 proteus4 dovecot: Dovecot v1.0-stable starting up Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): open(/var/spool/mail/.temp.proteus4.4485.e3eec7b26a559bac) failed: Permission denied Jul 13 17:24:35 proteus4 dovecot: POP3(obantec):

Hi all: I have a problem running my dovecot server. I get the following error message when trying to get mail from my account with INBOX in /var/spool/mail/tanim (username tanim). Nov 22 19:23:00 phobos imap(tanim): file_lock_dotlock() failed with mbox file /var/spool/mail/tanim: Permission denied What permissions should I set for the mailbox? I am running dovecot-0.99.11-1.1. Tanim --

Hi Ignacio, I'm running Centos 4.2 on some machines and just wonder which is the correct procedure to build one of your packages i've fonund in the fedora.ivazquez.net for FC4 but for CentOs for kernel-modules: http://fedora.ivazquez.net/yum/4/i386/SRPMS.ivazquez/kernel-module-qc-usb-0.6.3-0.iva.1.src.rpm

dovecot: Oct 05 16:03:07 Info: imap-login: Login: user=<kartagis>, method=plain, rip=212.98.201.1, lip=192.168.1.2 dovecot: Oct 05 16:03:07 Error: IMAP(kartagis): open(/var/mail/.temp.kunduz.org.14095.855b9feb950c2c78) failed: Permission denied dovecot: Oct 05 16:03:07 Error: IMAP(kartagis): file_lock_dotlock() failed with mbox file /var/mail/kartagis: Permission denied Hi, I get these

I've installed fail2ban, it seems to be working as it identified my failed test logins, BUT, my question is: what can I do when I see same invalid name trying to login to dovecot, different IP each time, how can I say block each IP as used by this name ? or it that a bad idea ? I can see two persistent attempts as so: I don't have such user 'ignacio' or 'julian' # grep

Oct 5 22:51:59 ns6 dovecot: POP3(aewhale): file_lock_dotlock() failed with mbox file /var/spool/mail/aewhale: Permission denied Any suggestions? -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ------------------------------------------------------------------------ ABS Computer Technology, Inc. <http://www.ABS-CompTech.com> - Email,

I have just upgraded to dovecot 1.0.13. All the documentation I can find in the example .conf file and the NEWS and ChangeLog files seems to say that the mail_privileged_group = mail setting is all I should need to make dovecot use group mail to create dotlock files. My understanding from what I read is that mail_privileged_group is used to set the group used while creating dotlock files in (in

Hello I am migrate FC1 to FC2, in FC1 i use ipop3d, but in the migration to FC2 this programa is obsolete, i decide migrate to dovecot, but i have problems with the old mail i have the mail stored into /var/spool/mail/USER and this error appears with examine the mail with Oulook Express: Jun 6 23:24:10 dakota pop3(dakota): open(/var/spool/mail/dakota.lock) failed: Permission denied Jun 6

Anyway everything seems to work well. The shares are correctly and users recognize them without problems. getent and wbinfo. The main problem is that apparently the Member DC does not get the UID properly containing the user in the ADDC. There is something that can change in the smb.conf the Member DC, I remember a few years ago with the same AD DC we get the UID correctly. 2016-06-14 12:58

FreeBSD 6.1-RELEASE-p8 postfix-current-2.4.20060903,3 dovecot-1.0.r7 I am experiencing a problem with dovecot as an LDA. It will not deliver mail unless the mail directory is chmod'd to 1777. Below is an example of the log file output. The dovecot.log file had over a hundred entries similar to this: deliver(gerard): Error: open(/var/mail/.temp.scorpio.seibercom.net.1123.cd38cd4d82e1368f)

I'm trying to replace procmail with deliver but I'm having problems with the group part of things. I keep getting: Aug 29 16:44:19 dingbat deliver(mimo): open(/var/mail/.temp.dingbat.3969.d1689935a308e0dd) failed: Permission denied Aug 29 16:44:19 dingbat deliver(mimo): file_lock_dotlock() failed with mbox file /var/mail/mimo: Permission denied My primary group is mimo and I think

I got this to work on Linux but it is not working on Windows. *My understanding is that this should also work on windows, is that correct?* If so, what should I do? differently? To get it to work on Linux, I modified my R script as follows: #' OpenMP Hello World #' #' @param nthreads The number of threads that you want to use #' @example #' hello(nthreads=2) #' @export

Hello, I'm sorry if I'm asking something that is documented - I could swear I saw something about this (dovecot changing to the uid of the entry in the userdb when accessing the mailbox), but now I cannot find it anywhere in the wiki! Dovecot seems to be getting the right uid for the mailbox, but then it is having permissions problems. The error is: Feb 27 17:31:08 rm-002-02 dovecot:

On 14/06/16 16:16, Juan Ignacio wrote: > Sorry, this is the Domain Member smb.con > Im using Debian last version. > Samba compiled from the sources. > > [global] > netbios name = XXXXX > security = ADS > workgroup = XXXXXX > realm = XXXXXXX > > log file = /var/log/samba/%m.log > log level = 1 > > # idmap

well, now that I have moved to dovecot, I'm not getting any spam... in fact, I'm not getting e-mail at all. default_mail_env =mbox:~/IMap2/:INBOX=/var/spool/mail/%u when I first tried to access my inbox, I was told I had permission problems: Aug 14 17:47:22 harvee imap(esj): open(/var/spool/mail/esj.lock) failed: Permission denied Aug 14 17:47:22 harvee imap(esj): file_lock_dotlock()

Hello, I'm trying to set up dovecot as the delivery agent for postfix. I configured postfix with: mailbox_command = = /usr/local/libexec/dovecot/deliver In the logs I see the following error: Sep 20 17:19:26 zalm deliver: open(/var/mail/.temp.zalm.8045.65c09c28953ea20c) failed: Permission denied Sep 20 17:19:26 zalm deliver: file_lock_dotlock() failed with mbox file

Am seeing: > Jul 19 14:59:19 mercury mail:err|error dovecot: IMAP(jab): dotlock /var/spool/mail/jab.lock was immediately delet > ed under us > Jul 19 14:59:19 mercury mail:err|error dovecot: IMAP(jab): file_lock_dotlock() failed with mbox file /var/spool/m > ail/jab: No such file or directory what does it mean, what should I be doing to alleviate or troubleshoot the problem? -- ====

Hi, We're running a Debian server with system users where the mail is by default delivered by postfix and procmail, before being served by Dovecot (mail_location = mbox:~/Mail:INBOX=/var/mail/%u) or read by local MUAs, depending on users' preferences. For people using mostly remote MUAs, it might be interesting to use Dovecot's LDA. I read on http://wiki.dovecot.org/LDA that this

Hello, Running dovecot 1.1.6 on centOS 5 and RHEL 5. With the settings: pop3_lock_session = yes mail_privileged_group = mail mail_location = mbox:~/:INBOX=/var/spool/mail/%u mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl and /var/spool/mail permissions: drwxrwx--x 2 root mail 4096 Nov 19 10:16 mail/ Trying to connect via POP3 results in this error: --- Nov 19 09:31:01

On 14/06/16 17:32, Juan Ignacio wrote: > Rowland, a question. > > > "is to copy idmap.ldap from the first DC to all others and then keep > them in sync, the other is to use RFC2307 attributes." > > I can do the same with my member server? Maybe it works, or not for > beign a member server. > > Maybe i can change my Member Server to a Domain Controller and