Trouble with custom port in Mail Security Web Qarantine

[katbert 3]

I'm trying to setup web quarantine in Mail Security 6.3.10005.2

Default port 80 and 443 used by IIS, which is required by MS Exchange

 

I'm try to set custom ports for Eset Mail Quarantine: 5080 for http, and 5443 for https

But when I use link hxxp://server.domain.local:5080/quarantine/- Eset Mail Quarantine server redirects to 443 port, not custom 5443. I see error 404 from IIS

If I use link https://server.domain.local:5443/quarantine/- I see error establish secure connection

[filips 44]

First problem is a bug - redirection from HTTP to HTTPS ignores custom port setting - will be fixed in EMSX 6.4

Second problem - which browser(s) did you use? can you give us a more detailed description of the error?

[katbert 3]

I use Firefox 47.0.1 and IE10 (part of Windows Server 2012)

Firefox show error: Secure Connection Failed

[katbert 3]

Error in Firefox:

[filips 44]

This is most likely a certificate problem. Can you try other certificate? It can be set in 5443 port binding in IIS - Default Web Site.

Also this might help: (https://support.mozilla.org/en-US/questions/1058856)
- Open Firefox's about:config
- Set security.tls.insecure_fallback_hosts = mail-kse.test-kse.local

[katbert 3]

In IIS - default web site I see only 80 and 443 port bindings

Eset don't create any bindings when I enable web qarantine

[katbert 3]

I changed Eset web quarantine port to default 443 - and this solved my problem.

Now web quarantine works

 

If Eset don't use own web server - then custom ports settings don't needed

Thanks!

[katbert 3]

Maybe Eset have bug with configuring IIS to use custom ports

[ajal 1]

Hi there

 

I use ESET MailSecurity 6.3.12010.0 on 2 Exchange 2013 Servers - in DAG.

I noticed the same as katbert - when we customize the ports, there is no way to get the webinterface.

 

Changing them to Default ports 443 and 80 - worked.

 

So, ESET is not using IIS for web quarantine?

[ajal 1]

Hi again

 

I tested ESET MailSecurity in a Exchange 2013 DAG - 2 x Exchange Servers.

All Mails in the Quarantine-Manager are also in the "Shadow-Redundancy" Queue - and the Queue is not getting empty.

 

Is this a known issue in Version 6.3.12010.0?

 

Thank you

[filips 44]

Hi ajal,

To make your custom ports work with quaratnine web interface open IIS and add a binding to this port to Default web site.

Messages stuck in the Shadow redundancy queue is a known issue. We were able to reproduce this problem even without our product installed (using MS Exchange transport rules).

Quarantined messages are discarded from the queue after specified period (ShadowMessageAutoDiscardInterval - default is 2 days).

[ajal 1]

Hi ajal,

To make your custom ports work with quaratnine web interface open IIS and add a binding to this port to Default web site.

Messages stuck in the Shadow redundancy queue is a known issue. We were able to reproduce this problem even without our product installed (using MS Exchange transport rules).

Quarantined messages are discarded from the queue after specified period (ShadowMessageAutoDiscardInterval - default is 2 days).

 

Hey filips

 

Thank you for your reply.

 

I use the Defaults for now, seems no Impact on Exchange Services.

 

Regarding "Shadow-Redundancy"-Queue

This Problem started as soon as we installed MailYSecurity 6 on our Exchange Servers.

One interesting Point is, only filtered Mails by ESET MailSecurity stuck in the Queue.

 

For us, waiting for AutoDiscardInterval is no solution - we have different Monitoring scripts an Tools checking the Queue.

Also, when I take on of the DAG-Members in Maintenance - the Queue is also checked, and must be empty - so big Impact in our production.

I opened a ticket for this issue - today.

 

 

Is there more Information about this issue? What can we expect from ESET?

Other Workarounds ?

 

Thank you