Nope, no mx records here, see below. I'm not even sure what nameserver I'm using because this is DHCP to some broadband service. Comcast, I think (wireless at a friend's house). Probably that's the source of the broken-ness.
The other question is why fetchmail flushes mail off the server if local sendmail won't take it. Probably a feature not a bug but still, seems pretty harmful default behavior. I just lost two critical emails. mite:~: host -a umd.edu Trying "umd.edu" Host umd.edu not found: 4(NOTIMP) Received 25 bytes from 192.168.0.1#53 in 21 ms Judah Daniel Carter <[EMAIL PROTECTED]> wrote: > There is not an actual hostname for umd.edu assigned for a variety of > reasons, but there are MX records for umd.edu which is why everything works > fine. I have not seen a mailer before reject mail for this reason. If you > do a host -a you will see the MX records for it. > > -----Original Message----- > From: UM Linux User's Group [mailto:[EMAIL PROTECTED] On Behalf Of > Judah Milgram > Sent: Monday, January 15, 2007 8:58 AM > To: [email protected] > Subject: [UM-LINUX] "umd.edu" doesn't resolve? > > very odd thing ... I just lost two emails from someone with an [EMAIL > PROTECTED] > address > because sendmail couldn't resolve his domain: (name x'd to protect the > innocent) > > reading message [EMAIL PROTECTED]:3 of 23 (2354 header octets) > ..fetchmail: SMTP error: 553 5.1.8 <[EMAIL PROTECTED]>... Domain of sender > address [EMAIL PROTECTED] does not exist > flushed > reading message [EMAIL PROTECTED]:4 of 23 (2327 header octets) > ..fetchmail: SMTP error: 553 5.1.8 <[EMAIL PROTECTED]>... Domain of sender > address [EMAIL PROTECTED] does not exist > flushed > > a quick check: > > mite:~: host umd.edu > Host umd.edu not found: 3(NXDOMAIN) > > and verified it on another machine. That's can't be right - or?! Anyone > else having this sort of problem? Meanwhile, I turned on > accept_unresolvable_domains. > > Judah >
