Although the task is really a minor change: one thing makes me a bit confusing.
Till, how do you distribute an update of the field `doctype_def`, inside the doctype table? It seems that you don't perform db updates during ISPConfig install (update) time, when forms have changed... - so how would this be done??

The other post in this forum ("ISPConfig doctype (form) handling"), regarding to a changed doctype handling from database to filesystem, didn't help me. There is no /home/admispconfig/ispconfig/lib/doctypes/ folder and maybe you've changed the doctype handling again?

EDIT: Oh - I had never supposed that you delete the comlete db during update. So my grepping after "ALTER TABLE" had no chance there

Look into the attachment, if you're in the mood. Otherwise: it's only half the way. In fact, I think, one can change this with similar effort to have FTP users without e-mail as well.

So instead of a checkbox - like in the attached solution - one could use an option field on the user tab, represented in the db as an char(1) field:

=> E-mail only

=> FTP & E-mail

=> FTP only

Then: only if the option value is > 1 you would define the /dev/false user directory in the password file. If the value is > 2 you would NOT write into virtualusertable of postfix.
Backward compabilty: for all already existing users the option '2' could be set. Make that sense?

I am almost ready with a complete e-mail // FTP separation. Changed only a couple of lines! I will post this to the tipps and tricks section.

I would deny to hack around on this subject further (like configurable FTP dirs or fully virtual mail users) - too much effort for a falling star ... ;-)

I think ISPconfig 3 is the real thrill now. I think I'm going to love it, although usability is much more an issue for v3 than for v2 - surprisingly. But that's always the cost of flexibility, if you look closer.

I think ISPconfig 3 is the real thrill now. I think I'm going to love it, although usability is much more an issue for v3 than for v2 - surprisingly. But that's always the cost of flexibility, if you look closer.

Click to expand...

Fully agreed. We tried to find a good path between flexibility and easy usage. I know that some iSPConfig 2 users think that ispconfig 3 is not so easy to use, but thats always the case if you add more features and if the layout of the system changes to achieve this. In ISPConfig 2 everyone complained before that the same features were missing So you will never make the product that everone likes...