Email administration

  • Release version: Yokohama
  • Updated January 30, 2025
  • 3 minutes to read
  • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Email administration

    Email administration in ServiceNow Yokohama release involves configuring email properties and accounts to manage inbound and outbound emails effectively. It ensures your instance connects reliably to external mail servers (POP3, SMTP, IMAP) and controls email size limits and service availability to optimize email transmission and prevent issues.

    Show full answer Show less

    Key Features

    • Email accounts: Set up by administrators to connect the instance to external mail services. You can use standard ServiceNow accounts or create custom accounts for your own email servers.
    • Email properties: Configure settings that apply across all email accounts for managing inbound and outbound email behavior.
    • Email service size restrictions: Standard ServiceNow mail servers limit emails to approximately 50 MB before encoding (75 MB after encoding). Alternate email configurations may have different size limits, so verify with your email service administrator.
    • Email service availability: Email processing continues during instance upgrades but is intentionally disabled on instance clones to avoid duplicate email delivery.
    • Instance-to-instance communication: Use web services instead of email for communication between ServiceNow instances.
    • Domain security: Use the Instance Security Center to designate trusted and untrusted email domains and monitor incoming email metrics.

    Next Steps After Enabling Email

    • Test the email configuration by routing all emails to a single test user to verify setup.
    • Review baseline notification categories, email notifications, templates, and inbound email actions to ensure they meet your business requirements.
    • Decide on using email layouts for consistent content and email filters to restrict incoming emails.
    • Consider implementing retention policies to archive or delete emails at set intervals.
    • Configure outbound email watermarks for associating emails with records.
    • Set up automatic user creation for emails from unrecognized users if needed.
    • Adjust the precedence of outgoing mail, with bulk as the default setting.
    • Prevent untrusted users from triggering inbound email actions to protect your instance.
    • Implement spam filtering to block unwanted messages sent to your custom email addresses.

    All email notifications use the email properties that you define for your instance and the email accounts that you set up. Your email service can also affect the successful transmission of incoming and outgoing email.

    Email accounts

    Email administrators set up email accounts to allow the system to connect to external mail services such as POP3, SMTP, or IMAP servers. You can use the ServiceNow - provided email accounts or create your own accounts for your own email services.

    Email properties

    Use Email Properties to configure settings for inbound and outbound email. Email properties apply to all email accounts.

    Email service size restrictions

    Your email service, whether you are using a standard ServiceNow email configuration or an alternate email configuration, determines the successful transmission of incoming or outgoing emails based on a maximum email size. An email configuration consists of your instance, email server, and email client.
    • Standard email configurations – For instances that use the standard email configuration, the ServiceNow mail servers cannot send or receive emails larger than approximately 50 MB (before encoding), including the email header, body text, and attachments. Email messages are encoded by an email client, which increases total email message size. The maximum ServiceNow mail server size restriction is 75 MB (after encoding). The maximum email size limit is enforced regardless of any configured attachment size limits.
    • Alternate email configurations – If your email service uses a company-owned or third-party server, the approximate size restriction of 50 MB (including the email header, body text, and attachments) may still apply. However, your service might support different maximum total file sizes for inbound and outbound emails. Check with the email administrator of your email service to verify email size limits.

    For details on how encoding can affect email message size and email transmission, see KB0521772.

    Email service availability

    Email service is intentionally shut down on instance clones to prevent resending already delivered email. Upgrades no longer require an extended interruption of email service. Instances continue to process email during an upgrade. For a possible explanation for undelivered emails, see this blog post by a ServiceNow Technical Support Engineer in the ServiceNow Community.

    For instructions on creating and sending custom emails when events on the instance occur, see the tasks in Email and SMS notifications.

    Instance-to-instance communication via email

    Use Web services to communicate between two instances.

    Designate untrusted and trusted email domains

    Using Instance Security Center, you can monitor the blocked and allowed incoming email metrics for your instance. For more information, see Designate untrusted and trusted email domains.

    Next steps after enabling email

    After enabling email on your instance, consider performing several of these important tasks.

    • Test the email configuration by routing all email to a single user (set the glide.email.test.user property).
    • Review the baseline notification categories, email notifications, and templates to determine if they meet your business needs.
    • Review the baseline inbound email actions to determine if they meet your business needs.
    • Determine if you want to use email layouts to add consistent content elements.
    • Determine if you want to use email filters to restrict the email the instance receives.
    • Determine if you want to implement a retention policy to archive and destroy email at certain intervals.
    • Determine what kind of watermarks outbound email uses to associate records with email messages.
    • Determine if you want to create users when the instance receives an email from an unrecognized user.
    • Set the precedence of outgoing mail. By default, the instance sends email with a precedence of bulk (set the glide.smtp.precedence_bulk property).
    • Consider preventing untrusted users from triggering inbound actions to prevent unwanted email from affecting your instance.
    • Implement a spam filter to restrict unwanted messages sent to your custom email addresses.