• Giuseppe Sacco via Exim-users [2024-10-04 11:14]: > Hello, > I have a DSL connection that always has its IP address listed in some > blacklist, so direct deliveries from my exim server sometimes fails > with permanent errors like this one: > > 550 5.7.1 Service unavailable; client [95......78] blocked using > zen.spamhaus.org > > I also have a smarthost, but I prefer direct delivery, so I added a > router that checks for the target domain against a list and use the > smarthost if the domain is listed, otherwise it goes for the direct > delivery. > > I would like to avoid to manually maintain such a list. One option > would be to let exim tries the smarthost after receiveing a permanent > error from the remote smtp transport. I could not find how to do this. > > Another option would be to let exim update the list adding domains that > fails permanently. This will bounce only the first message, and will > use the smarthost on subsequent messages to the same domain. > > Or maybe, such a list is available and maintained somewhere on the > Internet. Or any other solution that I do not currently see. > > This is for sure a common problem, so I wonder how other people solved > it.
I'm just using _my_ smarthost in such cases. An option I'd consider would also be to use SOCKS5 proxy on the smtp transport: https://www.exim.org/exim-html-current/doc/html/spec_html/ch-proxies.html Have you considered using RCPT ACL to do callout verification? Not to reject RCPT in case of a callout failure, but to check whether or not use a smarthost. An unsucessfull callout would set som $acm_m variable, which later could be used to route the message via smarthost. Just an idea, not even sure it would work. > Thank you, > Giuseppe -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
