Got it, Thanks
Michael
> >Ok, I think I have it now. He won't be able to use the web interface to
get
> >his mail.
>
> whoa, that's not what I said. Imail web messaging does not apply
> "relaying" rules/restriction to "roaming" clients coming into Imail
through
> HTTP. So he can very well pick up his mail with a browser, from any ip
> address. Sending mail via web msging does not qualfity as an smtp relaying
> action.
>
> >He'll need Outlook or something like that to read his mail.
>
> He can use outlook to read his POP3 and IMAP mail, I recommend
> POP3. apparently, IMAP has lots of security holes. POP3 should
> suffice. And you really want to encourage your clients to POP their mail
> and delete it from the server, as frequently as possible.
>
> >In Outlook, when he is setting his account up, he'll need to select IMAP
> >instead of POP3??? Does this sound right.
>
> no, he can use POP3 like anybody else, such as Eudora, etc. If you want
> him to use IMAP, then you have to activate IMAP in Imail control panel and
> specify IMAP in outlook.
>
> > Here's an off the wall question. Is it possible to setup two Imail
servers
> >on one domain.
>
> A mail server shoul resolve to one ip address, usually, so no, in general.
>
> If you had two Imail machines, you could have people set up their mail
> clients so that they send (ie, via smtp) mail out through machine X, and
> pick up (POP3 or Imap or http) mail at machine Y. Their accounts would
> only be Y.
>
> In DNS, the MX record points to machine Y.
>
> Machine X, if it doesn't receive mail, doesn't have to be in the DNS at
all.
>
> >Just a thought if things were to get out of hand on one server.
>
> Certaintly, web msging on machine Y could get very heavy, so having a 2nd
> machine for sending mail from remote POP3/IMAP clients would share the
> load. All incoming mail (the MX record!!) for POP3/IMAP pickup and
> webmsging goes to machine Y, while mail clients send their outgoing mail
> via machine X.
>
> In fact, machine Y could use machine X as a "gateway", which allows
machine
> Y to avoid doing DNS lookups and distant mail sending. Y would just dump
> all it outgoing mail directly on X's ip adddress (no DNS lookup), and then
> Y would do the dirty work of DNS lookups and contacting the remote MX
> destinations, retries, etc, etc to deliver's Y-originated mail.
>
> Len
>
> Please visit http://www.ipswitch.com/support/mailing-lists.html
> to be removed from this list.
>
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
