Hi,

The numbers are timestamps for when the file was created in Unix epoch time. The file contents are formatted as timestamp[tab]CLIENT.

Hi, Do all your clients route through a common IP address to connect your MailEnable server ( a proxy/spam gateway)? If so then you will need to disable the option for "Abuse detection and prevention" under the localhost > policies properties as this will be the problem. Most likely one of your clie...

Hi,

Try the solution in this article: http://www.mailenable.com/kb/content/article.asp?ID=ME020618

Hi, There is no way to stop the attacks hitting the server. You can enable the "Abuse detection and prevention" option so that the inbound connections are banned after a total of 10 invalid authentication attempts (http://www.mailenable.com/documentation/10.0/Professional/Localhost_-_Policies.html)....

Hi, You first need to determine if the inbound message is hitting the SMTP service when you send to the list address. Open the SMTP activity log file for the date/time your sending to the list and search the log file for the inbound message to the list address. Use the "Track Message" utility locate...

Hi, There can be many reasons why a remote mail server can delay your messages. Normally the bounce messages returned to the sender contain the reason for the delay (which it does state the reason in your bounce message). As to why they delayed the message we don't know. You would need to contact th...

Hi,

Which list command are you referring to?

Hi, You need to start by inspecting the SMTP activity and debug log files in respect to the messages your sending. They will contain information or errors relating to the outbound messages your sending. Here is an article to help troubleshoot outgoing sending problems: https://www.mailenable.com/kb/...

Hi,

There are no current exploits that we are aware of .

Hi,

Most likely an index file corruption. There has been many fixes and updates to MailEnable core services since 10.25 and it would ideal upgrading first to see if this fixes your problems.

Hi, You should be able to send outbound. Although without using a fully qualified domain you may have problems sending to remote mails servers as they will perform look ups on your domain to see if its from a valid domain. The first step is to inspect the SMTP log files to see what is happening when...

Hi, Use nslookup within a Windows command prompt and see you can resolve the domain your trying to send to. If it cant resolve then you have issues with your DNS server that is set on your NIC. Try and set the DNS server addresses within MailEnables SMTP service to Google DNS 8.8.8.8 to see if it fi...

Hi

Not aware of nay issues with the clam service. If you can lodge a support ticket under "upgrade" and provide access to the server then we can check further.

Hi, If client machines are infected with viruses (in particular key loggers) then the first step is to clean the client machines and ensure they run security software to prevent this. Although these scenarios are rare the most common cause of a spammer exploiting the mail server is by guessing simpl...

Hi,

Ensure the username is mailbox@postoffice name and not mailbox@domain name.