On Mon, August 4, 2008 2:19 pm, Scott Ragen wrote: > [EMAIL PROTECTED] wrote on 29/07/2008 07:15:47 AM:
> One could argue that either server is incorrectly configured. I suspect > the receiving email server is checking if the sending email is valid in an > attempt to stop spam. You could just alias apache@ to your (or another > valid) email address, and that should stop the problem. thanks, Scott, everyone sorry for 'suspicious' headers, I tend to get it on regular basis perhaps someone is trying to tell me something... the email procedure picks 'apache' as the httpd user, there is a directive to provide a desired email address instead, but, when I tried to apply it, it didn't seem to work, I most likeley mis-applied it, or, there was some other pre-req required for this to work. that was some time ago, and, I never went further to resolve it, as it didn't seem to cause any real issues (till now...) I guess I should really go back to fix up the Apache directive, and, try to fix that... meanwhile, the ISP addedd the offending address to his exemption list. -- Voytek -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
