FTGate .NET Script Extensions

One of the most flexible new features in FTGate 7 is the ability to add .NET Script extensions.
This allows you to hook into various points in FTGate and add your own processing. So for example, you could:

  • Write your own password authentication system
  • Change values in your message headers
  • Write anything that hooks FTGate into your own software product

The .NET scripting allows you to individually tailor FTGate’s message processing to suit your own needs. For more specific instructions on how to do this, please see our Documentation

Although you are free to add your own extensions, we also offer a tailored scripting service. If you are interested in this, please contact support@ftgate.com for further details.

FTGate Update 7.0.206

This update is available via auto-update.

It can also be applied manually if your UPSP is up to date: http://download.ftgate.com/files/FTGate7/updates/ftgau70206.fau

Changes:

  • Fixed quota issues
  • Fixed issue with forwarding attachments in WebMail
  • Fixed semicolon issue with sending from WebMail
  • Fixed auto-update issue
  • Fixed activation of licence issue
  • Modified RBL handling for odd DNS server responses
  • Modified SMTP to block RBL blacklisted sites from trying to AUTH
  • Fixed text attachment encoding issue
  • Added assignee “Anyone” option to tasks and projects
  • Fixed SMTP sequence/timing error for some servers

 

FTGate and reliable DNS

In order for mail to be delivered both to and from your server, for filtering to be performed and for sender validation, your FTGate server will need access to a reliable DNS server. This is so that names can be converted to addresses, delivery information, blacklists et al can be checked.

Unlike most connection types on the internet, DNS uses a packet transmission system rather than opening a connection. A request is made by sending a packet to a server and waiting for a response. If the DNS server is down, or busy, or doesn’t service that type of request you often get no reply at all. So the mail server just will just sit there waiting for a reply until it times out. This will happen for every request. So an unreliable DNS will bring your server to a complete standstill.

Your ISP should give you the address of their DNS servers, and this should be used as the DNS server for your FTGate PC. This gives the fastest response and their servers should be reliable.

However, we have seen a rise in customers who are using a public DNS service, either because they don’t know their ISP’s DNS address or because of their ISP doesn’t have a DNS server (which is very bad if they are offering a business service).

The most common of these are GoogleDNS and OpenDNS. The GoogleDNS is not suitable in any way for use with a mail server. It only stores records for web browsing and all other traffic will fail. The OpenDNS servers will respond to most requests but will fail for many SPF and blacklist lookups, making them pretty much useless for business and we have noted that they appear to have periods during which they do not respond.

We would recommend that you use the ISP DNS servers whenever possible, but in the event of their not offering a complete service to their customers you can always run your own inexpensive DNS server on the same PC as FTGate.

We have used the product SimpleDNS (http://www.simpledns.com/) here and have found it to be suitable for most business sizes and can recommend it to our customers. Please note that we are in no way associated with SimpleDNS.

FTGate Update 7.0.203

This update is available via auto-update.

It can also be applied manually if your UPSP is up to date: http://download.ftgate.com/files/FTGate7/updates/ftgau70203.fau

Changes:

  • Fixed mislabelled POP button
  • Added Connect Now option to SmartPop
  • Modified SMTP filtering to exclude base64 attachments from phrase and word scans
  • Modified SQL handling to limit resource use on busy systems
  • Modified Group Manager access rights for projects
  • Fixed webmail access for remote domains
  • Fixed creation of new SmartPop accounts

FTGate Update 7.0.200

This update is available via auto-update.

It can also be applied manually if your UPSP is up to date: http://download.ftgate.com/files/FTGate7/updates/ftgau70200.fau

This release has a huge new feature that makes FTGate probably the most flexible mail server available. We have added support for adding your own .NET c# code to FTGate.

Through a series of hooks you can intercept FTGate’s processing and add your own custom actions. As FTGate continues to be developed, these hooks and access to the modules in FTGate will be extended giving even greater capabilities to FTGate.

Changes:

  • Fixed: Postmaster mail fro unknown users options not working in SMTP
  • Fixed: Problem with forwarding messages with attachments
  • Fixed: WebMail not showing multiple entries for TO and CC
  • New: WebMail now has a search bar for sender/subject
  • Fixed: Inbox rules path formatting
  • Fixed: IMAP access to quarantine
  • Fixed: Added password setup to group mailboxes
  • Fixed: Issue with sender address selection when replying to project emails
  • Fixed: SQL tracking search not escaping characters correctly
  • Fixed: Changed start-up sequence to better handle slow system starts
  • Fixed: Signatures not being correctly added to new messages
  • New: Added .NET scripting support – See documentation here

 

FTGate Update 70104

This update is available via auto-update.

It can also be applied manually if your UPSP is up to date: http://download.ftgate.com/files/FTGate7/updates/ftgau70104.fau

Changes:

  • Fixed: Routing table IP:aa.bb.cc.dd test matching wildcard addresses
  • Fixed: Registration key whitespace sensitivity when entering keys/activation codes
  • Fixed: Tracking page times not correcting for DST
  • New: Web Mail Compose window now allows selection of valid email addresses in the from field for users with multiple accounts, aliases and group projects.

FTGate Update 70101

The latest update to FTGate7 is now available via Auto Update.

Changes in 7.0.101:

  • Fixed project access rights
  • Removed Group Folder from members view
  • Added Project mode to Group Mailboxes:
    Project mode makes the mailbox visible to project members in read only mode, and makes the project contents visible in the projects tab.
    Project mailboxes have group delivery and tracking codes disabled.
  • Users can now set their deleted items folder
  • Fixed some message display issues
  • Fixed a message expansion bug that could bloat message sizes
  • Fixed additional localisation issues
  • Users can now rename folders in WebMail
  • Improved WebMail data caching  and handling of large folders and added a status bar for feedback.
  • Fixed some spam filtering issues that caused ratings to be bypassed
  • Cleaned up WebMail mail and project views and added icons to show the item type