Ok, I've changed some char[] declarations to unsigned char[]; gcc gives
me no warnings with -Wall, but I'm not sure that doesn't mean it's all
fine now.
Also, thanks a lot for the per-user install instructions -- I've added
them to the README.
C
On Fri, 2002-02-22 at 12:54, Erik B. Berry wrote:
> Craig Hughes wrote:
> > Sorry about that, I used to be much better about not using // and only
> > /**/, precisely for cc compatibility. I'll go through and fix all the
>
> This seems fixed in the latest CVS now. There are some unrelated
> compilation warnings, in case they are worth fixing:
>
> cc -O spamd/spamc.c \
> -o spamd/spamc -lsocket -lnsl -ldl -lm -lc -lcrypt
> "spamd/spamc.c", line 135: warning: argument #2 is incompatible with
> prototype:
> prototype: pointer to uchar : "spamd/spamc.c", line 91
> argument : pointer to char
> "spamd/spamc.c", line 137: warning: argument #2 is incompatible with
> prototype:
> prototype: pointer to const uchar : "spamd/spamc.c", line 113
> argument : pointer to char
> etc....
>
> > For personal installations, the Makefile should be able to read an
> > environment variable called PREFIX and install there. I think you'll
> > need to hand-edit SpamAssassin.pm after installation though to modify
> > where it's looking for config files. I'm not a perl installation
>
> I managed to get SA working for my personal account. I think it is
> easier
> for most novice users to supply a command line switch to determine the
> config
> file location (rather than editing Perl code), so I used that method.
> Feel
> free to edit and add this to the README if it would be useful to others:
>
> Installing SpamAssassin for Personal Use (Not System-Wide)
> ----------------------------------------------------------------
>
> These steps assume the following, so substitute as necessary:
> - Your UNIX login is "user"
> - Your home directory is /home/user
> - The location of the procmail executable is /usr/bin/procmail
>
> 1. Uncompress the SpamAssassin archive
>
> 2. Move/rename the created SpamAssassin directory where you want to
> permanently place it in your user directory:
> mv Mail-SpamAssassin-2.1 ~/bin/SpamAssassin
>
> 3. Make SpamAssassin as normal ("perl Makefile.PL", "make")
>
> 4. If you already use procmail, skip to step 6. If not, ensure procmail
> is installed using "which procmail" or install it from www.procmail.org.
>
> 5. Create a .forward file in your home directory containing the below
> lines:
>
> "|IFS=' ' && exec /usr/bin/procmail -f- || exit 75 #user"
>
> 6. Edit or create a .procmailrc file in your home directory containing
> the below lines. If you already have a .procmailrc file, add the lines
> to the top of your .procmailrc file:
>
> :0fw
> | /home/user/bin/SpamAssassin/spamassassin -P -c
> /home/user/bin/SpamAssassin/rules
>
> The above line filters all incoming mail through SpamAssassin and tags
> probable spam with a unique header. If you would prefer to have spam
> blocked and saved to a file called caughtspam in your home directory
> instead of passed through and tagged, append this directly below the
> above lines:
>
> :0:
> * ^X-Spam-Status: Yes
> caughtspam
>
> 7. Now, you should be ready to send some test emails and ensure everything
> works as expected. First, send yourself a test email that doesn't contain
> anything suspicious. You should receive it normally, but there will be a
> header containing X-Spam-Status: No. If you are only tagging your spam,
> send yourself an obvious spam mail and check to be sure it is marked as
> spam. If your test emails don't get through to you, immediately rename
> your .forward file until you figure out cause of the the problem, so you
> don't lose incoming email.
>
> _______________________________________________
> Spamassassin-talk mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
>
>
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
