; These are my private settings. If you're running a non-private gate, you'll
; need to change almost all of these settings. Remember to change CROSSPOST
; and NAUGHTYREPLY

; Your Site-name.
;
SITE "boble.ping.dk"

; Give me a place to work
;
TEMPDIR "t:"

; Your UUSpool directory
;
; Defaults to UUSPOOL:
;UUSPOOLDIR "UUSPOOL:"

; Where shall I look for FidoNet messages to gate?
; Fully qualified name of the packet.
;
FIDOTOUUCP "Mail:OutBound/2.999.99.0.OUT"

; Shall I delete the FidoNet original-packet after processing it?
;
; NOTE: Just comment out this line if you don't want packets to be deleted
;
DELETEPACKET

; Your FidoNet-address, sir?
;
NODEADDRESS "2:999/99.9"

; The "fake" FidoNet-address assigned to AmiGate?
;
; Your tosser should toss U->F messages to this address.
; In case you are running a node this will usually be a point address.
;
GATEADDRESS "2:999/99.0"

; The origin for FidoNet-messages coming from UseNet?
;
; NOTE: This will only be used if the message does not contain an Organization
;       header unless you also specify STATICORIGIN.
;
ORIGIN "Boblebadet"

; This will be put in the UseNet-messages coming from your site via AmiGate
;
ORGANIZATION "Boblebadet, Copenhagen, Denmark"

; Crossposted UseNet messages will be gated to the appropriate FidoNet areas.
;
; Comment out this line and it will only be gated to the first matching
; FidoNet area (very useful is you run a private site and don't want to look
; at all these MB crossposts).
;
;CROSSPOST

; The following is to support STUPID UseNet news readers
; which cannot figure out how to break lines that are too long.
;
; LINEBREAK will cause an EXPLICIT line break to be inserted into
; any line which is longer than 79 characters. This slows down F->U gating
; a bit.
;
; Leave it on unless you are wearing a flamesuit!
;
LINEBREAK

; Your FidoNet Inbound directory, please?
;
; I'll stuff my UUCP->Fido-gated packages there.
;
INBOUND "Mail:Inbound"

; TimeZone si'l vous plait.
;
TIMEZONE "CET"

; Fully qualified name of your RNews executable along with arguments
;
; Leave blank for manual processing
;
;RNEWS "uucp:c/rnews -h -t T:"

; Fully qualified name of your RNews executable along with arguments
;
; This will be used for posting news and MUST be filled out
;
SENDNEWS "uucp:c/rnews -h -p -t T:"

; Fully qualified name of your BatchNews executable along with arguments
;
; Leave blank for manual processing
;
BATCHNEWS "uucp:c/batchnews -t T:"

; Fully qualified name of your SendMail executable
;
SENDMAIL "uucp:c/sendmail -R \"\" <"

; Fully qualified name of your UnCompressBatch executable
;
UNCOMPRESSBATCH "uucp:c/uncompressbatch -u \"Gzip -d -c\" -t T:"

; Do you want me to delete incoming UUCP-news after processing them.
;
; Comment out this line if you want to keep them for manual processing
;
; NOTE: If you have specified RNEWS then the news files will always be
;       deleted, so this only makes sense, if RNEWS is left out.
;
DELETEUUCPNEWS

; Do you want me to delete incoming UUCP-Emails after processing them.
;
; NOTE: Comment out this line if you want to keep them for manual processing
;
DELETEUUCPMAIL

; where to put the logfile...
;
LOGFILE "Logs:AmiGate.log"

; Set the loglevel.
;
; 0 Error                  LogChar "+" 
; 1 Warnings               LogChar "-"
; 2 General info           LogChar "|" 
; 3 Detailed info          LogChar "!"
; 4 Accounting             LogChar "$"
; 5 General debug          LogChar "#" 
; 6 Detailed debug         LogChar "*"
;
LOGLEVEL 4

; Set the Consolelevel.
;
CONSOLELEVEL 6

; If you want accounting infomation placed in a separate log-file
; specify the name here. 
;
; NOTE: You still have to set the LOGLEVEL to 4 or higher.
ACCFILE "Logs:AmiGateAcc.log"

; AmiGate can be configured to be a public gate if you like.
; 
; Specify PUBLIC and the type.

; 0 This is the same as leaving out the PUBLIC keyword.
;   AmiGate will only gate to and from users in the AmiGate.users file.
; 1 Public gating with FTN style addressing for both news and emails.
;   AmiGate will the search the AmiGate.users file before falling back to FTN
;   style adressing.
; 2 Same as no. 1 but Fidonet users not listed in the AmiGate.users file will
;   only be allowed to send news (no emails).
; 3 Public gating with site style addressing for both news and emails.
;   AmiGate will the search the AmiGate.users file before falling back to site
;   style adressing.
PUBLIC 0

; PACKETAPPEND will make AmiGate append U->F messages to existing packets
; your INBOUND directory.
;
; It traverses the INBOUND directory looking for a packet which is smaller
; than 100 KB. If it exists gated messages will be appended to this packet,
; if not a new packet will be created.
;
; If you use AmiGate together with AmiTCP/NNTPXfer please set this or else
; you will get a PKT file for each news-file.
PACKETAPPEND

; Okay now it's time to specify what AmiGate should do with the UUCP-headers
; when gating U->F. You have three different choices:
;
; PORT   The header will be ported directly to FidoNet and become part of
;        the message text.
;
; STRIP  The header will be stripped from the FidoNet message.
;
; KLUDGE The header will be ported to FidoNet but hidden with an IFNA kludge
;        (^A).
;
; First specify the default:
KLUDGE
;
; Now specify exceptions to the default:
;
STRIP "Received:"
STRIP "Subject:"
STRIP "X-Charset:"
STRIP "X-Char-Esc:"
STRIP "Lines:"
STRIP "Path:"
STRIP "Sender:"
STRIP "NNTP-Posting-Host:"
STRIP "Distribution:"
STRIP "References:"
STRIP "From"
STRIP "Message-ID:"
STRIP "Organization:"
STRIP "Newsgroups:"
STRIP "To:"
STRIP "Reply-To:"
STRIP "Date:"
STRIP "Xref:"
STRIP "Originator:"
STRIP "Content-Length:"
STRIP "Precedence:"
STRIP "X-Listprocessor-Version:"

PORT "Content-Type: multipart/mixed;"
PORT "Content-Type: message/partial;"

; /* *********************************************************************** */
; /* Seldomly used keywords follows here. Under normal circumstances all of  */
; /* these should remain unset.                                              */
; /* *********************************************************************** */

; AKA-Site, usually not needed
;
;AKASITE "blob.ping.dk"

; If your tosser needs fakenet SEEN-BY's on FidoNet Echomail messages
; specify your fakenet here.
;
;FAKENET "10311"

; The origin for FidoNet-messages coming from UseNet will normally contain the
; Organization header from the UseNet article.
;
; If you use this switch, then it will always contain the text from the ORIGIN
; keyword.
;STATICORIGIN

;You can use the HEADERTEXT to put a headertext in all UUCP-messages
;coming from your site.
;
;Use at your own risk. RTFM before using this keyword.
; Potentionally dangerous, since you can use this
;  to create headers that are non-RFC conforming.
;
;Under normal circumstances there is no need to use HEADERTEXT.
;
;It accepts some limited format specifiers:
;
; %n inserts the users email-address (without sitename appended).
; %N inserts the users real name.
; %s inserts your SITENAME.
; %% inserts a % character.
; \n inserts a newline character.
;
;It is for instance useful to generate a different Reply-To: header.

;HEADERTEXT "Reply-To: %n@%s (%N)\nX-CrazyHeader: Afternoons and coffeespoons"

;This allows you to specify the maximum size of messages that will be gated.
;
;Currently this only applies to U->F gating.
;
;Only the size of the message text is measured, so set it a few hundred bytes
;lower to account for the message header and trailer.
;
;Messages that exceeds this size will be splitted.
;
;If you comment out this keyword no size splitting will be done.
;
;MAXMSGSIZE 16000

; AUTOAREA will cause areas not listed in the AmiGate.areas to be added
; on the fly when gating from UseNet->FidoNet. Postings will be gated into
; a "JUNK" area. This is similiar to the junk conference used by GRn.
;
; You can not reply to messages gated into this area. AmiGate will refuse
; them.
;AUTOAREA

; When using a news to mail gateway, you might get your news postings tossed
; back at you. If you specify:
;DELETENEWSFROMUS
; AmiGate will ignore news from your feed that has a user on your SITE as a
; sender. Recommended setting is off.

; If you are using a servide that won't allow you to post news as news (like
; demon in the UK) you can use this option in conjunction with the "N" option
; in the areas setting to have the news posted from your site gated into an
; email with the name of this server appended.
;
; RTFM for further explanations.
;NEWSSERVER "news.demon.co.uk"

; If you want to put a blank line in FidoNet messages
; after kludges but before the message text
; + a blank IFNA ^A kludge between "true" FidoNet kludges and KLUDGED
; UUCP headers specify:
BLANKLINE

; When determining whether a user is allowed to use the gate AmiGate normally
; only searches the AmiGate.users file.
;
; Specifying DLGMODE causes AmiGate to also check the UUCP flag in
; USER:uucpname/User.Data as used by DLG.
;
; If the UUCP flag is set to 2 then the user will be allowed to post.
;DLGMODE

; XENOLINK Will cause AmiGate to ignore who sent the packet
; (packetheader sender) and always put INTL: kludges on netmails.
;
; Only use if you _have_ to.
;XENOLINK

; If you specify USEORIGID AmiGate will translate:
;
; 1) UseNet->FidoNet: "Message-ID:" header will be translated to "^ORIGID:" kludge
;
; 2) FidoNet->UseNet: "^ORIGID" kludge will be translated to "Message-ID:" header
;
; This is a german extension to the FSC (FidoNet proposals).
; Don't use it if you don't need it.
;USEORIGID

; Some BBS software/FidoNet editors do not support the REPLYADDR kludge as
; described in FSC-0035. 
; If you specify
;NOREPLYADDR
; AmiGate will try to put the email address of the sender into the FidoNet
; To: field instead of the real name. If the email-address is longer than
; the 36 characters allowed in the FidoNet To: field, it will use the
; REPLYADDR kludge anyway.
; Don't use it if you don't need it.

; RTFM before using this switch. This switch will cause AmiGate to generate
; illegal FidoNet MSGID kludges, use with extreme caution.
;
; Comment it out if you are gating for anyone else but yourself.
NAUGHTYREPLY