At 09:29 PM 3/11/02, Alan Brown wrote: >On Mon, 11 Mar 2002, Daniel Senie wrote: > > > DRAC requires portmapper. So if you use up2date to try to load DRAC (and if > > the dependencies are properly set up in the drac RPM), you'll get a bunch > > of stuff you might not have wanted on your server. This is the one big > > danger with up2date. > >DRAC is a rpc service, so of course it needs portmaper. > > > I, for one, do NOT EVER run portmapper, NFS, YP or other such stuff on > > production servers unless absolutely necessary. I do have an alternate > > solution for SMTP-after-POP (which will get merged in to qpopper sometime) > > which does not rely on those components. > > >Can we _please_ get away from kludges like DRAC and POP-before-SMTP?
We have our customers using SMTP AUTH. >They both leave windows of opportunity for a resourceful spammer to get >in. > >It has been nearly 2 years since AUTH SMTP came out. It works, it's >secure and it's now widely supported. > >Concentrate development on that model T, instead of making better buggy >whips. > > >I'm going to make a similar statement about pop3: > >If you have users who want to leave some mail on the server or access >from multiple locations, they should be using IMAP. That was designed >for this scenario. > >I know the reasons for soldiering on with kludge solutions, but it >really is time to stop trying to drive in screws with a mallet. > >It may take a bit more time to get a working IMAP server running and to >get AUTH SMTP working, but the reduced support load will pay for itself >shortly afterwards. Well, we allow SMTP-after-POP to reduce our support load. We have some users who just don't get their stuff set up right no matter what. As for IMAP, that would also increase support costs. Users have a harder time understanding it. ----------------------------------------------------------------- Daniel Senie [EMAIL PROTECTED] Amaranth Networks Inc. http://www.amaranth.com
