<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div></div><div><br></div><div><br>On Mar 9, 2016, at 7:11 PM, Indunil Jayasooriya <<a href="mailto:indunil75@gmail.com">indunil75@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 10, 2016 at 12:57 AM, Tom Johnson <span dir="ltr"><<a href="mailto:tj@terramar.net" target="_blank">tj@terramar.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto"><div></div><div>I'm sorry if I wasn't clear - adding to trusted_networks is not an option. Different users have different needs. One person might want x.x.x.x whitelisted, but another may not. </div></div></blockquote><div><br></div><div> Why don't you need to whitelist or blacklist domains per user basis in following way in amavisd.conf file<br><br> # ENVELOPE SENDER SOFT-WHITELISTING / SOFT-BLACKLISTING<br><br>@score_sender_maps = ({ # a by-recipient hash lookup table,<br> </div></div>
</div></div>
</div></blockquote><br><div>We do whitelisting and blacklisting if senders (using sql). </div><div><br></div><div>But we also have some customers who need to whitelist everything coming from a given ip address. </div></body></html>