Hi folks,

I've read over all the documentation on the tmda-cgi site, but I'm more than
a little confused as to how a stub program is supposed to be written.

XAMS is a virtual mail system based on MySQL, Exim, and Courier-IMAP. All
user data is stored in MySQL. I understand that stub programs are supposed
to convert output from virtual user information programs into Python DICTs.
But as far as I know, up until today XAMS had no such virtual user
information program. This morning one of my colleagues wrote up a quick
getpath.pl Perl script that was originally meant to be used with
tmda-filter's -S option: it takes the domain and username as parameters and
outputs the appropriate MailDir path. I may be able to re-purpose this Perl
script for use with tmda-cgi, or I could re-write it in Python such that it
retrieves the needed information from MySQL and then outputs the proper
DICTs so that an extra stub isn't needed.

But regardless as to whether I write one program or two, for the life of me
I can't determine exactly what the input/output is supposed to look like.
The documentation says to look at the vpopmail1.py example, but even after
doing so I still don't understand the input side of things.

* What environment is the stub supposed to run from within? In which exact
situations is it called?
* What variables does the virtual user information program have at its
disposal? In order to perform a MySQL DB lookup, I'll have to know what
which information I'm supposed to use to look up the corresponding data.

Given the sparse coverage of stub programs on the tmda-cgi site, it would be
most appreciated if someone could offer a bit more background information,
as well as specific suggestions in light of the environment described above.

If I haven't provided enough information, please let me know and I will
expand. Thanks in advance for any assistance you can offer!

Cheers,

Justin

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

Reply via email to