Thanks so much for taking the time to respond. Your input is much appreciated.
1. The main issue I see is that the XAMS maildir looks a bit different than
a standard maildir: it inserts the site name in between /mail/ and
/_USERNAME_/.
This isn't a maildir structure at all. A maildir consists of a directory (any name you like) with three subdirectories: new, cur and tmp. Messages are delivered to tmp, atomically renamed to new and the MUA that reads them moves them to cur after they've been read.
I'm sorry -- I communicated this very poorly. From what I understand, XAMS is fully maildir compliant. The only difference is that users are grouped by sites, with each site containing one or more grouped domains. So where a standard maildir path might look like...
/var/mail/_USERNAME_/(new,cur,tmp)/(actual message files)
...the XAMS maildir path instead looks like...
/var/mail/_SITENAME_/_USERNAME_/(new,cur,tmp)/(actual message files)
The actual maildir directory (the top-level one) can be anywhere in a directory hierarchy, so your _USERNAME_ would be a perfectly valid maildir name as long as it had new, cur and tmp subdirectories.
So, theoretically, the .tmda directory could be stored at...
/var/mail/_SITENAME_/_USERNAME_/tmda/
...alongside the (new,cur,tmp) directories.
All paths can be customized in the config file. The bootstrap problem is finding the config file, which TMDA (by default) assumes is in ~/.tmda. However, you can tell it to look elsewhere by giving the "-c <path_to_config_file>" switch to tmda-filter. If _SITENAME_ is the actual domain name, like 'example.com' and Exim can give that to you in an environment variable, then you could run tmda-filter with a per-site config file from a .forward file like this:
| tmda-filter -c /private/var/mail/tmda/$SITENAME/config
Excellent. Just so I understand, does this describe a set-up in which individual users can configure TMDA's behavior? Is the idea that users would override the site-wide setup by editing their preferences in:
/var/mail/_SITENAME_/_USERNAME_/tmda/config
Folks who run TMDA with Exim have also figured out how to run it directly from Exim without requiring a .forward file. You'll want to check the archives and the FAQ.
I had seen the docs that describe a server-wide setup using Exim 4...
http://mla.libertine.org/tmda-users/2002-11/msg00283.html
...but wasn't sure if such a configuration would allow individual users to turn TMDA on/off. Given a server-wide TMDA installation, is there a way to turn off TMDA via the ~/tmda/config file? If so, perhaps we can get the 2nd Exim process to pass both _SITENAME_ and _USERNAME_ as environment variables to TMDA with a slightly modified tmda_pipe command:
command = /usr/bin/tmda-filter -c /var/mail/$SITENAME/$USERNAME/tmda/config
3. Integrating MailScanner into the XAMS set-up looks like this...
Without knowing much about Exim, I can at least tell you that TMDA operates at delivery time, not during the SMTP conversation, so as long as the second Exim process (the delivery process) can run TMDA, you should be fine. TMDA will also need to relay through an MTA, possibly the first Exim but not necessarily, in order to send out its challenges.
Assuming we get the mail to TMDA somehow, how can we get the mail delivered? For example, one of the options is listed as:
DELIVERY = "/var/mail/$local_part"
Assuming a server-wide setup, do you think there is a way for TMDA to use the environment variables passed from the 2nd Exim process, along the lines of:
DELIVERY = "/var/mail/$SITENAME/$USERNAME"
Or, alternatively, should we just create individual files containing "DELIVERY = "/var/mail/mysite/myusername" for each user, which would be located at:
/var/mail/mysite/myusername/tmda/config
I'm sure by now that the sheer magnitude of my ignorance must be abundantly clear. ;) Thank you very, very much for your guidance!
Justin
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
_____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
