On Thu, 14 Sep 2000, F.F. Jacot-Guillarmod wrote:
> For some time I've been receiving more moans than usual about
> our institutions RBL implementation. I thought I had things covered
> by generating an instructive little essay via this entry in my
> reject.messages file:
>
> ===============================================================
> rbl_reject_recipients: The host $sender_fullhost is in an RBL. | Please refer your own or your ISP's system administrators or tech support to: | $rbl_text | The Rhodes University stance on RBL's is available at: | http://www.ru.ac.za/rblfaq.html
> ===============================================================
Unfortunately, if you RTFM, you will see that "rbl_reject_recipients" is
not listed in section 43.6 as one of the values for $prohibition_reason.
The relevant value is "rbl_reject" because the only kind of rejection
for RBL is in fact to reject recipients.
On Thu, 14 Sep 2000, John Horne wrote:
> The 'rbl_reject_recipients' applies to those rbl hosts *not* listed with a
> /reject or /warn. All of yours are. (see manual pages 88). Hence you get the
> default message. Either change the entry in the reject file (to
> 'rbl_reject:'), or the rbl_domains entry.
The use of /reject or not should not affect the generation of the error
message.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
