MailServer/390 Modernization Guide

MailServer/390 is an email server designed for mainframe environments, specifically z/OS and z/VSE. It provides SMTP and POP3 services, enabling applications running within CICS to send and receive email. It solves the problem of integrating email functionality into mainframe-based applications.

MailServer/390 is an application that runs on mainframe systems. It provides email services to other applications running within the CICS environment. It is not a general-purpose toolset or framework, but rather a specific application designed for email handling.

Organizations that rely on mainframe systems for their core business processes and need to integrate email functionality into their CICS applications would use MailServer/390. This includes large enterprises in industries such as banking, finance, insurance, and government.

A company should consider MailServer/390 when they have existing CICS applications on z/OS or z/VSE that require email sending and receiving capabilities. It is a good fit when direct integration with mainframe applications is needed.

Alternatives to MailServer/390 include other mainframe-based email servers or using external email services with integration through APIs. Examples include OfficeVision VM, OfficeVision MVS, SMTP-Send, Lotus Domino, and EuropaMail. The key difference is direct CICS integration.

MailServer/390 runs on z/OS and z/VSE operating systems. It operates within an LPAR and requires the CICS subsystem to be present. It is not a standalone product and extends the capabilities of CICS by adding email functionality.

MailServer/390 requires the CICS subsystem to be present. It uses standard SMTP and POP3 protocols for communication. Specific configuration files are used to define email routing and security settings.

The main system components likely include an SMTP server component, a POP3 server component, and a CICS interface module. These components communicate using standard inter-process communication mechanisms within the mainframe environment.

MailServer/390 likely uses VSAM datasets for storing configuration data and email messages. It uses standard ports for SMTP (port 25) and POP3 (port 110).

MailServer/390 provides business value by enabling mainframe applications to participate in email-based workflows. This can improve communication, automate processes, and integrate mainframe systems with other enterprise applications.

Without MailServer/390, organizations would need to find alternative ways to integrate email functionality into their mainframe applications. This could involve complex workarounds or using external email services, which may be less efficient and secure.

MailServer/390 integrates with enterprise ecosystems by allowing mainframe applications to exchange email with other systems. This can facilitate data sharing, workflow automation, and improved communication across the organization.

MailServer/390 likely supports authentication methods such as username/password and potentially integration with mainframe security systems like RACF or ACF2. Access control is likely based on user IDs and groups defined within the mainframe environment.

MailServer/390 likely uses encryption for securing email transmissions, potentially using SSL/TLS for SMTP and POP3 connections. Audit logging capabilities likely exist to track email activity and security events.

MailServer/390 provides security by controlling access to email functionality from within CICS applications. It can restrict which users and applications can send and receive email, and it can encrypt email transmissions to protect sensitive data.

MailServer/390 is typically deployed on-premise within the organization's mainframe environment. Implementation requires technical expertise in mainframe systems, CICS, and email protocols. Ongoing operational requirements include monitoring system performance, managing user accounts, and maintaining security.

Administrative interfaces likely include a command-line interface (CLI) and potentially a web-based console. User management is handled through the mainframe security system (e.g., RACF, ACF2). Configuration parameters are defined in configuration files.

Monitoring and logging capabilities likely include system logs, email activity logs, and security event logs. These logs can be used to track system performance, troubleshoot issues, and detect security threats.