Email administration
Summarize
Summary of Email Administration
Email administration in ServiceNow involves configuring email accounts and properties to manage inbound and outbound email effectively. Administrators can utilize ServiceNow's provided email accounts or set up custom accounts to connect with external mail services like POP3, SMTP, or IMAP. It is crucial to understand the implications of email size restrictions on successful email transmission.
Show less
Key Features
- Email Accounts: Set up to connect with external mail services, allowing for flexibility in email management.
- Email Properties: Configure settings that apply to all email accounts, enabling consistent email behaviors.
- Email Size Restrictions: Standard configurations have a limit of approximately 50 MB for sending/receiving emails, while the maximum size after encoding is 75 MB.
- Email Service Availability: Email service is paused on instance clones to prevent duplicate emails, but it remains active during upgrades.
- Instance Communication: Use web services for communication between instances and manage trusted and untrusted email domains.
Next Steps
- Test email configuration by routing emails to a single user.
- Review notification categories and templates to meet business needs.
- Evaluate inbound email actions and consider using email layouts and filters.
- Implement retention policies for email archiving and destruction.
- Determine watermarking for outbound email and manage user creation from unrecognized emails.
- Set the precedence of outgoing mail and consider spam filtering for unwanted messages.
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.