scriber> As all of you know RBL rejection occurs during RCPT TO
scriber> and ends with 'User unknown':
scriber>
scriber> RCPT To:<novikov@???>
scriber> 550-Open relay - see
http://www.orbs.org/verify.cgi?address=194.154.71.131
scriber> 550 mail from 194.154.71.131 rejected: administrative prohibition
scriber> 550 <novikov@???>... User unknown
That cannot be right. The syntax is wrong - an SMTP status message
consists of 0 or more lines with code followed by hyphen, and exactly
one with code followed by space. If exim is doing that (and a
reasonably quick look at the code cannot see *how* it is doing that)
then it is a bug. A test (using the RBL test address of 127.0.0.2)
also showed that this was not happening.
That final line must be inserted by an overclever sendmail.
djc> Anyway, many of us (including myself) dont want to accept a message
djc> from a host listed in the RBL.. Way too many have false/bogus envelope
djc> senders.. And to do so would defeat the entire reason we use RBL..
djc>
djc> What might be a good idea, is instead of exim saying "550 ... user
djc> unkown", would be to allow the string after the 550 to be configurable
djc> (possibly with an expansion, including the rbl_text).. Remote mailers
djc> dont parse antything but the 550, but hopefully sendmail is inserting
djc> the text that comes after, rather than interpreting the 550 and
djc> displaying its own messages.. Is there perhaps another 5xx code that
djc> exim could use on RBL that just means something along the lines of "I
djc> dont want to accept mail from you for this user", but does not
djc> necesarrily mean "user unknown" ?
The exim message is
550 mail from 194.154.71.131 rejected: administrative prohibition
Nigel
--
[ Nigel Metheringham Nigel.Metheringham@??? ]
[ Phone: +44 1423 850000 Fax +44 1423 858866 ]
