Chimera Computing Ltd




You DO...

  • ... require a domain name such as ""
  • ... require a single "catch-all" Pop3 account where all "" mail goes
  • ... need a local mail server (any RFC compliant SMTP server)

  • You do NOT...

  • ... require a static IP address. EFS can work with both static and dynamically assigned IP addresses
  • ... need to continually maintain EFS such as adding new users - once it's setup, you rarely need to touch it!
  • ... need to configure ETRN (a somewhat dangerous protocol for retrieving mail)
  • ... need DNS (domain name server) setup (although it is preferred)
  • ... need multiple and costly Pop accounts at your ISP. All mail is routed to and picked up from a single mailbox
  • ... necessarily need an expensive email server, there are plenty of really good freeware mail servers!
  • ... need to pay your ISP $$$ to route mail to you - that's EFS' job

  • Some other uses for EFS based on our customers feedback

  • For those who have a permanant Internet connection and a primary MX record to have mail sent direct to your server, many clients have made use of the (usually free) catch-all mailbox provided by their Internet Provider with their account, and configured a secondary MX record to send email to that. EFS is then used to collect mail on a scheduled basis. If the primary MX record becomes unavailable due to Internet connectivity issues, email is delivered to the secondary MX record (pop3 mailbox) and collected by EFS when the connection returns.
  • Many have utilised EFS as a migration tool - an "intermediary" solution in between mail server migrations.
  • EFS has been utilised to retrieve email from a single pop3 account but not forward it (with mail optionally left on the server) then use the Rules tab to perform certain tasks depending on message content. Other customers have used 3rd party tools or scripts to read the (text based) message files from the EFS Inbox folder then perform various other tasks depending on their content.

  • (Chimera Computing Ltd)