Whitelist being ignored
|
Logged in as: Guest
|
|
Users viewing this topic:
none
|
|
Login | |
|
Whitelist being ignored - 15.Sep.2009 8:54:23 AM
|
|
|
grimal
Posts: 5
Joined: 11.Dec.2007
Status: offline
|
I am using version 14.1 (20090826). Some entries from my whitelist are being ignored and tagged as SPAM. My filter priority is: Directory Harvesting IP Whitlist Keyword Whitelist Email\Domain\Auto Whitlist SPF Phishing SpamRazer Blacklist DNS Blacklists DPM URI Bayesian Header Checking Keyword Checking My autowhitelist.mdb is 4676 kb. I've tried rebooting the server and restarting IIS.
|
|
|
|
RE: Whitelist being ignored - 15.Sep.2009 10:30:36 AM
|
|
|
grimal
Posts: 5
Joined: 11.Dec.2007
Status: offline
|
Actually, I have an additional problem. GFI is tagging email as SPAM, but the mail is still arriving in users' Inbox.
|
|
|
|
RE: Whitelist being ignored - 16.Sep.2009 4:04:17 AM
|
|
|
benvincenti
Posts: 163
Joined: 30.Apr.2008
Status: offline
|
grimal, Which module is blocking the spam? What actions have you configured on this module? Regards, Ben Vincenti GFI Software - www.gfi.com Web & Mail Security, Archiving & Fax, Networking & Security Tel: +44 (0) 1784 448 838
|
|
|
|
RE: Whitelist being ignored - 17.Sep.2009 4:06:11 AM
|
|
|
sunny
Posts: 1
Joined: 10.Nov.2008
Status: offline
|
Hi guys, My customer is also having such issue. Currently using ME version 14.1 (20090826). External sender needs to conduct a survey to XXX company staffs. Therefore, sender sends to all sender within the company. First, it was blocked by SpamRazer. Then putting the sender's domain into Domain Whitelist and scanned by Bayesian. Blocked email then put into pickup folder then arrive at all user's mailbox. Secondly, another different sender (from same domain whitelisted) send another survey to HR department. It was blocked by Bayesian this time. Blocked email then put into pickup folder then arrive at all user's mailbox. Ip Whitelist and Email\Domain\Auto Whitelist is at the top.Why it doesn't work? Please help...
|
|
|
|
RE: Whitelist being ignored - 17.Sep.2009 10:00:00 PM
|
|
|
ict
Posts: 25
Joined: 18.Jan.2009
Status: offline
|
Similar problem here, Whitelist is 2 and header checking is 12 prioity header checking action is forward to emailaddress I have both the sender and receiver whitelisted, but header checking keeps catching it. It ends up in Qtine in Mailsecurity, I release it and Mailessentials gets it again, header checking and it keeps looping back and forward. Why is my whitelist being ignored, since 14.1 Regards
|
|
|
|
RE: Whitelist being ignored - 18.Sep.2009 8:56:40 AM
|
|
|
PhilH
Posts: 41
Joined: 19.Jun.2004
From: Dearborn, MI
Status: offline
|
Is the MIME TO: blank by any chance? The whitelist is ignored in 14.1 if the MIME TO: is blank - confirmed bug in 14.1 by GFI. See http://forums.gfi.com/fb.aspx?m=900780318
|
|
|
|
RE: Whitelist being ignored - 23.Sep.2009 2:27:41 AM
|
|
|
AndrewZT
Posts: 103
Joined: 28.Jul.2004
Status: offline
|
Hi all, There is a patch you can try to resolve this issue: http://ftp.gfisoftware.com/patches/me14/20090826/ME141_PATCH_20090917_01.zip This patch should be applied to installations of the following builds of GFI MailEssentials 14.1 and above: -> 20090826 Issues fixed: 1. This patch fixes an issue whereby the Whitelist entries are ignored and antispam filtering is still performed. 2. The MailEssentials Scan Engine crashes whilst processing the Whitelist entries. I encourage anyone who experiences the issues noted above to install this patch.
_____________________________
Andrew Zammit Tabona GFI Software Blog: www.gfi.com/blog - Twitter: www.twitter.com/gfisoftware - YouTube: www.youtube.com/gfisoftware
|
|
|
|
RE: Whitelist being ignored - 29.Oct.2009 1:18:29 PM
|
|
|
ACsto
Posts: 3
Joined: 29.Oct.2009
Status: offline
|
I have this same issue after upgrading to 14.1 20090826. I opened a support case, received the whitelist.dll patch and have just applied it. I'm wondering if anyone can confirm the patch has fixed the issue for them. Thanks.
|
|
|
|
RE: Whitelist being ignored - 1.Nov.2009 7:12:58 AM
|
|
|
Monogram
Posts: 4
Joined: 1.Nov.2009
Status: offline
|
I applied ME14.1 this week and am experiencing the same issue where the whitelist is ignored and header checking (12) is causing issues, especially with what the code thinks are malformed MIME From: field which in many cases are formed properly. I applied the patch from the link above and it does not fix the issue. I am having to forward the messages from header checking to my address and then forward legitimate messages to the normal recipient.
|
|
|
|
RE: Whitelist being ignored - 2.Nov.2009 7:59:40 AM
|
|
|
ACsto
Posts: 3
Joined: 29.Oct.2009
Status: offline
|
The patch is actually only for the whitelist problems. Post #6 by AndrewZT has the notes that describe what is in the patch. However, I also had issues with the SMTP and MIME TO mismatch detecting things incorrectly. A simple message I sent from an outside webmail account, to the same webmail account, but CC my work account, was filtered by MailEssentials as an SMTP and MIME TO mismatch. I got the following note from GFI tech support about it: quote:
There is a known issue with the header checking module that is causing the MIME/SMTP To mismatch. The fix is going to be released in SR1 which is tentatively scheduled for next Tues. You can disable this option in header checking til then if it is blocking legit messages. I have disabled the option in header checking for now...
|
|
|
|
RE: Whitelist being ignored - 2.Nov.2009 8:19:36 AM
|
|
|
Monogram
Posts: 4
Joined: 1.Nov.2009
Status: offline
|
Yes, I realize the patch is only for the whitelist problems. I have entries in the whitelist that are still being ignored after applying the patch and the anti-spam filtering is still being performed.
|
|
|
|
RE: Whitelist being ignored - 2.Nov.2009 8:22:15 AM
|
|
|
ACsto
Posts: 3
Joined: 29.Oct.2009
Status: offline
|
You may have better luck if you can open a support case, if you haven't yet. When I called support and got the whitelist patch last week they advised to call back if there were further whitelist problems and it would be escalated. Our whitelist problems were intermittent to begin with but I don't have a report of them recurring yet.
|
|
|
|
RE: Whitelist being ignored (even in 14.1 RC 3) - 14.Jan.2010 4:49:43 AM
|
|
|
Zenetti
Posts: 11
Status: offline
|
Hi, are there any news about this problem? We are using ME 14.1 RC3 (20091123) but still emails are handeled as spam (Header filter). The whitelists have the priority 4 (IP), 6 (domain, email, auto) and 7 (keyword) Header checks priority is 12! The mails that fail are the reports of a cron job, I added the address to the whitelist by copying the mail to the public folder "GFI Whitelist", I can see "root@XXXXX.domain.de" in the whitelist settings of the ME configuration (so it was added successfully). Could it be that the "from" in the header causes the problem (I only changed the domain name, the parentheses and order was not touched)? Microsoft Mail Internet Headers Version 2.0 ... From: root@XXXXX.domain.de (Cron Daemon) ... X-GFIME-MASPAM: SPAM Christian
|
|
|
|
RE: Whitelist being ignored (even in 14.1 RC 3) - 14.Jan.2010 5:29:53 AM
|
|
|
rmiquel
Posts: 127
Joined: 18.May2009
Status: offline
|
Hi Zenetti, Please try adding the same email address as "SMTP FROM" entry in the whitelist and check if the same email is being stopped. Regards,
_____________________________
Roger Miquel GFI Software Blog-Twitter-YouTube-Facebook
|
|
|
|
RE: Whitelist being ignored (even in 14.1 RC 3) - 29.Jan.2010 3:36:47 AM
|
|
|
Zenetti
Posts: 11
Status: offline
|
Hi Roger, quote:
Please try adding the same email address as "SMTP FROM" entry in the whitelist and check if the same email is being stopped. Thanks for the tip, adding it to SMTP FROM worked for me. But I still got two questions: Why did the automatism not use SMTP FROM, when I moved the Mail to the public folder "Add to Whitelist"? I included the complete header of a mail that did not work with MIME FROM below. Can you explain please the difference between MIME FROM and SMTP FROM and why the automatism did fail, thanks. Microsoft Mail Internet Headers Version 2.0
Received: from exchange-pop3-connector.com ([192.168.a.b] RDNS failed) by mail.YYY-domain.de with Microsoft SMTPSVC(6.0.3790.3959);
Fri, 29 Jan 2010 03:04:03 +0100
Return-Path: <web111@XXX-domain.de>
X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on ZZZ-domain.de
X-Spam-Level:
X-Spam-Status: No, score=-0.6 required=6.0 tests=AWL,BAYES_50,RDNS_NONE
autolearn=no version=3.2.3
X-Original-To: pb1@ZZZ-domain.de
Delivered-To: pb1@ZZZ-domain.de
Received: from localhost (localhost [127.0.0.1])
by ZZZ-domain.de (Postfix) with ESMTP id 3273B1868002
for <pb1@ZZZ-domain.de>; Fri, 29 Jan 2010 03:02:10 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at ZZZ-domain.de
Received: from ZZZ-domain.de ([zzz.yyy.xxx.17])
by localhost (ZZZ-domain.de [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id inM15HV7YwoR for <pb1@ZZZ-domain.de>;
Fri, 29 Jan 2010 03:02:10 +0100 (CET)
X-Envelope-To: xyz@YYY-domain.de
X-policyd-weight: using cached result; rate: -4
Received: from XXX-domain.de (www.webserver.de [zzz.yyy.xxx.2])
by ZZZ-domain.de (Postfix) with ESMTP id 143F91868001
for <xyz@YYY-domain.de>; Fri, 29 Jan 2010 03:02:09 +0100 (CET)
Received: by XXX-domain.de (Postfix)
id B676CBFC25C; Fri, 29 Jan 2010 03:02:10 +0100 (CET)
Delivered-To: web111@XXX-domain.de
Received: from localhost (localhost [127.0.0.1])
by XXX-domain.de (Postfix) with ESMTP id A4A67BFC1C4
for <web111@XXX-domain.de>; Fri, 29 Jan 2010 03:02:10 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at XXX-domain.de
Received: from XXX-domain.de ([127.0.0.1])
by localhost (XXX-domain.de [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id rPe5zIqyXjd7 for <web111@XXX-domain.de>;
Fri, 29 Jan 2010 03:02:10 +0100 (CET)
Received: by XXX-domain.de (Postfix, from userid 122)
id 8694FBFC25C; Fri, 29 Jan 2010 03:02:10 +0100 (CET)
From: root@XXX-domain.de (Cron Daemon)
To: web111@XXX-domain.de
Subject: Cron <web111@my-domain> files/cronjob.sh
Content-Type: text/plain; charset=ANSI_X3.4-1968
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/home/www/web111>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=web111>
Message-Id: <20100129020210.8694FBFC25C@XXX-domain.de>
Date: Fri, 29 Jan 2010 03:02:01 +0100 (CET)
X-OriginalArrivalTime: 29 Jan 2010 02:04:03.0316 (UTC) FILETIME=[548EE340:01CAA087] Regards Christian
|
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|