From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from oat.nine.sirjofri.de ([5.45.105.127]) by ewsd; Mon Aug 31 09:49:59 EDT 2020 Received: from sirjofri.de ([94.222.62.23]) by oat; Mon Aug 31 15:48:47 CES 2020 Date: Mon, 31 Aug 2020 13:49:38 +0000 (UTC) From: sirjofri+ml-9front@sirjofri.de To: Alex Musolino <9front@9front.org> Message-ID: In-Reply-To: <35CD785AA83F011A10E04FCE9084A2C9@musolino.id.au> References: <35CD785AA83F011A10E04FCE9084A2C9@musolino.id.au> Subject: Re: [9front] Smtp greylist possible missing feature? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Correlation-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: stable anonymous base ACPI over SQL lifecycle metadata app Hey Alex, 31.08.2020 05:20:16 Alex Musolino : > Sounds plausible.=C2=A0 Have a look in qer(8); there's an example cron > job at the bottom for periodically (re-)processing the mail queues. Thank you very much for this hint. I followed the notes of qer and it works= now. To anyone reading this, I was unable to create a /cron/none/cron file with = auth/cron -c. Creating the file as glenda and changing ownership didn't wor= k, too, so I created the file like this: Write to cwfs.cmd: create /cron/none none none 755 d create /cron/none/cron none none 666 And then I was able to write to this file as glenda (not as none!) and add = my line. Since then I tested greylisting testers and also one of my recipients and i= t seems to work. At least their mail server responds as expected. Thank you for your help. I'll write that up later to help others (configuri= ng qer properly etc). sirjofri