Carlos E. R. wrote:

The Monday 2003-12-01 at 13:25 -0900, John Andersen wrote:

...

SuSE installs it and runs it because you included it in the selections of packages you made when you installed. Furthermore, SuSE sets it up correctly. If it fails it must be something you did. ;-)

Mmmm... No, I have found bugs related to susehelp and apache on all versions of SuSE - at least, all of those I tried.

Thank you. I know that the default directory structure was not right when I tried it before modifying anything. -- Jim Sabatke Hire Me!! - See my resume at http://my.execpc.com/~jsabatke Do not meddle in the affairs of Dragons, for you are crunchy and good with ketchup.

Carlos E. R. wrote:

The Monday 2003-12-01 at 15:51 -0600, Jim Sabatke wrote:

...

I've been toying with my apache config files, and it seems that SUSE help runs just fine after removing all references to it.

No, that is not so. Help works without apache _only_ on kde, not outside.

...

I was just wondering if I'm breaking something that I don't know about, or if SUSE just installs and runs apache for no good reason.

It is installed because you requested it - it is not a default package. Try to remove apache with yast and see if it complains or some other package depends on it.

I wonder which version of SuSE this happens on, I vaguely remember something like that on a previous version, but not 8.2 or 9.0, i.e there is no /usr/local/httpd. It may not be a SuSE package that was installed as all I've seen so far use /srv/www/ and /etc/httpd. Regards Sid. -- Sid Boyce .... Linux Only Shop.

Jim Sabatke wrote:

Sid Boyce wrote:

...

Carlos E. R. wrote:

...

The Monday 2003-12-01 at 15:51 -0600, Jim Sabatke wrote:

...

I've been toying with my apache config files, and it seems that SUSE help runs just fine after removing all references to it.

No, that is not so. Help works without apache _only_ on kde, not outside.

...

I was just wondering if I'm breaking something that I don't know about, or if SUSE just installs and runs apache for no good reason.

It is installed because you requested it - it is not a default package. Try to remove apache with yast and see if it complains or some other package depends on it.

I wonder which version of SuSE this happens on, I vaguely remember something like that on a previous version, but not 8.2 or 9.0, i.e there is no /usr/local/httpd. It may not be a SuSE package that was installed as all I've seen so far use /srv/www/ and /etc/httpd. Regards Sid.

I've been using SuSE for over 5 years and I had never touched the apache config files until a month ago, so I don't know when it was initially loaded. I'm running 7.3 right now and I don't have a /srv/www. The file /etc/httpd/httpd.conf configuration wouldn't properly run either suse help or the test home page in /usr/local/httpd/htdocs until I modified it.

AHA! 7.3, that figures, it was around then .... it definitely installed in /usr/local/httpd, but I can't remember if it was installed by default, it probably was. Regards Sid. -- Sid Boyce .... Linux Only Shop.

poeml@cmdline.net wrote:

Hi,

On Mon, Dec 01, 2003 at 08:30:09PM -0600, Jim Sabatke wrote:

...

Sid Boyce wrote:

...

I wonder which version of SuSE this happens on, I vaguely remember something like that on a previous version, but not 8.2 or 9.0, i.e there is no /usr/local/httpd. It may not be a SuSE package that was installed as all I've seen so far use /srv/www/ and /etc/httpd. Regards Sid.

I've been using SuSE for over 5 years and I had never touched the apache config files until a month ago, so I don't know when it was initially loaded. I'm running 7.3 right now and I don't have a /srv/www. The file /etc/httpd/httpd.conf configuration wouldn't properly run either suse help or the test home page in /usr/local/httpd/htdocs until I modified it.

The move from /usr/local/httpd to /srv/www came with SuSE Linux 8.1.

Peter

To address the real question, SuSE installs apache because very few people do not need it and the "Why doesn't ......" emails would overwhelm the lists. For those that do not need it, a simple "rpm -e apache" and its dependants will cure that in 5 minutes. Regards Sid. -- Sid Boyce .... Hamradio G3VBV and keen Flyer Linux Only Shop.

poeml@cmdline.net wrote:

On Sat, Dec 13, 2003 at 07:30:08PM +0000, Sid Boyce wrote:

...

To address the real question, SuSE installs apache because very few people do not need it and the "Why doesn't ......" emails would overwhelm the lists. For those that do not need it, a simple "rpm -e apache" and its dependants will cure that in 5 minutes.

I don't quite understand: Apache is not installed in any default package selection. You get it only when you specifically choose the webserver software selection. This must be a misunderstanding :^}

A long time ago, apache was in the default selection because the susehelp was based on it. But that's at least 2 years ago.

Peter

And that answers the original question. I've been doing updates for about 5 years and wondered why it was installed, and why its configuration didn't work right when I finally tried to use it a couple months ago. A fresh install of 9.0 and "intentionally" installing it yielded a configuration that did work properly. -- Jim Sabatke Hire Me!! - See my resume at http://my.execpc.com/~jsabatke Do not meddle in the affairs of Dragons, for you are crunchy and good with ketchup.

The Monday 2003-12-01 at 20:21 -0600, Jim Sabatke wrote: You emailed direct to me:

Date: Mon, 01 Dec 2003 20:18:08 -0600 From: Jim Sabatke To: Carlos E. R. Subject: Re: [SLE] Why does SUSE install apache?

But your server rejects my emails: |> : host *.voyager.net[216.93.*.*] said: 550 5.7.1 *** |> We do not accept spam *** (in reply to MAIL FROM command) I'm certainly no spammer - please correct that if you intend to send and receive direct emails from me.

Carlos E. R. wrote:

...

The Monday 2003-12-01 at 15:51 -0600, Jim Sabatke wrote:

...

...

It is installed because you requested it - it is not a default package. Try to remove apache with yast and see if it complains or some other package depends on it.

I don't believe I ever installed it. It's been hanging around through a lot of upgrades. Somewhere around 6.0 I asked the same question and the answer here was that SUSE help needed it and I shouldn't uninstall it.

It was installed by default around that version, I think. Later (7.x) it was thought that the help gadget in kde worked sufficiently well not to need apache. However, it is needed if you need susehelp outside kde: for example in text mode, gnome, etc.

It really doesn't matter now. I do want it installed now as I'm building an intranet. I suppose the conflicted directories (which I did NOT do) may be an artifact of many upgrades.

That may easily be - or simply, you no longer remember :-) -- Cheers, Carlos Robinson

The Wednesday 2003-12-03 at 08:50 -0600, Jim Sabatke wrote:

...

|> : host *.voyager.net[216.93.*.*] said: 550 5.7.1 *** |> We do not accept spam *** (in reply to MAIL FROM command)

I'm certainly no spammer - please correct that if you intend to send and receive direct emails from me.

No, you are not a spammer. Actually, I don't have any program to send reject notices. My only spam control is the Mozilla filter, and I don't believe it rejects anything. I will send a note to my ISP to ask what's going on.

I had no idea this was happening. I'm very sorry.

Thanks! I could send you the full text, but it would be probably be rejected. Maybe they are rejecting my IP, wich is not fixed and belongs to a pool. It is known that spammers do use dial-up access, but rejecting a range of IPs is unfair. They should use some other method, a scoring method like spamassassin or who knows what. -- Cheers, Carlos Robinson

The Wednesday 2003-12-03 at 22:45 -0600, Jeffrey L. Taylor wrote:

An increasing number of e-mail servers will not accept messages from dynamic IPs.

If I were a millonaire with bagfull of lawyers I probably would sue them :-p

I route these domains thru my ISP's SMTP server. In Postfix, add an entry like this to your transport map:

example.com smtp:[smtp-server.myISP.com]

Impossible. The ISPs refuse to handle email with a "from" of another ISP. I have several adresses, each of a different ISP (and some of no ISP, like ieee.org), and each one has its own server which rejects emails that should be handled by another provider. I would need a rule for postfix matching both origin and destination before selecting a transport route. Such a thing does not exist in suse 8.2 Not to talk about the quality of the providers SMTP servers... for instance, some do not report 'failure to deliver' to the originator, that's why I started to send mail by my own means time ago. -- Cheers, Carlos Robinson

The Friday 2003-12-05 at 22:08 +0100, James Mohr wrote:

<SNIP>

...

Impossible. The ISPs refuse to handle email with a "from" of another ISP. I have several adresses, each of a different ISP (and some of no ISP, like ieee.org), and each one has its own server which rejects emails that should be handled by another provider.

I would need a rule for postfix matching both origin and destination before selecting a transport route. Such a thing does not exist in suse 8.2

Not to talk about the quality of the providers SMTP servers... for instance, some do not report 'failure to deliver' to the originator, that's why I started to send mail by my own means time ago.

Just to be clear on this, that's entirely a configuration/programming issue and nothing absolute about it. My ISP accepts and sends email from me although the from: address is in a completely different domain. I just need to authenticate myself when I send.

I have never configured it myself, but from what I have seen postfix supports SMTP AUTH.

Right, I tried that and it works. I use it for one server that needs auth even to send email destined for his domain...

So, if the ISP supports it, then there should be no reason why you could not do the same thing I do with Kmail. Or am I missing something?

It depends on the provider. Some just use "pop before smtp". Some require that your IP belongs to a certain range. Some will reject a different "from" address even after authentication. What you say it is easy enough to use with programs that, like mozilla, handles sending on its own, and sends mail from each account on a separate smtp server based on the "from" address. Postfix chooses transport based on destination. So, the steps would be: 1. define auth for smtp servers. 2.1 define transport for certain destinations that reject direct email to use a ISP server 2.2 choose ISP SMTP server based on from address. This can be done easily with mozilla, but not with postfix. -- Cheers, Carlos Robinson