[Dovecot] An unconstructive grumble
5 hours of configuration attempts, error after confusing error, documentation with examples that only show extracts of working configurations. I really feel like throwing in the towel with dovecot.
It should not be this hard and frankly almost impossible to understand and configure for such an incedibly simple configuration.
/home/vmail/domain.name/username/cur /home/vmail/domain.name/username/new /home/vmail/domain.name/username/tmp
3 virtual users. All I want is a username and password to access my email.
I have to have hit every error and problem there can be. No response at all from server, unable to find password file, unable to recognise user, invalid password. God it went on and on and on for five or more hours. For such a simple config.
I know this is a totally unconstructive complaint and I should be taking the time to set out a careful explanation of my problem along with errors and logfiles but I just can't be bothered. I've tried so many many configurations and options and nothing works. How can it possibly be this hard to ghet some emails off the server with simple username/password configurations.
Go ahead and flame me to a crisp.
-- View this message in context: http://dovecot.2317879.n4.nabble.com/An-unconstructive-grumble-tp42598.html Sent from the Dovecot mailing list archive at Nabble.com.
On Mon, Jun 03, 2013 at 06:23:09AM -0700, dd wrote:
5 hours of configuration attempts, error after confusing error, documentation with examples that only show extracts of working configurations. I really feel like throwing in the towel with dovecot.
It should not be this hard ...
Why not? You're really not in a position to make this claim. But having said that...
and frankly almost impossible to understand and configure for such an incedibly simple configuration.
/home/vmail/domain.name/username/cur /home/vmail/domain.name/username/new /home/vmail/domain.name/username/tmp
3 virtual users. All I want is a username and password to access my email.
... you complicated things by wanting virtual users. System users would have been much simpler to set up. Also, you missed the fact that virtual users should have a $HOME directory just like system users:
http://wiki2.dovecot.org/VirtualUsers http://wiki2.dovecot.org/VirtualUsers/Home
The only constructive suggestion I can make here is to scrap it and start over with system users. Let PAM / your OS handle the username and password and other daunting tasks.
http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
On Jun 3, 2013, at 9:48 AM, /dev/rob0 <rob0@gmx.co.uk> wrote:
The only constructive suggestion I can make here is to scrap it and start over with system users. Let PAM / your OS handle the username and password and other daunting tasks.
+1. I've spent a lot of time waist-deep in dovecot, but one of the things I love about it is that when I need to set up IMAP mail access for a couple users for someone's home or business, it can be done in less than ten minutes. Create the system users, change about four lines in the default configuration, and done.
-brian
On 3 Jun 2013 16:49, "/dev/rob0" <rob0@gmx.co.uk> wrote:
On Mon, Jun 03, 2013 at 06:23:09AM -0700, dd wrote:
5 hours of configuration attempts, error after confusing error, documentation with examples that only show extracts of working configurations. I really feel like throwing in the towel with dovecot.
It should not be this hard ...
Why not? You're really not in a position to make this claim. But having said that...
and frankly almost impossible to understand and configure for such an incedibly simple configuration.
/home/vmail/domain.name/username/cur /home/vmail/domain.name/username/new /home/vmail/domain.name/username/tmp
3 virtual users. All I want is a username and password to access my email.
... you complicated things by wanting virtual users. System users would have been much simpler to set up. Also, you missed the fact that virtual users should have a $HOME directory just like system users:
I've never understood this antipathy to virtual users. But your knowledge is greater than mine :)
http://wiki2.dovecot.org/VirtualUsers http://wiki2.dovecot.org/VirtualUsers/Home
I sort of see why for legacy reasons a $home directory might once have been needed. But surely however you word it all you're doing is telling the server where to put the mails, the structure you want and the format of the files. 3 variables...
Simon
On Mon, Jun 03, 2013 at 05:10:35PM +0200, Simon B wrote:
On 3 Jun 2013 16:49, "/dev/rob0" <rob0@gmx.co.uk> wrote:
On Mon, Jun 03, 2013 at 06:23:09AM -0700, dd wrote:
3 virtual users. All I want is a username and password to access my email.
... you complicated things by wanting virtual users. System users would have been much simpler to set up. Also, you missed the fact that virtual users should have a $HOME directory just like system users:
I've never understood this antipathy to virtual users. But your knowledge is greater than mine :)
My antipathy? I have none. Virtual users are ideal in certain circumstances. They are NOT ideal for people who are just starting out and have no idea how all the pieces fit and work together. That way lies frustration and madness (and if you noticed, a very high percentage of the questions we see on this list.)
I started out with system users, and I learned how it all works. Taking it a piece at a time is always best when starting into unfamiliar territory.
http://wiki2.dovecot.org/VirtualUsers http://wiki2.dovecot.org/VirtualUsers/Home
I sort of see why for legacy reasons a $home directory might once have been needed. But surely however you word it all you're doing is telling the server where to put the mails, the structure you want and the format of the files. 3 variables...
No, there are other files kept in the $HOME. Quoting the link:
" Some uses for home directory are:
- By default Sieve scripts are in user's home directory.
- Duplicate mail check database is in user's home directory. Suppression of duplicate rejects/vacations won't work if home directory isn't specified.
Debugging: If an imap or pop3 process crashes, the core file is written to the user's home directory. "
http://rob0.nodns4.us/ -- system administration and consulting Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
dd skrev den 2013-06-03 15:23:
Go ahead and flame me to a crisp.
why not join the fun of google apps mx ? :)
dovecot is not for everyone
if you like more help provide "dovecot -n" and if using postfix "postconf -n", what a combo ?
-- senders that put my email into body content will deliver it to my own trashcan, so if you like to get reply, dont do it
Most problems like this can be attributed to trying to follow some $Random_HowTo from the internet, rather than reading the dovecot docs themselves.
But yeah, ranting like you just did without providing any details at all is totally counter-productive, and is likely to get you flamed - or more probably just ignored.
On 2013-06-03 9:23 AM, dd <dukedougal@gmail.com> wrote:
5 hours of configuration attempts, error after confusing error, documentation with examples that only show extracts of working configurations. I really feel like throwing in the towel with dovecot.
It should not be this hard and frankly almost impossible to understand and configure for such an incedibly simple configuration.
/home/vmail/domain.name/username/cur /home/vmail/domain.name/username/new /home/vmail/domain.name/username/tmp
3 virtual users. All I want is a username and password to access my email.
I have to have hit every error and problem there can be. No response at all from server, unable to find password file, unable to recognise user, invalid password. God it went on and on and on for five or more hours. For such a simple config.
I know this is a totally unconstructive complaint and I should be taking the time to set out a careful explanation of my problem along with errors and logfiles but I just can't be bothered. I've tried so many many configurations and options and nothing works. How can it possibly be this hard to ghet some emails off the server with simple username/password configurations.
Go ahead and flame me to a crisp.
If you're hosting this on the domain where the users will have email, then do you have a good reason for wanting to use virtual stuff? If not, use system users.
If you are hosting for another domain (or plan to) I don't have enough info to tell you more - I routinely set up virtual domains (I use postfixadmin for most of this maintenance. I probably followed the instructions in the dovecot virtual user readme file(s).
H
participants (7)
-
/dev/rob0
-
Benny Pedersen
-
Brian Hayden
-
Charles Marcus
-
dd
-
Harlan Stenn
-
Simon B