Secondary MX failover problem

[Elliot Nesterman]

We've got 2 DSL lines leading into our LAN. Firewalls on either one
point all SMTP traffic to our GroupWise box. One of the DSL addresses is
set as our primary MX record, the other as our secondary MX record.

Previously, if our primary DSL line went down mail would start coming
into our secondary line within a period of a few hours to overnight.
Certainly by the next day SMTP servers would be sending mail to our
secondary MX record address.

However, our primary MX address went down early Friday morning, and as
of Monday morning we still were not getting any significant amount of
email through our secondary MX address. (SPAM was finding its way down
our second line, of course.) We've temporarily changed our records so
that the working DSL line is now our primary,

Has something changed in the last year or two in the way most SMTP
servers resolve addresses? I'm troubled because one of the reasons I've
always insisted on redundant Net connections was for relatively seamless
failover of email.

Any thoughts?

Thanks,
Elliot

--
Elliot Nesterman
ell...@inch.com
Standard Disclaimers Apply
-----------------------------------------------------------
The closer you are to the code, the happier you are.
- Ancient Geek Proverb
-----------------------------------------------------------

[Michael Bell]

Nope, but this is not GW related. This has to be a DNS issue.

--
Michael J. Bell
Novell Support Connection Volunteer Sysop
Author of Guinevere (http://www.openhandhome.com)

PLEASE: Do not e-mail me privately unless specifically asked.
I'm a volunteer, not a Novell employee!

All opinions and advice provided are MINE alone and NOT Novell's unless
specifically identified as such.

Novell does not officially monitor these forums.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

"You've got a way to keep me on your side/You give me cause
for love that I can't hide/For you I know I'd even try to
turn the tide/Because you're mine, I walk the line"

Johnny Cash (RIP)

"Elliot Nesterman" <ell...@inch.com> wrote in message
news:YxwRb.876$Wh...@prv-forum2.provo.novell.com...

[Elliot Nesterman]

So I thought, up until last night. Now it looks different.
I can telnet to port 25 and manually send an email to the GWIA. The
message never turns up in the post office.
Here's a telnet session:
*****
220 lancelot.mbooth.com GroupWise Internet Agent 5.5.7.1 Ready (C)1993,
1999 Novell, Inc.
helo merlin
250 lancelot.mbooth.com Ok
mail from: ell...@inch.com
250 Ok
rcpt to: ell...@mbooth.com
250 Ok
data
354 Enter mail, end with "." on a line by itself
from: elliot
to: elliot
subject: test
testing testing testing
.
250 Ok
quit
221 lancelot.mbooth.com Closing transmission channel
*****
But this email never gets to my mailbox.
All the groupwise parts seem to be loaded. And mail from inside the
house goes out onto the Internet normally.

How's that fro a conundrum?

Elliot

Michael Bell wrote:
> Nope, but this is not GW related. This has to be a DNS issue.
>
>
>

--

[Michael Bell]

It's probably going to GWIA\GWPROB, possibly.

Are you sure the foreign ID, etc is set for this gwia?

--
Michael J. Bell
Novell Support Connection Volunteer Sysop
Author of Guinevere (http://www.openhandhome.com)

PLEASE: Do not e-mail me privately unless specifically asked.
I'm a volunteer, not a Novell employee!

All opinions and advice provided are MINE alone and NOT Novell's unless
specifically identified as such.

Novell does not officially monitor these forums.
Enhancement requests for all Novell products may be made at
http://support.novell.com/enhancement

"You've got a way to keep me on your side/You give me cause
for love that I can't hide/For you I know I'd even try to
turn the tide/Because you're mine, I walk the line"

Johnny Cash (RIP)

"Elliot Nesterman" <ell...@inch.com> wrote in message

news:CPPRb.1703$Wh....@prv-forum2.provo.novell.com...

[Elliot Nesterman]

Nope. There's nothing in GWPROB. Also, foreign ID is set.

Turns out one of the problems was that there was no route.cfg. GWIA was
resolving the primary MX via DNS and trying to send to itself
externally; and with the main line down it couldn't, so we were seeing
many 450 errors. Also, I got on the horn with Nick Braak and he looked
at our config files and made a couple of small changes. After another
reboot things seem to have straightened themselves out.

But we still have no idea what precipitated this condition.

Thanks for the suggestions,
Elliot.

Michael Bell wrote:
> It's probably going to GWIA\GWPROB, possibly.
>
> Are you sure the foreign ID, etc is set for this gwia?
>

--