[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [vps-mail] Back to the maybe_spam folder topic
- Subject: Re: [vps-mail] Back to the maybe_spam folder topic
- From: Brian Haines <providertalk@xxxxxxxxxxxxxxxx>
- Date: Sat, 6 Mar 2004 09:39:55 -0700 (MST)
PS. I have installed the latest SA V 2.63 and the procmail file I am changing is /etc/procmail
For clarification $HOME expends to what is root for me when I log into a VPS, or is it still /usr/local/<MAIN_ID>/ which is the same thing, but I guess some things have to be run through the later to get proper permissions?
#Hey, I use a Windows PC every day, and I don't know much more about it - he says medestly.
Brian
On Mar 06 09:28, Brian Haines <providertalk@xxxxxxxxxxxxxxxx> wrote:
>
> Subject: Re: [vps-mail] Back to the maybe_spam folder topic
>
> Okay, I am on a VPS1 and so I think $HOME is the main login of the VPS.
>
> I have the default SA stuff in procmail and I can see that it delivers SPAM to "/var/mail/spam" as I instructed during instalation.
>
> So do I need to CHANGE this: //Rather than just add a rule?
> :0:
> * ^X-Spam-Status: Yes
> /var/mail/spam
>
> to this:
> :0
> * ^X-Spam-Status: Yes, hits=\/[0-9\.]+
> {
> :0:
> * $ -${MAXSPAM}^0
> * $ ${MATCH}^0
> /var/mail/spam
>
> :0:
> /var/mail/maybespam
> }
>
> assuming I want to check spam and maybespam via iManager?
>
> I am thinking that as long as I don't get any false+ in "/var/mail/spam" then I can later change that to "dev/null" and forget about it.
>
> I am very green, so if i am really messing up please comment.
>
> Thanks!
>
> Brian
>
> On Mar 05 11:48, Scott Wiersdorf <scottw@xxxxxxxxxxxx> wrote:
> >
> > Subject: Re: [vps-mail] Back to the maybe_spam folder topic
> >
> > On Thu, Mar 04, 2004 at 07:38:15PM -0500, Brian Haines wrote:
> > > Now, the questions I have about the maybe_spam folder are...
> > >
> > > 1. Is "$HOME/maybe_spam" the same location as "/usr/home/maybe_spam" on the
> > > file system?
> >
> > No. Procmail expands $HOME to be the home directory of the current
> > UID (i.e., $HOME/maybe_spam => /usr/home/<username>/maybe_spam). If
> > this kind of recipe appears in /usr/local/etc/procmailrc (on a VPS v2)
> > it should certainly appear after a DROPPRIVS=yes.
> >
> > > 2. This is straight procmail, rather than SA. I have no other procmail
> > > rules, but I know SA has some. Where should the rule be placed in the
> > > procmail file?
> >
> > This kind of rule should be placed after SA has had a chance to mark
> > it up. The X-Spam-Status header is applied by SA, so any procmail
> > rules that depend on that header being there should appear after the
> > SA markup rule.
> >
> > > Sorry for such academic questions - I have not been keeping up with my VPS
> > > accounts as I should, and I am always feeling like I am relearning.
> >
> > Procmail config files are different than a typical configuration file
> > in that order means everything. They're really not configuration files
> > as they are rule files, and the rules are applied in order as if the
> > incoming email messages were flowing down from the top to bottom of
> > the rc file.
> >
> > Scott
> > --
> > Scott Wiersdorf
> > scottw@xxxxxxxxxxxx
> > ======================================================================
> > This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/>
> > Before posting a question, please search the archives (see above URL).
> >
> >
> ======================================================================
> This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/>
> Before posting a question, please search the archives (see above URL).
>
======================================================================
This is <vps-mail@xxxxxxxxxxxx> <http://www.perlcode.org/lists/>
Before posting a question, please search the archives (see above URL).
Main Index |
Thread Index