> I had deleted the MX records earlier because of the mail routing
> problem. If I have MX records for filtered and unfiltered, it
> randomly sends the email through which I thought was related to the
> priority.
I think you're confusing "MX records FOR" and "MX records that ARE" a
given host. For example, in--
example.com IN MX 10 mail.example.com
--mail.example.com is an MX record FOR example.com; one of
example.com's MX records IS mail.example.com.
If you want to have the hostname.example.com receive mail, it needs,
preferably, an MX record (an A record can/will be used if there's no
MX, but ignore that for now). This MX record will be consulted for
mail going to [EMAIL PROTECTED] Similarly, if you want
example.com to receive mail, it needs an MX record. If you want to
trifurcate your mail to @example.com, @hostname1.example.com, and
@hostname2.example.com, you should have MX records FOR each of these
hosts, and there should be no overlaps in what the records ARE.
Complicating this issue slightly is the fact that IMail will accept
mail for any domain on any of its interfaces, which is fine design but
may be exploited by spammers who intuit that the MX record for
unfiltered.example.com might also accept mail for example.com without
filtering it (as it will enter on the unfiltered IP). Note that a
product like Declude Junkmail, which is not tied to the entry IP but
to the true IMail virtual host, does not have this issue.
-Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail: [EMAIL PROTECTED]
------------------------------------
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/
