similar to: Migration Issues UW-POP3

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

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 }

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

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

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

On 18.10.2018 15.15, Albert Whale wrote: > > 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

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 am attempting to integrate a Linux Samba Server with an NT 4.0 PDC. Ideally I am looking to authenticate the users on the PDC, and then permit access to the Samba Shares on the Linux Box. I have several issues, but the one which is presenting itself currently is when I attempt to Browse the PDC using smbclient. I get the following: smbclient -L dumbo added interface ip=192.168.0.11

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

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

We've been running ipv6 for a year or so now, but some of our newer instances (all on an ESX cluster) are not working. It looks like it's all of our Centos 6 instances. I'm hoping someone can point me in the right direction... tshark indicates that it's neighbor discovery that's failing: <centos666.peak.org> [26] # cat ../network NETWORKING=yes

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

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

Not sure what happened here, but today, all of a sudden, pop3 emails are not being deleted. I was using the 1.1.3 version then upgraded to 1.1.4 now it no longer deletes emails. Suggestions? -- Albert E. Whale, CHS CISA CISSP Sr. Security, Network, Risk Assessment and Systems Consultant ------------------------------------------------------------------------ ABS Computer Technology, Inc.

Hello everyone - I run bind version 9.8.2 on CentOS 6.5. The daily logwatch run sends me the following items. Are any of these a real problem? ============ checkhints: extra NS 'A.ROOT-SERVERS.NET' in hints: 170 Time(s) checkhints: extra NS 'B.ROOT-SERVERS.NET' in hints: 170 Time(s) checkhints: extra NS 'C.ROOT-SERVERS.NET' in hints: 170 Time(s)

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

All: I'm posting this to FreeBSD-security (rather than FreeBSD-net) because the problems I'm seeing appear to have been caused by spyware, and because they constitute a possible avenue for denial of service on FreeBSD machines with default installs of the operating system. Several of the FreeBSD machines on our network began to act strangely during the past week. Some have started to