On Sat, 2002-02-02 at 23:17, marc lindahl wrote: > > I see instructions on how to build my own RPMs from the source, but I don't > see a link to any built RPMs, and didn't see them on the sourceforge ftp > site.... that's why I installed from source, what's the point of building > your own RPM and then installing it, if you're just doing one machine?
Le'see... The build and install are scripted, so you can't screw them up. Upgrades won't wipe out config files. You can choose to install parts of courier, rather than the whole things... There's plenty of good reasons. > >> 2. anyone have any idea (before I put this online) how effective the > >> 'require authorization' option is at stopping spam? > > > > It would be wise for you to actually read what that option does, instead of > > speculating. > > The only reference I could find among the somewhat scattered documentation > was http://www.courier-mta.org/install.html#esmtpauth which tells me that an > auth step (in my case PAM) similar to that used to check mail is performed > before sending mail. Seems like that would make it harder for my smtp to be > used as an unauthorized relay. Exactly. It's relay authentication. It has nothing to do with incoming SPAM (which your request sounded like you expected). If you *only* relay messages for people who authenticate, then spammers would have to sniff someone's password, or otherwise break into their account to use you as a relay. Relay authentication removes the need for pop-before-smtp, or other silly (and crude) hacks.
signature.asc
Description: This is a digitally signed message part
