Les Mikesell wrote: > > All programs are like programming... What does that have to do with how they are configured? The difference is that with most of > the others, the distribution provides something that works so you don't > have to rewrite the programming yourself. That is because they use more rational configuration method. Maybe if Sendmail did as well, it could be treated the more like other services. The fact that sendmail's > macro language permits you to add unique operations is a feature, but > unless you need something unique (rare in a service with a standard > specification...) you shouldn't have to modify anything at that level. > This is the key - services with standard specifications. Sendmail is non-standard when compared to other services. So why should it be treated like other services. Or are you saying that there should be a configuration program that directly modifies sendmail.cf? If you want a mail program that can be configured like other services, then you need a mail server that is configured like other services. You keep harping that Sendmail should accept incoming mail by default, but you never give a valid reason why that should be the default. Everything I hear comes back to "That is the way I use it, so it should be configured that way." What you can't seam to grasp is that your setup will work for maybe 1% of the users. The shipped default probably works for 45% of users, and no other configuration is going to work for more then 5% of users. So we should increase the security risk for 45% of the users so that 1% of the users do not have to change the configuration? Mikkel -- Do not meddle in the affairs of dragons, for thou art crunchy and taste good with Ketchup!
