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: