similar to: Dovecot 1.1.3 / 1.1.4 - not deleteing

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 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

I have been using UW's IMAP server and I am converting to Dovecot for Maildir support. When a user fails authentication, or a user does not exist, it appears that the same message is used for these events. Is there a way to indicate that the user does not exist (Invalid user), and authentication Failure (Failed Password)? Clearly these two failures indicate a different error in the system.

OK, I am attempting to use the userdb connection to facilitate per user migration to Maildir format from mbox. Here's the first user: more /home/dovecot.passwd health:$1$MCtvt/Tz$FmKqU/cbWlBhKnhc5W.Ko.:1152:1152:/home/health:userdb_mail=maildir:~/Maildir The configuration was set up as: userdb passwd { } I changed this to: userdb passwd-file { args = /home/dovecot.conf }

Is there an automatic solution to this? Oct 27 08:00:48 192.168.50.5 dovecot: POP3(evelina2): mail_location: mbox: mkdir(/home/popuser_evelina2/mail) failed: Permission denied Oct 27 08:00:48 192.168.50.5 dovecot: Fatal: POP3(evelina2): Namespace initialization failed Oct 27 08:00:51 192.168.50.5 dovecot: POP3(evelina2): mail_location: mbox: mkdir(/home/popuser_evelina2/mail) failed: Permission

OK, I have been running the UW-POP3 server which currently translates all login ids as lowercase (i.e. Anthony becomes anthony). Now the Dovecot server is very flexible and currently I have not found how to translate the upper case characters to lowercase. What configuration setting will translate the userids to lowercase? -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk

I recently am attempting a mbox to Maildir conversion, initially for a single email address, and then for everyone. To further this diagnostic here is the dovecot -n: dovecot -n # 1.1.4: /etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login

I've been running a mbox solution using UW's IMAP server. I've run it for years. Now do to heavy message volumes, I've decided to to take the plunge to convert to the Maildir format. I am currently testing a single user, and have successfully converted the mail messages from mbox to Maildir format, and now I am setting up the procmail tool to place the messages into the correct

I am transitioning an existing server from using exclusively mbox, to being able to support both mbox and then fully maildir formats. I need to support the mbox format until I can get everyone switched over to maildir. What do I need to to use in the config of /etc/dovecot.conf to support the default of mbox, and then the new Maildir format (users will get upgraded individually from mbox to

Yes, there is currently concurrent usage because the Mail spool is NFS Mounted. Here is the current configuration: dovecot -n # 2.1.15: /etc/dovecot/dovecot.conf # OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3 base_dir = /var/run/dovecot/ disable_plaintext_auth = no lock_method = dotlock login_greeting = SpamZapper Email ready. login_log_format_elements = user=<%u> method=%m

I am using Dovecot in two Server environments. My Legacy (5 years+ old) servers are running dovecot 1.1.20, and are responding as expected. These servers are using an NFS based storage for the /home directory structure, and are working beautifully. However, I need to replace these inefficient servers, and get more current. That brings me to the problem, where I am implementing Dovecot

I have, but I will be happy to review it once again. On 12/18/18 2:14 PM, admin wrote: > Am Dienstag, den 18.12.2018, 14:06 -0500 schrieb Albert E. Whale, CEH > CHS CISA CISSP: >> >> I have two servers pointing to an NFS mounted mail spool with >> dovecot.? Since I recently switched from using Dovecot v1.X, I have >> been experiencing high CPU use with the two

Maybe I misunderstand. Each user is only able to access their mailbox from a single connection at a time. Other users can access the NFS Spool from other connections, I think that is what I am calling Concurrent connections. Is that the same definition you have? From: dovecot [mailto:dovecot-bounces at dovecot.org] On Behalf Of Aki Tuomi Sent: Friday, October 19, 2018 10:05 AM To: Albert

In attempting to reactivate my IMAP communications with my Email Spool (NFS Mounted), I have gotten the following while attempting to download the Emails via POP3. Oct 18 08:00:45 ns4 dovecot: pop3-login: Login: user=<aewhale>, method=PLAIN, rip=74.109.213.194, lip=66.207.133.232 Oct 18 08:02:40 ns4 dovecot: pop3(aewhale): Error: Timeout (180s) while waiting for dotlock for transaction

dont play net cop here but since you want to try force your opinion down others throats heres one for you, if you want to try dictate to someone to bottom post to suite you how about you use proper net etiquette yourself and TRIM your posts On 12/19/18, admin <admin at awib.it> wrote: > Am Dienstag, den 18.12.2018, 14:26 -0500 schrieb Albert E. Whale, CEH > CHS CISA CISSP: >>

I have two servers pointing to an NFS mounted mail spool with dovecot.? Since I recently switched from using Dovecot v1.X, I have been experiencing high CPU use with the two Dovecot servers. I am not certain why they are not well behaved.? Here is the configuration information. This configuration is currently running at a load average of 17. /usr/sbin/dovecot -n # 2.1.15:

Am Dienstag, den 18.12.2018, 14:26 -0500 schrieb Albert E. Whale, CEH CHS CISA CISSP: > I have, but I will be happy to review it once again. > > > On 12/18/18 2:14 PM, admin wrote: > > > > > > > Am Dienstag, den 18.12.2018, 14:06 -0500 schrieb Albert E. > > Whale, CEH CHS CISA CISSP: > > > >

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Concurrent access is not supported. One user should access mail using one backend at a time. You can use dovecot in director mode to prevent this. </div> <div> <br> </div> <div> Aki </div> <blockquote

Am Dienstag, den 18.12.2018, 14:06 -0500 schrieb Albert E. Whale, CEH CHS CISA CISSP: > I have two servers pointing to an NFS mounted mail spool with > dovecot. Since I recently switched from using Dovecot v1.X, I > have been experiencing high CPU use with the two Dovecot > servers. > I am not certain why they are not well behaved. Here is the >

I have a problem with Dovecot 1.1.6 after having reset the UID/GID information for a few email accounts. I get the following error: Dec 5 12:26:03 ns6 dovecot: POP3(mike): stat(/home/popuser_mike/Maildir/tmp) failed: Permission denied (euid=1366 egid=1366 missing +x perm: /home/popuser_mike/Maildir) Dec 5 12:26:03 ns6 dovecot: POP3(mike): Couldn't open INBOX: Internal error occurred. Refer