This page lists some of the common user problems and their resolution. If the problem is not listed on this page then please check the index for any relevant material. This document also has a search function.
At installation the UBEBlock processor is disabled. This is because the basic training of UBEBlock must be performed before it will work correctly and many users were not training it at all. To enable UBEBlock rating of the messages perform the initial UbeBlock Training and then enable the filtering in the filter policy options page.
This is usually seen in the SMTP , LDAP or WebMail service but can be seen occasionally in the other services. It is caused by another program running and using those ports. To resolve the issue the running program must be located and stopped or the service moved to another port.
The usual cause is the Microsoft Simple Mail Transport Service. To resolve this error open the windows service control panel, stop the service and set its startup mode to disabled.
This is usually cause by IIS. If you are not using the PC as a web server then you should open the windows service control panel and then stop and disable the Web Publishing Service. Additional information is available here.
This is usually a problem on Windows 2003 servers because the Active Directory service uses LDAP. In this case you must change the port used by the FTGate LDAP service and alter the mail clients to use the new port.
Many service providers will not accept mail from servers that have an invalid or incorrect hostname configured for the HELO/EHLO SMTP command (Outbox/Connection). Your hostname should be the name that will be resolved by a reverse lookup for your ip address, or at the very least a valid name used in a DNS which resolves to your IP.
For example :
lookup mx0.ftgate.com = 18.104.22.168
lookup 22.214.171.124 = 225.128-255.16.224.195.in-addr.arpa = mx0.ftgate.com
So it resolves to the same address both ways. This is the correct way to have a host defined when sending out using MX records. If both paths are not there then some servers will reject.
To configure this you will have to contact your ISP/DNS hosting company.
This is the same cause as 3 above, however, Hotmail simply delete the messages without notification to the server or recipient.
Users of AVG anti-virus and Cisco PIX firewalls may have problems as these two products can be configured to modify the EHLO/HELO message. They replace the EHLO command with XXXX which causes the error. You must reconfigure these devices to allow the command through correctly.
See: Backup and Restore
See: Firewall ports
In order to share mail folders you must reconfigure your client application to connect to FTGate using the IMAP protocol. The IMAP protocol stores the messages on the server with the client being used to read/create messages but not to remove them from the server. The protocol allows for multiple folders and access to shared folders. This also allows Outlook users to stop using PST files on the local PC and allows an administrator to centralise the backup of mail.
If you are having problems with SmartPop deliveries please check the following before requesting support:
SmartPop overview: SmartPop
Reasons why problems may exist: SmartPop limitations
Duplicate delivery of messages: SmartPop Duplicate Delivery
General delivery problems: SmartPop delivery problems
This is caused by the number of addresses in the messages header exceeding the limit set by the administrator. You can change this in the SMTP tab of the global security policy together with the settings for the maximum number of recipients for a message.
The bulk sends rejection relates specifically to the number of addresses appearing the in To, and CC lines of the message header.
If you get this message it is because the email address of everyone you are sending to is in the message header. Thus if you send to 35 people, every person who receives the message gets the email address of the other 34. If you are in the UK or Europe we would strongly recommend that you do not change this setting. Unless you have permission from each of them to distribute their details you will be breaking the UK/EU data protection act and could face a heavy fine. We would recommend moving the addresses into an FTGate mailing list, or contact list. These will send the message as a BCC so none of the recipients get the details of any of the others.
This limit is set in the security policy being used by the SMTP service in the SMTP tab (Services/SMTP Service/Security, click on the Edit Service Policy Settings link).