sieve not move spam email to .Junk folder

Discussion in 'General' started by themark, Oct 1, 2014.

  1. themark

    themark Member


    we have a server installed with that perfect server howto:

    All the software (included ispconfig) are at the latest stable version.
    The problem it's that basically all the mail that are grab as spam by amavis/spamassassin are never moved on the .Junk folder.

    For example, on the mail.log file I have that entry:

    Sep 30 17:50:57 node238 amavis[29461]: (29461-01) Passed SPAMMY {RelayedOpenRelay}, [XX.XXX.XXX.XXX]:45421 [XX.XX.XX.XXX] <[email protected]> -> <[email protected]>, Queue-ID: A11D262B2C, mail_id: U3l_o45mVHgY, Hits: 17.182, size: 4812, queued_as: DC9B662B2A, 1861 ms

    but that email (that it's look recognized as spam) is in the inbox folder, and in addiction without any additional headers.

    Have you some idea, of what happen there?
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The spam movinf i done by sieve based on the spam header, as you dont have a header, the mail is not moced to junk. the mail headers are controlled by the two spam scores. Which score is set for spam tag level 1 and which score is set for spam tag level 2 in the policy that you assigend to this address?
  3. themark

    themark Member

    i have used aggressive policy standard.
    that mean the value:

    1 for tag level 1


    3 for tag2 level

    But i don't know what scores the mail, due the fact that no spamheaders appear on the mailheader....
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    try to set tag level 1 to: -100

    This should ensure that you always get headers.
  5. themark

    themark Member

    I have created a new policy called "test" that is a copy of normal policy, with a tag-level 1 of -100

    An then I have assigne that policy to the mailbox (and for sure also to the domain).

    Then I have send an email to that email address, but none spam headers are added to the I have to think that spamassassin is not working?
  6. themark

    themark Member


    problem was that several mailuser was created via api system, without the flag local=Y on the database.

    So spamassassin didn't see that users as local, and don't parse them.
    Simply solved with a query that correct them.


Share This Page