Joshua Alexander <[EMAIL PROTECTED]> writes:

> Since this isn't likely to change any time soon, I would appreciate it
> if anyone else on the list could answer my two questions above as well
> as these:
> 
> Is this file [crypt_key] necessary for TMDA to send confirmation
> emails?

'crypt_key' is necessary for TMDA to do just about anything, including
sending confirmation requests and validating the responses.

> If so, how do I make one without TMDA.cgi?

$ /path/to/tmda-keygen

> 1) What is the minimum user configuration (files & their content)
> necessary for TMDA to send confirmation request emails?

For a standard qmail installation, you need 'crypt_key' and .qmail and
.qmail-default files at a minimum.  The .qmail-default is usually a
symlink to .qmail.  This means that everyone who sends you mail will
have to confirm, every time they send you mail.  Any more flexibility
requires your active participation to configure it.  Different people
do this differently, which is why there is no boilerplate.

Unfortunately, vpopmail complicates things.  It looks like (from your
statements below) that you have a shell account (you can log in) and
that your mail is delivered somewhere inside ~/mail.  I'll have to
understand your particular configuration before I can tell you what
files you'll need and where to put them.  The dot-qmail files you need
will be determined by whether you want all email accounts, most of
them or just a few to be protected by TMDA.

> 2) In my account's ~/mail directory I see test/inbox and
> mydomain.com/test/inbox which seem to always contain the same
> content. Does .tmda go in ~/mail/test/ or ~/mail/mydomain.com/test/ or
> both? I know my host is using exim and vpopmail. If there are any
> questions about their setup, I can ask.

Exim and vpopmail.  Hmmm.  I have no idea how that works.  In fact,
I've never heard of such a combination even being attempted.  I'm
afraid I'd have to know how Exim is configured in order to figure out
where mail is delivered.  TMDA integrates into the mail delivery
process and without detailed information about how that process takes
place I can't begin to guess how to set this up.  It's also extremely
odd that you have both ~/mail/test and ~/mail/mydomain.com/test
directories....

If you can get Exim config information from your provider you can
either post it here or, if your provider isn't comfortable with that,
send it to me privately.

> 3) Does TMDA.cgi work with virtual domains and their multiple email
> accounts? In other words, does the fact that it didn't seem to when I
> used it only a result of my host's incorrect configuration.

tmda-cgi does work with vpopmail, although it may assume that the MTA
is qmail.  If your host's configuration is weird (although not
necessarily incorrect), tmda-cgi may not work automatically.  Perhaps
your host can configure tmda-cgi to work with their particular setup.

> When my host's installation of it was working, I could only log in
> with my primary account name and it created files in ~/.tmda. I
> could not log in with other email account names & passwords or see
> how I could edit other .tmda folders.

Looks like they didn't set up tmda-cgi with virtual domains in mind.
They would have needed to inform the installation process that
vpopmail was being used.

Sorry I can't be of more help, but the configuration you describe is
so far removed from anything I've ever seen that I'm flailing.  It is
almost certainly possible to get TMDA working with the software you
have.  We'll just need some more information.


Tim

_____________________________________________
tmda-users mailing list ([EMAIL PROTECTED])
http://tmda.net/lists/listinfo/tmda-users

Reply via email to