Frequently Asked Questions
- Why does eWall only filter SMTP traffic and not POP3?
- All emails go through an SMTP server, even those sent by local users. POP3 is a CLIENT based protocol used to manage/download emails from a mail server.
eWall is designed to prevent the actual ingress of spam INTO your mail server, before it is even distributed to a POP3 client. This way the majority of spam
is stopped at the server itself, lessening the workload of the server, as well as eliminating spam before the email clients download theirs messages.
In most cases this will also eliminate the need for any spam control products on your workstations, saving you even more money.
- How can PHP be useful for mail filtering?
- We started initially with a very simple product: MailFilter — a plug-in for a single mail server ArGoSoft Mail Server.
MailFilter had a very limited set of pre-defined conditions and actions. We soon realized that it was not flexible enough, and we soon added the
- How does eWall save mail server resources?
Being installed on the same computer as the mail server itself doesn't save CPU or RAM resources. We highly recommend that you install eWall on a separate
computer. At that point you will then see the load on the mail server's SMTP service drop by up to 90%, and it will have more time available for serving local users,
getting/managing their POP3 or IMAP mail, or web services, instead of dealing with the inbound flood of SMTP SPAM, which is now handled by eWall.
- What is the difference between Free and Unlimited editions?
- The Free edition is limited to 5 mailboxes and intended for small companies.
The Free edition monitors the number of recipients, and if this value exceeds the limit eWall will go into transparent mode: the emails will still
be passed but will no longer be filtered for spam by eWall.
- Can the Free edition be used in commercial environment?
- Yes. But please keep in mind, it only supports 5 mailboxes.
- What ports should be opened to use eWall?
- eWall uses the following ports: 25 by SMTP service, 5432 by PostgreSQL and 8888 by Control Panel. So if you
want to connect to the eWall service remotely using the Control Panel, port 8888 must be opened in firewall.
- *PLEASE NOTE* This does not include the port used for your internal connection from eWall to your SMTP server which you define when you create
the allowed server entries. Also, port 8888 should be considered 'well known', and it is recomended you do not open this port directly through your firewall.
We recommend selecting a random port on your firewall and using NAT to port-forward that to port 8888 on eWall. This is more secure.
- What PHP version used in eWall?
- Currently, 188.8.131.52 is used.
- Does eWall connects to your servers and what information is exchanged?
- Yes, eWall connects hourly to our server and checks for the latest version. During this session, it also sends
its own Serial Number, OS name, amount of RAM installed, CPU speed and own performance counters, such as memory and CPU consumption, the number of
processed sessions and emails. The aggregate of those performance stats help us understand how stable and effective the release is.
The data is sent Base64-encoded.
- Where does eWall keep the data (settings, logs, stats etc.)?
The eWall keeps all changeable data under %CommonAppData%\Server Side Solutions\eWall 4.0 path. To easily access that folder type
shell:common appdata in Windows Explorer and then navigate to the Server Side Solutions\eWall 4.0 subfolder.
The configs for Control Panel are stored under %LocalAppData%\Server Side Solutions\eWall 4.0.
You may want to change the default storage paths, for example, if partition doesn't have enough room, you want to move it at more fast drive or don't
want to clog the system partition. The default storage paths can be changed at Control Panel -> Proxy -> Options -> Paths tab.
- How to reset Control Panel password?
To reset Control Panel password open %CommonAppData%\Server Side Solutions\eWall 4.0\ew_config.xml in any text editor,
locate the <login> node under <gui> node, remove key parameter, and save the file. Re-start eWall service.
The username and password will be set to default values: admin:pass.