http://spamassassin.apache.org/tests.html isn't being maintained, but was
a useful quick reference for tests and their default scores. Is there any
chance of it being revived, or is there a current equivalent?
As a consequence of that page being deprecated,
On Thu, 2 Jun 2016, John Hardin wrote:
On Thu, 2 Jun 2016, Antony Stone wrote:
On Thursday 02 June 2016 at 13:16:57, Martin Gregorie wrote:
> On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
> > > Therefore I agree that there could be better way of noticing admins
> > >
Am 02.06.2016 um 17:32 schrieb John Hardin:
On Thu, 2 Jun 2016, Antony Stone wrote:
On Thursday 02 June 2016 at 13:16:57, Martin Gregorie wrote:
On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
Therefore I agree that there could be better way of noticing admins
of a
On Thu, 2 Jun 2016, Antony Stone wrote:
On Thursday 02 June 2016 at 13:16:57, Martin Gregorie wrote:
On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
Therefore I agree that there could be better way of noticing admins
of a [URIBL_BLOCKED] issue.
create and install a
Antony Stone wrote:
> On Thursday 02 June 2016 at 15:12:58, Reindl Harald wrote:
>> it's highly unlike in a proper setup that SA faces enough email to hit
>> the URIBL limit
>
> Once again, as you said yourself, "highly unlikely". That does not mean
> "impossible".
Indeed. We received notice
On Thursday 02 June 2016 at 15:12:58, Reindl Harald wrote:
> Am 02.06.2016 um 15:07 schrieb Matus UHLAR - fantomas:
> > On 02.06.16 14:48, Reindl Harald wrote:
> >> that typically happens only when one is using a forwarding resolver
> >> get it finally
As you said yourself, "typically". That's
Am 02.06.2016 um 15:07 schrieb Matus UHLAR - fantomas:
On 02.06.16 14:48, Reindl Harald wrote:
that typically happens only when one is using a forwarding resolver
get it finally
you did not get it:
there are cases where it's not caused by forwarding DNS but by getting much
mail.
just for
On 02.06.16 12:35, Reindl Harald wrote:
the setup IS CRIPPELED in it's function as long URIBL/DNSBL/DNSWL are
not working - period
Am 02.06.2016 um 14:42 schrieb Matus UHLAR - fantomas:
hitting the others' limits does not mean that the setup is crippled.
get it finally. period
On 02.06.16
Am 02.06.2016 um 14:42 schrieb Matus UHLAR - fantomas:
On 02.06.16 12:35, Reindl Harald wrote:
the setup IS CRIPPELED in it's function as long URIBL/DNSBL/DNSWL are
not working - period
hitting the others' limits does not mean that the setup is crippled.
get it finally. period
that
On 02.06.16 12:35, Reindl Harald wrote:
the setup IS CRIPPELED in it's function as long URIBL/DNSBL/DNSWL are
not working - period
hitting the others' limits does not mean that the setup is crippled.
get it finally. period.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ;
On Thu, 2016-06-02 at 13:22 +0200, Antony Stone wrote:
> On Thursday 02 June 2016 at 13:16:57, Martin Gregorie wrote:
>
> > On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
> > > > Therefore I agree that there could be better way of noticing
> admins
> > > > of a [URIBL_BLOCKED]
>> On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
>> > > Therefore I agree that there could be better way of noticing admins
>> > > of a [URIBL_BLOCKED] issue.
>>
>> create and install a logwatch service that scans /var/log/maillog
>> for lines containing "URIBL_BLOCKED" - this
Am 02.06.2016 um 13:16 schrieb Martin Gregorie:
On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
Therefore I agree that there could be better way of noticing admins
of a [URIBL_BLOCKED] issue.
There's one obvious way of doing this for very little cost & effort:
use
On Thursday 02 June 2016 at 13:16:57, Martin Gregorie wrote:
> On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
> > > Therefore I agree that there could be better way of noticing admins
> > > of a [URIBL_BLOCKED] issue.
>
> create and install a logwatch service that scans
On Thu, 2016-06-02 at 12:28 +0200, Matus UHLAR - fantomas wrote:
>
> >
> > Therefore I agree that there could be better way of noticing admins
> of a [URIBL_BLOCKED] issue.
>
There's one obvious way of doing this for very little cost & effort:
use logwatch.
If you're a pukka sysadmin you'll
Am 02.06.2016 um 12:28 schrieb Matus UHLAR - fantomas:
On 6/1/2016 3:06 AM, Reindl Harald wrote:
write 1000 times " YOUR SETUP IS CRIPPLED
http://uribl.com/refused.shtml " in the rpeort header and
every 5 seconds into the maillog so that the biggest fool can't
ignore
On 6/1/2016 3:06 AM, Reindl Harald wrote:
write 1000 times " YOUR SETUP IS CRIPPLED
http://uribl.com/refused.shtml " in the rpeort header and
every 5 seconds into the maillog so that the biggest fool can't
ignore it
Am 01.06.2016 um 15:24 schrieb Matus UHLAR -
Am 02.06.2016 um 06:48 schrieb Peter Carlson:
In fact, now that I am confident the script is correct and that my email
chain is in fact processing as I would like, I have moved the script
into cron as user amavis. With amavis having read permissions to the
appropriate folders
--
Ma domena pouziva zabezpeceni a kontrolu SPF (www.openspf.org) a
DomainKeys/DKIM (s ADSP) a implementaci DMARC. Pokud mate problemy s
dorucenim emailu, zacnete pouzivat metody overeni puvody emailu
zminene vyse. Dekuji.
My domain use SPF (www.openspf.org) and DomainKeys/DKIM (with ADSP)
19 matches
Mail list logo
