A backup mail server router entry is typically: domain.com = domain.com.smtp
Using this, a dictionary attack on the secondary server results in lots of failed bounce messages for the domain in question since the backup server accepts mail for any account at domain.com only to find out later that many of those accounts do not exist on the primary server and are rejected. I had hoped that replacing "domain.com = domain.com.smtp" with: [EMAIL PROTECTED] = [EMAIL PROTECTED] [EMAIL PROTECTED] = [EMAIL PROTECTED] [EMAIL PROTECTED] = [EMAIL PROTECTED] [EMAIL PROTECTED] = [EMAIL PROTECTED] I'd hoped that the backup server, having no router rule for, let's say, [EMAIL PROTECTED] would simply refuse to accept mail for that account with a "relaying denied" error or something. That doesn't seem to happen. In the absence of an entry of "domain.com = domain.com.smtp" why does the backup server continue to accept mailo for accounts with no router entry? Additionally, I'd hoped that including: [EMAIL PROTECTED] = spamtrap would keep the backup server from accepting mail to this account too. Why doesn't SIMS just disappear email to the spamtrap account? -- Warren Michelsen <[EMAIL PROTECTED]> Online Tools For Business -- <http://www.OTFB.com/> Small Business & E-commerce web hosting ############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
