----- Original Message -----
From: Max Paperno <[EMAIL PROTECTED]>
To: inFusion Support List <[EMAIL PROTECTED]>
Sent: Saturday, June 17, 2000 2:22 PM
Subject: Re: [iMS] MX backup question
> At 6/17/2000 02:15 PM -0400, you wrote:
>
> >> OK, thanks, that's what I thought. I'd suggest that the FAQ artivle
be
> >adjusted to reflect this step, since it's misleading at this point. If
> >server 2 doesn't have server 1 defined in it's Outgoing Servers entry,
the
> >current instructions would cause an endless loop (the way I understand
it).
> >>
> >
> >No, it wouldn't. The MX edition is incapable of sending mail to any
server
> >unless listed in the Outgoing Servers setting. So, if you left that
blank
> >then you would not get a mail loop but the mail would be stuck in the MX
> >backup server.
>
> Ah, OK, well the FAQ didn't say "use the iMS MX Backup edition" although
that certainly is a logical thing to do and is what I was planning... Still
seems like an important step to point out though :)
>
>
> >> On a related note, is there a way to have a backup mail server that is
> >backup for some domains, but is also primary for others? Say a client
wants
> >to run their own mail server, but have us run a backup for them. Well,
I'm
> >sure I could code something like that (store the primary server's IP with
> >the relay domain record, then only forward mail for that domain through
the
> >defined IP using cfx_imsmail), but is there an easier way?
> >>
> >
> >Assuming you are using FusionMail - you would configure this something
like:
> >
> >DNS:
> >
> >mail.customer.com = MX 10
> >iMS.yourserver.com = MX 20
> >
> >In the iMS server configure the customer domain to be a relay domain.
>
> So, assuming that iMS.yourserver.com is NOT running the MX Backup edition
(because it handles full domains as well), therefore it will just send mail
out based on a MX lookup.
Correct.
> If mail.customer.com is down, won't iMS just keep sending the mail to
itself, thereby causing a loop? I must be missing something basic....
sorry.
>
Hmmm...you are correct. The present version of FusionMail will do this.
The code that does domain relaying simply says:
result=relay
So, as a temporary fix you would do the following (nice to have most of the
functionality outside of iMS so you can do these things):
Add a string field in the domains database for domainMX
Change FusionMail from the above to result=accept
In the data.cfm you use cfx_imsmail to send the mail to the other domain
using the MX from the database.
For example:
mx10=mail.customer.com
mx20=ims.yourserver.com
In the db you would only put mail.customer.com
I'm going to have the SMTP Server changed to allow for the following:
result=relay
MX=mail.customer.com
This would be a much cleaner solution.
Even though the feature set for version 1.3 is supposed to be frozen I'll
have this added before release this week.
Regards,
Howie
> Thanks,
> -Max
>
>
>
> ========================================================================
> This list server is Powered by iMS
> 'The Swiss Army Knife of Mail Servers'
> --------------------------------------
> To leave this list please complete the form at
> http://www.CoolFusion.com/iMS.htm
>
> List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
> ========================================================================
>
========================================================================
This list server is Powered by iMS
'The Swiss Army Knife of Mail Servers'
--------------------------------------
To leave this list please complete the form at
http://www.CoolFusion.com/iMS.htm
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
========================================================================
