> And actually this is a MAJOR drawback to ever use the Max invalid > rcpt at the SMTP connection registry fix, when you have a secondary > MX.
A secondary MX _that doesn't validate addresses_, you mean. (In addition, when you do have one that can validate, having a max-invalid policy that isn't enforced on the secondary is ridiculous, given that spammers love secondaries.) > Does anyone have some suggestions on how to prevent those dictionary > attacks? See my sig for ldap2aliases if applicable. The secondary needs to communicate with the primary via LDAP. > Spare me from 3rd parties solution, Imail mainly does what we need > it to do and we don't NEED (and/or) WANT to add another point of > failure. Do scripts count as third-party? If so, you're out of luck. --Sandy ------------------------------------ Sanford Whiteman, Chief Technologist Broadleaf Systems, a division of Cypress Integrated Systems, Inc. e-mail: [EMAIL PROTECTED] SpamAssassin plugs into Declude! http://www.imprimia.com/products/software/freeutils/SPAMC32/download/release/ Defuse Dictionary Attacks: Turn Exchange or IMail mailboxes into IMail Aliases! http://www.imprimia.com/products/software/freeutils/exchange2aliases/download/release/ http://www.imprimia.com/products/software/freeutils/ldap2aliases/download/release/ To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
