Hi, I have added a new volume in my linode. Mounted it on /mnt/VMAIL Can i change few high use email clients to this directory?
https://www.howtoforge.com/use_moun...ctory_of_a_ispconfig_server_to_a_new_location shows how to move all mail there
I want move it partially ... Don't want to move all emails. Can we make some domains to move on new mounted directory?
I have this entry in fstab /dev/disk/by-id/scsi-0Linode_Volume_VMAIL /mnt/VMAIL ext4 defaults 0 2 Should I bind /var/vmail to /mnt/VMAIL?
You should be able to use multiple bind mounts to accomplish that, you just can't do it through the ispconfig interface. Eg. something like: Code: mv /var/vmail/domain1 /mnt/VMAIL mkdir /var/vmail/domain1 chown 770 /var/vmail/domain1 chmod vmail:vmail /var/vmail/domain1 bindfs /mnt/VMAIL/domain1 /var/vmail/domain1 That assumes "mv" works across filesystems on your system, which it may or may not (if not, use tar or something to copy, then delete the original). Then add an entry to /etc/fstab to bind mount /var/vmail/domain1 at boot, and repeat all steps for domain2, etc.
maybe, in addition, ease filesystem access more by changing [dbispconfig] mail_user.maildir entry for specific accounts ( no guarantee there are no downsides ) thus saving a few lookups
yes, you can change both, even if it gets changed back for whatever reason, it shouldn't matter much - there's no open_basedire restriction like in php or suexec prefix needed like for apache. just if you happen to remove the mountpoint/symlink ... one would need to revert the change for obvious reasons.
Works like charm ... I think add new user will be default to /var/vmail Can I change it ispconfig source files?
oh yeah absolutely, no source change needed. go to system -> server configuration -> choose your server -> E-Mail tab and you see two template paths
ohh .. we have this configuration ... then we can simply move /var/vmail to /mnt/vmail and then change the path. If I make the change in config, will it also change already existing entries in maildir and homedir?
no, it won't change existing - maybe when using resync feature, but I don't know / wouldn't assume it.
my intention was an addition, create the bind to keep the expected file structure but to save some fs-lookups set the final path where possible.
