From: "Palvelin Postmaster postmaster@palvelin.fi" Received: from posti.palvelin.fi ([83.150.109.27] verified) by mail.tffenterprises.com (CommuniGate Pro SMTP 6.2.7) with ESMTPS id 20146168 for cgpsa-discuss@mail.tffenterprises.com; Wed, 04 Sep 2019 13:40:16 -0700 Received-SPF: pass receiver=mail.tffenterprises.com; client-ip=83.150.109.27; envelope-from=postmaster@palvelin.fi X-ClamAV-Checked: YES DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=palvelin.fi; h=from :content-type:content-transfer-encoding:mime-version:subject :date:references:to:in-reply-to:message-id; s=posti; bh=UWlACbCj dvbX9wUxw3sMPSZ/+IgYVbcfrcYdY0ikQWo=; b=KgQ2XyzEblaS/zRlhXFshBkp +f6zborDQzuwx6QnN9zPZQ25KlzxLyUaMSxXA18qoaxsM4z+BbY6LcLJCKc8+81l bJ9KQf0PkFUs+DtMuT0XRHHcAI8mlCkoLa1BtmjH2cv5apxFA0sseG49oH/1Z7a+ kYLxLaIBQySr0lK8VGM= Received: from [136.44.0.151] (account postmaster@palvelin.fi HELO ip-10-234-16-171.eu-central-1.compute.internal) by palvelin.fi (CommuniGate Pro SMTP 6.2.13) with ESMTPSA id 10687725 for cgpsa-discuss@mail.tffenterprises.com; Wed, 04 Sep 2019 23:40:03 +0300 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: [CGPSA] Delivering spam to Junk mailbox of each recipient Date: Wed, 4 Sep 2019 13:39:59 -0700 References: To: "Daniel M. Zimmerman dmz@tffenterprises.com" In-Reply-To: Message-Id: <370A73CA-B1DE-454B-AB53-FE5F9647A25C@palvelin.fi> X-Mailer: Apple Mail (2.3445.104.11) Hi Dan, sorry, I completely forgot about this because it wasn=E2=80=99t a = burning issue at the time. But it=E2=80=99s starting to become one now, = so here I am. :) Any suggestions as to what I should do? > On 20 Jun 2019, at 11.07, Daniel M. Zimmerman dmz@tffenterprises.com = wrote: >=20 > I think you might want to turn on a higher level of debugging, to see = what=E2=80=99s actually going on with respect to queue files being = written/rewritten and CGPSA=E2=80=99s internal actions. Feel free to = take the discussion offline (that is, email me back directly) so as to = avoid the rest of the list getting caught up in the minutia of it, and = we can summarize it for them when we figure it out=E2=80=A6 >=20 > -Dan >=20 >> On 19 Jun 2019, at 14:37, Palvelin Postmaster postmaster@palvelin.fi = wrote: >>=20 >> That=E2=80=99s correct. The log entry looks like this: >>=20 >> 02:21:08.018 2 DEQUEUER [10631102] = SYSTEM(name@domain.dom)#Junk-SpamAssassin delivered: delivered via = Automatic Rules >>=20 >> If the mbox file didn=E2=80=99t exist yet, one appears. The mbox file = size stays at 0 bytes. >>=20 >>=20 >>> On 19 Jun 2019, at 9.30, Daniel M. Zimmerman dmz@tffenterprises.com = wrote: >>>=20 >>> That is odd=E2=80=A6 So the log is saying that the mail should be = delivered to the direct mailbox address, and the mailbox exists, but the = mail isn=E2=80=99t ending up there?=20 >>>=20 >>> -Dan >>>=20 >>>> On 14 Jun 2019, at 21:39, Palvelin Postmaster = postmaster@palvelin.fi wrote: >>>>=20 >>>>=20 >>>>=20 >>>>> On 28 May 2018, at 23.37, Patrick Sneyers = wrote: >>>>>=20 >>>>>=20 >>>>>=20 >>>>>> Op 29 mei 2018, om 08:17 heeft Palvelin Postmaster = het volgende geschreven: >>>>>>=20 >>>>>> Hi, >>>>>>=20 >>>>>> I have a system-wide rule which delivers all recognized spam = addressed to all domains and recipients to one centralized spam folder = (of an account created exclusively for this purpose) for temporary = storage and teaching SpamAssassin=E2=80=99s bayes filter. >>>>>>=20 >>>>>> I=E2=80=99m considering changing my strategy to having a per-user = spam folder instead. I=E2=80=99m thinking this could, at the very least, = empower the users to actually receive these messages and manage possible = false positives. >>>>>>=20 >>>>>> Does anyone have any experience or insights about the strengths = and weaknesses of alternate handling strategies? >>>>>>=20 >>>>>> What would be the best way to implement this? Do I just need to = make a =E2=80=99Store In=E2=80=99 domain-wide rule for each domain = instead of the single system-wide rule I have now? >>>>>>=20 >>>>>> -- >>>>>> Palvelin.fi Hostmaster >>>>>> postmaster@palvelin.fi >>>>>>=20 >>>>>=20 >>>>>=20 >>>>> You can use this option in cgpsa.conf (line 552 in my file), and = keep using the server wide rule. >>>>> Of course, learning spam/ham becomes a bit more complicated then. >>>>>=20 >>>>>=20 >>>>> # A flag that determines whether messages tagged as spam will be = filed >>>>> # automatically using direct mailbox addressing. This eliminates = the need >>>>> # for users to add rules to their accounts to handle spam = filtering, but >>>>> # only works on systems where direct mailbox addressing is = enabled. If >>>>> # this setting is enabled, spam will be filed in the mailbox = specified by >>>>> # the "spam_mailbox_name" setting; the mailbox will be created = when needed >>>>> # if it does not exist. >>>>> # >>>>> use_dma_spam_mailbox =3D true >>>>>=20 >>>>> # The name of the mailbox to use for direct mailbox addressing = when=20 >>>>> # the "use_dma_spam_mailbox" setting is enabled.=20 >>>>> # >>>>> spam_mailbox_name =3D Junk >>>>=20 >>>> I=E2=80=99m now testing this. For some reason, my Junk mailboxes = remain empty even though CGP log indicates mail should end there and the = junk mailbox mbox files got created. I wonder what could be wrong? I = have direct mailbox routing enabled. >>>>=20 >>>>=20 >>>>=20 >>>=20 >>> --- >>> Daniel M. Zimmerman >>> http://www.tffenterprises.com/~dmz/ >>>=20 >>>=20 >>> ----- >>> This message is from the CGPSA Mailing List. >>> To unsubscribe, E-mail to: = . >>=20 >=20 > --- > Daniel M. Zimmerman > http://www.tffenterprises.com/~dmz/ >=20 >=20 > ----- > This message is from the CGPSA Mailing List. > To unsubscribe, E-mail to: = .