JLM <[EMAIL PROTECTED]> writes:
I can't help you with the Exim-specific issues. Hopefully some of our
Exim users will be able to make suggestions. I will make A few
comments about the possible interaction of TMDA with the XAMS system.
> 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.
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. I'm
afraid I have no idea what MESSAGEID means, since no messages are
stored in the maildir itself, but rather in the new and cur
subdirectories.
A Courier maildir++ adds the ability to nest one level of maildirs
(and only one level) inside a top-level maildir. It requires that the
names of those sub-maildirs start with a dot ('.'). It simulates
deeper levels of nested folders by using a dot as a separator. Thus
the logical INBOX/Sent is stored on disk as INBOX/.Sent (.Sent is a
maildir) and INBOX/Current/SPAM is stored as INBOX/.Current.SPAM
(.Current.SPAM is a maildir).
> The TMDA "Pre-Configuration" and "Server Configuration" section
> talks about a lot of files that are stored in ~/.tmda/, but I get
> the feeling that putting /.tmda/config and .forward files in the
> /private/var/mail/My Virtual Host Site/myuser/ directory isn't going
> to mesh with the way that either TMDA or XAMS operates. If you feel
> this assumption is wrong or if you need more information to answer
> this, please let me know.
Putting the .tmda directory in the _USERNAME_ directory is certainly
possible, but may collide with Courier's maildir++ specification,
assuming _USERNAME_ is actually the maildir++ directory used by
Courier. You can also put the .tmda directory elsewhere. You can
have one per user or one for the Virtual Host Site or one for the
entire XAMS installation. There are pros and cons each way.
> 2. Assuming my intuition above is correct, is there any flexibility on the
> part of TMDA as to where the relevant configuration data (whitelists,
> blacklists, user prefs, etc.) can be stored? Is it possible to somehow store
> TMDA's information in a custom directory? [Tangent: While XAMS stores most
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
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.
> 3. Integrating MailScanner into the XAMS set-up looks like this... Exim
> receives mail and puts it in /var/spool/exim_incoming. MailScanner checks
> this queue every few milliseconds and processes its anti-virus/SpamAssassin
> options on mail it finds there before putting "clean" mail into
> var/spool/exim_outgoing. Another Exim process then takes this outgoing mail
> and delivers it. (The first Exim process listens on port 25 and only puts
> mail into the exim_incoming queue, while the second Exim process doesn't
> listen on port 25 and only delivers mail.) How will this set-up affect the
> installation instructions for TMDA? Assuming the above TMDA config data
> issues can be solved, are there any other changes that need to be made to
> get TMDA to work in an XAMS/MailScanner environment using two Exim processes
> as described above?
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.
Tim
_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users
