Re: [SLE] Sendmail Woes (Help?)

If you get the answer to this question, would you please email me because I have the same exact problem! Thanks, Brandon Caudle -------------- 15yr Old Avid Unix User (HP-UX,FreeBSD,Linux) Larkhaven Golf Course Charlotte, NC "There cannot be a crisis next week. My schedule is already full." -- Henry Kissinger

From: David Grove Reply-To: pete@petes-place.com To: suse-linux-e@suse.com Subject: [SLE] Sendmail Woes (Help?) Date: Thu, 20 Sep 2001 22:26:50 -0400

I'm seeing two apparently but synchronous (started at the same time) problems, beginning last night. Last night I added two users. This should have had no effect on sendmail. However, that's about the time these problems started.

I host multiple sites on a SuSE 7.2 server (90.0.0.2) running sendmail behind a WinNT (yeah, eek) firewall (90.0.0.1). /etc/mail/access has the appropriate RELAY directives, but doesn't have a RELAY from 90.0.0.1 (for obvious reasons, if I did, anyone connecting to 90.0.0.1 could send mail). My workstation is 90.0.0.7. I'm not sure how it works, but in the past sendmail has been able to see past the messages coming through 90.0.0.1 and see the original sender's IP.

The first message is:

Sep 20 22:21:37 camel popper [12314]: pete at eagle.petes-place.com (90.0.0.7): - ERR [SYS/TEMP] POP authentication DB not available (user pete): No such file or directory (2) [pop_apop.c:206]

I've run /etc/init.d/sendmail restart. I've rebooted (yeah, but it doesn't hurt). I've done the 'makemap hash access < access' and newaliases steps all the way through and I've run SuSEconfig. What file is this thing complaining about?

The second message is (and one that's really painful, please help):

Sep 20 22:26:00 camel sendmail [123455]: f8L2Pxpl...: ruleset=check_rcpt, arg1=, relay=pete@llama.petes-place.com [90.0.0.1], reject 550 5.7.1 ... relaying denied

Now, I understand about the relaying denied message. But I don't understand why it's there in this case, especially out of the blue, especially after it's worked for more than two years with this kind of setup. Every IP that should be allowed to relay is in /etc/mail/access, as are all domains.

Something weird happened last night and I'm clueless. Anything you can think of? Might these two problems be related? (If so, if I screwed something up without realizing it, i'll alias that command to fortune -o...).

Oh, I did install a new version of my proxy software a few days ago. I don't see that it's related but I'll certainly give it a think.

David

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq and the archives at http://lists.suse.com

_________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp