<div class="gmail_extra"><br><div class="gmail_quote">On Fri, Nov 23, 2012 at 11:28 AM, Peter Bonivart <span dir="ltr"><<a href="mailto:bonivart@opencsw.org" target="_blank">bonivart@opencsw.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Fri, Nov 23, 2012 at 6:16 PM, Chris Stone <<a href="mailto:axisml@gmail.com">axisml@gmail.com</a>> wrote:<br>
> milter-ahead is going to be a ton more efficient than any perl based script.<br>
> milter-ahead is written in C, supports caching and numerous indexed or flat<br>
> text file databases for the local cache.<br>
<br>
</div>I assume the script was only used to extract the recipient addresses<br>
from AD and build the necessary Sendmail files via a cron job so<br>
performance shouldn't be an issue at all.<br>
<span class="HOEnZb"></span></blockquote><div><br>But, that would mean though that any changes to accounts on the Exchange server(s) would not be reflected until the next time the script runs. Using milter-ahead or smf-sav makes it dynamic rather than static.<br>
<br>I did look at smf-sav and while it worked good, there was a problem that made it so I decided to license milter-ahead instead - don't recall for sure, but I think it was that it uses null sender or postmaster as the MAIL FROM on lookups, whereas, milter-ahead can be configured to use the original MAIL FROM - which suits my needs better. Probably could add that support to smf-sav, but since milter-ahead already did it, I went route.<br>
<br><br>Chris<br> <br>-- <br></div></div>Chris Stone<br>AxisInternet, Inc.<br><a href="http://www.axint.net">www.axint.net</a><br><br>
</div>