Hi Peter,<br><br><b><i>shuttlebox <shuttlebox@gmail.com></i></b> wrote:<blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"> On Nov 28, 2007 1:13 PM, Michael Mansour <micoots@yahoo.com> wrote:<br>> Yes it is a memory hog, but 400Mb of virtual memory isn't that much<br>> considering I have over 72,000 auto-managed records per server.<br><br>It's also easy to tune the memory consumption by adjusting how long it<br>will keep grey/whitelisted entries in the database.<br><br>> I have tried others and found they may work well for one server, but not in<br>> a distributed environment which requires sync between MX servers.<br><br>The sync is very important and I haven't found an alternative that is<br>capable of that.<br></micoots@yahoo.com></blockquote>Yes, sync is critical. I have also used and tested the greylist server that comes with DCC by Vernon. I use DCC anyway so though I might as well turn on
the greylist feature and not have to worry about yet another third party app.<br><br>DCC's greylist also has a "peer" feature which does what milter-greylist's sync does (not exactly the same way or as instantaneous as milter-greylist, but still works), so provides the necessary sync between MX peers.<br><br>DCC's greylist work fine for *non-MX* servers, however for inbound MX servers which don't have local recipients (but pass the message onto an internal mail server after releasing the message from the embargo), DCC greylist tries to authenticate the recipients with the MX server itself, which of course fails with a "user unknown" and bounces the message to the sender.<br><br>DCC greylist doesn't bother reading sendmail's mailertable to determine where the destination recipient is or to even consider that it's just an inbound MX server and should just greylist (embargo in DCC terminology) the email and then send it on to the real mail server with the inboxes.<br><br>I
explained and reported this problem to Vernon but he didn't accept it as a problem, instead tried to convince me that I didn't need MX servers and I should just run a beefy mail server. <br><br>A few emails bounced between us before I gave up trying to explain to him why his greylist implementation doesn't work for inbound MX servers.<br><br>He's a cluely guy and knows his stuff, but I just couldn't get through to him, he simply didn't accept the setup I had as a valid setup. Go figure.<br><br>Michael.<micoots@yahoo.com></micoots@yahoo.com><br><micoots@yahoo.com></micoots@yahoo.com><blockquote class="replbq" style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><micoots@yahoo.com>-- <br>/peter<br>-- <br>MailScanner mailing list<br>mailscanner@lists.mailscanner.info<br>http://lists.mailscanner.info/mailman/listinfo/mailscanner<br><br>Before posting, read http://wiki.mailscanner.info/posting<br><br>Support MailScanner development - buy the
book off the website! <br></micoots@yahoo.com></blockquote><br><p> 
<hr size=1>
Make the switch to the world's best email. <a href="http://au.rd.yahoo.com/mail/taglines/default_all/mail/spankey/*http://au.yahoo.com/worldsbestmail/spankey/" target=_blank>Get the new Yahoo!7 Mail now</a>.