Good evening, Linda,
        I'm pretty sure linktel and Mike aren't interested in this, so 
CC's trimmed.

On Tue, 27 May 2003, L. Walsh wrote:

[snip]
>       I'll have to note that he got alot more response than my message
> (below)
> did.  I've had problems because "something" is rewriting the envelope "From "
> (not "From:") line that is tagged to the front of the message.  As a result
> my normal mail filtering scripts are only half working and I still haven't

        So when you disable spamassassin, the headers are written 
correctly?

> even figured out how Spamassassin is being called.  I see a directory added

        That completely depends on the MTA; sendmail uses procmail which 
can then call spamassassin.  Others use milters.  qmail can patch spamc 
right into the entry point, etc...

> under /etc/mail for spamassassin -- is that all it takes to add something
> to a sendmail config?  any directory added gets processed for .cf files?

        Sendmail's configuration is handled completely separately.

        All the files in /etc/mail/spamassassin get automatically called 
for spamassassin configuration.

> How does it know where to look for binaries?  I can't see any config files 

        spamassassin (in a simple sendmail environment) gets called from 
/etc/procmailrc or ~/.procmailrc .  Those files search the patch (or 
specify a full path to) spamc/spamassassin.

> specifying what to call.  My .forward file still only references my mail
> filter, so where / how does SA get called? 

        Sendmail on Linux generally calls procmail automatically; if you 
have a .procmailrc in your home directory, procmail uses that to decide 
where to put the message.  Otherwise it's sent to 
/var/spool/mail/{username} .

>        I did my install by doing an install of the SA module under perl, and
> that seems to have installed it and turned it on as well.  I don't even know
> how to configure it fully yet -- so I certainly didn't want to turn it on.
> 
>       My normal method -- install SW -- read documentation that is installed
> with the SW, then configure SW and turn SW 'on'.  I'm not used to sw that
> turns 
> itself on just by installing it -- except maybe vendor supplied RPM packages
> --
> but even then they'll often tell you to go configure something first, then
> turn the package on when things are setup the way you want them.

        I have a tutorial on setting up spamassassin at 
http://www.stearns.org/doc/spamassassin-setup.current.html

>       But the civil approach to asking a question seems to get alot less
> attention:

        Apparently nobody knew the answer off the top of their heads.  I 
spent an hour looking for what I though might be an answer to your 
question and came up dry.
[snip]
        Cheers,
        - Bill

---------------------------------------------------------------------------
        "return(ECRAY); /* Program exited before being run */"
        -- Martin Mares <[EMAIL PROTECTED]>
--------------------------------------------------------------------------
William Stearns ([EMAIL PROTECTED]).  Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at:   http://www.stearns.org
Linux articles at:                         http://www.opensourcedigest.com
--------------------------------------------------------------------------



-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk

Reply via email to