Skip to main content Skip to complementary content

Configuring the email provider

Qlik NPrinting can distribute your reports by attaching them to email messages.

NPrinting supports SMTP or Microsoft 365 email providers.

Best practices

When you set up an email provider for distributing Qlik NPrinting reports via email, consider the following best practices for configuration and troubleshooting:

  • Check the attachment size limit of the email provider and modify or disable it if possible. Qlik NPrinting reports can be considerably large in size and can sometimes exceed the attachments size limit set by email provider.
  • Information noteSome SMTP providers impose size limits on email attachments. The maximum allowed size varies among providers. If the size of an attached file exceeds the limit, the email is not delivered. A warning is added in the logs.

  • Some email providers limit the number of emails that a user can send during a given period of time. If a user sends more emails than the set limit, emails exceeding the limit are not delivered. Modify or disable such setting where possible.
  • Check the email provider anti-spam setting and verify that emails can be successfully sent to all Qlik NPrinting users. If the email provider only lets you send emails to an allowlist of users, make sure that all required Qlik NPrinting users are registered in the allowlist.
  • Add the IP of your Qlik NPrinting server and the Qlik NPrinting default sender address to the email provider allowlist, if necessary.
  • If the email provider only allows the delivery of emails within an organization, grant Qlik NPrinting users the right to send emails outside the organization, if necessary.
  • If you want to configure custom sender addresses, your email provider settings must allow users to send emails using email addresses other than their assigned email address.
  • When using a email provider cluster, make sure that the authentication is correctly distributed from the SMTP proxy to all the servers that are part of the cluster.
  • When encountering issues with email delivery, check the Qlik NPrinting scheduler service log files and the email provider log files with the help of your email provider administrator.

SMTP email settings

First, you need to set SMTP parameters, including outgoing mail server address, and port number. You may need to set user name and password parameters if the server requires authentication.

Do the following:

  1. From the top menu, click on Admin, and then select Settings.
  2. Click Email.
  3. Enter a name and description for the email settings.

  4. Click SMTP.

  5. Enter the address of the outgoing SMTP mail server in the Address text box.
  6. Enter the port number.
  7. Select the check box for:
    • Use TLS (transport layer security) if your SMTP server requires you to use Transport Layer Security. The default ports are 25 and 587.
    • Use SSL (Secure Sockets Layer) if your SMTP server requires the whole session to be encrypted using SSL. The default port is 465.

    • Disable certificate validation: If you do not want to validate certificates.
  8. Specify the Username and Password required for authentication.
  9. Configure the Default sender email address to use when sending email messages.

  10. Enter a Test email address and click Send test email to verify that the SMTP configuration works. An email with a time stamp is sent to the specified address to confirm.
  11. Click Update.

Microsoft 365 email settings

When setting up Microsoft 365 as email provider for Qlik NPrinting, you need to provide tenant ID, client ID, and client secret. These details are part of the OAuth 2.0 authentication process, ensuring secure communication between your application and Microsoft 365.

Information note

If you are using the Microsoft 365 SMTP service connection, please review the specific limits for a single mailbox in Microsoft Graph service-specific throttling limits under "Outlook service limits".

Do the following:

  1. From the top menu, click on Admin, and then select Settings.
  2. Click Email.
  3. Enter a name and description for the email settings.

  4. Select Microsoft 365.

  5. For Tenant ID, enter the unique identifier assigned to your Microsoft 365 tenant.

  6. Enter the Client ID and Client secret for your Active Directory app registration. These are used for authentication with the email service.

  7. Enter the sender email address.

    This should be a UserPrincipalName (UPN) for a Microsoft Entra ID user account. The email address that recipients will see in the From field of the email will be the user's full email address.

    Information note

    You can restrict the sender to specific mailboxes. For more information, see Limiting application permissions to specific Exchange Online mailboxes.

  8. Click Save to activate the email provider.

    Information noteIf you have a previously active provider, it will be deactivated.
  9. Enter the email address where you want to receive a test message and click Send test email.

    If the configuration is correct, you should receive an email with a time stamp to confirm.

Obtaining the tenant ID, client ID, and client secret

To find the tenant ID, log in to the Microsoft Entra admin center and go to Identity > Overview. The Tenant ID is shown on the Properties tab.

To obtain the client ID and client secret, you need to create a new app registration in Microsoft Entra ID. Once the app is created, do the following:

  1. Go to the app overview page and copy the Application (client) ID.

  2. Go to Certificates & secrets > Client secrets and select New client secret. Copy the secret and store it safely.

You also need to add Microsoft Graph permission for sending emails.

  1. Go to API permissions and click Add a permission.

  2. Under Microsoft APIs, click Microsoft Graph and select Application permissions.

  3. Add the permission Mail.Send.

For more information, see the following Microsoft Learn articles:

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!