Anyone?

I am curious as to popular opinion. Is Version 4 of MailEnable Enterprise ready for production or should one wait a few more months?

The number and type of issues reported here seem a little scary.

Hi Ian - Sorry to be hard-headed with this, but I still don't understand. Isn't MailEnable simply extracting the domain name information from URL's embedded within an email and checking them against all configured/enabled blacklist(s), or is something else going on? Looking at the Spamhaus website, ...

Hi Ian - Sorry to be hard-headed with this, but I still don't understand. Isn't MailEnable simply extracting the domain name information from URL's embedded within an email and checking them against all configured/enabled blacklist(s), or is something else going on? Looking at the Spamhaus website, ...

Hi Ian -

Could you please explain, why would only spamhuasSBL-XBL work for URL blacklisting?

What version are you using?

I was running some network sniffer software and caught that MailEnable version 2.32 seems to be making double queries for DNS Blacklisting. The first query seems "correct" for example: 10.232.178.68.sbl.spamhaus.org However, immedately aftwards is a second query that appends our internal DNS name (i...

Looking at the version history on the download page for Professional 2 and Enterprise they both reference 2.1.2 18 Aug, 2006.

Is this something coming in 10 days?

I agree.

It would also be nicie if the ability to drop a connection immedately would also apply if you require the sender to have a a reverse DNS pointer (i.e. PTR). For some reason the "drop immedately" logic does not apply to this situation.

Please consider adding the name of the blacklist causing a reject to the messages found in the Activity log. I find the Activity log 'the best' for general troubleshooting and monitoring and it would be helpful if the blacklist name appeared in these messages. I realize you can look debug log, but t...

I found in this forum the registry setting to allow a connection to drop if it is found in a DNS Blacklist. My suggestion is to please enable this function through the user interface. I have found than most any change I make in the user interface, in SMTP connector, causes the registry setting to re...

Here are a few sample IP addresses that do not have reverse DNS and yet were allowed in by MailEnable. These came in today.

218.146.14.135
201.214.247.233
60.16.71.92
61.77.151.197

Still a problem in 2.09.2 .

This issue sure lets lots of SPAM in.

I even opened a problem ticket up and used one of my tokens to report a problem.

Still a problem in 2.08.

This issue sure lets lots of SPAM in.

Seems to be fixed in 2.08.