SPAM problem (Full Version)

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



Message

dak11 -> SPAM problem (30.Apr.2008 9:18:39 AM)

I took a day off yesterday and I returned to a problem that I'm unsure how to address. We currently redirect all SPAM to the Junk Mail folder in Outlook and each user periodically goes in and deletes them while checking for client E-mails. This procedure has worked out pretty well, at least for me since I don't receive much from clients, but starting yesterday some users have told me that they've started to receive these SPAM e-mails in their Inbox instead of Junk Mail.

The thing that's throwing me is that it's not the entire office that's receiving them in the Inbox but only a select few (about 1/2).

If anyone has any ideas or guidance to dealing with this problem I'd appreciate it.

Thanks



John Letourneau -> RE: SPAM problem (30.Apr.2008 9:29:48 AM)

dak11,

There are many reasons that this can happen.  The first thing I would recommend doing is going over our "SPAM emails are not blocked - Checklist" knowledge base article.  This article can be found at http://kbase.gfi.com/showarticle.asp?id=KBID003256. 

When GFI MailEssentials is configured to deliver messages to the Junk E-mail folder we rely completely on Exchange routing the message.  All that happens is GFI MailEssentials tags the message with a SCL value of 9 and relies on Exchange IMF to move the message to the Junk E-mail folder.  There are times where Junk E-mail filtering is disabled in OWA and this can cause the message to end up in the Inbox.  Can you log into OWA for one of the users and click on "Options" and verify that under "Privacy and Junk E-mail Prevention" that "Filter Junk E-mail" is checked.

This may not resolve the problem but will be a good place to start.



dak11 -> RE: SPAM problem (30.Apr.2008 10:18:02 AM)

John,

I checked the users and the one's I looked at had the Junk Mail setting already checked, so I went about reinstalling MailEssentials and everything seems to be working correctly for the time being.

If things change I'll start looking deeper into the link you provided.

Thanks



John Letourneau -> RE: SPAM problem (30.Apr.2008 10:54:41 AM)

dak11,

Sounds good, let us know if we can help you further.



dak11 -> RE: SPAM problem (9.May2008 9:46:34 AM)

John,

Our newest issue.

Since I re-installed MailEssentials I have some users who are saying that e-mail addresses which were coming inot their Inbox are now going into Junk Mail. Seems like there's an issue with the software using the white list.

Is there a way for me to export the white list entries, clear them out, and then import them back in to see if I can get it back to the way it was prior to the initial issue? MailEssentials is telling me that 5500 entries are in the white list so I'm looking for ideas/reasons the list no longer seems to be working.

Any ideas or suggestins would be appreciated.

Thanks



John Letourneau -> RE: SPAM problem (9.May2008 10:23:23 AM)

dak11,

The autowhitelist is stored in an Access database and can be found at ..\Program Files\GFI\MailEssentials\autowhitelist.mdb.  If you are familiar with Microsoft Access and feel comfortable editing this database you can copy the autowhitelist.mdb from the installation directory and edit this copied file.  After you are done you would need to stop all GFI MailEssentials services as well as IIS Admin and shut down any GFI MailEssentials windows you have open to place the edited file back into the installation path.



dak11 -> RE: SPAM problem (9.May2008 10:29:05 AM)

If I just remove that autowhitelist.mdb from that location does the mail essentials software automatically recreate it?

Since the list doesn't seem to be working I was looking to start with a fresh database and repopulate it by importing the old information back into it.



John Letourneau -> RE: SPAM problem (12.May2008 9:09:06 AM)

dak11,

If you remove the autowhitelist.mdb GFI MailEssentials will not automatically create it.  I'd suggest opening that file in access and removing the entries.  This will get you back to a clean autowhitelist.mdb.



Page: [1]