Chimera Computing Ltd

EFS - FAQ / GENERAL

General FAQ

BACK


  • Is EFS supported on 64 bit operating systems?
  • EFS is not supported in a 64 bit Windows environment. If you are running EFS with Exchange 2010 (64 bit only) then you can run EFS on another server thats 32 bit, and retrieve email / send email to Exchange across the network. EFS does not need to be installed on the local mail server.
  • How does EFS handle BCC'd email?
  • EFS (or any Pop3 connector for that matter) is never guaranteed to deliver BCC'd email. This is because it is "blind" carbon copied and therefore, depending on the receiving mail server, the recipients address maybe stripped from the email headers. The only way to test this is to send an email BCC'd to a test account. Have EFS pop for email (temporarily turn SMTP forwarding off) then open the .MSG file from the C:\Program Files\E.F.S\Inbox folder in notepad.exe. Check through the top of the message and see if the recipients address exists in any of the headers. If there is a Bcc: header with the recipients address, then ensure its not "ignored" under the Headers section of EFS. If its in one of the Received: headers, ensure that this header is not ignored in the Headers section of EFS. Most often than not, there will be a header such as "X-Rcpt-to:" of "Delivered-To:" or similar that will contain all end recipient(s) addresses that the message is destined for. If this exists, then add this header to the list (and if necessary, choose to ignore all the standard header fields)
  • How does the pre-check ping work in EFS?
  • EFS pings the remote host 4 times with 32 bytes of data ("EFS12345678901234567890123456789"). The first 3 pings are (if required) to establish the connection. If the last (4th) ping is un-successful, then EFS determines the remote host unreachable, regardless of whether the first 3 pings were successful or not.
  • How do I change the port number that the IMC listens on under Microsoft Exchange?
  • On the Microsoft Windows NT server that Exchange is installed, open the following file in notepad:

    C:\Winnt\System32\Drivers\Etc\Services

    Look for the line:

    smtp 25/tcp mail

    and replace 25 with the desired SMTP port number that the IMC will listen on. Port 97 or 8025 is recommended. Stop and Start the Microsoft Internet Mail Service.
  • How does scheduling work?
  • For EFS Version 5.5 or later, the next check is scheduled BEFORE it connects to the POP3 server. If the next scheduled time is triggered while EFS was checking from the previous check, the time is simply re-scheduled to the next check time.

    NOTE: If the connection to the Pop3 server timesout, then EFS reschedules to check again in 2 minutes. It does this 3 times before setting to the next check time. This is also a reason why mail may be checked at various times in the hour.

    For more information, see Scheduling options with EFS
  • Where in the registry are the settings stored?
  • For EFS Version 4.20 and greater, settings are stored at:

    \\HKEY_LOCAL_MACHINE\Software\Chimera\EFS\

    NOTE: For EFS Standard, settings are stored under the key as shown above. EFS takes the name of the folder where EFS is installed. For example, if EFS were installed to:

    C:\Program Files\EFSGateway\

    then EFS would store it's settings under \\HKEY_LOCAL_MACHINE\Software\Chimera\EFSGateway\ The only exception to this is that "E.F.S" is converted to "EFS"


    Tip: Use 'E.F.S Support' (efs3chk.exe) to export registry settings
  • Where can I get a copy of the latest mail control, MMAIL32.OCX?
  • Download the file here and copy the updated files to your System folder (Windows\System folder for 95/98 or Winnt\System32\ for NT) This is only relevant for EFS 5.0 or lower. EFS 5.5 uses separate mail controls for Pop3 and Smtp.
  • What version of EFS am I running?
  • When you run EFS the first entry in the Log displays version information. Alternately click the EFS icon from the Log screen to display the About box. The mail control version(s) are shown on the red background. Please ensure you quote both these versions when emailing for technical help or submitting bug reports.
  • How come my HTML transaction log clears by itself?
  • EFS automatically clears the HTML transaction log after the file reaches 6,000 bytes or larger (approx. 100 entries) for EFS 4.17 and higher. This is because this file could grow to an enormous size, reducing performance each time you viewed it in your browser!
  • EFS (or ERC) can't send mail to my SMTP server, what's wrong?
  • As an example, let's say your SMTP server's name (under SMTP server in the SMTP section of EFS/ERC) is "smtpserver". Here's a list of things to check:

    1. Check the spelling of "smtpserver" (alternatively, try replacing "smtpserver" with the IP address of the server)
    2. Enable the detail window and see if you get a response from "smtpserver"
    3. Open a command prompt and type:

    ping smtpserver

    4. Telnet to the server using the following syntax:

    telnet smtpserver 25

    (don't press any keys, wait a few seconds) and see if you get a response (such as "220 smtpserver.chimera.co.nz ESMTP Server (Microsoft Exchange Internet Mail Service 5.5.2448.0) ready)

    Timeout's when pinging means that the servers name can be resolved but the server is not responding to the request or it's IP address no longer exists. If you receive a response from a ping, then check that the SMTP service running on that server is responding (by telneting - or optionally use the 'Test' button under the SMTP tab of EFS). If you are sending mail via your Internet providers SMTP server and you do not have a direct connection (have a connection via a firewall/proxy server instead) ensure you have permission to send SMTP mail (usually on port 25) through it (ask your Systems Administrator). You can also check whether you have a DNS server setup by running winipcfg from Windows 95 machines or ipconfig /all from the command prompt on Windows NT or higher machines. If the SMTP server is local and you are not using DNS, ensure that WINS is running to resolve the internal server name or, that there is any entry in the local "hosts" file. If you are not using WINS or hosts files, then put the IP address of the SMTP server in the SMTP Server box. If you have a direct connection (via modem or similar) to your ISP, then it's most likely that your DNS settings are missing or pointing to the wrong server. Click here for more information on troubleshooting delivery failures
  • Can EFS work with MS Exchange?
  • Yes, EFS will work with all versions of MS Exchange server and in fact, any POP3/SMTP servers that are RFC1725 and RFC0821 compliant. Note that EFS is NOT mail server specific, ie: it works with the majority of mail servers that support SMTP so you can still use EFS if you intend on upgrading to a different Mail Server in the future.
  • Can EFS accept mail for multiple Domains/Pop3 accounts?
  • Pop3 Accounts - No. Domains - Yes. EFS can only check from a single pop3 account setup as a catch all account. For those with multiple domains, we recommend consolidating all your pop accounts into one and direct all your domain and individual recipient mail to that single catch all account. You can also setup aliases if you wish so that mail is redirected to users at external sites (wildcard aliases are not yet supported) Please realise the whole idea is to have a single Pop3 account that "catchs all" mail sent to it for your domain. You can then utilise the functionality of Exchange (eg: OWA or RPC over HTTPS) to provide users with remote access to their mailboxes
  • Can EFS run as a service under NT?
  • Yes, simply tick the option under the 'Control' tab to enable EFS to run as a service. For instructions, read here
  • Where's the best place to run EFS?
  • There is no real "best place" to run EFS. So long as EFS has access to your ISP's pop3 server and access to your local mail server, then it can really run anywhere. We recommend running EFS either on your proxy server (if any) or on the actual mail server
  • What's the best way of testing my connection(s)?
  • There are many networking tools available to assist you in checking your connections. Probably the most useful (and common) is the "ping" command. This command tests if you can "see" a machine. Go to a "DOS prompt" and type C:\>ping destination where destination is the machine you want to test. First, you should test whether TCP/IP is setup on your local machine by pinging the loopback interface. To do this, type:

    C:\>ping 127.0.0.1

    If you get any form of error, check that TCP/IP is installed and operational (to check IP configuration settings, Start, Run winipcfg on Windows 95/98 machines or run ipconfig from a DOS prompt on NT Machines) If this is operational, test that you can see your mail server. Note: If EFS is on the same machine as the mail server, then by pinging the loopback interface as above and receiving a reply, you have proven that TCP/IP is working, otherwise you will have to ping the remote computer that is running your mail server. For example, if you have setup your SMTP host in EFS to "mailserver", then type:

    C:\>ping mailserver

    Pinging mailserver [192.168.0.100] with 32 bytes of data:

    Reply from 192.168.0.100: bytes=32 time<10ms TTL=128
    Reply from 192.168.0.100: bytes=32 time<10ms TTL=128
    Reply from 192.168.0.100: bytes=32 time<10ms TTL=128
    Reply from 192.168.0.100: bytes=32 time<10ms TTL=128

    You should receive a reply similar to the above. If you get "Bad IP address mailserver" then try pinging the actual IP address instead. If you get a reply, then the name "mailserver" is not being resolved - check your "hosts" file, WINS or DNS settings. If you still receive an error or get "Destination host unreachable" check your Network and/or default gateway settings.
  • What's a good reason NOT to run EFS?
  • Of course there's no good reason! However, if you have a permanent connection to the Internet you could have your ISP setup an MX record to send mail directly to your firewall (which redirects mail to your internal mail server) This generally means you will require a fixed IP address and MX record setup at your ISP - this option usually means extra ongoing monthly costs from your ISP which can be easily saved by running EFS. Several larger companies who use EFS use a static IP address and delivery of email via MX records direct to their site however they utilise a secondary MX record that points to their ISP and use EFS as a backup Pop3 Connector incase their primary connection fails. This is considerably cheaper than needing a secondary fixed IP address and connection into their premises.
    TOP OF PAGE


    (Chimera Computing Ltd)