similar to: Problem with logging in on pop3

I have to make dotlock work because this openwebmail thing only supports one of dotlock or flock, but procmail delivery does dotlock and fcntl. procmail correctly creates a dotlock file in /var/spool/mail/username.lock when delivering, I can watch this with `while :; do ls -la | grep lock; done`. It works fine when lock_method=fcntl, but no dotlock file shows up in /var/spool/mail.

FreeBSD 6.1 STABLE Postfix version 2.4-20060806 Dovecot v1.0.rc2 I have the following in the postfix main.cf file: mailbox_command = /usr/local/libexec/dovecot/deliver This is from the dovecot.conf file: default_mail_env = mbox:/var/mail/%u However, mail is never delivered with this configuration. This is an excerpt from the 'dovecot.log' file: deliver(gerard): Error:

I jumped right in and followed the "Quick Configuration" guide after installing dovecot (dovecot-1.0.beta3.tgz) on my OpenBSD 3.9 box. I had previously been using akpop3d (which worked, but was flaky). I am getting the following errors in /var/log/maillog: Jul 23 22:40:29 kingcull dovecot: pop3(jm): open(/var/mail/.temp.myserver.mymail.com.19038.10090e2f3cc51a4b) failed: Permission

I've been trying to get Dovecot 1.0a3 running on OpenBSD 3.7, with little luck. I'm getting the following: Oct 16 17:00:50 mailtest dovecot: pop3(testuser):open(/var/mail/.temp.mail.mailtest.com.7078.43c0f93e9fecb54a) failed: Permission denied Oct 16 17:00:50 mailtest dovecot: pop3(testuser): file_lock_dotlock() failed with mbox file /var/mail/testuser: Permission denied Oct 16

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, i've upgraded from 1.0.5 to 1.1.2 on 2 server and work fine for user that grab email on client, but some customer (that leave the email on server) have 2 problems. Some client can't read new mail: dovecot: Aug 19 11:00:46 Info: pop3-login: Login: user=<agenzia>, method=PLAIN, rip=xxx, lip=91.102.48.12 dovecot: Aug 19 11:00:46 Info: POP3(agenzia): Disconnected: Logged out

I have just upgraded from 1.0.7 to 1.0.13. I read the comments in the example .conf file and it seemed what I needed to enable dotlock access to mailboxes in /var/spool/mail (writable by 'mail' group) was "mail_privileged_group = mail" so I removed the "mail_extra_groups = mail" that I had in 1.0.7 and added "mail_privileged_group = mail", but I got errors

I have to migrate some old system to new one with installed dovecot (It's my first time using dovecot). I have all mails inside /var/spool/mail folder (mbox files). I can connect and receive mails via POP3, but problem is that dovecot doesn't clear mbox file (everytime when I make send/receive in mailclient program I get all mails again). If I look into log file I see (when I do

Hi, I've installed dovecot on my server (pop3 service on dovecot 1.0 stable plus patch for more logging, postfix as mta) and it's ok (not all, need more fine-tuning) but on one account i've a problem.. the account is read by oe 6, message on server mode. dovecot: Jun 09 15:00:18 Info: pop3-login: Login: info-xxx, auth: PLAIN, lip: [151.8.36.12], rip: [xx.xx.xx.xx] dovecot: Jun 09

Hi, I often see this message: Feb 1 14:42:44 vlk dovecot: POP3(obec at nizkov.cz): Mailbox init failed top=0/0, retr=0/0, del=0/0, size=0 Feb 1 14:42:44 vlk dovecot: POP3(obec at nizkov.cz): mbox sync: UID inserted in the middle of mailbox /var/mail/obec at nizkov.cz (68386 > 68346, seq=2, idx_msgs=3) this is on FreeBSD at i386 runnin 1.0.r19 (but I have seen this with all versions of

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

Its been a while since I tried dovecot on my mail server where I have quota issues. I am using mbox file format. There still seems to be a quota problem. I have only /var with quotas and basedir is under /usr (not quotaed). default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u. I tried with mbox_locks = dotlock fcntl (1st set of logs below) and with mbox_locks = fcntl (2nd set of logs) dotlock:

I recently had a system crash and my inbox became inaccessible via IMAP. ls -ld /var/spool/mail drwxrwxr-x 2 root mail 4096 Sep 1 07:54 /var/spool/mail ls -l /var/spool/mail/ignacio -rw-rw---- 1 ignacio mail 7222021 Sep 1 07:54 /var/spool/mail/ignacio /usr/libexec/dovecot/imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT IDLE CHILDREN LISTEXT LIST-SUBSCRIBED

Starting at 05:32 this morning, one user on my dovecot server is receiving hundreds of copies of old email. This is a short excerpt from my dovecot.log showing the problem: > dovecot: Nov 03 05:27:02 Info: pop3-login: Login: > user=<howard at obfusca.ted>, method=PLAIN, rip=::ffff:81.44.31.210, > lip=::ffff:zz.zz.zz.zz, TLS > dovecot: Nov 03 05:27:02 Info: POP3(howard at

This should be simple, but I'm missing something. My virtual users cannot access their mail. I would like Unix users to get their mail via imap which is deposited in /var/spool/mail/username. (This works.) I would like virtual users to get their mail via pop3 which is deposited in /var/spool/mail/vhosts/example.com/auser/mail/inbox (postfix does in fact put the mail there). Those users

I have two accounts where the inboxes sometimes get corrupted. In that case they begin with "FFrom". I saw similar reports in July/August last year. So I applied the patch http://dovecot.org/pipermail/dovecot/attachments/20100720/e87b32ae/attachment-0001.bin Yesterday a mbox corruption happened again. Here are the log lines. Jun 29 18:08:12 mail dovecot: pop3-login: Login:

Jun 8 23:14:09 dakota pop3(dakota): open(/var/spool/mail/dakota.lock) failed: P ermission denied Jun 8 23:14:09 dakota pop3(dakota): file_lock_dotlock() failed with mbox file / var/spool/mail/dakota: Permission denied Jun 8 23:14:09 dakota pop3(dakota): open(/var/spool/mail/dakota.lock) failed: P ermission denied Jun 8 23:14:09 dakota pop3(dakota): file_lock_dotlock() failed with mbox file /

I am migrating from UW's POP3 server (mbox), to Dovecote (mbox -> maildir). Anyway, I am concerned about the Logging details offered by Dovecot, as I manage several details from the logging information provided by UW's Syslog information. Here's a sample of the UW information: Oct 7 22:08:39 ns6 ipop3d[15432]: pop3 service init from 66.207.133.233 Oct 7 22:08:39 ns6

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,

Dear All? When the user login P0P3 more than 10 times in 1 minute that the dovecot temporary suspension all of pop3 login about 5 minutes. How to disable the setting for dovecot. Mail Log: Apr 24 16:11:14 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8767, session=<5USPZMX3/QDAqBBU> Apr 24 16:11:14 mww dovecot: