Email administration
Summarize
Summary of Email administration
Email administration in ServiceNow involves configuring email properties and accounts to enable successful transmission of inbound and outbound emails. Administrators can use ServiceNow-provided or custom email accounts connecting to external mail services (POP3, SMTP, IMAP). Email properties are globally applied settings that govern how emails are processed across these accounts.
Show less
Key Features
- Email accounts: Setup allows connection to external mail servers, essential for email communication in your instance.
- Email properties: Centralized configuration for inbound and outbound email settings affecting all accounts.
- Email service size restrictions: Standard ServiceNow mail servers enforce a maximum email size of approximately 50 MB before encoding (up to 75 MB after encoding). This limit includes headers, body, and attachments and is independent of attachment size limits. Alternate email configurations with third-party or company-owned servers may have different size limits—confirm limits with your email administrator.
- Email service availability: Email is temporarily disabled during instance cloning to avoid duplicate sends. Upgrades no longer require prolonged email interruptions; email processing continues during upgrades.
- Instance-to-instance communication: Recommended to use web services rather than email for communication between instances.
- Security controls: Use the Instance Security Center to designate trusted and untrusted email domains, monitor incoming email metrics, and apply spam filtering and restrictions to protect your instance.
Next Steps After Enabling Email
To ensure email functions effectively and securely, perform these important tasks:
- Test email configurations by routing all emails to a single user using the
glide.email.test.userproperty. - Review and customize baseline notification categories, email notifications, templates, and inbound email actions to fit your business needs.
- Consider implementing email layouts for consistent content and email filters to restrict inbound emails.
- Define retention policies to archive and delete emails periodically.
- Set up outbound email watermarks to associate emails with records.
- Decide whether to create user accounts automatically upon receiving emails from unknown senders.
- Adjust outbound mail precedence settings, with the default set to bulk (
glide.smtp.precedencebulkproperty). - Implement spam filters and prevent untrusted users from triggering inbound email actions to protect the instance from unwanted emails.
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
- 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.