Differences

This shows you the differences between two versions of the page.

--- mutil_import_echomail [2016/04/01 04:33] – import echomail page - added further options avon
+++ mutil_import_echomail [2023/01/03 02:24] (current) – added dos_filename switch avon
@@ Line 26: / Line 26: @@
   ;dupe_db_size = 32000
+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 ==
@@ Line 36: / Line 40: @@
   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.  To disable this function comment it out or
+set it to a blank value.
+bad_packet = c:\mystic\echomail\badpkt
 == Strip SEEN-BY lines ==
@@ Line 48: / Line 59: @@
   ; Strip SEEN-BY lines from messages when importing?
   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=<msgs> D=<days> or else the rescan will refuse to perform any action.  The default is the last 250 messages for each base.  Setting it to D=90 for example would give the last 90 days of messages.  If you want the default to send every message in the base, then set it to go back a ridiculous number of messages R=999999999
+  default_rescan = R=250
 == 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 <orig>;<new>
+If you want to remap netmail from one user name to another, you can define up to 50 remapped names below using the format <orig>;<new>  The new portion can optionally contain @net_address
+Names are case insensitive.  Each line is processed in the order in which they appear meaning a single message can be processed by many lines. This means for example you can map multiple names to "Sysop" and then on the last line map "Sysop" to something else.  If the "New" portion of the definition contains @<address> then the Netmail will be forwarded to another address entirely.  Forwarding even works for automated To fields like Areafix, so if you are a hub and someone accidentally Areafix your BBS you can have your BBS forward that Netmail to your hub system so it can be processed properly.
 Uncomment this setting to enable it.
@@ Line 57: / Line 78: @@
   ;forward = sysop;g00r00
   ;forward = system operator;g00r00
+  ;forward = g00r00;James Coyle
+  ;forward = James Coyle;James Coyle@21:1/108
 == Twit Filter ==
@@ Line 62: / Line 85: @@
 This option allows you to filter names and other key metadata so that messages from 'twits' are not imported or tossed to down-links your BBS may be sending messages on to.
-Your can define multiple terms for what you consider a 'twit' is - one entry per line - with a maximum of up to 100 entries. Uncomment and customize this setting to enable it.
+Your can define multiple terms for what you consider a 'twit' is - one entry per line - with a maximum of up to 100 entries. Please note that this should not be used if you are a HUB system that feeds echomail to other users unless there is very good reason to do so as it will prevent the messages from passing through your system. This feature is intended to be a moderation tool used only in extreme cases.
+Uncomment and customize this setting to enable it.
   ;twit=John Guillory
@@ Line 76: / Line 101: @@
   auto_create = true
+== Create JAM filenames in the DOS 8.3 file format ==
+  dos_filename = 0
+Valid options are:
+= Do not use 8.3 filename (uses echotag for filename)
+= Use shortened 8.3 filename (trimmed based on the echotag name)
+= Use random hex 8.3 filename
 == Convert Filenames to Lowercase ==
@@ Line 81: / Line 116: @@
 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.
-  lowercase_filename = 1 ; Convert filenames to lowercased 1=true
+  ; 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:
-  base_format    = 0         ; base format 0=jam
-  acs_list       = s10       ; ACS to see the message base
+  ; ACS to see the message base
-  acs_read       = s10       ; ACS to read messages in the message base
+  acs_list       = s10
-  acs_post       = s20       ; ACS to post a message in the message base
+  ; ACS to read messages in the message base
-  acs_news       = s20       ; ACS to post a message via NNTP server
+  acs_read       = s10
-  acs_sysop      = s255      ; ACS to use the message base with sysop access
+  ; ACS to post a message in the message base
-  header         = msghead   ; ANSI header to use in the message base
+  acs_post       = s20
-  read_template  = ansimrd   ;
+  ; ACS to use the message base with sysop access
-  index_template = ansimlst  ;
+  acs_sysop      = s255
-  max_msgs       = 500       ; maximum messages to retain
+  ; ANSI header to use in the message base
-  max_msgs_age   = 365       ; maximum number of days to hold messages
+  header         = msghead
+  ;
+  read_template  = ansimrd
+  ;
+  index_template = ansimlst
+  ; maximum messages to retain
+  max_msgs       = 500
+  ; maximum number of days to hold messages
+  max_msgs_age   = 365
   ; true/false type values 0=false 1=true (newscan 2=forced)
-  use_autosig    = 1  ; allow auto signatures in this base?
+  ; allow auto signatures in this base?
-  use_realname   = 0  ; use real names in this base?
+  use_autosig    = 1
-  kill_kludge    = 1  ; kill kludge lines in this base?
+  ; use real names in this base?
-  new_scan       = 1  ; base is part of new messages scan?
+  use_realname   = 0
-  qwk_scan       = 1  ; base is part of new messages scan for QWK network?
+  ; kill kludge lines in this base?
+  kill_kludge    = 1
+  ; base is part of new messages scan?
+  new_scan       = 1
+  ; base is part of new messages scan for QWK network?
+  qwk_scan       = 1
 == Define Specific Auto-Create Settings Based On Sender ==
@@ Line 109: / Line 158: @@
 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 , and you had defined fsxNet as message group #1 in the Message Group Editor in your Mystic BBS. You would set the following:
+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:
 :1/100_acs_list     = s10g1
 :1/100_acs_read     = s10g1
 :1/100_acs_post     = s20g1
-:1/100_acs_news     = s20g1
 :1/100_acs_sysop    = s255g1
 :1/100_use_realname = 0