Automatic answer
The implementation of GT-Net is not yet complete. This documentation describes the planned and partially implemented functionality.
Work in Progress
How It Works
For each message type that requires a response, multiple response rules can be defined. These rules are evaluated in order of their priority. As soon as a condition is met, the corresponding response is sent and the evaluation ends. If no rule applies, the message waits for manual processing by the administrator.
Rule Configuration
Each automatic response rule includes the following properties:
- Request Message Type: The type of incoming message to which this rule applies.
- Response Message Type: The response to be sent when the condition is met (e.g., Accept or Reject).
- Priority: The evaluation order of the rules. Lower values are checked first.
- Condition: A formula that determines whether this rule is applied. An empty condition is always met.
- Message Text: An optional text sent with the response.
- Waiting Time in Days: A cooldown period after a rejection before the sender can request again.
Available Variables for Conditions
Various variables can be used in condition formulas:
- Time of day and day of the week for controlling by business hours.
- Current request load and daily counters for capacity management.
- Information about the requesting server such as domain and time zone.
- Values from the incoming message.
Examples of Automatic Responses
Typical use cases for automatic responses are:
- Automatic acceptance of handshake requests during business hours.
- Automatic rejection when the daily request limit is exceeded.
- Automatic acceptance of data requests from already known instances.
Waiting Time After Rejection
To avoid repeated requests from rejected servers, a waiting time in days can be set. During this time, renewed requests of the same type from the same instance are automatically ignored or delayed. This gives the administrator time for a manual review of persistent requests.