Hey folks over at Xeams,

Been a while with Christmas and New Year being on the table.

Quick question as I haven't really had the time to divulge through all the options and articles.
Sometimes these URL's are stored in bookmarks and it would be fantastic if these connections would automatically be redirected to an SSL/TLS connection.
Am I right in saying you currently have no option to redirect port 80 requests to 443 to complete the login and configuration..?
If not, roadmap on this...?

Thanks,
James

James, 

You are right. This feature does not exist in Xeams and is left out by design. It is very common to run into errors when HTTPS, which happens due to several reasons. For example, an error with the certificate. In that case, you will get locked out if port 80 redirects the traffic to 443. 

A better way is to block port 80 from your firewall. This way, no one from the Internet will be able to connect to port 80, but you will have access from the LAN in case there is a problem with HTTPS.

Guys you know we work as a team on this

Whilst true in its own right, simple wire sniffing can retrieve this information on the LAN side compromising the admin login. It's not always the external users you have to worry about. Internal malware can also compromise live wire data. Certificate errors are the responsibility of the internal admins to get right if they are going to use this facility.  If anything certificate redirect errors provide admins with a sign that there is a problem with their config.

Would it not be a better option to provide users an option to deal with this on a case by case basis..?

Could you not just provide me a switch I can add to the config files to apply this setting until you internally decide if you wish to implement this crucial option?

Regards, James

Sure, no problem. We will add that as an option in the next build.

Thanks - look forward to it.

As always, fantastic support and a fantastic product.

Regards, James

James,

Send us an email to support@synametrics.com if you would like to get this new update before it is made available publicly. We should have this ready by next week.

Will it be implemented as part of the auto update feature in the current build (5968) for a next week release or will it be going through some internal ring for testing first..?

We are not planning to release an update next week. I said the change you asked should be ready by next week. Internally, we are already at build 5970. Changes we make to Xeams run on our test servers for a few weeks before they are published. The feature you asked won't be made public until it has been throughly tested. I was wondering if you were okay getting the update before it gets released publically - meaning a beta release.

No problem - I'll drop you an email shortly.

p.s. When is your cut off date for 5970 as I have another request which I would like to have squeezed in for testing.

James

Build 5970 is an interim release number. I am sure this number will go up before it's made publicly available. What is your other feature request? We will try putting that in if it does not require too much work.

Grey listing - presently the only way we can tell if an email server has been grey listed is thorough the logs. We then have to subtract the time of connection from the current time to know how long before we know the remote server can retry. This can be tedious with cross site implementations as the spam filter whitelist doesn't presently integrate with the grey listing facility.

Dev team have whisked up a little app that takes initial server connect time from current time to give a difference in when the remote server time can retry (based on grey listing times).

1. Could we just add a counter to the log file that shows how many minutes is left on the grey listed server before it can try again.
This is for reporting and audit purposes only as we obviously have no control over when the remote server will try again.

2. Integration with whitelisting would also be a benefit.

James

Just a minor push on this. Thanks, James