mutil_import_echomail
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
mutil_import_echomail [2016/03/30 03:57] – import echomail page - work in progress avon | mutil_import_echomail [2021/12/22 12:43] – g00r00 | ||
---|---|---|---|
Line 26: | Line 26: | ||
; | ; | ||
- | | + | |
+ | Duplicate scanning by checking for a circulate PATH reference can be enabled or disabled although it is extremely highly recommended to keep this enabled unless you have a very specific reason you need to temporarily disable it. | ||
+ | |||
+ | dupe_circular = true | ||
== Import Unsecure Packets == | == Import Unsecure Packets == | ||
Line 36: | Line 40: | ||
unsecure_dir = false | unsecure_dir = false | ||
| | ||
+ | == Bad Packets == | ||
+ | |||
+ | This setting defines a directory where any PKT files will be moved to if the password check fails or there is some other issue with addressing that would cause it to not be processed. | ||
+ | set it to a blank value. | ||
+ | |||
+ | bad_packet = c: | ||
+ | |||
== Strip SEEN-BY lines == | == Strip SEEN-BY lines == | ||
- | Should | + | This setting instructs |
- | SEEN-BY lines are used by mail tossers to check that they are not importing something that they have already seen (a dupe). SEEN-BY lines also provide a good record of which BBS' | + | SEEN-BY lines are used by mail tossers to check that they are not importing something that they have already seen (a dupe). SEEN-BY lines also provide a helpful |
+ | |||
+ | Some system operators prefer to strip SEEN-BY lines when importing messages | ||
This setting uses a Boolean True or False switch. | This setting uses a Boolean True or False switch. | ||
Line 46: | Line 59: | ||
; Strip SEEN-BY lines from messages when importing? | ; Strip SEEN-BY lines from messages when importing? | ||
strip_seenby = false | strip_seenby = false | ||
+ | |||
+ | == Default Rescan Settings == | ||
+ | |||
+ | This setting allows you to define what the default behavior of your Mystic BBS will be when it receives a full %RESCAN command via netmail from someone. | ||
+ | |||
+ | This must be a valid command (ie R=< | ||
+ | |||
+ | default_rescan = R=250 | ||
== Remapping Netmail == | == Remapping Netmail == | ||
- | | + | If you want to remap netmail from one user name to another, you can define up to 50 remapped names below using the format < |
+ | |||
+ | Names are case insensitive. | ||
+ | |||
+ | Uncomment | ||
+ | |||
+ | ;forward = sysop; | ||
+ | ;forward = system operator; | ||
+ | ;forward = g00r00; | ||
+ | ;forward = James Coyle;James Coyle@21: | ||
+ | |||
+ | == Twit Filter == | ||
+ | |||
+ | This option allows you to filter names and other key metadata so that messages from ' | ||
+ | |||
+ | Your can define multiple terms for what you consider | ||
+ | |||
+ | Uncomment and customize this setting to enable it. | ||
+ | |||
+ | ;twit=John Guillory | ||
+ | ; | ||
+ | ; | ||
+ | ; | ||
| | ||
+ | == Automatically Create New Message Bases == | ||
+ | |||
+ | This is one very cool and powerful feature. Use this if you would like MUTIL to auto create message bases when it finds an Echomail message for a non-existing base while importing messages in to your BBS. | ||
+ | |||
+ | This setting uses a Boolean True or False switch. The default setting is True. | ||
+ | |||
+ | auto_create = true | ||
+ | | ||
+ | == Convert Filenames to Lowercase == | ||
+ | |||
+ | This setting allows you to create data files associated with the auto-created message base to be either named in an upper or lowercase naming convention. Lowercase tends to be the preferred option. | ||
+ | |||
+ | ; Convert filenames to lowercased 1=true | ||
+ | lowercase_filename = 1 | ||
+ | |||
+ | You then set a number of options as the **default values** MUTIL will apply when a message base is auto-created: | ||
+ | |||
+ | |||
+ | ; ACS to see the message base | ||
+ | acs_list | ||
+ | ; ACS to read messages in the message base | ||
+ | acs_read | ||
+ | ; ACS to post a message in the message base | ||
+ | acs_post | ||
+ | ; ACS to use the message base with sysop access | ||
+ | acs_sysop | ||
+ | ; ANSI header to use in the message base | ||
+ | header | ||
+ | ; | ||
+ | read_template | ||
+ | ; | ||
+ | index_template = ansimlst | ||
+ | ; maximum messages to retain | ||
+ | max_msgs | ||
+ | ; maximum number of days to hold messages | ||
+ | max_msgs_age | ||
+ | |||
+ | ; true/false type values 0=false 1=true (newscan 2=forced) | ||
+ | | ||
+ | ; allow auto signatures in this base? | ||
+ | use_autosig | ||
+ | ; use real names in this base? | ||
+ | use_realname | ||
+ | ; kill kludge lines in this base? | ||
+ | kill_kludge | ||
+ | ; base is part of new messages scan? | ||
+ | new_scan | ||
+ | ; base is part of new messages scan for QWK network? | ||
+ | qwk_scan | ||
+ | | ||
+ | == Define Specific Auto-Create Settings Based On Sender == | ||
+ | |||
+ | If you want to create settings specific to certain node addresses that send your system messages - you can! | ||
+ | |||
+ | For example, if you wanted to auto create bases that were linked to your fsxNet feed using the fsxNet HUB address of 21:1/100 , you have defined fsxNet as message group #1 in the Message Group Editor, you want non-validated users (s10) to see and read messages in the message base, but only validated users (s20) to be able to post. You would set the following: | ||
+ | |||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ | 21: | ||
+ |
mutil_import_echomail.txt · Last modified: 2023/01/03 02:24 by avon