Tag: Spam filtering

I don’t receive email from a specific domain

Symantec Community Leave a comment
I do not need a solution (just sharing information)

Good afternoon, I followed all the steps in the link https://support.symantec.com/us/en/article.TECH855….
In the audit lod does not display e-mail and some e-mails appear without content. I increased the timeout from 60 seconds to 5 minutes in inbound, outbound and delivery, I also disabled reverse dns, restarted messaging, without success. I checked at the firewall and there are no blocks. In smg there are no restrictions on bad senders domain, help me please.
Note: I contacted the recipient and they informed me that the messages are being delivered to the company where I work, but the m-emails do not arrive here.

0

Related:

  • No Related Posts

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

Symantec Community Leave a comment
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:

  • No Related Posts

Set Up Your Company's Branding in RightSignature

Citrix Leave a comment

To access your branding options, log into RightSignature and click Account, followed by Branding. You can then access the branding options highlighted below.

Background and Footer Color

This option allows you to change the color of the background and the footer shown on the signing page and in the email signers receive. Use the drop down color menu to make your selection, then click Choose.

User-added image

Company Logo

This option places your company logo on the RightSignature signing screen where the designated signing parties will fill out and sign your documents. Your logo will also be included in emails sent containing the signing links. First click Show your logo, then click Upload.

Footer Options

This allows you to customize what information shows on the footer of the signing screen. You can choose between Sender Name, Company Name, or both. You can also choose to show your Avatar photo here. Once finished with any changes to the custom branding options, click Update.

Email Header

Show sender name in from: This option will show the user name in the email “from” field. If this option is disabled, the email “from” field will show RightSignature.com.

Show company name in subject: This option gives you the ability to designate a custom prefix in the subject line of the notification and reminder emails sent to your signers. When sending a document or a reminder to your signers, your company’s name will appear in the subject of the email.

Use document filename in subject: This option will insert the document filename into the subject of the email, rather than the document name.

Custom Signer Email Greeting

This option lets each user set a custom greeting in the body of the email used to deliver the document signing links. Each user on the account will be able to set a unique custom greeting. To enable the Custom Signer Email Greeting, follow the steps above to access the Branding page; then turn on the Custom Email Greeting switch and click Update.

User-added image

Custom Email Signature

This option lets each user set a custom email signature in the body of the email used to deliver the document signing links. Each user on the account will be able to set a unique email signature. To enable the Custom Signer Email Signature, follow the steps above to access the Branding page; then turn on the Custom Email Signature switch and click Update.

Related:

  • No Related Posts

“The IP Address 185.153.222.46 was found to have a negative reputation.”

Symantec Community Leave a comment
I need a solution

We have been receiving “The IP Address 185.153.222.46 was found to have a negative reputation.” error for months and our mails cannot be delivered. We are a legit company and we are sure that we are not sending and spam or soliciting emails. When we request our ip to be cleared, it is cleared for a while but then, gets to the “bad reputation” list again in a short time. I searched the forum but could not find a solution to this matter. Could you please help us to resolve the issue and clear our ip permanently?

Thanks in advance!

0

Related:

  • No Related Posts

Remote Server returned ‘< #5.0.0 smtp; 550-Please turn on SMTP Authentication in your mail client.

Symantec Community Leave a comment
I need a solution

We are not receiving email from a company that uses Message Labs and we use Proofpoint. We do not see the email hitting Proofpoint at all. Proofpoint does NOT require SMTP authentication.

Is this a Messagelab configruation issue?

Thank you!

Here is the header info, stripped of personal data:

Delivery has failed to these recipients or groups:
MyClient@myclient.com

A problem occurred while delivering this message to this email address. Try sending this message again. If the problem continues, please contact your helpdesk.

Diagnostic information for administrators:
Generating server: server-2.bemta.az-a.us-west-2.aws.symcld.net
MyClient@myclient.com
Remote Server returned ‘< #5.0.0 smtp; 550-Please turn on SMTP Authentication in your mail client. >’

Original message headers:
Return-Path: <TheSender@sender.com>
Received: from [xx.yy.zz.aa] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits))
    by server-2.bemta.az-a.us-west-2.aws.symcld.net id 1C/63-27934-3AB50BD5; Wed, 23 Oct 2019 13:54:43 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrOKsWRWlGSWpSXmKPExsUy45Bij+6i6A2
  xBkcvaVj83TiBzaJ1/zc2ByaPvkVv2QIYo1gz85LyKxJYMy7u3M5U8HUBY8W9L/+YGhhvz2Hs
  YuTiEBLYwSix7+gSti5GTiBnP6PEuY8yIDabgIPEpe37WEFsEQF3iXctTUxdjBwcwgKSEqvf+
  YKYIgJSEivv8UFUGEn86HzBBhJkki68FiTMK+Am0bPuAwuIzSggJvH91BomEJtZQFzi1p
  P5YLaEgIjEw4un2SBsUYmXj/+xQtgGEluX7mOBsBUldv75zwLRmyLx4NZ6Roj5ghInZz5hmcA
  oOAvJ2FlIymYhKYOIZ0lcnNPPDGHrSCzY/YkNwtaWWLbwNTOMfebAYyZUcQ4gO1mib3oyRFhe
  YtLP7UCtXED2MkaJjdMOQfUqSkzpfsi+gJFnFaNFUlFmekZJbmJmjq6hgYGuoaGRrqGRha6hq
  bleYpVuol5psW55anGJrpFeYnmxXnFlbnJOil5easkmRmDcphQ0zN3B+PbIa71DjJIcTEqivK
  mn1scK8SXlp1RmJBZnxBeV5qQWH2KU4eBQkuA1itwQKyRYlJqeWpGWmQNMITBpCQ4eJRHeGyB
  p3uKCxNzizHSI1ClGV44JL+cuYuY4eHQekPy4agmQ/A4m2zcCSSGWvPy8VClx3hMgzQIgzRml
  eXCjYenvEqOslDAvIwMDgxBPQWpRbmYJqvwrRnEORiVh3qgooCk8mXklcBe8AjqOCeg4Of71I
  MeVJCKkpBqYFGYYzhMUs5+t7xzGFLpItED86wSdllkNdjEG68PD4nNfpCtV/YlSVltx9v8bg/
  uZwp3aBrP6nuSd+nb2r85Fn2BJ/91P9z7+MfHBmbDSxBSDx5J8nfUsKzbZn/31R1psfv1XNc9
  aVg07ffUNr1MNp3lazf8UGMzv9vAn44+/Snu2vOe7zrp7z3Sjov9CleYTFKVYv5i2P59gPylE
  /pUdc01+pmqTR4q+XOaH8oT0GVK5dasnNijtZrkru/8c4+JdcWs+LPX4nGbobda4gX+e4Zw40
  2OnHhWoBV+9eJmLtY3Z7pDs7QOWK8T+pVjEFYr8C+/c8iXkame0PfvxdE3NOy/fT1i7Y8ccUZ
  bXM7qVWIozEg21mIuKEwHMKYbv+gMAAA==
X-Env-Sender: TheSender@sender.com
X-Msg-Ref: server-11.tower-331.messagelabs.com!1571838881!115107!1
X-Originating-IP: [111.222.333.444]
X-SYMC-ESS-Client-Auth: outbound-route-from=pass
X-StarScan-Received:
X-StarScan-Version: 9.43.12; banners=-,-,-
Received: (qmail 7940 invoked from network); 23 Oct 2019 13:54:42 -0000
Received: from ptr1.sender.com (HELO mail.sender.com) (111.222.333.444)
  by server-11.tower-331.messagelabs.com with ECDHE-RSA-AES256-SHA384 encrypted SMTP; 23 Oct 2019 13:54:42 -0000
Received: from SENDER-EXCH-03.SENDER.COM (111.222.333.113) by
 SENDER-EXCH-02.SENDER.com (111.222.333.112) with Microsoft SMTP Server (TLS) id
 15.0.1497.2; Wed, 23 Oct 2019 08:54:17 -0500
Received: from SENDER-EXCH-03.SENDER.COM ([fe80::49aa:4b74:6495:96d4]) by
 SENDER-EXCH-03.SENDER.com ([fe80::49aa:4b74:6495:96d4%13]) with mapi id
 15.00.1497.000; Wed, 23 Oct 2019 08:54:17 -0500
From: “Sender, Sender” <TheSender@sender.com>
To: Person 1<MyClient@myclient.com>, Person 2 <SNoel@myclient.com>
Subject: FW: Sales
Thread-Topic: Sales
Thread-Index: AdWJqEYIueyQsz8ypTwSTmmWe97H46wAAQ94g
Date: Wed, 23 Oct 2019 13:54:16 +0000
Message-ID: <363823bb7f0b4b0a8d0205f8cfa2287f@SENDER-EXCH-03.SENDER.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.1.10.100]
Content-Type: text/plain
MIME-Version: 1.0

0

Related:

  • No Related Posts

Why denied category “denied” is not marking in the access log

Symantec Community Leave a comment
I need a solution

Hi Team,

I have blocked categories “File Storage/Sharing” and “Email”. When proxy is hitting “Email” category it is showing “DENIED” message in logs. But when Proxy hitting “File Storage/Sharing” category. It is denirying the access but not shwoing DENIED message in logs.

Why it is like that?  It has show in Access logs the same status?

Thanks,

Mayur

0

Related:

  • No Related Posts

Custom Plugin & Attribute having issues with LDAP Lookup.

Symantec Community Leave a comment
I need a solution

Hi All,

I’ve successfully integrated our proxy via ICAP which is feeding our Web Prevent Server.

I noticed the username was showing up as “local://sAMaccountname@domain.com”.  I added a new plugin successfully which outputs Username=sAMaccountname after parsing the ‘sender-email’ argument.  I then created a custom Attribute in our Employee field called “Username”.  We did not have this value prior.  My custom script successfully populates the new “Username” field.

My plugin Chain is as follows:

  1. Custom ICAP Username Parse
  2. LDAP

The exsting LDAP Plugin is as follows:

attr.Employee = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):displayName
attr.Employee Email = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):mail
attr.Employee FirstName = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):givenName
attr.Employee LastName = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):sn
attr.Employee Title = :(|(mail=$sender-email$)(sAMAccountName=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):title
attr.Employee Dept = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):department
attr.Employee Division = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):division
attr.Cost Center = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):ou
attr.TempManager = :(|(mail=$sender-email$)(mail=$data-owner-email$)(sAMAccountName=$endpoint-user-name$)):manager
attr.Supervisor First Name = :(distinguishedname=$TempManager$):givenName
attr.Supervisor Last Name = :(distinguishedname=$TempManager$):sn
attr.Supervisor Email = :(distinguishedname=$TempManager$):mail

When I generate a new ICAP event, DLP successfully executes my custom plugin and fills in the attribute “Username” with what is parsed as the AD sAMaccoutname.  All other fields are blank and from my understanding its due to my LDAP plugin missing the new field to lookup with.

1) I’ve tried to modify my LDAP lookup by adding (sAMAccountName=$Username$) but the lookup never works for Network Events and does not autopopulate or populate with a manual lookup.  I may be doing this incorrectly but I tried multiple ways.  I’m not sure if my order is maybe incorrect?  I need some guidance here.

2) After this change, Endpoint Incidents do not populate any custom attribute fields and when i click on “Lookup” an error message occurs with “Custom Attribute Lookup failed”.  I think this is due to my new custom attribute called “Username”

I think I’m missing something easy here but I’m not too sure at this point I’m getting confused.  Maybe how I modified my LDAP plugin? 

Any guidance at this point would be apperciated.

0

Related:

  • No Related Posts