> Can't lyris be configured to listen/use another port? It sounds like
Lyris
> wants to the the front end, and the mail server to be the backend, which
is
> just the opposite from what we want, well, you anyway, since I plan to
have
> Lyris on its own machine forwarding all of its outbound to Imail, and
Imail
> relaying inbound to Lyris.
Yes it can. But if you're running on different boxes, why does imail have to
do any redirecting of lyris mail anyway (which it can't do even if you
wanted to)? You simply have 2 MX records like:
domain.com IN MX 10 mail.domain.com # IMAIL server
lists.domain.com IN MX 10 lyris.domain.com # lyris FreeBSD box
> > The problem with this is that now, if Lyris crashes
> >for some reason, both Lyris and Imail are out of service,
>
> Well, that's where secondary MX's come in.
Not true. In my case where I want to have both on the same box, and I make
Imail run on port 26, MX records will not do me any good. If the MX record
pointing to the Lyris IP fails, it will lookup the MX record pointing to the
Imail IP. That's fine, but Imail is listening on port 26, and no matter how
many MX records you have, Imail will never answer the regular port 25 SMTP
request. It's relying on the Lyris server, on port 25, to forward all
non-lyris messages to the Imail server running on port 26. If Lyris is down,
no SMTP inbound connection to that server will occur. I know I can configure
backup IMAIL servers, but that's not really the focus of this discussion.
> >since Imail is
> >just sitting there listening on port 26 for example, but every mail
server
> >in the world is trying to connect on port 25 (where Lyris was sitting and
is
> >now down).
>
> The remote MTA's should/will switch to the 2ndary MX's, non?
See above. They will switch to the secondary MX, but they will not switch to
port 26.
-Scot
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
