This file contains a sample Multi-List Configuration File. Refer to the Multi-List documentation for a detailed discussion of the correct format for this file.

list configuration file version = '1.0'

; Multi-list configuration file for various dog-related mailing lists

; Each list will generate its own server files, but all defunct addresses
; will be written to the same BCC file (the BCC file name is specified in
; the Preferences file).

; I'll assume that "separate fuzzy files" is turned off in the Preferences
; file, so all matches will be placed into the standard (non-fuzzy) server,
; secondary server, and BCC files, unless otherwise instructed. Also, I'll
; assume that the list server type specified in the Preferences file is
; 'ListProc', so all server files will be formatted for ListProc unless
; otherwise specified.

; We'll also assume that all of the lists are running on LISTSERV servers,
; EXCEPT the Labrador list, which is running on a Majordomo server. Further,
; let's assume that the Labrador list is extremely large.

; The default configuration in the Preferences file will be that of the
; Doberman list; thus, no parameters need to be changed to process that
; list:

;------------------------------------------------------------------------
; Doberman list (use default configuration):
;------------------------------------------------------------------------

START CONFIG
END CONFIG

;------------------------------------------------------------------------
; German Shepherd list
;------------------------------------------------------------------------

START CONFIG
list name = 'german_shepherd'
list password = 'WOOF!'

bounce file name = 'shepherd_bounces.txt'

subscriber list file name = 'german_shepherd_list.txt'
server file name = 'german_shepherd_server_file.txt'
redirects file name = 'german_shepherd_redirects_file.txt'
END CONFIG

;------------------------------------------------------------------------
; Golden Retriever list -- for this list ONLY, turn on separate fuzzy files
; Note that exact matches are still written to the primary BCC file, so we
; don't need to reiterate the file name here. But we do need to specify the
; name of the BCC fuzzy file, unless we want to use the one that is
; specified in the Preferences file.
;
; In addition, let's assume that bounces from the Golden Retriever list
; are grouped with those of the Doberman list -- and since we've already
; processed that bounce file, there is no need to process it again, so we
; will not insert a new bounce file name here.
;------------------------------------------------------------------------

START CONFIG
separate fuzzy files = 'YES'

subscriber list file name = 'golden_retriever_list.txt'
server file name = 'golden_retriever_server_file.txt'
redirects file name = 'golden_retriever_redirects_file.txt'

list name = 'golden_retriever'
list password = 'gold!'

server fuzzy file name = 'golden_retriever_server_fuzzy.txt'
redirects fuzzy file name = 'golden_retriever_redirects_fuzzy.txt'
BCC fuzzy file name = 'golden_retriever_BCC_fuzzy.txt'
END CONFIG

;------------------------------------------------------------------------
; Poodle list -- for this list ONLY, turn off address verification,
; do not check Ignored-file addresses, and do not process unsubscribes
; or redirects.
;------------------------------------------------------------------------

START CONFIG
process unsub requests = 'NO'
process redirects = 'NO'
use ignored file = 'NO'
match bounce addresses to subscriber list = 'NO'

list name = 'poodle'
list password = 'stealth_cats'

bounce file name = 'poodle_bounces.txt'

subscriber list file name = 'poodle_list.txt'
server file name = 'poodle_server_file.txt'
redirects file name = 'poodle_redirects_file.txt'
END CONFIG

;------------------------------------------------------------------------
; Labrador list -- Since this list is huge, turn off the detailed display.
; Also, since this file is running on the Majordomo server, put all the
; defunct addresses on the "BOUNCE" list, rather than unsubscribe them.
; Also, let's export bounces from this list to a separate file, so that
; we can manually process the bounces that MailBounce doesn't recognize.
;------------------------------------------------------------------------

START CONFIG
detailed display = 'NO'
list server type = 'MAJORDOMO'
list name = 'labrador'
list password = 'labbies'
address removal mode = 'BOUNCE'

bounce file name = 'bounces.txt'

write unrecognized bounces to file = 'YES'
unrecognized bounces file name = 'unrecognized_labrador_bounces.txt'

subscriber list file name = 'labrador_list.txt'
server file name = 'labrador_server_file.txt'
redirects file name = 'labrador_redirects_file.txt'
END CONFIG

;------------------------------------------------------------------------
; All done.
;------------------------------------------------------------------------

[home]

[ReadMe]