This group of topics describes the operation of the CopiaFacts SMTP Gateway in greater detail for the benefit of advanced users who require greater control over the processing. You do not need to read or understand this section in order to make use of standard Gateway features, and there are no links from the remainder of this manual into topics below this level.
The Gateway runs in a Windows service application. It has up to three components, which essentially run independently of each other:
•An SMTP Server running normally on port 25, which receives incoming e-mail from the internet or from a corporate intranet. It can accept e-mail with or without explicit TLS, which when used is started using STARTTLS. Messages are saved in a designated folder.
•An optional SMTP Server running normally on port 587, which receives incoming e-mail using implicit TLS (encrypted from the start). This would normally by used by a closed user group under the control of the organization running the Gateway. Messages are saved in the same designated folder as the first SMTP server.
•A Message Processor which reads the messages, in .MSG files, saved by the SMTP server(s), and processes them to initiate fax transmissions or for other purposes. The processor component also reads a .MIF message information file saved with each message, containing data from the SMTP session. The MSG files are raw, as received on the wire. The message processor can optionally read and process MSG files saved by other applications into different folders, without accompanying .MIF files.
When two SMTP server components are configured, they must be on different ports, but must share the same domain certificate, which may be a wildcard certificate if required.
The Gateway service is managed by using the GWMANAGER Gateway Manager application. GWMANAGER is used to configure the service sections, to create templates and set template options, and to stop and start the service.
