21:09 2002-11-02


	
	Sparse HOWTO run Scopee and XMail on different machines.

	  Secure NFS via SSH Tunnel
	   http://www.math.ualberta.ca/imaging/snfs/


	Scopee 'remote-temp-dir' server directive.


	   If you run Scopee and XMail on different machines, this setting
	   is crucial if want to be able to access message-files passed in by
	   reference from the client. Since in this case the client and server
	   operate on separate file-systems, Scopee cannot get to files
	   referenced with @@TMPFILE or @@FILE as they dwell on a remote system.

	   The 'remote-temp-dir' directive enables Scopee to perform transparant path
	   re-writing on the incoming tmpfile paths to match a mountpoint
	   resolving to the temp directory on the remote box which XMail uses to store
	   temporary message files shared at the serverside via NFS or Samba.

	   From a procedure/filter's point of view, they can now access tmpfiles
	   references passed in without having to pay attention on the fact that
 	   the file isn't around locally. This will even work OS assuming the mounting
	   is set up properly,  so for example you can run XMail on a Linux box and
	   have Scopee running on a Win32 box or vice versa without any problems
	   (huh, tough standpoint but it does work, atleast it does over here..:)

	   That is, assumed you utilize Samba on the Linux box in the former case
	   or use smbmount in the latter. File permissions might be another
	   obsticle to resolve though, but that part is beyond this Scopee. :)
	   A client/server combo both understanding NFS would the most appropiate
	   approach I figure.
	   
	   In the Xmail case, it uses the temp dir assigned for the owning user
	   for temporary message storage while it lets any filter/mailproc script
	   have a go at the message. With this in mind, you therefore have to
	   export/share the temp dir on the XMail side and then and mount/map it to a
	   path on the Scopee side to be able to access the remote temp dir.
	   The 'remote-temp-dir' setting inturn must reflect this mountpoint.


	   A simple NFS setup.
	   
	   Assuming you run both XMail and Scopee as root. (use with care...)

	   There might be better ways to do this, I am by far no *nix guru.
	   If you feel you have suggestions to contribute with, please
	   let me know and I'll happily add it.

	   (# <- indicates shell)

	   1. On the XMail side: (the Scopee side)
 	      * Start the nfs daemon if not already running
	      * Add XMail's working directory (eg. /tmp) to the exports file
	        and allow write access to the IP/name of the client machine.
	        Since both processes run as root on their respective machines,
	        we make it easy for us and let the remote machine's root-user
	        inherit the local root privileges for the exported directory.
		  This is achieved by adding the following line to '/etc/exports':
		   /tmp IP_OF_Scopee_MACHINE(rw,no_root_squash)
	      # exportfs -r
	       
	   2. On the Scopee side:
	      # mkdir /tmp/xmail-tmp-dir
	      # mount -t nfs IP_OF_XMAIL_MACHINE:/tmp /tmp/xmail-tmp-dir
		* Make attribute 'remote-temp-dir' read '/tmp/xmail-tmp-dir'


	   3. Done. If you want to make the mountpoint persistant you need either
	      to add the above mount command to rc.local or another startup
	      script, or add an entry to /etc/fstab on the Scopee side.

	   (Some time ago I heard something that with XMail 1.11 you'll be able
	    to manually set its temp dir, so the example above might need to be
	    alterered depending on your local setup)