[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vps-mail] Spamassassin VPS1/2 complete paper?



Abigail Marshall wrote:
Here's what worked for me - on a FreeBSD VPS1 (Server B):

% unlimit
% vcpan Net::DNS
Hi Abagail,

Yes I found that jewel in one of the threads and it *did* work.

What "bad things" are happening for you?  (I'm no expert,

During the make, error messages made me think something essential wasn't working. Going further with perl,

Makefile.PL
gmake test
virtual gmake install

Worked out, once I realized the error message on the last line was simply that gmake wasn't being found and needed to be linked in as written.

but the only bad thing that happened for me was running out
of memory) - everything else worked fine.

I was getting one memory error on one VPS1 server B (out of 4 running SA.) For the moment I dumped Bayes entirely AND cut the language tests until I have more time to watch it. This server is exceptionally busy. In fact, I just added spamcop and spamhaus and it is refusing about 15 connections/hour. There was an 80 meg spam file the customer never looked at!

I do think someone should assemble all the important instructions into a single tutorial. A lot of the stuff is crystal cxlear in the SA docs, all the variables and tweaks are well explained. What isn't is the complete theory of installing and whether to use daemons or not, etc. So far I am not, btw.

I have a VPS specific question:

I guess on Server B, there is only one user in regard to Bayes, right? But on VPS2pro, is this the same? Or, do the users need shell access to enable userlevel bayes control? I ask this because only the main user's bayes seems to work on VPS2.

thanks

RM

======================================================================
Technical questions regarding this list may be sent to
<vps-mail-owner@xxxxxxxxxxxx>. You may request an automated help
response by sending an email with the word 'help' (w/o quotes) in the
BODY of the message (subject is ignored) to <vps-mail-request@xxxxxxxxxxxx>.
======================================================================


Main Index | Thread Index
Match: Format: Sort by:
Search: