553 Message filtered – zero support from Symantec

I need a solution

Let me start off with stating that we are currently not a Symantec Cloud Email customer. However a lot of our clients appear to be using this product.

Start around Feb 25, 2019 we would get a bounce back with the following message:

553 Message filtered. Refer to the Troubleshooting page at http://www.symanteccloud.com/troubleshooting for more information. (#5.7.1)

This comes from the destination email server that has Symantec Cloud Email in use, which in our case is at least 5 of our clients.

The only thing that gets the email through is to remove all links and images before sending out the email. Of course this doesn’t work with Calendar invites as those contain links (Google Calendar).

Following this article https://support.symantec.com/en_US/article.TECH246726.html#553-filtered everything checks out perfectly. In fact an external tool like mxtoolbox says we are just fine as well. 

I even submitted a sample to the email address provided but I don’t even get an auto-responder. Also it’s been 2 days and no response.

Calling support just gets met with a “You can’t call us as you don’t have a subscription” so that’s no help.

There is very little diagnostic information in order to solve this issue provided by the response and no way to figure out why it’s being blocked. We don’t know if this is more global or just affecting anything from our domain (really shouldn’t because google calendar invites come from a different address with ours as the reply-to).

We were interesting in your product up to this point, however I cannot recommend this product to anyone as it’s going to block more legitimate emails than spam. 

Am I the only one with these issues? What else is there to do? Waiting weeks to get this cleared is not a valid option, we could just start using USPS at that point for faster response and reliability.

HELP

0

Related:

No Symantec AV Pattern Update since 2018/11/07

I need a solution

Hi!
We have an issue with no updates on our two Proxy ASG-S200-40 (ver. 6.7.3.5). Here’s a piece of cas.log and screenshot with AV Patterns:

Feb 27 10:45:23 cas-asg1 symantec[6299]: 2019-02-27 10:45:23 (UTC),Symantec on cas-asg1(10...)  failed to update,Reason: Failed to process update

AV license is valid, I tried to force update, without success.

Is there anything I can do besides of ASG update version? 

I’ll be greatful for any advice. 

0

Related:

Dell Technologies Set to Drive 5G Transformation

Don’t blink – yes, you read the headline correctly. But just to clarify, we’re not announcing our intention to compete with industry telecom giants like Ericsson, Samsung and Nokia. Connected everything revolution Of course, it is an exciting, brand new foundational architecture for the telecom world, but for Dell Technologies, 5G is far more than just a telecom play. We believe it will deliver massive transformational change across all businesses and societies. As a leader in digital transformation, Dell Technologies will help define the underlying infrastructure technology. In other words, we will provide the rocket fuel … READ MORE

Related:

Google Ads

I need a solution

I would like to check on the work around for page advertised by google analytical or other advertise vendor before reaching the actual landing page.

FYI, currently we block ads from our proxy, but some search result will return page which consist the ads header before reaching the actual page. In this case, the page will be blocked totally

0

Related:

Prevent Policy for NCR – Wincor

I need a solution

Hello dears,

I have been struggling with our Symantec Critical Protection V8.0 building some Prevention Policy for Windows Machine used by NCR and Wincor

After reading some of the 1000 pages etc of the manual I have done some tests but without luck.

Is there any way to build or find some policy for my purpose ?

Already tried with sandbox but I’m having difficulties ?

Anyone is using Symantec CSP or had previous experience for NCR or Wincor ?

Thank You

0

Related:

Samsung SDS Reveals Blockchain Accelerator Tech Following Hyperledger Testing

The IT arm of South Korean tech giant Samsung announced it had developed technology to speed up blockchain transactions, the company confirmed in a press release on Feb 14.

Presenting at the ongoing IBM Think 2019 conference in San Francisco, Samsung SDS said its new technology, Nexledger Accelerator, had already passed testing with Hyperledger Fabric.

“In order to improve transaction processing speed, which is a key consideration in applying blockchain technology, Samsung SDS has developed its own Nexledger Accelerator, which can be applied to Hyperledger Fabric,” the press release explained:

“Samsung SDS tested the Nexledger Accelerator in Hyperledger Fabric last December and found that the transaction processing speed was significantly improved.”

For the Accelerator, a dedicated Github repository aims to offer developers tools for testing and expanding the technology via a scheme dubbed “Innovation Sandbox.”

“The intent is to enable blockchain developers to run it to see how many performance benefits they can expect in reproducible ways,” Samsung SDS said in the press release.

SDS added it would also be joining the IBM Blockchain Platform Board.

Hyperledger is an open-source enterprise blockchain solution developed by the Linux Foundation. The technology has seen participation from and deployment among major players, including IBM, over the past two years.

Samsung first debuted its Nexledger product, itself an enterprise blockchain platform, in April 2017.

Related:

Chris Ferris on how IBM has led the way in open technologies and

Few people have been more involved in the evolution of open source and open standards technologies than Chris Ferris. The IBM Distinguished Engineer and CTO of Open Technology has been an enthusiastic proponent of open governance for two decades, and was instrumental in IBM’s efforts to take a leading role in developing and promoting open technologies. Chris recently sat down with IBM Developer’s Kevin Allen to discuss IBM’s role in the evolution of open technologies, including Hyperledger. What follows are some key portions of that conversation. (Watch the entire interview here.)

Chris Ferris

Kevin Allen: What are some of the things that you learned early on that have bridged your career — the keys to creating, maintaining, and having successful open source communities?

Chris Ferris: I recognized early on that doing anything in a sort of a closed, proprietary manner in terms of developing software was a losing proposition. It’s a slower process, you are limiting your innovation to the people that you have, and so forth. And what I was perceiving was that when things are developed out in the open, they just exploded. They would develop an order of magnitude more quickly, and then you’d have this blossoming ecosystem of sub-projects, related projects, tooling, and so forth that would develop around them … that’s what really what brought me to IBM — I was invited to bring some of that appreciation to IBM, to help IBM sort of get it, to be more involved and to take this beyond just the things that we were doing around Java and XML, and apply that pretty much across the board.

[Around 2010], inside IBM we had six independent, non-interoperable, prototypical virtualization platforms, and we were thinking this could become cloud. The problem is we had six of them, they were all different business units, they were competing against one another. So that was when I started looking at open source as being an answer to what we were doing, and we started looking around at some of the various projects, and that led me to OpenStack. At the time, OpenStack was still very young, it was fairly immature from a software development perspective — but you could tell that there was something special about it, and it was the community that really was what attracted us to the technology platform.

KA: OK, so you were able to start to use OpenStack as a way to articulate our cloud story, and to make a cohesive offering?

CF: So we thought about this. We could take these six non-interoperable, non-workload-portable implementations and try to consolidate them, unify them into a single, coherent offering of an IBM data center virtualization/private cloud kind of a solution. Or we could adopt for this emerging technology in OpenStack that seemed to be garnering both a community of dedicated developers and interest from a large number of vendors — and make a go of that. And so we managed to convince the business that the right thing to do was to start new. And that helped significantly to transform IBM from a closed, proprietary software development shop to one that was really fully embracing open source, and I think that was a nice turning point for IBM.

KA: How did you get from OpenStack to starting to work on Blockchain?

CF: So OpenStack then led to CloudFoundry. We [saw that] this Platform as a Service was going to be an important aspect of what we deliver … We had the beginnings of a cloud, but where developers were moving was beyond just provisioning VMs and deploying things into a virtual machine context, to wanting to just focus on the application development, not so much on the infrastructure details. So we started looking around and we saw CloudFoundry, and we said again, another really good opportunity. And so I worked … to help establish the CloudFoundry Foundation. So now I’ve got a reputation inside of IBM: I know how to sort of get these communities up off the ground and engage IBM in them and ramp up our contributions and so forth into those, build a community, build an ecosystem, and so forth.

So fast forward to 2015 … we’d been exploring Ethereum and bitcoin and a lot of the lightning and sidechains and various other things, but none of them seemed suitable for the enterprise. And so we started to build our own proprietary blockchain technology. [IBM Vice President of Blockchain Technology Jerry Cuomo], in his infinite wisdom, felt that if this is going to be successful, it can’t just be IBM. It has to be open source. And so I said we should definitely open source it. Again, a technology that’s intended to be essentially ubiquitous has to be open source. If it’s going to be successful, it can’t just be IBM. So I worked with the Linux Foundation because we had worked very closely with them most recently on CloudFoundry and Node.js and a few other projects — and that’s how Hyperledger began. I approached them with a proposal and we built a set of initial sponsors and formed the governance model, and the rest is history. We’ve grown nearly tenfold since the launch in February of 2016. So I think an impressive start. It’s actually the fastest-growing community at the Linux Foundation of all time.

KA: So how does someone get involved in Hyperledger, specifically?

CF: Basically if you go to Hyperledger.org, there’s a number of different pages and then a number of different tabs. One of them is “Projects.” We now have 12 top-level projects, five of which are blockchain frameworks, and then we have some tooling and so forth to go with those. So I would start there.

Related:

How to Change the Percentage of the Virtual Desktop Agents in Powered State for Catalogs

This article describes procedures for managing Delivery Groups. In addition to changing settings specified when creating the group, you can configure other settings that are not available when you create a Delivery Group.

Refer to Citrix Documentation – Manage Delivery Groups

Related:

Citrix Receiver Updates Troubleshooting Guide

For information about configuring Receiver Updates, see Configuring Receiver Updates in Citrix product documentation.

Update: Citrix Receiver for Mac 12.9.1 contains the fix for Auto Update.

Note: Review CTX234657 to resume Auto Update and fix the “Problem Checking for updates” error displayed in Citrix Receiver Updater.

There are three sections in this document:

Section 1: Key Citrix Receiver Updates settings for troubleshooting

Section 2: Citrix Receiver Updates Logging

Section 3: Troubleshooting Citrix Receiver Updates

Section 1: Key Citrix Receiver Updates settings for troubleshooting

You can configure Citrix Receiver Updates as follows:

  1. Right-click the Citrix Receiver for Windows icon in the notification area.
  2. Select Advanced Preferences, and click Auto Update. The Citrix Receiver Updates dialog appears.

By default, the Yes, notify me option is enabled.

User-added image

If an administrator manages the user account or if an user is under a company policy, the Receiver Updates options might be set according to the administrator-specified settings.

This is the only setting for Citrix Receiver Updates that is available for an end-user modification.

Citrix Receiver Updates rollout period:

Citrix Receiver Updates rollout do not happen to all users on same day or at the same time. It depends on the delivery period and delay groups. Ideally delivery period is 30 days. So, users will get Receiver and related plug-ins updates any day between Day-01 and Day-30.

Based on the delay group settings, updates are available at the beginning, the middle, or the end of the delivery period.

The delay groups are categorized as follows:

  1. Fast – Update rollout happens at the beginning of delivery period.
  2. Medium – Update rollout happens at mid-delivery period.
  3. Slow – Update rollout happens at the end of delivery period.

Citrix Receiver Updates can be configured to deliver only updates marked for Long Term Support Releases (LTSR) or Current Releases (CR). The default is to accept CR updates.

These settings can be configured during Citrix Receiver for Windows installation, or using the Group Policy Object administrative template, or the StoreFront Account.

The registry location for each of these methods is:

  1. Install Time: HKEY_LOCAL_MACHINESOFTWAREWOW6432NodeCitrixICA ClientAutoUpdateCommandline Policy
  2. GPO: HKEY_LOCAL_MACHINESOFTWARE[WOW6432Node]PoliciesCitrixICA ClientAutoUpdate
  3. StoreFront: HKEY_CURRENT_USERSOFTWARECitrixReceiverSRStore<some random number>Properties

The relevant registry values to examine are:

For Install Time and GPO configured settings

Value: Auto-Update-Check

possible data:

Auto” (default) – perform auto updates,

Manual” – updates are only fetched when the user makes a check request from the Receiver menu,

Disabled” – no updates checks will be made.

Value : Auto-Update-LTSR-Only

possible data:

True” – the updater will ignore any updates that are not marked as being LTSR valid,

False” (default) – the updater will accept any updates.

Value : Auto-Update-Rollout-Priority

possible data:

Fast” – updates will be accepted towards the beginning of the delivery period,

Medium” – updates will be accepted towards the middle of the delivery period,

Slow”– updates will be accepted towards the end of the delivery period.

For StoreFront Account configured settings

Value: Enable

possible data:

True” (default) – perform auto updates,

False” – updates are only fetched when the user makes a check request from the Receiver menu

Value : LTSROnly

possible data:

True” – the updater will ignore any updates that are not marked as being LTSR valid

False” (default) – the updater will accept any updates.

Value : BucketId

possible data:

Fast” – updates will be accepted towards the beginning of the delivery period,

Medium” – updates will be accepted towards the middle of the delivery period,

Slow” – updates will be accepted towards the end of the delivery period.

Section 2: Citrix Receiver Updates Logging

Before you troubleshoot any issues with the Citrix Receiver Updates functionality, enable logging for Citrix Receiver Updates.

In Citrix Receiver for Windows Version 4.9, Citrix Receiver Updates logging is disabled by default.

In Citrix Receiver for Windows Version 4.8, Citrix Receiver Updates logging is enabled by default.

Citrix Receiver Updates logs can be found at /%temp%/<CitrixAutoUpdate _.log>

To enable Citrix Receiver Updates logging using the registry editor:

  1. Launch the registry editor.

  2. Navigate to HKEY_LOCAL_MACHINESOFTWARECITRIX.

    Note: If you are an individual user, navigate to HKEY_CURRENT_USER SOFTWARECitrix.

  3. Add a new DWORD value.

    On 32-bit systems:

    HKEY_LOCAL_MACHINESOFTWARECitrix

    Name: AutoUpdateTracingEnabled

    Type: REG_DWORD

    Data: 1

    On 64-bit systems: HKEY_LOCAL_MACHINESOFTWAREWow6432NodeCitrix

    Name: AutoUpdateTracingEnabled

    Type: REG_DWORD

    Data: 1

  4. Save and close the registry editor.

  5. Restart the Citrix Receiver for Windows session for the changes to take effect.

Section 3: Troubleshooting Citrix Receiver Updates

Check for the requirements below as part of troubleshooting Citrix Receiver Updates.

  1. If you have configured an SSL intercepting outbound proxy, you must add an exception to the Receiver Citrix Receiver Updates Signature service (https://citrixupdates.cloud.com) and the download location (https://downloadplugins.citrix.com).
  2. If the Receiver for Windows session is running on a VDA, Citrix Receiver Updates is disabled.
  3. If the Receiver for Windows is running on an end-point where the Desktop Lock component is enabled, Citrix Receiver Updates is disabled.
  4. In Citrix Receiver for Windows Version 4.8, Citrix Receiver Updates was not functioning in a proxy setup. This issue has been addressed in Version 4.9.
  5. The Citrix Receiver Updates functionality is not available when a user with administrator-level privileges has installed Citrix Receiver for Windows, and an individual user(non-admin) is accessing Citrix Receiver for Windows.

Common issue #1: Software is up-to-date:

To check for updates manually, select the Check for Updates option from the Citrix Receiver for Windows icon in the notification area. When you check for updates manually and do not find any update available, it is due to one of the following reasons:

  1. No updates are available.
  2. Your account is set to a medium or slow category in the delay group. This indicates that the update rollout happens at the middle or at the end of the delivery period.

The following dialog appears when you check for updates manually and when no updates are available.

User-added image

Solution:

You can check for updates at a later time or wait for the Citrix Receiver Updates notification.

Common issue #2: Issue when checking for update:

An update check can fail for various reasons. For example:

  1. No network connection during update check.
  2. Firewall settings don’t allow the connection to update server.

The following error message appears if there is an issue when checking for update.

User-added image

Solution:

Ensure that your network connection is working properly. Alternatively, also verify that the firewall settings are not blocking the connection to Citrix update server.

Common issue #3: Issue when downloading the update

There is a network connection issue when checking for update or when you click the Download option.

The following error message appears if there is an issue when downloading the update.

User-added image

Solution:

Ensure that your network connection is working properly.

Common issue #4: Error during installation:

During update installation, the following issues might occur:

  1. Not enough disk space
  2. During installation, if the operating system starts with any other installation, Citrix Receiver installation turns unresponsive and the update installation fails.

The following error message appears if the Receiver Update install occurs at the same time as another install on the system.

User-added image

Additional Resources:

Resume auto-update for Citrix Receiver

Receiver for Mac Auto-Update Troubleshooting Guide

Citrix Receiver Auto-Update Frequently Asked Questions

Related: