Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| ref:fidonet_files [2010/02/25 19:07] – digitalman | ref:fidonet_files [2020/12/24 17:23] (current) – [Stored Message] typo digital man | ||
|---|---|---|---|
| Line 48: | Line 48: | ||
| attachments, | attachments, | ||
| style mailers always send NetMail messages packed into Packets, | style mailers always send NetMail messages packed into Packets, | ||
| - | so there is no " | + | so there is no " |
| associated with a Binkley/ | associated with a Binkley/ | ||
| deal with Stored Messages (a.k.a. ".msg files" | deal with Stored Messages (a.k.a. ".msg files" | ||
| Line 58: | Line 58: | ||
| one or more Packed Messages. | one or more Packed Messages. | ||
| - | Packets may contain NetMail or EchoMail messages. | + | [[ref: |
| - | Packet files have a '' | + | Packet files have a '' |
| files "in process" | files "in process" | ||
| of a Packet can actually be *anything*, but is usually a | of a Packet can actually be *anything*, but is usually a | ||
| - | numeric time stamp of some sort. SBBSecho | + | numeric time stamp of some sort. SBBSecho |
| - | (where each pair of letters is a 2-digit zero-padded decimal | + | where each pair of letters is a 2-digit zero-padded decimal |
| - | number representing the Day of the month, hour of the day, | + | number representing the day of the month, hour of the day, |
| - | minute, and second at the time the packet was created) | + | minute, and second at the time the packet was created |
| + | SBBSecho v3 uses the packet creation time in Unix time_t format | ||
| + | (seconds since Jan-1-1970) represented with hexadecimal digits | ||
| as the base file name when creating Packet files. The | as the base file name when creating Packet files. The | ||
| important thing is that the Packet files have unique names. | important thing is that the Packet files have unique names. | ||
| Line 162: | Line 164: | ||
| Flow Files are unique to Binkley/ | Flow Files are unique to Binkley/ | ||
| - | BSO) mailers | + | BSO) mailers |
| containing plain text (so they can be easily viewed or edited, unlike the | containing plain text (so they can be easily viewed or edited, unlike the | ||
| other file types described in this document). | other file types described in this document). | ||
| Line 170: | Line 172: | ||
| NNNNnnnn.Flo | NNNNnnnn.Flo | ||
| - | where " | + | where " |
| - | hexadecimal number, and " | + | hexadecimal number, and " |
| a 4-digit zero-padded hexadecimal number, and " | a 4-digit zero-padded hexadecimal number, and " | ||
| " | " | ||
| - | (C)rash, (D)irect/Immediate, (H)old, or F, for " | + | (C)rash, (D)irect/(I)mmediate, (H)old, or F, for " |
| - | Another | + | Another |
| address is a " | address is a " | ||
| is the destination point number as an 8-digit zero-padded hexadecimal | is the destination point number as an 8-digit zero-padded hexadecimal | ||
| Line 184: | Line 186: | ||
| NNNNnnnn.pnt | NNNNnnnn.pnt | ||
| - | where " | + | where " |
| - | hexadecimal number, and " | + | hexadecimal number, and " |
| for example: | for example: | ||
| Line 205: | Line 207: | ||
| indicates whether or not to delete or truncate the file after its | indicates whether or not to delete or truncate the file after its | ||
| been sent (i.e. '#' | been sent (i.e. '#' | ||
| - | |||
| ==== BT-USER.TXT ==== | ==== BT-USER.TXT ==== | ||
| Line 350: | Line 351: | ||
| ===== BT-REF.TXT ===== | ===== BT-REF.TXT ===== | ||
| - | Snippet | + | Snippets |
| + | |||
| + | ==== Outgoing file requests ==== | ||
| + | These can be generated by BinkleyTerm or by using one of the many | ||
| + | utilities designed for the purpose, such as Amax, Bonk, Please, | ||
| + | etc. Any Opus-compatible file request builder can be used with | ||
| + | BinkleyTerm. | ||
| + | a single-line flat ASCII text file, and are named in the same | ||
| + | manner as packets (refer to the User Manual section "How | ||
| + | BinkleyTerm Handles Mail" for information on the naming convention) | ||
| + | and have a file extension of .REQ. Outgoing requests should NEVER | ||
| + | have a drive and path designation; | ||
| + | system handles the drives and paths. | ||
| + | |||
| + | The '' | ||
| + | |||
| + | BinkleyTerm will not place calls for a stand-alone .REQ file. In | ||
| + | order for a call to be placed, a packet or file attach of the | ||
| + | proper flavor must also exist (this will be prepared, along with | ||
| + | the .REQ file, by utilities such as Bonk and Amax). | ||
| + | manually poll to send the request immediately. | ||
| - | ==== Where is the outbound area for points? | + | ==== Points |
| - | Let's say you are storing | + | Where is the outbound area for points? |
| mail for points off of a system whose address is 1: | mail for points off of a system whose address is 1: | ||
| would do so by creating a directory '' | would do so by creating a directory '' | ||
| Line 365: | Line 386: | ||
| C: | C: | ||
| + | |||
| ===== See Also ===== | ===== See Also ===== | ||
| * [[: | * [[: | ||
| - | * [[:util:SBBSecho]] | + | * [[:util:SCFG]] |
| * [[: | * [[: | ||
| * [[: | * [[: | ||
