me too!
I am also very interested in doing this.
I have a client whose verizon dsl assigned IP is listed in dsbl.org. I know that the "right" solution is to pursue having their IP removed from the list, but in the meantime, I'd like something, even if only temporary, to let this particular client continue to send via my server.
So solutions I see:
1. turn off spamlist checking
(I'd rather not as this would be server-wide and to date it has helped reduce the mail load... I think)
2. add my client's IP to a whitelist
(this would be ok... I'm having trouble finding some good pointers to how to do this with exim, but I may just need to search more)
3. have some setting so that authenticated users can send regardless.
(this would be ideal)
Actually, now that I think about it, the only people sending FROM my server are my clients (i.e. it's not an open relay... authentication required to use SMTP)...
So I'm suddenly wondering why I want dnslist/dsbl checks on emails sent FROM my server? Doesn't it make more sense to only use it to reject emails coming IN TO my server that are from a known spam IP?
Can someone shed some light on this? And of course I welcome any specific pointers on how to set this up, either #2 or #3... or best of all, the option to not check outgoing emails against spamlists.
Thanks!
-Danimal
