Re: softdnserror problem
Quoth "Chris Garrigues": > --==_Exmh_841381948P > Content-Type: text/plain; charset=us-ascii > > > From: Joel Uckelman <[EMAIL PROTECTED]> > > Date: Wed, 06 Jun 2001 14:15:11 -0500 > > > > Furthermore, the IP that shows up in the header when it's working is a > > local IP---192.168.254.101---which it should find in /etc/hosts without > > needing to resort to DNS. The lookup order in /etc/host.conf has hosts > > before dns, so it should be looking there first. > > Red Herring. qmail (and most MTAs, I believe) only use the DNS and never loo > k > in /etc/hosts. > > Is it possible that this is your issue? Try checking things out with dig or > nslookup. > > Chris That's good to know; I'm glad it's now "documented" (heh!) on the net. I'd be willing to bet having this list archived on the web answers 90% of people's questions, actually. (I know I find answers to most of mine that way!) Anyhow, what you and Mr. van Dijk mentioned suggested to me how I might fix the problem. I spent a few minutes reading the manual for BIND 9 (which I switched to from 8 last week), and discovered a rather neat feature called "view". I set up two different views, one for my local network and my static IPs, and one for the rest of the world, and then put a zone file for 254.168.192.in-addr.arpa in the former but not the latter. That way, qmail can resolve my local IPs to real domain names, and anything else that does reverse lookups on my domain names will get my world-recognized static IPs. Problem sovled. What still perplexes me is why qmail sometimes gave me the "softdnserror" header and other times gave me one with a local IP address when using my old DNS configuraiton. Based on what I know now, I don't see why I ever got anything but "softdnserror" headers, actually! Of course, I don't *need* an explanation for this now, but I'm still curious. Chalk another one up to the vagaries of networking, I guess. Thanks, guys. :) -- J.
Re: [OT] qmail & php
Quoth "Bill Andersen": > OK, I hate to go back "on list" with this, but since I got about > 30 replies, it's easier to go back to the list then to reply to each > of you. THANKS for all the replies though. > > Almost all the replies were "did you set up links to qmail's sendmail > wrapper"... Yes! I've had qmail running for 6 months without any > problems. Followed LWQ to the letter and have since re-verified the > links are in place... > > [bill@mail bill]$ cd /usr/lib > [bill@mail lib]$ ls -l sendmail > lrwxrwxrwx1 root root 23 Jun 3 11:25 sendmail -> > /var/qmail/b > in/sendmail > [bill@mail lib]$ cd /usr/sbin > [bill@mail sbin]$ ls -l sendmail > lrwxrwxrwx1 root root 23 Jun 3 11:25 sendmail -> > /var/qmail/b > in/sendmail > > I even did the following: > > 1) Stopped qmail and removed the symlinks > 2) Installed sendmail (from RPM) > 3) Did a complete install (./configure , make, make install) for >both PHP and Apache (per their instructions) > 4) Uninstalled sendmail using RPM > 5) Re-create the symlinks to "qmail's sendmail" > 6) Restarted qmail (actually restared the machine, qmail's working) > > STILL, get the error: "mail() is not supported in the PHP build" > > The only thing I haven't tried is the suggestion from Michael Geier below. > Nothing personal Michael, but Hell, I don't want to have to start from > scratch... surely I don't need to re-install Linux! > > Anybody else? > > Bill > > (OK, back to "off list" mode!) Hi, I've been using a PHP build from the source RPM on my box for a while without any problems, though admittedly I haven't been doing anything that would use the mail() function, so I might actually have the same problem you do, I just don't know. Of course, my telling you that helps you not at all, so here's my suggestion: (1) Test to see if the mail() function works with sendmail installed. I know that involves some work, but maybe it's just broken in the version of PHP you have. (2) If you've done (1) and found that mail() works, leave sendmail installed, but just delete all of the sendmail binaries (so nothing can be run) and put the symlinks back, etc. That way, all of the sendmail libraries are still there and hopefully PHP will stop complaining. Admittedly, this is an ugly solution, but it *might* work if you can't fix it any other way. -- J.
Re: softdnserror problem
Quoth Peter van Dijk: > On Wed, Jun 06, 2001 at 02:05:54AM -0500, Joel Uckelman wrote: > [snip] > > But I still get the softdnserror header when sending mail from charybdis to > > > scylla, and I know this wasn't happening yesterday. > > > > Any ideas about what's going on here? I'm stumped. > > My wildest guess is that the resolver listed in /etc/resolv.conf is > broken. > > Greetz, Peter. [Sorry, Peter, I'd meant to send this to the list, not just you.] Hmmm. That seems weird, since the only nameserver I have listed is mine, and it appears to be working. If it is broken, it must be something rather subtle, since I've had no trouble doing all sorts of DNS-heavy things like web surfing, and the few hundred messages my mail server handles daily all seem to be getting through. Furthermore, the IP that shows up in the header when it's working is a local IP---192.168.254.101---which it should find in /etc/hosts without needing to resort to DNS. The lookup order in /etc/host.conf has hosts before dns, so it should be looking there first. Does this give anyone an idea about what, specifically, is broken w/r/t the resolver? -- J.
softdnserror problem
Today I noticed an unusual delay when sending mail between two of my computers, along with something I'd never seen before in one of the Received headers. Quoted here is the relevant header: Received: from scylla.ellipsis.cx ([EMAIL PROTECTED]) by softdnserror with SMTP; 6 Jun 2001 06:15:47 - This would seem to indicate some sort of a DNS problem, I gather. Charybdis, the machine receiving the mail, is also my DNS server, which is working fine, as far as I can tell. Just now, when I tried to generate another example of the problem, I noticed that it seems to have fixed itself, at least for mail being sent from scylla to charybdis. The Received header I got this time is just like the ones I was getting before the problem started: Received: from scylla.ellipsis.cx ([EMAIL PROTECTED]) by 192.168.254.101 with SMTP; 6 Jun 2001 06:54:31 - But I still get the softdnserror header when sending mail from charybdis to scylla, and I know this wasn't happening yesterday. Any ideas about what's going on here? I'm stumped. -- J.
Re: why does qmail eat my From headers?
> [EMAIL PROTECTED] wrote: > > >Hmm. That is curious. I'm running 1.03, no patches. Is there any way I could > >have configured qmail to cause this? If not, do you have any > >suggestions about what could be happening here? > > Russ Nelson pointed out that fetchmail and sendmail had both had a > hand on the example message you posted. Both are notorious header > mungers. > > -Dave As you can see, it works now. Thanks, everyone, for the help. It appears that setting QMAILINJECT to 'f' solved the problem. As for what was actually the cause, I'm certain it wasn't fetchmail -- when I sent the same message to my roommate, the result was the same, despite that he uses Eudora. Secondly, everyone else's From's seem to be ok. I would be very strange if fetchmail altered my From's and no others. Again, thanks much for the help!
