Configuration file readout

specification of the format in the spec

spec/spec.md

@@ -72,6 +72,7 @@ $completed - marker to set if the request has been completed
 
 ## email delivery
 email is sent via email server given by the admin, while the software functions as a client to it.
+https://hackernoon.com/how-to-implement-smtp-client-on-c
 
 # Interface
 
@@ -206,3 +207,21 @@ Monetary payouts will be handled through the payment gateways provided. For now,
 This means that, in the case of BTCPayServer, the [payout system](https://docs.btcpayserver.org/Payouts/) should be used. In the case of Stripe, the transaction should use the [multiparty payout system](https://stripe.com/docs/connect/add-and-pay-out-guide). Both will require a central, authoritative set of accounts respectively to shuffle money between client and freelancer.
 
 This authoritative account, by default, should give 97% of a commission's value to the freelancer, with the 3% being reserved for itself as a service fee. This ratio should be able to be edited by the system's administrator.
+
++ configuration file can be given as a parameter at startup else it is "cavecomm.conf".
+
+must start with
++configstart+
+and end with
++configend+
+
+comment +
+
+mandatory:
+	emailAddress=
+	emailPassword=
+	emailServerAddress=
+
+optional:{default}
+	emailServerPort={587}
+	emailAddressDisplay={Cavecomm Automated Management System}