03-25-2019 04:11 AM - edited 03-27-2019 12:57 AM
Hi!
We have setup notification emails on our SMA (12.0.0.452).
Management interface:
Server hostname
Appliance management activated.
The ESA sends spam to the quarantine on port 6025 on that interface
Public:
antispam.domain.com
Spamquarantine port 80&443
Default interface for spam quarantine.
Name set to https://antispam.domain.com
But the clickable links in the emails points to the wrong URL?
First they pointed to the URL for the new look. But when I disabled trailblazerconfig they pointed towards the name of the sma, ervers managementinterface.
Example:
Release (clickable link that points to servermanagentname) xxx@gmail.com Your account has been locked! 25 Mar 2019
View All Quarantined Messages(14) (clickable link that points to servermanagentname)
Note: This message has been sent by a notification only system. Please do not reply
If the above links do not work, please copy and paste the following URL into a Web browser:
https://serverhostname-managementinterface/quarantine?h=f&action=search
In order to access spam quarantine in old portal, please copy and paste the following URL into a Web browser:
https://antispam.domain.com(public interface)/Search?h=f356b009a.....
The URL above is the only one that points correctly. Is there any way to fix this? Do I need to skip one interface and run everything over one interface and set the of the server and so on to antispam.domain.com?
As far as I see you cant separate the management interface from the interface that the users access? I would like to have them on separate IP:s.
03-26-2019 03:56 AM
I found these two bugs.
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvn97580/
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvo58327
And it looks like there is no way of fixing this right now?
03-27-2019 07:17 AM
No, not really.
The new gui is on a different web server than the old gui, but since they want both to be available they can't be on the same ports, and they decided the new gui would be accessed through the "system" name, no matter what you put on the interface.
Trailblazer basically puts a proxy in the middle so the names all get straightened out but they picked a DIFFERENT port (4431)...
Hopefully when they abandon the legacy interface this should get straightened out...
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide