Ok, Bob was right about hearingsociety.org dns entry being wrong since it is in hearing.org zone. So, I don't have a MX entry for hearingsociety.org pointin to my server. So somehow, mail for hearingsociety.org e-mail from the intranet is being put in the queue and not being delivered when I had these connection problems; however, I've watched network activity and e-mail headers, and intranet mail isn't going to theo utside work and then being brought back to the intranet. When I telnet to the server 25 I get: 220 hearingsociety.org ESMTP Sendmail 8.9.3/8.9.3; Wed, 6 Sep 2000 14:50:54 -0700 and sendmail.cw has hearingsociety.org so why is it queuing mail for hearingsociety.org? And how come it is working in the queu even with bad dns MX records? Thanks for all the help and info, Ben On Wed, 6 Sep 2000, Adam Maloney wrote: > Well, make sure you have something on the network doing name resolution > for your hostnames and IP's (be it DNS or /etc/hosts). Sendmail will > probably try to do lookups on the client when it gets the SMTP connection. > > If it's queueing the messages for that domain when they should be > delivered locally, then that's the whole problem. sendmail -q won't work > because you /want/ them delivered locally, not queued. If they're queued > that means that sendmail doesn't think they should be delivered locally so > it'll try to find an MX for the remote mailserver. > > Adam Maloney > Systems Administrator > Sihope Communications > > On Wed, 6 Sep 2000, Ben Luey wrote: > > > > Wouldn't Sendmail accept the mail locally, regardless of the MX, if the > > > domain is in it's cW? > > > > I totally forgot about that. Here's the setup: > > > > Clients use local server "server" as pop/imap/smtp server. This machine > > has sendmail.cw with hearingsociety.org in it to it accepts mail for that > > domain. Does this mean that dns shouldn't accept anything (assuming server > > can be resolved to 192.168.1.1?) What I'm trying to understand is why when > > I took down the ppp0 link (which wasn't working) so there would be no > > outside route to the internet and hopefully dns would fail quickly -- > > something, maybe dns was very slow and users sending mail to server:25 was > > very slow. Shuttind down named spend things up a lot (I'm guess that the > > win95 clients cached server->192.168.1.1), but no internal mail messages > > were being delivered even when I did a sendmail -q -- adding > > hearingsociety.org into /etc/hosts fixed the problem. I don't really > > understand it, except that it works when the link is up, but I'd like some > > internal tolerance to looking our internet connection. > > > > > > > > > > > > > > > > > > I thought the logic was something like, it does some address munging > > > in S3 and then decides what mailer to use based on the domain. Only > > > if the mailer comes up as SMTP or ESMTP (not local) then it will do > > > the MX lookup to find out where to send it. If it's a local domain > > > (in sendmail.cw or the W class in the sendmail.cf) it should just > > > deliver it locally without DNS. > > > > I think that is how I set it up -- sendmail accepts mail for hearing.org > > and hearingsociety.org (I assume doing local delivery since it is in the > > sendmail.cw) and relays for address in our intranet. Or so I thought until > > these weird slow downs and queueing but not delivering when the link went > > down. (slow down not from cpu or memory, I checked) > > > > Thanks, > > > > > > Ben > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org > > For additional commands, e-mail: tclug-list-help at mn-linux.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org > For additional commands, e-mail: tclug-list-help at mn-linux.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org For additional commands, e-mail: tclug-list-help at mn-linux.org