On 14-May-2001 Dave Palmer wrote:
> Hello...
> before anyone says "rtfm" I want to state quite clearly that I have read the
> entire thing, from top to bottom (thanks to eye-catcher for providing a
> readable version!!!).
>
> I am going to quote directly from the documentation:
>
> "You can use external modules ( executables ) to perform user authentication
> instead of using XMail mailusers.tab lookups."
> -- Excellent! This is what I need to do!
>
> "Suppose We must authenticate USERNAME inside DOMAIN , XMail first try to
> lookup ( inside userauth/pop3 ) a file named :
> DOMAIN.tab
> else :
> defaultauth.tab"
> -- I created a file: MAIL_ROOT/userauth/pop3/stratumllc.com.tab
> -- In this file I have the following contents:
> "userauth" "d:/MailUtilities/auth.bat" "@@USER"
"@@PASSWD"
>
> I "test fired" my 'auth.bat' script (which calls my JVM, which in turn
> executes a Java application [non gui] I wrote which queries our Oracle
> database). Everything works just as it should with the auth.bat script.
>
> First problem... XMail appears to ignore this directive (the .tab file with
> the 'userauth' command). I have enabled logging, and have found nothing out
> of the ordinary (no bad login attempts with the POP3 service)... it just
> appears that XMail is ignoring this. Yes... I did a stop/start of XMail.
Date 08-04-2001 0.70
Added the message ID to the received tag and extended the SMTP log file
with the username of the authenticated user ( if any ).
>>>> Fixed a bug in external authentication ( POP3 ).
The USERDEF.TAB file is now checked inside $MAIL_ROOT/DOMAIN before and
then in $MAIL_ROOT.
This permit per domain user default configuration.
Added a new CTRL server command "frozsubmit" to reschedule a frozen
message.
Added a new CTRL server command "frozdel" to delete a frozen message.
Added a new CTRL server command "frozgetlog" to retrieve the frozen
file log file.
Added a new CTRL server command "frozgetmsg" to retrieve the frozen
message file.
Try 0.70
>
> Second (not really a problem)... in the documentation it states:
>
> "that in success case must return zero. Any other exit code will be
> interpreted as authentication operation failure, that in userauth case means
> that such user will be not authenticated."
>
> This *could* mean anything... does this mean, simply writing out to STDOUT a
> '0' or something else... or does this mean: System.exit(0), or
> something like:
The only way to mean this is that the program must exit with a 0 exit code.
- Davide
