|
| |
|
FAQ (1)
|
| 1. Why can't I send messages
to external (internet) addresses? |
I. DNS service:
In most cases, failure to send external messages (internet)
is caused by inappropriate settings of DNS. You may
click the icon on the lower right corner of the screen,
select "service" from the pop-up menu, and confirm the
following is correct about the DNS server address:
1. Is the DNS server address set?
2. Is the DNS server address valid?
3. Is the DNS server working properly?
Solutions:
1. In this case changing the DNS
address is always a good idea.(To make the new settings
effective, you should restart the computer after you change
the DNS)
2. Prepare an alternative DNS
address. Thus when the preferred DNS service is down,
WinWebMail will automatically switch to the alternative
DNS server, thus ensuring the smoothness of communication.
3. Generally, do not use an IP
within the LAN (e.g., 10.96.0.1) as a DNS server address.
4. To ensure that the chosen DNS
is properly functioning, you can use ping utility to test
it. If you can ping the DNS address successfully, then
it can be considered that the DNS server is working properly.
Note that the DNS server with the shortest respond time
to a ping request should be given the highest priority,
in that a fast DNS server can significantly increase the
performance of message delivery.
II. Inappropriate security policy or firewall settings
that cause the system unable to perform the UDP-based
communication with external address:
When delivering a message to a external address, the
mail server needs to perform a UDP-based communication
with the DNS server regarding the DNS resolvement of
destination mail server, which require your mail system
to permit UDP packets to pass. Even under certain circumstances
when security concerns require UDP ports to be disabled,
you should still keep all the UDP ports above 1024 open.
III. If your mail domain is not resolved to
the IP address where WinWebMail is installed, or if
HELO info is not correctly set, delivery to some mail
servers may fail:
Solution: Refer to detailed
explanations within this page.
IV. Inappropriate anti-virus software settings:
You need to appropriately set up the anti-virus software
installed on your system so that it can best assist
the work of mail server. At the server side we recommend
installing McAfee VirusScan, and one thing to note is
that we should remove WinWebMail running directory\mail
directory and its subdirectories from the anti-virus
scan range.
[Use McAfee
Antivirus Filter]
[Use McAfee
Antivirus 8.5 or above Filter]
[Use Symantec
Antivirus Filter]
When antivirus software is installed
on the server side. The \mail directory and all its
subdirectories must be excluded to avoid miscount of
mail items and false "mailbox full" alert.
V. Too many junk mails. Too many junk mail messages
might clog the outgoing message delivering process,
thus causing the failure of the external message delivery:
Solution: Please refer to detailed
instructions within this page.
VI. If the IP of your server is blacklisted
by anti-spam organizations, you will not be able to
send outbound emails:
Solution: Submit the IP address of your mail server
at http://rbls.org/
for a query, which may return some sites in red background,
indicating you are blacklisted there. You may go to
these sites to request for removal.
Note: To minimize
mail send failures, you ought to read the error causes
specified in the returned mail and seek solutions. In
a mail like the following, the part in red is the cause
of failure:
Delivery to the following recipient(s)
failed:
user@domain.com : 553
Connection block by DNSBL, [http://www.spamhaus.org/query/bl?ip=xx.xxx.x.xx]
We can learn from the message that your mail is returned
because the sending IP address is blacklisted in www.spamhaus.org,
an anti-spam organization. You may then go to the url
provided, http://www.spamhaus.org/query/bl?ip=xx.xxx.x.xx,
to request for removal from the blacklist.
Enabling these may enhance the success rate of mail
delivery:
 Use
DNS root server for destination address query : Click
the icon at the lower right corner of the screen. From
the popup menu, select "Search from DNS root server"
in "Service" from the pop-up menu.
Use
relay server to forward failed mails. Click the icon
at the lower right corner of the screen. From the popup
menu, select "Use relay server when delivery failed"
in "Configurations | Delivery" from the pop-up menu.
|
| 2. Why can't I receive messages
sent from external mailboxes (e.g. yahoo.com or hotmail.com)? |
To successfully receive messages from the
Internet, you must:
1. Get a valid domain name on the Internet (e.g., mydomain.com).
2. Find a DNS server that can successfully resolve the
sender's domain into the IP address from which the WinWebMail
server is running.
3. Make sure that the service program of WinWebMail successfully
started SMTP service at the port 25 of the server.
Most frequently occurred problems include:
I. port 25 is used by other service program:
If your system has other mail servers, anti-virus software,
or firewall installed, it is very likely that port 25
is taken by another service program, thus the WinWebMail
service program will not be able to process the messages
sent to the port 25. The following command may help you
to check if the port 25 is used by WinWebMail or not:
telnet your server IP address 25
If the results is: 220 ESMTP on
WinWebMail [x.x.x.x] ready. http://www.winwebmail.net.
Then it indicates everything is working OK, otherwise
you might have to uninstall the program that are currently
occupying port 25 and then restart the service program
of WinWebMail.
The greatest possibility is: Microsoft STMP service in
IIS is not completely uninstalled on the server, causing
a conflict in port 25, which results in anomalies in WinWebMail.
Solution: Uninstall or disable Microsoft SMTP service,
then reboot WinWebMail service.
(Click)
II. Domain name resolution problem:
Please do the following test to check if your domain name
resolution encountered problem. Assuming your email address
is user@mail.domain.com, we need to confirm the MX record
or A record of mail.domain.com is directed to the correct
address, you can check it at the following link:
http://centralops.net/co/NsLookup.vbs.asp
1. You can find the MX record address in the return
information, something similar to the following content
highlighted in red:
| yahoo.com |
IN |
MX |
| preference: |
1 |
| exchange: |
mx1.mail.yahoo.com |
|
6090s |
(1h 41m 30s) |
|
2. If your domain name has not made any MX record, you
may try retrieve the A record address by pinging mail.domain.com,
or you may extract the A record address info from the
following return information:
| yahoo.com |
IN |
A |
66.218.71.198 |
690s |
(11m 30s) |
|
By verifying if the MX or A record (use MX record when
both are available) of your domain is the IP address from
which your WinWebMail is running, we can decide whether
the domain resolution encountered some problems or not.
III. Port 25 block by firewall, or other inappropriate
settings.
Note: Careful reading of the error cause specified
in the returned mail may help solving your problem. |
| 3. I'm having the "wrong username
or password" error every time I try to log in, why is
that and how can I fix it? |
Seven most possible causes:
1. Permissions:
For
example, the WinWebMail Server installation directory
is D:\WinWebMail.
After permissions
are set, reboot IIS for them to take effect. |
| D:\WinWebMail (and subdirectories) |
Users or Everyone |
Full Control |
| D:\ (root) |
Users |
Read |
2. Inappropriate "Application Protection" setting for
IIS website or virtual directory.
For example, in this figure, you should choose "Low (IIS
Process)" to ensure you can successfully logon to your
system through browser.
3. Older version not properly uninstalled. Please follow
the correct steps of uninstallation
and upgrading.
4. If you're installing an upgrade version, you may need
to reboot the computer after a full installation. Failure
to conform to this requirement might cause problems.
5. Inappropriate settings of firewall software.
6. Inappropriate settings of anti-virus software. Please
uninstall (not just stop) the anti-virus software and
restart the server, and then reinstall the anti-virus
software and set it up appropriately. (It is recommended
to disable all monitoring capabilities of anti-virus software,
including: mail monitoring, file monitoring, memory monitoring
etc)
7. If easymail.exe or emsvr.exe is infected with viruses,
WinWebMail may malfunction. |
| 4. How to handle junk messages? |
For mail servers, junk messages fall in
two categories:
1. Outgoing junk messages sent out to external
addresses using mail server.
2. Ingoing junk messages sent within the system.
I. Outgoing junk messages:
1. Outgoing junk messages are
usually caused by spammers who utilize the mail server
as a relay server to send out large volume of junk messages.
These messages will consume huge amount of system resources
(including: CPU, memory and bandwidth etc). The typical
characteristic of outgoing junk messages is a large volume
of (thousands of, ten thousands of, or even hundred thousands
of) outgoing messages (including .mhd, .in, .tmp files
etc )will be created in \WinWebMail\Mail directory. Note
that the DNS service shutdown or failure to establish
connection will both result in a long pending messages
queue.
2. First you need to clear
all the Purge Pending Mails. To do that, click the
server icon at the lower right corner of the screen, select
"Tools | Purge Pending Mails" from the popup menu. Then
a function interface displaying the current number of
pending messages will show up. (This process may take
a while if the number of pending messages is too large).Click
"start" button to begin the clearing process.
3. Block outgoing junk messages:
Click the icon at the lower right corner of the screen.
From the popup menu, select "Enable SMTP Authentication"
in "Configurations | Delivery", which is perhaps the most
effective anti-spamming measure.
Click the icon at the lower right corner of the screen.
From the popup menu, select "External Message Delivery
allowed for internal users only" in "Configurations |
Delivery".
Click the icon at the lower right corner of the screen.
From the popup menu, select "Enable outgoing messages
constraints" in "Configurations | Safety".
Enable and configure anti-virus options to prevent this
from happening.
If too many mails are returned, outgoing traffic may be
jammed. Anti-spam organization may also blacklist the
IP for suspicion of junk mail sending. Therefore it is
recommended to disable the options "Enable notification
when delivered to non-existent account" and "Notify sender
when virus detected".
II. Ingoing junk messages:
1. Ingoing junk messages are caused
by spammers who utilize your mail server as a relay server
to delivery large volume of junk messages within the system.
The typical Characteristic of ingoing junk messages is
that the mailbox within the system will receive numerous
junk messages.
2. Block ingoing junk messages:
Enable SMTP domain name verification. Recommended for
a great improvement of anti-spam efficiency. Click on
the icon at the lower right hand corner of the server,
then select on the popup menu "Configurations | Safety
| Enable SMTP domain name verification".
Click on the icon at the lower right hand corner of the
server, then select on the popup menu "Configurations
| Delivery" , select "Enable SMTP authentication " and
"Enable receiving auth".
The user should choose the anti-spam policy that best
suits his needs. The anti-spam policy includes: Spam Protection,
Mail Filtering, Sender Blocking and Safe List. The administrator
should coordinate the use of "Non-junk-mail confirmation".
To start this capability, click the icon of the lower
right corner of the screen, from the popup menu, select
"Configurations | Safety".
Click the icon at the lower right corner of the screen.
From the popup menu, select "Message content filtering"
or "keyword filtering" in "Configurations | Safety" according
to your needs. You may block some junk messages by selecting
"Reject connection from specified IP/server".
III. The methods that work with both outgoing and ingoing
junk messages:
1. Since spammers would carbon
copy or blind copy the junk messages to numerous addresses,
so you may restrict the maximum number of recipients.
To do that, Click the icon at the lower right corner of
the screen. From the popup menu, select " Configurations
| Delivery", and set the "maximum number of recipients"
. Usually the maximum number should be no more than 10.
2. Start connection protection
capability. Spammers need to keep connecting the server
in order to delivery the junk messages. So you may prevent
some junk messages from being sent out by using this protection
capability. To do that, click the icon at the lower right
corner of the screen. From the popup menu, select "Start
connection protection" in "Configurations | Safety". Then
you can set up "Start Auto-Protection capability". |
| 5. Setting HELO/EHLO host name. |
Click on the icon at the lower right hand
corner of the server, then select on the popup menu "Configurations
| Delivery", where you may configure HELO/EHLO host name.
Settings:
1. If your domain (e.g.: domain.com)
has MX record (e.g. with an MX record of mail.domain.com),
you may set the HELO/EHLO as the MX record (mail.domain.com).
2. If your domain (e.g.: domain.com)
does not have an MX record, you may set the HELO/EHLO
as the domain name (domain.com).
Note: For multiple official domain names, simply
choose one as the HELO/EHLO host name. |
| 6. I have encountered many
"Overtime, please try again" errors at web login. How
to avoid this? |
I. Incorrect settings of firewall:
The problem may happen when local UDP communication is
disabled or WinWebMail and/or Microsoft component palette
communications are blocked.
II. The problem may also occur if "Multiprotocol"
in the "SQL Server | SQL Server Network Utility" was disabled
while installing SQL Server.
III. Inappropriate settings in IIS 6.0 of Windows
2003:
When creating multiple virtual WinWebMail directories
or websites in IIS 6.0, the same pool should be used
for application programs. Otherwise, these problems
may be incurred.
It is recommended to allocate a separated application
palette for WebMail (property set to non-reclaimable).
If the palette is shared with the website, when error
occurs at the site, the system will reclaim the palette,
resulting "Overtime, please try again" error.
Please uncheck the "Recycle worker processes" and "Shutdown
worker processes after being idle for (time in minutes)"
in the "DefaultAppPool Properties" of WebMail,
then reboot IIS to solve the problem.(see the following
figure)
IV. When creating multiple virtual WinWebMail directories
or websites in IIS 5.0, the Application Protection of
the directories or websites should be set to Low (IIS
process) as shown in the figure below. Then restart IIS.
|
| 7. Does WinWebMail support
same user account in different domains? Why does it always
fail when creating accounts of the same name in different
domains? The system reports that the user already exists? |
WinWebMail does support same user name
in different domains.
You should learn more about how multiple domains and multi-users
are used. Detailed information can be found in the "How
to make account name exist in multiple domains" section
in the help file (easymail.chm in the installation directory).
In addition, if you wish to register an account with a
domain name through webmail, you should login to the WebMail
interface as the system administrator, select "Public
registered accounts contain domain name" in " Other Settings
| Web Usage Settings". Now you can apply for accounts
with domain name through WebMail. |
| 8. Why can't I upload an attachment
larger than 200k in Windows 2003 IIS 6.0 and download
larger than 4M attachment? Is there any solution? |
|
The default settings of IIS 6.0 are prudent and secure.
It has a restriction of maximum 204,800 bytes on upload
data (not found in earlier versions), in an effort to
minimize the attack surface of the system, which used
to be a huge vulnerability due to long timeout permission
and other loosely restricted configurations.
Solution:
1. Stop the IIS admin service.
2. Navigate to windows\system32\inesrv\, find a file
named metabase.xml.
3. Open the file, and find a key named "ASPMaxRequestEntityAllowed",
and set the value of this key to your desired value
(e.g., 10240000). The default value is 204800, i.e.,
200K.
4. Save the file, and restart IIS admin service.
Download larger than 4M attachment:
1. Stop the IIS admin service.
2. Navigate to windows\system32\inesrv\, find a file
named metabase.xml.
3. Open the file, and find a key named "AspBufferingLimit",
and set the value of this key to your desired value
(e.g., 20480000).
4. Save the file, and restart IIS admin service.
|
| 9. Solution to the HTTP 500
error (or ASP:0177 800401f3) after installation of WinWebMail. |
|
The most common cause is failure of registrating easymail.dll
component by the WinWebMail installation program, which
can be solved by typing:
regsvr32 C:\WinNT\System32\easymail.dll
To manually registrate the component and then rebooting
the server.
If the error persists after the above procedure, it
is probably because the iusr_computer name (Internet
guest account) is not allowed access to easymail.dll.
A simple solution is to stop IIS, move C:\WinNT\System32\easymail.dll
to the installation directory of WinWebMail, and then
type:
regsvr32 C:\WinWebMail\easymail.dll
Restart IIS.
If the problem is still not solved, you may need to
check and make sure the appropriate access rights are
properly set. Refer to the following documents:
IIS 5 - How
to set required NTFS permissions and user rights for
an IIS 5.0 Web server
IIS 6 - Default
permissions and user rights for IIS 6.0
The problem should not exist if you have performed the
above procedures exactly as stated, unless you have
missed some steps. You may try adding iusr_computer
name (Internet guest account) to the local administrators
group, but only temporarily
and for the purpose of error detection. You should never
leave the Internet guest account in the administrators
group after the problem is solved!
If the problem is solved after adding the account and
restarting IIS (or server), it is certain that improper
access right settings is the cause. Please recheck the
access right settings through the above procedures.
If the problem is not solved, please remove the Internet
guest account from the administrators group and consult
specialized technical personnel.
|
| 10. What am I supposed to do
if I've forgotten the administrator password? |
|
You may start the easymail.exe program on the server
to directly change the admin password. If the access
to easymail.exe requires password, you may use windows
notepad (must edit with plain text format) to open a
file named SysInfo.ini using Notepad program under the
installation directory, and find this line:
useLogonPass = 1
Set the key value to 0 and save it. Now you can execute
easymail.exe without password.
|
|
|
|
Download
