RE: GFI MailEssentials & Feature Requests (Full Version)

All Forums >> [Content Security] >> GFI MailEssentials for Exchange/SMTP



Message


Frelisb -> RE: GFI MailEssentials & Feature Requests (5.May2008 6:24:36 AM)

quote:

ORIGINAL: eschefer

We have the same problem than Frelisb here, half of our users have french outlook and the other half has english outlook.

I have been told by GFI Support in November 2006 that my request has been added to the Features Request List. It's becoming really urgent now. I think that a patch to ME 12 could be easily made to give the possibility to have multiple strings to be searched to determine if the mail is an OOO reply.


The earliest post I found on this, is from 2004. Even then GFI said they would add it to the Feature request List.

Apparently GFI does not find this issue urgent, at all, as it should be very easy to fix.

I agree with Eschefer, that this is so urgent that an intermediate patch is needed, even waiting for a new version will take too long.

This must be considered an urgent bug, not a feature request. After all, our anti-spam system automatically whitelists spammers!




joestern -> RE: GFI MailEssentials & Feature Requests (5.May2008 10:49:34 AM)

David et. al.,

I'd like to see DomainKeys in a future build of MailEssentials.

Thanks,

Joe




JLefebvre -> RE: GFI MailEssentials & Feature Requests (6.May2008 11:28:32 AM)

quote:

ORIGINAL: Frelisb

quote:

ORIGINAL: eschefer

We have the same problem than Frelisb here, half of our users have french outlook and the other half has english outlook.

I have been told by GFI Support in November 2006 that my request has been added to the Features Request List. It's becoming really urgent now. I think that a patch to ME 12 could be easily made to give the possibility to have multiple strings to be searched to determine if the mail is an OOO reply.


The earliest post I found on this, is from 2004. Even then GFI said they would add it to the Feature request List.

Apparently GFI does not find this issue urgent, at all, as it should be very easy to fix.

I agree with Eschefer, that this is so urgent that an intermediate patch is needed, even waiting for a new version will take too long.

This must be considered an urgent bug, not a feature request. After all, our anti-spam system automatically whitelists spammers!



I agree with both of you, this feature is long overdue and should be implemented on an urgent basis.








tonyhowarth -> RE: GFI MailEssentials & Feature Requests (7.May2008 10:11:33 AM)

Allow multiple filters to be combined.

At present if a filter fires it ignores all other filters, effectively whitelisting the email.  This is a problem if a trigger is higher in the list and contains inappropriate material.  All that happens is it gets marked as say 'blacklisted' and is then delivered quite happily, with all the porn and profanities in clear view.

Tony




rczyzewski -> RE: GFI MailEssentials & Feature Requests (7.May2008 2:32:22 PM)

Some great ideas in here.  It is nice to see feedback being looked at.  Everytime we get a new wave of spam I feel like I have to justify why we use MailEssentials.
A few of my recommendations (most have already been posted but a 2nd, 3rd or 10th voice never hurt):
1. Put all the registry edit work arounds into the GUI (attachment spam, remote image size).  This would make it easier for our dept to see what settings are and help me not forget to re-change them after product updates.
2. List the whitelist/blacklist alphabetically and allow aging options in the whitelist.  We'd probably leave addresses/domains indefinitely, but this could be great for others
3. Allow custom or removal of BlockedReasons in the Subject line.  It is great for me to see them in the logs, but my users have having usability issues.
4. The reporting features are getting more useful (or I'm just using it more than before).
5. Two-tier body keyword filters would be nice.  I'd like to block "viagra" spam but just move "medicated" to a junk mail folder
6. Allow roll over/archiving of logs (by date or size).
7. Allow separate Action options in the Header Checking module components
8. Improved cluster stability (sometimes we have issues during upgrades)

Looking forward to the next version!  Any release date estimates?




davidbuj -> RE: GFI MailEssentials & Feature Requests (7.May2008 6:27:02 PM)

Here are a couple things I would like to see.  The honeypot concept may help with this.

Logging of an emails source IP addresses.

IP subnet blocking based on historical logging of spam's source IP address.
Blocking of a specific country's IP ranges.
   Work with Firewall suppliers to develop a way to communicate this to various firewalls.

A tool to dig into the Bayesian Analysis.




overloadnn -> NEW FEATURE REQUEST (8.May2008 7:38:12 AM)

How about applying some rule when multiple spam modules discover that an incoming email is spam? For example "if keyword checking AND SPF return POSITIVE then delete message".

This is similar to MailSecurity when detects a virus when more that X antivirus modules return POSITIVE.

Thanks!




azivo -> RE: NEW FEATURE REQUEST (8.May2008 11:49:52 AM)

Is there any news on http://forums.gfi.com/fb.aspx?m=900745062?




qwerty1 -> RE: GFI MailEssentials & Feature Requests (8.May2008 12:48:49 PM)

I would like a searchable master log of all emails, some details about the message, and the status of the message. It is very difficult to troubleshoot. For example, if a user asks me why an email was not received, I have look at several different log files, get info from the user and sender (such as the subject) and then start searching. It takes too long. Take a look at a barracuda, it has a great master list. You can easily apply different filters and find the messages you are looking for. It even has a nice status column so you know why it was not received.

To me, this is an essential tool. I am working around it now, but everytime I need to find something, I can only wonder why there is not a feature like this. I need information about what is going on, I can't search 8 log files everytime I need to find the reason an email was blocked.

Please note: I am a developer and could write a program to combine logs into a searchable database. I just don't have the time. Please add this. Everytime we can't find an email we seriously consider another solution. We have it installed at 4 sites and the time saved by not performing "word match" searches on log files is well worth the additional cost of other solutions compared to yours.

Please add this. PLEASE.




AJStevens -> RE: GFI MailEssentials & Feature Requests (14.May2008 12:27:20 PM)

Hello,

I'd like to be able to input the following types of email address in the whitelist, specifically for MIME To:/SMTP To: however it could just as well apply to From's as well.

recipient*@*
recipient*@*.co.uk
recipient.*@*
recipient.*@*.co.uk

Unfortunately, it will not let me currently, there's plenty of options for the domain (part after "@"), but not for the recipient (par before the "@").

The reason I need it, is we have several "service" email addresses, and it's vital no email is blocked (these are emails of faults) and aren't simply sales@ so it's unlikely for them to get spammed (if they do, then the MD will have me change it, but for now it must be allow all).

The problem is we have multiple domains, so I REALLY do NOT want to have to enter every service email address with every possible domain at the end.

Please can you update GFI ME 12 to allow the above whitelist email masks (probably a good idea to add it to the custom blacklist and anywhere else you can enter email masks too).




sergeda -> RE: GFI MailEssentials & Feature Requests (15.May2008 4:26:07 AM)

It would be great to be able to add a bunch of emails to whitelist using metod like: ap*@mydomain.com 




pbparker -> RE: GFI MailEssentials & Feature Requests (19.May2008 10:53:12 AM)

Don't know if anyone is reading/considering all these suggestions we're adding - but one I need desperately is some useful status results from the GFI Monitor.  Right now I'm trying to diagnose spam getting through, I'd like to be able to see via the monitor if each of these emails was caught by a anti-spam module or whether they were passed through.




mbiesheuvel -> RE: GFI MailEssentials & Feature Requests (20.May2008 5:49:56 AM)

quote:

I would like a searchable master log of all emails, some details about the message, and the status of the message. It is very difficult to troubleshoot. For example, if a user asks me why an email was not received, I have look at several different log files, get info from the user and sender (such as the subject) and then start searching. It takes too long. Take a look at a barracuda, it has a great master list. You can easily apply different filters and find the messages you are looking for. It even has a nice status column so you know why it was not received.

To me, this is an essential tool. I am working around it now, but everytime I need to find something, I can only wonder why there is not a feature like this. I need information about what is going on, I can't search 8 log files everytime I need to find the reason an email was blocked.

Please note: I am a developer and could write a program to combine logs into a searchable database. I just don't have the time. Please add this. Everytime we can't find an email we seriously consider another solution. We have it installed at 4 sites and the time saved by not performing "word match" searches on log files is well worth the additional cost of other solutions compared to yours.

Please add this. PLEASE.
ORIGINAL: qwerty1


quote:

Don't know if anyone is reading/considering all these suggestions we're adding - but one I need desperately is some useful status results from the GFI Monitor.  Right now I'm trying to diagnose spam getting through, I'd like to be able to see via the monitor if each of these emails was caught by a anti-spam module or whether they were passed through.


Very nice features which i want to have added.

Also i have another one. We are using alot of Public Folders which have attached emailadresses. Our policy in our company is that we move the spam to the users Inbox => spammodule. As you can guess a Public Folder doesn't have a user account which the spam can be send too. So the email detected as spam are deleted. Please add a feature so ME can check by Active Directory if the emailadres is a user or public folder. If you can implent this it's easy to add a feature where you can tell what to do with public folder spam. For example move it to another public folder or let it create a gfi antispam folders below the public folder.




logicalnet -> RE: GFI MailEssentials & Feature Requests (21.May2008 12:49:36 PM)

We are also considering dumping GFI because of the missing emails that get logged in IIS SMTP logs and GFI Monitor, but go into a black hole, without any other modules or logs explaining where they went.  Also the Barracuda type ability for users to get quarantined type messages for spam (not AV) and have the ability to approve /delete messages themselves via a http type interface would BE HUGE!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!




kvetsch -> RE: GFI MailEssentials & Feature Requests (23.May2008 12:42:43 PM)

I would like to see some sort of condition filtering. We have a general email address that is listed on the website. This address, of course, gets a large amount of spam, but also large amounts of legitimate customer requests. What I would like to do, but it would require this filter, is setup a condition where noreply@* is blocked to the email address general@corp.com. But I wouldn't want noreply@* blocked to all email addresses.

This would help if you analyze some of the spam and find certain trends, like I have of noreply@* being nothing but spam to one address.

It could be useful with a bunch of and/or/if conditions that accept email addresses and actions. Such as:

if noreply@* to general@corp.com delete

if spam@spammer.com to general@corp.com and someother@corp.com forward to garbage@corp.com

That kind of thing could be handy.




Page: <<   < prev  1 2 [3] 4 5   next >   >>