Mail, ISDN, issues...

[bedlam <bedlam@xxxxxxxxxxxx>]

I sent a long post to this list previously, but a valid member address was
necessary somewhere. I had had a Reply-To, but had lost that configuration
during other changes. 

Anyway, I want to thank (again) Tony Gettig and Adam Williams for their
time, consideration and words. This migration was easy, thanks to these two
pitching in with advice.

Speaking of advice.... ;)

Our mail and file serving is now handled by Linux. Some issues have cropped
up, though: our internet connection through ISDN is distressingly
intermittent. Ameritech and WMIS (the ISP) both say their sides are fine.

Now, Novell probably 'papered over' these problems more or less invisibly, 
while Debian and Exim complain, loudly. I think I shall have to ensure that 
Exim accepts mail from our 192.168.1. with an understanding that nameservice 
may not be up.

Yet... we have some undeliverable addresses. msn.net seems to be having
problems, among others. I can't find an MX entry. Is MS having problems?
Anyone else have no response to 'host -t mx msn.net'?

Basically, I have 4 mails with undeliverable addresses, msn.net and
state.mi.us. 

killdevil:02:21am:~# host -t mx state.mi.us
state.mi.us             MX      10 smtp-av1.state.mi.us
state.mi.us             MX      20 smtp-av2.state.mi.us
killdevil:02:21am:~# telnet state.mi.us 25
telnet: could not resolve state.mi.us/25: No address associated with
hostname
killdevil:02:22am:~# host -t mx msn.net
msn.net has no MX record (Authoritative answer)

Are these just given up for lost?