Using a command line and Windows task scheduler (or another one), you can completely automate mailing lists checking.

Syntax:

AMV.EXE [keys]  [“input file”  [“output file”   [“reverse output file” [“third output file”]]]]

All incorrect values of keys are ignored without warning messages. The available key values are:

-MINIMIZED – to start the program in minimized state;

-SAVELOG – to save log, log will placed in input file directory and with the same name as input file, but with .LOG extension;

-SAVESHORTLOG – to save “short” log, log will placed in input file directory and with the same name as input file, but with .SLOG extension if –SAVELOG key is specified and .LOG otherwise;

-EXITCOMPLETE – to close the program when mailing list is checked and saved. This key works only if the operator did not pause and did not stop the check, and if the output file was given;

-ODBCSQL – the work with ODBC SQL sources, not with mailing lists, see the details below.

The input and output files can have the same name. “Reverse” file is the same as output file but saved with inverted filtering settings. In “third” file AMV save bad, unchecked and unknown emails independently of filtering settings. If the output file is not specified, AMV does not do automatic save of results, and the –EXITCOMPLETE, -SAVELOG and -SAVESHORTLOG keys does not work.

Also, since v1.67 you can set filtering settings for each output file in command line with –FILTER key. The key must be specified after output file. If –FILTER is not specified, output files are used as it described above.

Format: -FILTER:EBUN, where

E – save “exist” emails in output file;

B – save “bad” emails in output file;

U – save “unknown” emails in output file;

N – save unchecked emails in output file.

The  –ODBCSQL key shows that input and output files are the files with SQL requests to ODBC data sources, not the mailing lists. This files contain SQL expressions in the following format:

data_source_name,<username>,<password>,SQL_expression

Angled fields (<>) may be blank, for example:

MyDatasource,

Admin,

Password,

SELECT 

   email

FROM

   customers

WHERE 

   email<>NULL

or

MyDatasource,,,

UPDATE customers

SET result='%result%'

WHERE email='%email%'

For details about SQL request features see the article “Working with ODBC sources” which describe the working of import and export wizards from ODBC sources. See also SqlImport.SQL and SqlExport.SQL files in the directory with Advanced Maillist Verify. When export,  SQL expressions are executed according to specified filtering settings (specified by default or by –FILTER key).

Examples:

AMV.EXE -MINIMIZED -EXITCOMPLETE my.lst “verified my.lst”

AMV.EXE -MINIMIZED “product customers.lst”

AMV.EXE my.lst my.lst

AMV.EXE “c:\program files\Eserv2\mail\lists\admins.txt”

AMV.EXE –SAVELOG –SAVESHORTLOG 1.lst 1.out 1reverse.out

AMV.EXE input.lst output.lst –FILTER:EUN bad.lst –FILTER:B

AMV.EXE in.txt o1.lst –FILTER:E o2.lst –FILTER:NU o3.lst –FILTER:B

AMV.EXE –EXITCOMPLETE my.lst myout.lst –FILTER:NEU

AMV.EXE –ODBCSQL SqlImport.SQL SqlExport.SQL –FILTER:EBUN

AMV.EXE –EXITCOMPLETE –ODBCSQL –SAVELOG SqlImport.SQL SqlOut_1.SQL SqlOut_2.SQL