Thanks Klaus.<br>
<br>
Just to make sure I understand what you suggested, I should replace<br>
<br>
if (uri!=myself) {<br>
t_relay();<br>
break;<br>
}<br>
<br>
with the code snippet you posted. Right?<br>
<br>
Many Thanks,<br>
Paul<br><br><div><span class="gmail_quote">On 6/29/05, <b class="gmail_sendername">Klaus Darilion</b> <<a href="mailto:klaus.mailinglists@pernau.at">klaus.mailinglists@pernau.at</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi!<br><br>It is simple, it just depends on your routing logic:<br><br>use domain module and check out-of-dialog methodes:<br><br>if ( !is_uri_host_local()) {<br> if (is_from_local() {<br> t_relay;<br> break;<br>
} else {<br> sl_send_reply("403", "Relaying not allowed");<br> }<br>}<br><br>cheers,<br>klaus<br><br>Java Rockx wrote:<br><br>> Hi All.<br>><br>> This link is to a discussion on how to keep SER from being an open relay
<br>> due to the following logic that most everyone uses in their ser.cfg files.<br>><br>> if (uri!=myself) {<br>> t_relay();<br>> break;<br>> }<br>><br>> <a href="http://mail.iptel.org/pipermail/serusers/2003-October/003264.html">
http://lists.iptel.org/pipermail/serusers/2003-October/003264.html</a><br>><br>> Some time has passed on this issue and the 2003 article described a few<br>> "in-progress" patches.<br>><br>> Does anyone know if SER now has the ability to prevent malicious users
<br>> from exploiting (uri!=myself) code blocks?<br>><br>> Regards,<br>> Paul<br>><br>><br>> ------------------------------------------------------------------------<br>><br>> _______________________________________________
<br>> Serusers mailing list<br>> <a href="mailto:serusers@lists.iptel.org">serusers@lists.iptel.org</a><br>> <a href="http://lists.iptel.org/mailman/listinfo/serusers">http://lists.iptel.org/mailman/listinfo/serusers</a><br></blockquote>
</div><br>