Documentation

30 search results

Additional Fine-Tuning via Environment Variables

https://www.axigen.com/documentation/additional-fine-tuning-via-environment-variables-p689438829

This article details these environment variables and their effects.
Axigen Specific Environment Variables
Axigen’s environment variables have to be specified in the service configuration file (e.g...When this variable is not set, the response body is not written in the logs (affects BIMI requests)

SMTP Filters Variables

https://www.axigen.com/documentation/smtp-filters-variables-p47120658

Apart from the predefined variables, custom variables also exist and they can be used later in the code

HSP Variables

https://www.axigen.com/documentation/hsp-variables-p45254814

A variable can have one of the following types:
Variables of different types are declared differently in HSP...VARIABLE = [a-zA-Z_][a-zA-Z_0-9]{0,255}
Types of Variable Values
Values of the variables that have this type must follow the regular expression:

Mailbox API – Contacts

https://www.axigen.com/documentation/mailbox-api-contacts-p666960100

// Note: when no folderId is provided, the syncToken will be a concatenation of sync tokens
// in all contact folders so it shall have variable...// Note: when no folderId is provided, the syncToken will be a concatenation of sync tokens
// in all contact folders from the address book so it shall have variable

Axigen (ai) Insight: Operation and Integration Guide

https://www.axigen.com/documentation/axigen-ai-insight-operation-and-integration-guide-p2567372803

4.2 Environment Variable
For WebMail and the Mobile App to display the AI Phishing Analysis and Summaries, the Axigen process must be started with a new environment variable

SMTP Policies

https://www.axigen.com/documentation/smtp-policies-p47120652

All variables are considered to be string or numbers and can be of three types: 
read-only variables (input variables);
read-write variables (input / output variables);
action variables – these variables...Furthermore, a variable will be set only after that variable's value is known

Backup and Restore

https://www.axigen.com/documentation/backup-and-restore-p45253835

That is why, depending on all these variables, you can adapt the workload to the server’s processing power to improve its performance or avoid overload by setting the minimum and maximum number of threads

HSP Instructions

https://www.axigen.com/documentation/hsp-instructions-p45254816

It has the following syntax:
FOR_EXPR = "<%" "FOR" VARIABLE "=" PARAM "TO" PARAM "%>" ENDFOR_EXPR = "<%" "ENDFOR" "%>"
<% FOR i = 1 TO 10 %>...It has the following syntax:
FOREACH_EXPR = "<%" "FOREACH" VARIABLE "IN" (VARIABLE|MAP_ACCESS|ARRAY_ACCESS) [ "INDEXED" "BY" VARIABLE ] "%>"
ENDFOR_EXPR = "<%" "ENDFOR" "%>"

HSP Call Methods

https://www.axigen.com/documentation/hsp-call-methods-p45254820

METHOD = VARIABLE "(" ARG_LIST ")"
PARAM = (NUMBER | STRING | VARIABLE...CONCAT = (PARAM "+" CONCAT) | (PARAM "+" PARAM)
VAR = VARIABLE | ARRAY_ACCESS | MAP_ACCESS
Definitions:

General HSP Language Methods

https://www.axigen.com/documentation/general-hsp-language-methods-p45254826

<%MAP m%>
<%inc(a, m)%> <%/* 7 + 0 = 7; m variable doesn't have a value */%>
Name...Explanation
Assigns the value of the variable that has the identifier <eval2> to the variable that has the identifier <eval1>
<% i2 = 4 %>

RFCs & Other Standards

https://www.axigen.com/documentation/rfcs-other-standards-p45253621

– Sieve Email Filtering: Variables Extension – starting with Axigen X4 (10.4)
RFC 6134!--https://datatracker.ietf.org/doc/html/rfc6134

LDAP Routing

https://www.axigen.com/documentation/ldap-routing-p45253736

That is why, depending on all these variables, you can adapt the workload to the server’s processing power to improve its performance or avoid overload by setting the minimum and maximum number of threads

Defining Mailing List Subscription and Posting Rules

https://www.axigen.com/documentation/defining-mailing-list-subscription-and-posting-rules-p1373440710

Use the predefined variables buttons to automatically insert details related to specific list messages...A list of the variable's significance can be found below:
%l – List Name

Axigen

https://www.axigen.com/documentation/axigen-p45253505

as /etc/sysconfig/axigen-axib1, with the following configuration:
# The AXIGEN_BACKEND variable is specific to failover domain
AXIGEN_BACKEND=..."axib1"
# The following AXIGEN_* variables are common on all nodes
AXIGEN_DATA_DIR="/var/clusterfs/${AXIGEN_BACKEND}-data/axigen"

WebMail

https://www.axigen.com/documentation/webmail-p45253823

That is why, depending on all these variables, you can adapt the workload to the server’s processing power to improve its performance or avoid overload by setting the minimum and maximum number of threads

Special HSP Requests

https://www.axigen.com/documentation/special-hsp-requests-p45254822

This session key MUST be used as a value for the "_h" variable in all HTTP queries, for session authentication.
login.hsp

Configuring Mail Processing

https://www.axigen.com/documentation/configuring-mail-processing-p1373442368

You can further define the content of the error notification by inserting a number of variables covering the recipient address, failure reason, sender address, email size, as well as the text to be added

Time Synchronization

https://www.axigen.com/documentation/time-synchronization-p45255024

= unreachable, 'x' = time may be in error, '~' = time too variable.
|| .- xxxx [ yyyy ] +/- zzzz

Other HSP Specifications

https://www.axigen.com/documentation/other-hsp-specifications-p45254838

GET, POST, and COOKIE are global MAP variables and contain values sent via a GET, POST command, or a Cookie HTTP header.
Version published after converting to the new editor

LDAP Synchronization

https://www.axigen.com/documentation/ldap-synchronization-p45253734

While configuring the LDAP connector, certain expanding variables can be used to substitute domain, account and other variable elements...The table below lists all of the usable variables, their meaning and an example of how they expand in practice:
3

Remote POP

https://www.axigen.com/documentation/remote-pop-p45253844

That is why, depending on all these variables, you can adapt the workload to the server’s processing power, in order to improve its performance or avoid overload by setting the minimum and maximum number

Axigen Cluster Deployment with DRBD

https://www.axigen.com/documentation/axigen-cluster-deployment-with-drbd-p45255028

created as /etc/sysconfig/axigen-ha, with the following configuration:
# The AXIGEN_BACKEND variable can be named as follows
AXIGEN_BACKEND="HA"...following AXIGEN_* variables are common on all nodes
AXIGEN_DATA_DIR="/var/clusterfs/data/axigen"

SMTP Sending

https://www.axigen.com/documentation/smtp-sending-p45253838

That is why, depending on all these variables, you can adapt the workload to the server’s processing power to improve its performance or avoid overload by setting the minimum and maximum number of threads

SMTP Receiving

https://www.axigen.com/documentation/smtp-receiving-p45253817

That is why, depending on all these variables, you can adapt the workload to the server’s processing power to improve its performance or avoid overload by setting the minimum and maximum number of threads

Axigen with Linux-HA and DRBD – Axigen

https://www.axigen.com/documentation/axigen-with-linux-ha-and-drbd-axigen-p45255211

created as /etc/sysconfig/axigen-ha, with the following configuration:
# The AXIGEN_BACKEND variable can be named as follows
AXIGEN_BACKEND="HA"...following AXIGEN_* variables are common on all nodes
AXIGEN_DATA_DIR="/var/clusterfs/data/axigen"