Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I would recommend that you:
1) look in your log file for the corresponding error messages. The message may contain more specific information that helps direct you to an answer
2) My guess is that Dovecot is having problems with access to the maildir, for example, creating the index file. Confirming from the logs which directory/file and the associated permissions would be of help.
3) I have not seen a service segment spelled out like yours before, but one thing I do recall is in the auth-worker section, and possibly in the other auth sections too, you can put a directive for the user that the system will run under. The user and group must correspond to the permissions of the mail directories. This also applies to the spool directory, which may be your permissions problem.

As an example, here is what I have from the Dovecot sections I am thinking of. Note that some of my trials are commented out:

thanks, that put me in the right direction. I had omitted to created the dovenull and dovecot users. I also found that running

Code:

/opt/sbin/dovecot

overcome the main error message

Code:

Fatal: execvp(/opt/include/dovecot) failed: Permission denied

and lead to useful error messages. It turns out that

Code:

/opt/include/dovecot

is placed ahead of /opt/sbin/dovecot in my $PATH
and even though /opt/sbin/dovecot is only a folder, my system was trying to run it as a program.

I then corrected a few other configuration errors via dovecot.conf after checking the logs (using syslog), the trickiest of which were the following:
1. needed this config in dovecot.conf for passwords:

3. I was trying to log into roundcube as the 'root' user, which is 'admin' rather than 'root' in a qnap device. I learned that dovecot does NOT allow the root user to log in
So the following is set this way: