David W SonicWall Employee
Comments
-
Yes Once it's web posted, but I can't tell you when that will be yet. If you have a case open we can see about posting it to the case. However that will also take time.
-
Hosted was updated already and should not be an issue. All on prem ES windows or appliance need to do the following. The builds are in process of web posting so if you want to wait you can but we have provided some temporary links to the builds. 1. Update the unit with newer build 2. Note that Junkbox and Auditing pages…
-
It's there and available for all flavors. I can see them all from my own account. May need to clear cache and refresh.
-
The SMTP code does not use anything from Apache. Please be watching the page for any updates on this issue. You will see updates to it throughout the day.
-
Everyone please remember that there will be no official comment to this issue here in the community due to this being a vulnerability. Also there will most likely be nothing on your Jira BWC until there is a formal announcement. We do not use Apache for SMTP either. The SMTP engine is our own coded product.
-
@BWC We can check with engineering but keep in mind that in most cases we cannot comment unless it's in release notes. Can you open a case for that and I can have Gailand follow up.
-
@BWC I will have to see what I can find out. I don;t think we have anything reported on it at the moment. However I do know that there are some instances where if there is anything in policy filters doing anything with compressed file types they may get missed due to being altered. Check and see if you have anything like…
-
There is presently no back end issue. If you did a hard reboot, power outage or any number of things it can cause corrupt data. Please follow the rebuild option in this KB and if you do have issues still please call support and open a case. Use the one for For appliances: Versions 7.4.6 – 9.x.x
-
These are correct assessments and I will be discussing with engineering about the length of records and what we are looking up. Obviously I wont have any immediate updates but hopefully we will be able to have them lengthen the depth we will go to do lookups. Permanent Error: SPF record is too long for ES, although it's…
-
@BWC I'm working several different projects at the moment not just Email Security. I will try and get you something together over this coming week. It's not a simple response for this one.
-
@BWC I will message you directly on this to explain the why. Anything else would have to be addressed by PM.
-
Port 587 would be TLS. It is a normal part of email delivery. If you are seeing issues with spam I would advise to open a case with support to review the issue.
-
You can add drive space but not while running. You have to shut it down, add the drive space and boot it back up. It will provision the space allocated as it boots up.
-
@BHO We do not reach out to clients using DNS. These would be responses to DNS requests coming to our servers. I would suggest a packet capture on the client IP to see what service on the computer is making the request. Also your firewall should never allow a DNS request in that the request did not originate from inside.…
-
@BHO Please check the client where you are seeing this and see if the Sonicwall antispam desktop client is installed or Zone Alarm from Checkpoint. That is most likely why you are seeing this.