WorkflowGen Documentation
10.0
10.0
  • WorkflowGen Technical Guide
  • System Requirements
  • Product Technical Components
  • Setup
    • PowerShell Installation
    • Manual Installation
    • WorkflowGen Windows Services & License Activation
    • Tests & Additional Configurations
  • Security
  • Advanced Configurations
    • File Storage
    • Database Authentication & Scaling
    • Web Farm Architecture
    • Configuring Multiple Instances of WorkflowGen
    • Custom Language Support & Layout
  • Operations
  • SMTP Notifications
  • Synchronizing a Directory in Command Line
  • SQL Reporting Module
  • Azure Integration
  • AD FS Integration
    • Authentication
    • WorkflowGen Plus v2
    • Server-Side Scripts
    • Single-Page Applications
    • Generating a Universal Link
    • Additional Information
  • Auth0 Integration
    • Authentication
    • User Provisioning
    • WorkflowGen Plus v2
    • Server-Side Scripts
    • Single-Page Applications
    • WorkflowGen CLI
    • Generating a Universal Link
    • Additional Information
  • Okta Integration
    • Authentication
    • User Provisioning
    • WorkflowGen Plus v2
    • Server-Side Scripts
    • Single-Page Applications
    • WorkflowGen CLI
    • Generating a Universal Link
    • Additional Information
  • Gardian Integration
  • Appendix: Web & Application Configuration Parameters
Powered by GitBook
On this page
  • Using an IIS SMTP gateway
  • Configuring an IIS SMTP gateway
  • Using a pickup directory
Export as PDF

SMTP Notifications

Using an IIS SMTP gateway

Using a local IIS SMTP gateway is strongly recommended to improve performance. A local SMTP gateway is configured to forward emails to the enterprise SMTP gateway ("smart host") only, so the current enterprise security will be applied.

There are several advantages to using an SMTP relay at the IIS WorkflowGen server:

  • Better performance, since messages are sent directly to the relay.

  • Local SMTP acts as a buffer to avoid loss of emails if the main SMTP server is not available.

  • Connection problems are reduced because the relay manages communication problems.

  • The relay traces email deliveries in its own log files.

  • The relay allows you to limit access to WorkflowGen.

  • The relay supports SMTP authentication and TLS encryption to connect to your Exchange SMTP (or other mail server).

Configuring an IIS SMTP gateway

  1. Make sure the SMTP service is installed on the Windows server used as the SMTP gateway.

  2. In IIS, edit the properties of the Default SMTP virtual server.

  3. On the Access tab, click Relay.

  4. Click the All except the list below radio button.

  5. Click Apply and close this window. (For an increased security level, grant access only to the web server IP.)

  6. On the Delivery tab, click the Advanced button.

  7. In the Smart host field, enter your SMTP gateway address (IP or hostname).

  8. Click Apply.

Using a pickup directory

Once you've properly configured the pickup directory in WorkflowGen, you need to configure your external SMTP service (such as IIS SMTP Server or Exchange) to process the emails that are created by WorkflowGen in the pickup directory.

PreviousOperationsNextSynchronizing a Directory in Command Line

Last updated 5 days ago

Alternatively, WorkflowGen also supports pickup directories. Notifications are created in a pickup directory managed by the SMTP server. The path to the pickup directory is set in the section on the General tab in the Administration Module . (Alternately, you can set the path to the pickup directory as the value of the ApplicationSmtpPickupDirectory parameter in the WorkflowGen web.config file.) The default pickup directory path is C:\inetpub\mailroot\Pickup.

SMTP server
Configuration Panel