Results 1 to 5 of 5

Thread: Zimbra Whitelist techniques don't work

  1. #1
    Join Date
    Feb 2006
    Posts
    20
    Rep Power
    9

    Default Zimbra Whitelist techniques don't work

    I have experimented with all the techniques for whitelisting a domain found in the wiki but none of them work or appear to work.

    I know it has been discussed here before and everyone points to that wiki for the answer. Can someone verify that it is working with GA5.0.4 x86_64? I just realized I'm outdated so I'll be upgrading from 5.0.3 to 5.0.4 but it would be nice to know for sure which method is supposed to work (as there are several listed).

  2. #2
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    Yes, the Whitelisting techniques do work.

    Perhaps if you gave details of what exactly you've tried, what results you're trying to achieve and the outcome you've seen then we might be able to help.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  3. #3
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

  4. #4
    Join Date
    Feb 2006
    Posts
    20
    Rep Power
    9

    Default

    What I did was use the suggestion here

    I added one line above the 'nobody@cert.org' => -3.0 ::

    'reports.spamcop.net' => -100.0,

    Restarted amavis with zmamavisdctl

    All mail from *@reports.spamcop.net still hit the Junk box. I'll check my logs to determine what is happening. The two different techniques mentioned in that post seem redundant. They both appear to be able to whitelist / blacklist entire domains and individual senders but one uses a score, the other uses a list.

    I assume that if it actually worked, I would want to use the :
    read_hash(\%whitelist_sender, '/etc/zimbra/whitelist');

    Here is a header from the 'spam'

    Code:
    X-Spam-Flag: YES
    X-Spam-Score: 7.77
    X-Spam-Level: *******
    X-Spam-Status: Yes, score=7.77 tagged_above=-10 required=4
    	tests=[BAYES_50=0.001, DATE_IN_PAST_12_24=0.992,
    	FORGED_MUA_MOZILLA=2.696, FROM_STARTS_WITH_NUMS=1.499,
    	SPF_PASS=-0.001, URIBL_OB_SURBL=1.5, URIBL_RHS_DOB=1.083]

    In this case, it would make more sense to use a distinct header that I know spamcop uses - like :

    X-SpamCop-sourceip: -or- X-Mailer: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1) via SpamCop.net - Beware of cheap imitations v647

    But it still would be nice to see the whitelist by domain name or sender working.
    Last edited by fireman949; 04-12-2008 at 10:34 PM. Reason: clarification

  5. #5
    Join Date
    Nov 2006
    Location
    UK
    Posts
    8,017
    Rep Power
    25

    Default

    We need to see what happened to that email, via the logfiles, to understand why whitelisting did not work.

    I have just tested this myself, using my googlemail account, and it passed through just fine. I followed the same steps of updating /opt/zimbra/conf/amavisd.conf.in and then a zmamavisdctl restart
    Last edited by uxbod; 04-13-2008 at 01:14 AM.

Similar Threads

  1. QUE Failure
    By tbullock in forum Administrators
    Replies: 31
    Last Post: 07-30-2008, 01:17 PM
  2. admin consol blank after 5.0.3 upgarde
    By maumar in forum Administrators
    Replies: 6
    Last Post: 03-21-2008, 06:16 AM
  3. Replies: 12
    Last Post: 02-25-2008, 07:28 PM
  4. Zimbra shutdowns every n hours.
    By Andrewb in forum Administrators
    Replies: 13
    Last Post: 08-14-2007, 09:55 AM
  5. Can't start Zimbra!
    By zibra in forum Administrators
    Replies: 5
    Last Post: 03-22-2007, 12:34 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •