On Thu, 27 May 1999, John Horne wrote:
> After changing to Exim 3 we had the configuration option:
>
> host_reject_recipients = "! TABLES/banned/networks-allow : \
> ! partial0-lsearch;TABLES/banned/hosts-allow : \
> +allow_unknown : \
> partial0-lsearch;TABLES/banned/hosts : \
> cdb;TABLES/banned/spam/reject_hosts.cdb : \
> TABLES/banned/networks"
Oh dear. Yet another "special case" that I didn't forsee when making the
changes to the syntax. I will add words to README.UPDATING.
> It seems, however, that unless the '+allow_unknown' is at the top of the list
> or before a file lookup entry then it, in effect, gets ignored.
It applies only to those items in the list which follow it, as
documented.
Prior to 3.00, Exim would have processed sender_host_reject_recipients before
sender_host_reject_except, and so would have noticed the +allow_unknown
early on and accepted the call before it got to the exception list.
> Second (minor) point: we have configured a file for prohibition messages, but
> would like to seperate out those from the above lists which are 'banned' by us
> as oppose to those which are rejected due to DNS failures (lack of PTR
> records). At present the DNS ones get a message saying we have banned them for
> mail abuse. Oops. If its easy to do could it be added to the wish list please?
Noted.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
--
*** Exim information can be found at
http://www.exim.org/ ***
