Citrix Director: Configuring,Managing Alerts and Notifications

If you are a XenDesktop admin and trying to understand the usage of your XenDesktop deployment, you need to be alerted when the number of concurrent sessions crosses a threshold value. Before you even get to configuring alerts and notifications, you need to configure your notification subscription. With this, you can add an SMTP exchange server which can be later used to send emails from when there is an alert.

  1. You need to navigate to the Email Server Configuration page. On the dashboard click on the Alerts tab at the top and then in the Alerts page click on the Email Server Configuration sub-tab to get there.

    Director Configure

  2. The Email Server Configuration Page – in this page, you need to enter all of the mandatory values like-

  • Protocol: Choose which protocol your email server supports. Director supports multiple protocols to connect with your SMTP server. They include SMTP, SMTP-SSL and SMTP-TSL
  • Host: The host name or the IP address of the SMTP server
  • Port: The port with which you want to connect to with your SMTP server
  • Sender Email: The email address from which you want to send email from incase of an alert. It’s best advised to create a separate email address on the email server and name it as CitrixDirectorAdmin@xyz.com and use it to send your alert emails.
  • Does SMTP server require authentication: In case your SMTP server does not require authentication, you can set the value to NO and you would not need a username and password.
  • Username and Password: Credentials required to authenticate the SMTP server connection
  1. Before saving the settings it is advised to test it by sending out a test email. Click on the “Send Test Email” button and verify if you get a test email to the email address you provided in the Send Test Email wizard.

    send test message

  2. Send Test Email Wizard -In case you do not get an email, recheck the configuration parameters and use the “edit” button to modify any incorrect values.

Note: You cannot configure more than one SMTP server. If you want to remove an existing notification subscription, click on the Remove Settings button.

Configuring a policy

Navigate to the Create Policy Page. On the dashboard, click on the Alerts tab and then on the Create Policy sub tab. If you do not see this tab then you do not have sufficient privileges to create a new policy.

For example, you want to create a policy that has a condition that, if the number of “Peak Connected Sessions” goes above 10, a warning alert is generated and when the number of “Peak Connected Sessions” is above 15 a critical alert is generated. The instructions below state how to configure such a policy.

peak connected sessions

The main components of a policy are:

Name: The name of the policy that you want to create

Description: A brief description about the policy and its conditions. Limit your description to less than 50 words

Scope: The entity on which the policy will be applied on. For e.g.:- If my policy has a condition; “Alert me when the peak connected sessions hits 90 on all the machines in my delivery group xyz”, then here, the delivery group xyz is the scope.

In general, alert policies can be targeted at three different scopes:

  1. Site – Will apply to all the machines in the entire site and the alert threshold will be applied on the aggregate value of all the machines included.
  2. Delivery Group – Will apply to all the machines in the entire delivery group and the alert threshold will be applied on the aggregate value of all the machines included.
  3. Server OS – Will apply to all the machines in the delivery group but the alert threshold value will be applied to individual machines.

Notification Preference: Who should be notified with an email when there is an alert for this policy?

Conditions: A list of conditions that you can choose to create a policy. A policy can have multiple conditions or just one.

Condition Type Condition Checked
Peak Connected Sessions Detected when an instantaneous (one minute samples) number of peak connected sessions for the entire site of a particular delivery group exceeds a configured count threshold.
Peak Disconnect Sessions Detected when an instantaneous (one minute samples) number of peak disconnected sessions for the entire site of a particular delivery group exceeds a configured count threshold.
Peak Concurrent Sessions Detected when an instantaneous (one minute samples) number of peak concurrent (total) sessions for the entire site of a particular delivery group exceeds a configured count threshold.
Connection Failure Count Detected when the number of connections in a configurable time period fail across the entire site of a particular delivery group exceeds a configured count threshold.
Connection Failure Rate Detected when the ratio of connection failures to connection attempts in a configurable time period across the entire site of a particular delivery group exceeds a configured percentage threshold.
Failed Desktop OS Machines Detected when an instantaneous (one minute samples) number of desktop OS machines in a failure state for the entire site of a particular delivery group exceeds a configured count threshold.
Failed Server OS Machines Detected when an instantaneous (one minute samples) number of Server OS machines in a failure state for the entire site of a particular delivery group exceeds a configured count threshold.
Average Logon Duration Detected when the average session logon time in a configurable time period across the entire site or for a particular delivery group exceeds a configured duration threshold.
RDS Load Evaluator Index Detected when the configured threshold of load index value is sustained consistently for 5 minutes. For e.g. If we configure a threshold of 68 % then an alert will be triggered only when the threshold is above or = 68% for 5 minutes without a dip in between.

Go ahead and click on create policy and select a Site policy and give in the name, description, notification preference and the condition of your choice. The scope by default would be the name of the Site and hence it would be pre-selected for your ease.

Assign Delivery Group

Note: Alert polices are site specific! An alert policy cannot be applied across multiple XenDesktop sites

Note: While adding the notification preference you can choose the name of the user whom you want to send the email to and the email address would be automatically added. In case you want to add an email address of an user outside you domain simply type in the complete email address in the search box and click on the add button!

Note: You will not be able to add notification preference unless you have configured an Email SMTP server. When it comes to the conditions remember to follow these mandatory rules without which you will not be able to save your policy.

  1. The warning threshold should always be less than that of the critical threshold
  2. Both the warning and critical thresholds are mandatory
  3. Warning and critical thresholds cannot be zero or in negative.
  4. Certain conditions like “Peak Connected Session” do not accept fractions or decimal values
  5. The Alert re-notification and Alarm re-notification periods would be by default specified. In case you want to change them, go ahead.
  • Alert Re-notification – Duration after which the warning notification will be re-triggered
  • Alarm Re-notification – Duration after which the critical notification will be re-triggered6

Note: You can use the “Reset Value” link is to clear modifications done on an unsaved policy. Once it’s saved, it will reset to the last saved value and not default initial value. Hence, once the policy is saved, you can modify the threshold values but resetting brings it to the last saved value..

6. Once all of the mandatory rules are followed you will get a green tick next to your condition and if not you will get a red cross next to the conditions that are incorrect.

Note: In cases where there are multiple conditions in a policy, none of the conditions will be saved until all the errors are corrected.

Group Policy

Once you hit on save you have created your first policy.

Get Notified

Visualizing your alerts

If there is any issue you will be notified immediately on the Director web console and also receive an email.

The notification tip and slide bar

Once there is an alert, may it be warning or critical, an admin will be notified on the notification tip. The notification tip will be available on all the paged except on the user details page.

Data updated every minute - Director

The notification tip gives you the number of active alerts. In case you have configured SCOM along with proactive alerts and notifications, you get a sum of both the active alerts on the notification bar.

When you click on the notification tip you get the notification slide. The notification slide gives you the option of classifying your alerts based on the source i.e. Director or SCOM and also based on the severity i.e. Critical or Warning.

Alerts - Director

The notification slide bar will give you a list of all the active alerts including details like the time when it occurred and the rule and condition that triggered it.

Emails

If you subscribe to the notification preference of a condition that triggered an alert, then you would receive an email. The email is localized and you will get it in the language you prefer.

Citrix Director

Managing your policy

Once you are done creating policies you now need to know how to manage them. In case you need to modify a policy, navigate to the policy page, search for the name of the policy using the search box provided and click on the EDIT button.

When your XenDesktop site is in a maintenance period and you do not want any alerts, you can use the DISABLE button to disable the policy. This will prevent any new alerts from being created. Once you are done with the maintenance work, you can go ahead and ENABLE these policies.

If there are any old policies that you want to get rid of, choose the policy and click on the DELETE button.

Note: Deleting a policy will not delete the history of alerts that were triggered prior. You can still see them on the Alert Summary page

Directory Policy

When there is an alert, you get notified on the notification tip. You can click on the notification tip to get a slide bar that will have brief details of the alert. You can also group them into warnings and critical alert.

Director Dashboard Alerts

Managing alerts

If you want to know more about an alert, click on it and that would take you to the alert details page. The alert details page gives you a picture of the alert, its history and its present condition. You can edit the policy that created the alert from this page too.

Manage Director Alerts

If you do not want this alert to be shown as active, then you can go ahead and DISMISS it. Dismissing an alert is an irreversible action. Only when the condition becomes healthy and then breaches the warning or critical thresholds will you get an active alert. Till then you will not be notified.

Note: If you dismiss a critical alert, you will not receive warning alerts. But if you dismiss a warning alert, you will be notified when the condition breaches the critical threshold

If you want to view the history or the summary of all the alerts triggered, then you can use the alert summary page. The alert summary page lets you filter alerts based on the time period, the scope and the present condition of the alert. To navigate to the alert summary page, click on the Alert tab on the dashboard and then on the Citrix Alerts sub-tab.

Note: If a delivery group is deleted, you will still find it listed in the scope. This is to make sure history of alerts that were triggered with that particular delivery group as scope are not lost.

Citrix Alerts

In the alert summary page, you can DISMISS an alert, navigate to the details of the alert (alert details page) and also export the data.

You can search for history of alerts by using the filters provided.

Source: You get to choose the scope on which the rule was applied. In case of delivery group or server OS you get to search for the particular scope and apply your condition on it.

Director - All Alerts

Category: The category of policies for which you want to see the alerts

Director - All Alerts Menu

State: You get to choose between four different kinds of severity; Critical, Warning, Dismissed and Healthy. This will help you group your alerts, and action upon the required ones.

All Alerts - Director

Time Period: You can choose a time frame from last 2 hours, last 24 hours, last 7 days and even last month. When you select the end date as now, you will be shown the active alerts exactly till the moment you hit on apply.

Choose End Date

You can choose a custom end date and time too.

All Alerts Director

Now let us take a look at the grid shown in the alert summary page.

User-added image

Time: Time and date when the alert was first triggered

Action: Any action that has to be performed. e.g.: Dismiss

Status: The current status of the alert. Is it healthy, critical, and warning or is it dismissed. If the policy that triggered the alert is deleted, then the history of the alerts will still be available but will be shown in the dismissed state.

Alert Policy Name: The name of the alert policy that was given when the policy was created

Scope: Where was the policy applied on? Was it on a delivery group level, was it on the site level or was it on a server OS level?

Source: The drilled down source that actually triggered the alert.

Category: What king of policy was it? It reflects the template that you took while creating the alert rule.

Description: Gives you a brief of what was the exact condition that triggered the alert.

Note: Proactive Notification and Alerting are Platinum features. More information about features and editions can be found in the links below. Please see Additional Resources.

Related:

Need help :Message not transmitted DLP Email Prevent SMTP_MESSAGE.5300

I need a solution

Hi,

We use DLP in our company, we have problem with email prevent showing on the log that a message is not transmitted.  we have an Error on the log :

SMTP_MESSAGE.5300 Error while processing

I have found a link below talking about this, but i didn’t understand where to put configuration? MTA or in our DLP prevent mail server. And which configuration do i have to add ?

https://support.symantec.com/us/en/article.tech219387.html

https://support.symantec.com/us/en/article.tech219387.html

Best regards

0

Related:

SMSMSE too many Administrator email notifications

I need a solution

Hello

we’ve got a DAG with 6 Exchange servers.

when a rule/threshold or whatever is reached the notifcation is sent multiple times with the same message to the administrator email (this is a distribution list containing 3 users).

It can occurs from the same server or from different server.

This notification was sent thrice to the same email address by the same server:

email subject : “Administrator Alert:  Symantec Mail Security detected an error (SYM:xxx442769)”

“Location of the message:  SMTP

        Sender of the message: user1@domain.com

        Subject of the message:  mail subject

        The attachment(s) “20200-01.pdf” and/or the message was Logged Only.

        This was done due to the following Symantec Mail Security settings:

        Scan: Auto-Protect

        Rule: Encrypted File Rule

 Server Name: Server01″

Any idea ?

Ty

David

0

Related:

Remote Server returned/ Client was not authenticated to send anonymous mail during MAIL FROM [BN6PR12CA0048.namprd12.prod.outlook.com]>

I need a solution

Hello,

We cancled our Symantec account a couple of years ago and sicne then quite a few institutuions/business have been unable to email us as emails addressed to our domain are retunred undeliverable.  Recently we were advised that the issues appears to be that as a former Symantec customer that we did not terminate the service properly after we moved to Office 365. We were advised to contact Symantec to have the service compeletly terminated.  Below is a sample of the error message inclusive of the Diagnostic Info,  recieved by someone attemntting to email us.  A Symantec message does appear in the diagnotic in the diagnostic information: 

(using TLS with cipher AES128-SHA (128/128 bits))

        (Client did not present a certificate)

        by znpcpapbrg01i.bnymellon.com (Symantec Messaging Gateway) with SMTP id 18.7C.04270.F113C6C5; 

Below is the full error message.  Please advise if this can be reolved.  Many many thanks. 

Delivery has failed to these recipients or groups:

erogers@bradmer.com
Your message wasn’t delivered because the recipient’s email provider rejected it.

Diagnostic information for administrators:

Generating server: server-2.bemta.az-d.us-east-1.aws.symcld.net

erogers@bradmer.com
Remote Server returned ‘554 5.7.0 < #5.7.57 smtp; 530 5.7.57 SMTP; Client was not authenticated to send anonymous mail during MAIL FROM [BN6PR12CA0048.namprd12.prod.outlook.com]>’

Original message headers:

Return-Path: <george.gasson@bnymellon.com>

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bnymellon.com;

        s=BNY071018; t=1550594340; i=@bnymellon.com;

        bh=6CKn9+xMacgVsGmREMvRZd4vqsvhSI3dyrd8owANg1Y=;

        h=From:Subject:Date:Message-ID:Content-Type:MIME-Version:To;

        b=hDVm3hyZkP8nMSAIMHRKbKCHkfVy5CuolxDZMQgfL5c0ZG/8kPeRB5s6iGJy17ny0

        rSvDe2KQlABFBoFpw5do1kJCAOY2zSl7T6CL8bme4Z1HPDQwc1jyGojWI7R+8JO839

        lv8ZXnqSoW4gSfDH+WbyI6Jn1mX7Pq/LGTtJHXXn+Y0VcsI2e3WUUv9P7YcSCwWH53

        l1c87rxg1ZdCbNlL8DYi8j3IsU0jsrJNinG3z6NcF3jklLox0ngbGQtMjXY9TrVBjG

        sm5etZNEnqxZQeR380yZJWKQqc0/WvjttDEZsYB7rjr7cqwBv7wLiRyUvqSXKR1c4E

        ROsTtP5On/0Vw==

Received: from [67.219.247.54] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits))

        by server-2.bemta.az-d.us-east-1.aws.symcld.net id 4B/16-27512-4213C6C5; Tue, 19 Feb 2019 16:39:00 +0000

Authentication-Results: mx.messagelabs.com; spf=pass

  (server-29.tower-426.messagelabs.com: domain of bnymellon.com designates

  67.219.247.54 as permitted sender) smtp.mailfrom=bnymellon.com;

  dkim=none (message not signed); dmarc=none header.from=bnymellon.com

X-Brightmail-Tracker: H4sIAAAAAAAAA2VUe0xTdxT2d1+9IMXy0h+ELbPE7GU7cC47y8b

  ijHE3kC0LZiQ6oxZbabNSSFsmbMmCk7HBeIgQgQKF8X5GkOIEBIoPnmMghsFU3gWCCE7jY06B

  3XLBueyfk++c7zvfOecmv8uSrrUOXqwqyqjS6xRaKeNIVfhXn5D5+GkP+l4/7QCmxgEE46MXK

  VhOfUDCaE09Be02CwnTKfk0xD48Q8CfkxYG+lqsNKwMt9KQUmSjIXXwKg3t8cUkXH4wKII/ho

  Pgae9dBIkX8yiIyXwFruR5QsvVDhoqG7IRTJzspCF7cYyB/sk+CmYzx0hYav2OhNrZERLi0vx

  hfqaFghpLLQ0J/c8ouJdoFcGVLBMN15uLKWg+X4JguqMaQX9+G4LR8WYR9NSdoWDwUR4DdS0m

  ChbKlkQwP15FwoW/ykXw26W/CRjJshBwcrGQgIfTJgbi41cQzFTEELCUdwxKZ54gsHYskfDwa

  rUIOptvMDBcZmWge+FHAgZLivgri8YJSK1JJeBmRxfBf6YC/p65eBIscYnMLiWXXmAjuZqnY4

  gbayoXce0lrSTXOeTCdY7EkFzS3DLBxa40iriaqbM0l/WDmeTSpnIQZy18SnIZyc00d/1+C8U

  lxjfS3EzsPPHZtgO0RhcSHnWEVncV6yLMxSgqp6mejEF9GSgBObBYshM3Fw5TCciRdZW0Efhu

  kpkRkssI9zZlEELyDOEnifMiITnHMyeshL2f4ftrkstWvdwkcjz+u13kwLpL3sbnJ6sJAcvxY

  Osdvs6ylGQbHur/2F4WSz7Ad2qnSTtGks34cXfVqpyUbME3bHmEsJ47nrjWwwjYA89NLdMC9s

  EdxWWUoP8W19fdIwVPF9yVZaOEsd4481Teaq+r5DWcZR5a83kZV5+9R9tvwZLTG7HtRAF9Cm0

  2vTDb9IKv6QVfoX4U30oaYwS8Hec33V/Db+KSn+fJdfyrdYr4f307rhtoWPPZiuPis3mNI48L

  EW6qSiHWRXMLi/S6KP2nCVE+ElegnSF6TajaGKbQaGV+vr4yP78dsvdkfnLF1zKlPNIgUykMR

  nt63CA3RIcd1SrlOpXxHOIfqDLCAV1AltLQS8iTJaQe4szXtQddnUPCldFqhUF9WB+pVRkuIW

  +WlWLxbl+ec9GrQlVRxzRa/pWv05h1krqLx+202BChCDNoQgWqGwWyDY8nckm2azUm187w0TJ

  mj42rcbRtNpd0pXThOpXXFvFHdguJ3UIdqXs+YP1PMoBe8nITow0bNrg6Raj0YRrjf/nbaAuL

  pG7Cnk4anfH5Hrf5FQl+RdPKl/YVjYp/Ka8YlNx7oPf9gMGQPTnKkMmSQJ+iykMb31pxf8f8f

  blNseMrj0/V3p8776UOffLL8eTgrVB+q+dm+iNiVLn/m1mb/yZ9256gRbiWG8080zq+OyIrjS

  rb3V8bLJIu9Kk/rMoMIKdUQQEe+5zLX927b1e/T4X8sH9gZ3Bw36aiI5VfeJrTdu2XUga1wu8

  NUm9Q/ANRxQlcRAUAAA==

X-Env-Sender: george.gasson@bnymellon.com

X-Msg-Ref: server-29.tower-426.messagelabs.com!1550594311!2056042!25

X-Originating-IP: [170.61.173.129]

X-SYMC-ESS-Client-Auth: outbound-route-from=pass

X-StarScan-Received:

X-StarScan-Version: 9.31.5; banners=bnymellon.com,-,bradmer.com

Received: (qmail 8740 invoked from network); 19 Feb 2019 16:38:59 -0000

Received: from znpcpapbrg01o.bnymellon.com (HELO znpcpapbrg01i.bnymellon.com) (170.61.173.129)

  by server-29.tower-426.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 19 Feb 2019 16:38:59 -0000

X-AuditID: 0aa06eb7-ff3ff700000010ae-64-5c6c311ff12f

Received: from WTPCPHTMEM02.ams.bnymellon.net (wtpcphtmem02.ams.bnymellon.net [160.254.249.175])

        (using TLS with cipher AES128-SHA (128/128 bits))

        (Client did not present a certificate)

        by znpcpapbrg01i.bnymellon.com (Symantec Messaging Gateway) with SMTP id 18.7C.04270.F113C6C5; Tue, 19 Feb 2019 11:38:55 -0500 (EST)

Received: from WTPCPEXMEM50.ams.bnymellon.net (10.88.250.171) by

WTPCPHTMEM02.ams.bnymellon.net (160.254.249.175) with Microsoft SMTP Server

(TLS) id 14.3.408.0; Tue, 19 Feb 2019 11:38:55 -0500

Received: from WTPCPEXMEM47.ams.bnymellon.net (10.88.250.168) by

WTPCPEXMEM50.ams.bnymellon.net (10.88.250.171) with Microsoft SMTP Server

(version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id

15.1.1531.3; Tue, 19 Feb 2019 11:38:54 -0500

Received: from WTPCPEXMEM47.ams.bnymellon.net ([10.88.250.168]) by

WTPCPEXMEM47.ams.bnymellon.net ([10.88.250.168]) with mapi id 15.01.1531.003;

Tue, 19 Feb 2019 11:38:54 -0500

From: “Gasson, George” <george.gasson@bnymellon.com>

Subject: Markets in review week ending 2/15/19

Thread-Topic: Markets in review week ending 2/15/19

Thread-Index: AdTIcZkQ+XuS/IPwQHKb7fmVvhjN7A==

Date: Tue, 19 Feb 2019 16:38:54 +0000

Message-ID: <ee9356a4afd54921b7587364d60ee53b@bnymellon.com>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

x-originating-ip: [167.222.211.240]

Content-Type: text/plain

MIME-Version: 1.0

To: Undisclosed recipients:;

X-CFilter-Loop: Reflected NPC6

X-Brightmail-Tracker: H4sIAAAAAAAAA2WTa0ybZRTHfd5radb5DmF7xGVBdIm6UYduyUncjPGDe78YxUSNCwnr4N0l

        K6UpEwdG0wki7dgY2QK0ENpxE9iQIoVtsJYOgRaQAcOOOsO9BUkHygQncrPwQkLit98553/+

        55wneSRk8DwbJjmjOidoVAplBCOlpGZVXWR4lDLmQLr+WTA2PkAwMnSXgpWcORKGLPUUtHut

        JPiyzTSkz+cS8OeYlYEeu4OGVU8zDdmlXhpy3G00tOvKSPhpzs3Cr56PYLH7DwRZd00UaPPD

        odX0PNjbnDTcuFOAYDTNRUPBzDADvWM9FEzmD5Ow3PwNCbWTgyRkXD0C/gk7BRZrLQ363iUK

        ZrMcLLQajDT028oosDWUI/A5qxH0mu8hGBqxsdBVl0uB+28TA3V2IwXTFcss+EduknD7n0oW

        7rf8S8CgwUpA2kwJAfM+IwM63SqCiSotAcumk/D9xAICh3OZhPm2ahZctkcMeCocDHROZxLg

        Li8NXFk6QkCOJYeA35wdROCZigP3TOlIsGZkMe/E89eKvSRvWRxG/HBTJcu3lzeTvGtgB+8a

        1JL8pakVgk9fbWR5y3gNzRu+KyL5q+OFiHeULJJ83mUbzfc/sVN8lq6R5ifS/cSHe49JD8cL

        yjPJgub1t49LT7d39iO1qQKdL2yqJ7WoJw/pUZAEcwexrcRD6ZFUEsy1ErjeYybFoA3hbwvm

        kBisIlzz1y/sWkswZ0X4ln3PGjOBdsvlinWr5zg5HnnoX9eEcG/ihrFqQmQ5djc/DuQlEorb

        iwd6j66lZdxh/LjWR64x4nbip5031+Uktws/8poIcbsQPNrXxYgciqfGV2iRX8LOsor1rUlO

        i3C39iItmu7AHQYvJc7djfOvmBhx51ewoWhgw2gPrq6Zpa+gUOOWecatXsYtXqIoHnf5pwiR

        92Nz0xNG5H24/Lqf3OSfHePE//P7cd2DOxs+L+IMXcHGsDKEO39vR5uiqekZelN07eIoa0ay

        KhSWqlLHqRXqE5pTB6LkJ1QpCYJSmaiSxyUm/IjED3jrNhrNe7cFcRIUsU3moZQxwbQiOSkl

        oQW9HDAbs9zoRWGUKlElRITIoqSBsixekZIqaBJjNZ8rhaQW9IKEitglu278LCaYO6U4J5wV

        BLWg2awSkqAwLdJ1h+kbihZii79wGXuOedXPhA/fazv/1cclH3D1Lu7T+KfJZ/HS/diDDbPj

        ubYg+depF97q2x5tlO88Hlp56NK+aMOS+Yejvo6+hcaknpPbIj/pr+HeM+vnH7pS2PfjstyF

            8t2HYrZXDUyGgynywpeZr2a/saQ5MpdW5Bvodnozo2MiqKTTiqjXSE2S4j+oY7LtiA

0

Related:

ShareFile Custom SMTP

ShareFile SMTP IP Address Information

Please see the following KB article for whitelist information.


User Requirements

  • An employee user with the Allow this user to modify account-wide policies permission

Microsoft Office 365 Users

If you are a Microsoft Office 365 user and would like to utilize Custom SMTP, view this set up guide from Microsoft.

Setting up Custom SMTP

  1. Navigate to Admin > Advanced Preferences > Email Settings > Configure SMTP Settings
  2. On the Custom SMTP Configuration page, enter the appropriate information to enable this feature.
  3. Ensure that the Enable checkbox is checked before saving.

User-added image

Required fields

Enable Custom SMTP – This must be selected if you wish to use these settings.

Email Address – This will be the “from” email address of sent emails.

Server – This is the host name of the email server that will be used to send emails.

Port – This is the port number to be used. Port 25 is the default. We allow the following ports: 26, 443, 465, 587, 2525.

Username – This should be the username needed to access the server.

Password – This should be the password needed to access the server.

Notify Email on Failure – This email address will be sent notices if ShareFile is unable to send an email with the given settings.

Optional fields

Use SSL – Choose between Implicit, Explicit, or Off.

Failback to ShareFile –If selected, messages that fail to send using the custom settings will prompt ShareFile to send future emails through standard ShareFile email settings

Authentication Method – Select an authentication method here if a particular one is required by your server


Troubleshooting Your SMTP Setup

“Email Notifications / Messages are Delayed”

This issue may occur when you are utilizing certain filter services or programs processing messages on your local mail servers. Before contacting ShareFile about delays in our system, please verify that your messages are not being delayed by local filter services. One means of verifying that information is to review the full header details of a message and reviewing the time messages send between services or filters.

“Email Notifications / Messages Do Not Arrive”

This issue may occur if you have IP restrictions or policies on your local mail servers. Please click here to make sure you have whitelisted the Custom SMTP IPs. Likewise, please review your mail server authentication methods to ensure that ShareFile can communicate with your servers.

“Too many connections from your host”

This issue may occur when you have exceeded the maximum allowed connections on your SMTP server. To resolve this, you must update or increase your max allowed connections in your SMTP configuration, or use Consolidated Notifications to limit the number of connections you receive on a typical basis.

Related:

Symantec DIP Urgent inquiry

I do not need a solution (just sharing information)

Hello, I will install and implement the Network Prevent for Mail soon in a site that has the Enforce Server and the Network Discover Module are already installed, So I would like to ask you about an issue if I installed the Network Prevent for Mail and integrate it with the MTAs ( forward or reflected ) mode and became inline in the network with the MTAs, when it receives mails from MTA and sends it to another MTA So what will happen or if the network prevent for mail fail over or became down in the network, or if the Enforce server has a problem like that Or any Reason to Become Down what will happen ? Does the mails will drop and doesn’t be sent Or the MTA will ignore the path of DIP and will redirect it to the other MTA directly ? and if that happen that will lead to data leakage and this is a problem too. So I would like to know what is the scenario of this case ? Does the detection server (Network prevent) keep the policies from the Enforce Server and apply it even if the enforce server is down or the Enforce Server is responsible of Applying the policies and configurations. And what is the best practice should I do to ignore this problems and the servers work stable with each other ? Thank you, and I would like to know your advice with this issue ASAP.

0

Related:

Deliver Email

I need a solution

Problems Delivering email

LOG: MAIN
  cwd=/usr/local/cpanel/whostmgr/docroot 4 args: exim -v -M 1iXvli-0006PP-3o
delivering 1iXvli-0006PP-3o
LOG: MAIN
  Sender identification U=interpar D=interpartesdemexico.com S=licitaciones@interpartesdemexico.com
Connecting to cluster9.us.messagelabs.com [67.219.247.54]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-13.tower-426.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.247.54]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.246.102]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-11.tower-386.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.246.102]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.251.54]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-22.tower-366.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.251.54]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.250.198]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-6.tower-346.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.250.198]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.250.102]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-2.tower-326.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.250.102]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.246.198]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-22.tower-406.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.246.198]: Remote host closed connection in response to EHLO s1
Connecting to cluster9a.us.messagelabs.com [3.222.201.247]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-12-131.us-east-1.aws.symcld.net [100.112.12.131]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster9a.us.messagelabs.com [3.222.201.247]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster9a.us.messagelabs.com [34.237.164.170]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-14-77.us-east-1.aws.symcld.net [100.112.14.77]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster9a.us.messagelabs.com [34.237.164.170]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster9a.us.messagelabs.com [52.73.243.182]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-13-247.us-east-1.aws.symcld.net [100.112.13.247]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  == humberto.villalobos@regalsprings.com R=dkim_lookuphost T=dkim_remote_smtp defer (-44) H=cluster9a.us.messagelabs.com [52.73.243.182]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
0

Related: