>Default Mail Host is empty.
amazing! you gotta have that.
default mail host: domain.com
mail host aliases: mail.domain.com whatever.domain.com
yetagain.domain.com etc etc
all accounts for [EMAIL PROTECTED] will be also aliased to the other
hostname aliases: [EMAIL PROTECTED], [EMAIL PROTECTED]
The key concept is to get Internet, via DNS MX records, to send mail to the
IP ADDRRESS of the Imail machine, where Imail will decide what to do with
it. You can't "fix" everything about mail routing within Imail.
So if you have 18 aliases behind an Imail domain.com host, you have to have
18 DNS MX records
domain.com MX 10 imail.whatever.com
mail.domain.com MX 10 imail.whatever.com
whatever.domain.com MX 10 imail.whatever.com
yetagain.domain.com MX 10 imail.whatever.com
etc
etc
Please note that Imail peering doubles the workload on, say 2 Imail
machines. If you receive 50,000 msgs per day,
25,000 WILL INITIALLY BE DELIVERED TO THE WRONG IMAIL MACHINE !!
And that machine will have to relay these 25,000 msgs to the other
machine. But the other machine has ALSO received 25,000 mails for the
other machine, so the it also has to relay 25,000 msgs to the other
machine. So now you have 50,000 external msgs sent to the peer group, and
ANOTHER 50,000 msgs re-delivered within the peer group, a 100,000 msgs
handled to receive 50,000 msgs. ie, on average, completely doubling the
mail traffic!!
I am still waiting for somebody to explain to me what is the use of Imail
peering??
Len < plus you expose Imail to SMTP VRFY dictionary attacks and address
harvesting >
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
