> Sorry, I should have elaborated.. But not when you have a domain > that does not resolve. As in our case, we have > @cottonwoodfinancial.com which is our main domain. Then a separate > domain @internal.cottonwoodfinancial.com with no MX records. So mail > being sent to an address on that domain will not go through.
Well, that's the case with any domain without an MX record. It has nothing to do with whether it's IP-ful or IP-less, or private-IP-ful or public-IP-ful, within IMail. And, of course, a determined person could send mail to that domain by hard-coding the mailroute. I think you're doing the right thing by making a domain that would require malicious/anti-policy intent to receive mail from the Internet, but there's nothing _technically_ totally segregating it from the outside world. --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/ --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
