exim, RBL and irony

There's nothing more annoying, when you want to send mail, than to receive the a "550-rejected because some.ip.add.ress is blacklisted at some.random.crap.rbl".

Actually, there is something more annoying : setting up an email alias to an external address and realize some weeks later that the server dealing with the external address does use such rbl. In such cases, senders get an error message and no way to warn about the problem. And the message is not queued.

So, I was wondering if there was a way, with exim (default mail server on debian, and suitable for my needs), to have a "conditional smarthost", something like "if when trying to deliver a mail, you get an rbl rejection from the remote server, try to send it through my ISP's smarthost".

Why not just use ISP's smarthost all the time ? The answer is simple : I don't see why i should do that while it just works the way it is most of the time.

And now for the irony : when trying to send a message to the exim-users mailing-list to ask for hints, what can have happened ?

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

exim-users@exim.org
SMTP error from remote mail server after RCPT TO:<exim-users@exim.org>:
host sesame.csx.cam.ac.uk [131.111.8.41]: 550 Access denied - x.y.z.t listed by rbl-plus.mail-abuse.ja.net -

Rhââââââââââ

2005-08-13 11:15:13+0900

miscellaneous, p.d.o

Both comments and pings are currently closed.

One Response to “exim, RBL and irony”

  1. Frans Pop Says:

    If you ever find a way to automatically reroute through the ISP after being blocked, please publish it. I’d be very interested.