It seems to me: the really hard approach of ISPConfig2.x is to have automatically e-mail users and ftp users merged into this one system user with at least these capabilities: send and recieve e-mail (optionally manage the e-mail account: autoresponder, antispam and antvirus settings, define forwarders and aliases) up- and download files in predefined zones of a clients web site publish content in predefined zones of a clients web site This is not always what clients or even hosters would prefer. What would you say, if these capabilities could be separated, even in ISPConfig 2.x? E-mail and FTP in this setup are completly independent from each other. If e-mail is not checked, then there will be no entry for this user in the virtusertable. If FTP is unchecked, it's the same for only this user as FTP were unchecked for the whole web. So all functionality to separate these two was always there - I've only tried to put the ends apart. Very few lines of code were necessary to do this. But the overall unix system user remains of course. There are still all these hidden config files of procmail, spamassassin and so on left; the structure and permissions of files and folders are not involved in my private solution. To have these files is quite useless - until one decides to grant an e-mailbox to an user or to let him upload and publish. then is all in the right place. My intention was not to make ISPConfig2 unstable, of course. So the less code I had to touch the happier I was. Therefore don't ask please for appearently next steps like defining an FTP root folder for an user etc. I think, ISPConfig 3 is the rising star in the background, containing really good stuff and much better and really amazing concepts. So all this stuff belongs there. For me it is almost like to say Good bye to ISPConfig 2. So try it out and give feedback. PLEASE don't use the attached patches in production environments. If so, do it on your own risk. Note, that until now there is no feedback from Till or Falko, so it's really dangerous.