Showing posts with label fortimail. Show all posts
Showing posts with label fortimail. Show all posts
Thursday, 29 December 2016
Tuesday, 22 September 2015
FortiMail quarantine URL points to the wrong address
Today I was testing out the quarantine feature on the FortiMail and noticed something strange with the release link. The domain name that the link forwarded me to was doubling the hostname of the FortiMail.
For example, below is the quarantine email I received. I click on the 'Release' link to try and release the email:
Unfortunately the quarantine page doesn't load. Looking at the URL I can see that it's pointing to mail.mail.ingramlabs.com.au instead of mail.ingramlabs.com.au. The 'mail' hostname here has doubled up for some reason.
For example, below is the quarantine email I received. I click on the 'Release' link to try and release the email:
Unfortunately the quarantine page doesn't load. Looking at the URL I can see that it's pointing to mail.mail.ingramlabs.com.au instead of mail.ingramlabs.com.au. The 'mail' hostname here has doubled up for some reason.
Labels:
fortimail,
fqdn,
quarantine,
troubleshooting,
webgui
Wednesday, 3 December 2014
How-to: Change WebGUI HTTPS certificate on Fortinet devices
Below is a list of commands required to change the default HTTPS certificate that gets presented on the admin WebGUI.
For each of these examples I've already loaded a certificate called 'webgui-cert'. Change this value to match the certificate you import.
Labels:
certification,
cli,
fortianalyzer,
fortiauthenticator,
forticache,
fortigate,
fortimail,
fortimanager,
fortinet,
how-to,
ssl,
webgui
Monday, 1 December 2014
How-to: Disable SSLv3 on Fortinet devices
With the release of the POODLE vulnerability, Fortinet have released a great article on howto disable SSLv3 on all the Fortinet devices that are affected.
The list goes on to include:
The list goes on to include:
- FortiGate
- FortiMail
- FortiAnalyzer
- FortiManager
- FortiAuthenticator
- FortiCache
- FortiWeb
- FortiDDOS
- FortiADC-D
- FortiClient
- FortiVoice-Enterprise
- FortiRecorder
- FortiDB
- FortiSwitchOS
- FortiSwitch ATCA
Fortunately disabling SSLv3 is very simple on all devices, with some just requiring an upgrade.
I won't go into detail on howto disable SSLv3 on every box as it's covered in the article linked above. I just wanted to go through on how you can test to ensure that SSLv3 has been disabled once you've made the configuration change.
Labels:
cli,
fortiauthenticator,
forticache,
fortidb,
fortigate,
fortimail,
fortimanager,
fortinet,
fortirecorder,
fortiswitch,
fortivoice,
fortiweb,
how-to,
poodle,
ssl,
vulnerability
Wednesday, 25 June 2014
How-to: Configure User Alias Options on a FortiMail
If your organisation is using aliases, it's generally a good idea to configure the 'User Alias Options' within the LDAP settings to ensure users only get one quarantine email for all their addresses, instead of one for each alias address.
To configure this, first edit the LDAP profile you've configured for your domain (found under Profile > LDAP) and expand the 'User Alias Options' section.
Ensure the tickbox has been enabled next-to 'User Alias Options', then configure your base DN, Bind DN and Bind password as normal. For the 'Alias member query' option use proxyAddresses=smtp:$m. Lastly untick the 'User group expansion in advance' box.
Your final configuration should look something like this:
To test this out click on the 'Test LDAP Query...' link near the top of the LDAP profile page. From here choose 'Alias' from the dropdown menu and type in your email address at the bottom. For the below example my normal email address is amouawad@wglab.com.au and my alias is allan@wglab.com.au.
Click on 'Test' and you should see the alias match!
To configure this, first edit the LDAP profile you've configured for your domain (found under Profile > LDAP) and expand the 'User Alias Options' section.
Ensure the tickbox has been enabled next-to 'User Alias Options', then configure your base DN, Bind DN and Bind password as normal. For the 'Alias member query' option use proxyAddresses=smtp:$m. Lastly untick the 'User group expansion in advance' box.
Your final configuration should look something like this:
To test this out click on the 'Test LDAP Query...' link near the top of the LDAP profile page. From here choose 'Alias' from the dropdown menu and type in your email address at the bottom. For the below example my normal email address is amouawad@wglab.com.au and my alias is allan@wglab.com.au.
Click on 'Test' and you should see the alias match!
Subscribe to:
Posts (Atom)