> Hello.
>
> We'd like to move from Sendmail(unix) to Mercury(win2003).
>
> We do not need to migrate existing mail, because it is a training lab.
>
> We'd like to create and delete Mailboxes via Script. How can that be done?
>
> Pointers to existing manuals very welcome
>
> Bye
>
Should be pretty straight forward to modify the pmail.usr file and make the subdirectories for the users. The default pmail.ini and passwd.pm files are also all self explanatory. The only thing that you probably need to do is use the reload users command if you are trying to do this with Mercury/32 running.
* The mail server now has its own password file, created and
managed on the "Mail server" configuration page. This is not
covered in the help yet, but you can create any number of mail
server passwords that can be used in a "PASSWORD" command to
handle the new operations described below. If you have no
password file, then no password will ever succeed and the new
operations will fail automatically - hence the operation is secure by
default. Mail server passwords are simply one-per-line (like
everywhere else) and cannot contain the character ';' (semi-colon).
* A new mail server command, "KILLFILE" has been added. This
command allows you to manipulate the MercuryS killfile by mail. At
present, the only implemented command is "KILLFILE ADD", which
adds the parameter you supply to the MercuryS killfile. An example
is at the end of this message.
* A new mail server command, "RELOAD" has been added. This
command allows you to force Mercury to re-read certain
configuration files by mail. At present, the only implemented
command is "RELOAD USERS", which takes no parameters, and
tells Mercury to reload the user database, PMAIL.USR.
Both of these commands need to be preceded by a PASSWORD
command specifying a valid password from the password file created in
the mail server configuration dialog.
Examples (these examples assume that the password 'foo4u' is
specified in the Mail Server password file):
* To add *@163.com to the MercuryS killfile, issue these commands:
PASSWORD foo4u
KILLFILE ADD *@163.com
* To force Mercury to reload its user database, issue these commands:
PASSWORD foo4u
RELOAD USERS
The commands are not case sensitive - I've shown them in uppercase only to emphasize them.
I plan to add more commands of this kind - administrative in nature - and will be adding a level of discrimination to the password file to allow passwords to work only for certain types of operation (hence the reason why ';' cannot be used in a password).
> Hello.
>
> We'd like to move from Sendmail(unix) to  Mercury(win2003).
>
>  We do not need to migrate existing mail, because it is a training lab.
>
> We'd like to create and delete  Mailboxes via Script. How can that be done?
>
> Pointers to existing manuals very welcome
>
> Bye
>
Should be pretty straight forward to modify the pmail.usr file and make the subdirectories for the users.  The default pmail.ini and passwd.pm files are also all self explanatory. The only thing that you probably need to do is use the reload users command if you are trying to do this with Mercury/32 running.
*   The mail server now has its own password file, created and
    managed on the "Mail server" configuration page. This is not
    covered in the help yet, but you can create any number of mail
    server passwords that can be used in a "PASSWORD" command to
    handle the new operations described below. If you have no
    password file, then no password will ever succeed and the new
    operations will fail automatically - hence the operation is secure by
    default. Mail server passwords are simply one-per-line (like
    everywhere else) and cannot contain the character ';' (semi-colon).
*   A new mail server command, "KILLFILE" has been added. This
    command allows you to manipulate the MercuryS killfile by mail. At
    present, the only implemented command is "KILLFILE ADD", which
    adds the parameter you supply to the MercuryS killfile. An example
    is at the end of this message.
*   A new mail server command, "RELOAD" has been added. This
    command allows you to force Mercury to re-read certain
    configuration files by mail. At present, the only implemented
    command is "RELOAD USERS", which takes no parameters, and
    tells Mercury to reload the user database, PMAIL.USR.
Both of these commands need to be preceded by a PASSWORD
command specifying a valid password from the password file created in
the mail server configuration dialog.
Examples (these examples assume that the password 'foo4u' is
specified in the Mail Server password file):
* To add *@163.com to the MercuryS killfile, issue these commands:
      PASSWORD foo4u
      KILLFILE ADD *@163.com
* To force Mercury to reload its user database, issue these commands:
      PASSWORD foo4u
      RELOAD USERS
The commands are not case sensitive - I've shown them in uppercase only to emphasize them.
I plan to add more commands of this kind - administrative in nature - and will be adding a level of discrimination to the password file to allow passwords to work only for certain types of operation (hence the reason why ';' cannot be used in a password).
