Re: [vchkpw] Re: Feature for vdelivermail
Hi Robin,
Zitat von Robin Bowes [EMAIL PROTECTED]:
As someone has already replied, maildrop can do this for you.
This sort of code does not belong in vdelivermail.
Yeah,
that mail was too late. I've seen it a few minutes after my last mail
:D. Some other question: Why maildrop doesn't executes the following
lines:
snip
`maildirmake $HOME/Maildir/.SPAM`
`chown -R vpopmail.vchkpw $HOME/Maildir/.SPAM`
/snip
Here is my complete mailfilter file:
snip
import EXT
import HOST
import HOME
HOME=$HOME/$EXT
if (/^X-Spam-Flag: *YES/)
{
`test -d $HOME/Maildir/.SPAM`
if ($RETURNCODE == 1)
{
`maildirmake $HOME/Maildir/.SPAM`
`chown -R vpopmail.vchkpw $HOME/Maildir/.SPAM`
}
to $HOME/Maildir/.SPAM/
}
to $HOME/Maildir/
/snip
Regards
Christoph
RE: [vchkpw] Re: Feature for vdelivermail
I don't believe you need the HOME=$HOME/$EXT line. $HOME should point
to the user directory containing Maildir.
I've had problems with maildrop when I first set things up. It was like
indentation had to be a certain way or something. Of course, it could
just be that while changing indentation I fixed something else.
I would put both commands on the same line.
Again, here's the way I do it and it works. Not sure about the changes
you made or why. You don't need the whole path when testing for the
.SPAM folder. Everything can be relative to where the maildrop script
is run from.
Also, check your logs. Maildrop errors will show up.
import EXT
import HOST
import HOME
import FROM
MAILDIRQUOTA=`~vpopmail/bin/vuserinfo -q [EMAIL PROTECTED]
if ((/^X-Spam-Flag:.*YES/))
{
`test -d ./Maildir/.SPAM`
if( $RETURNCODE == 1 )
{
`maildirmake ./Maildir/.SPAM;chown -R vpopmail.vchkpw
./Maildir/.SPAM`
}
to ./Maildir/.SPAM/
}
to ./Maildir/
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 03, 2006 8:22 AM
To: vchkpw@inter7.com
Subject: Re: [vchkpw] Re: Feature for vdelivermail
Hi Robin,
Zitat von Robin Bowes [EMAIL PROTECTED]:
As someone has already replied, maildrop can do this for you.
This sort of code does not belong in vdelivermail.
Yeah,
that mail was too late. I've seen it a few minutes after my
last mail :D. Some other question: Why maildrop doesn't
executes the following
lines:
snip
`maildirmake $HOME/Maildir/.SPAM`
`chown -R vpopmail.vchkpw $HOME/Maildir/.SPAM` /snip
Here is my complete mailfilter file:
snip
import EXT
import HOST
import HOME
HOME=$HOME/$EXT
if (/^X-Spam-Flag: *YES/)
{
`test -d $HOME/Maildir/.SPAM`
if ($RETURNCODE == 1)
{
`maildirmake $HOME/Maildir/.SPAM`
`chown -R vpopmail.vchkpw $HOME/Maildir/.SPAM`
}
to $HOME/Maildir/.SPAM/
}
to $HOME/Maildir/
/snip
Regards
Christoph
RE: [vchkpw] Re: Feature for vdelivermail
Zitat von Charles J. Boening [EMAIL PROTECTED]: I don't believe you need the HOME=$HOME/$EXT line. $HOME should point to the user directory containing Maildir. The first error was, that maildrop has forgotton the username. So HOME=$HOME/$EXT ends in the absolute path to the maildir for me. I've had problems with maildrop when I first set things up. It was like indentation had to be a certain way or something. Of course, it could just be that while changing indentation I fixed something else. I would put both commands on the same line. I've tried it with one line and other variants. I printed out the commands an tried it manually on the commandline - everything works fine. When I try to call these commands from inside the mailfiler - nothing happens even not, when I try to call TEST=`ls`. Again, here's the way I do it and it works. Not sure about the changes you made or why. You don't need the whole path when testing for the .SPAM folder. Everything can be relative to where the maildrop script is run from. I've allready tried it with relative paths. The same error shows up... Also, check your logs. Maildrop errors will show up. Yeah, I get the maildrop:_Unable_to_create_a_dot-lock. error because the target Maildir doesn't exists. Thanks for any help. Regards Christoph
RE: [vchkpw] Re: Feature for vdelivermail
Make sure you check permissions on the mailfilter file. Should be vchkpw.vpopmail and chmod 600 One thing you can do is echo out information to a temp file as you're running. `echo $HOME /tmp/home.txt` I think that should work. May help in debugging. Are you running the latest version of maildrop? This seems to be turning more into a maildrop discussion than a vpopmail discussion. Email me direct and we can continue the discussion. Charlie -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 03, 2006 8:42 AM To: vchkpw@inter7.com Subject: RE: [vchkpw] Re: Feature for vdelivermail Zitat von Charles J. Boening [EMAIL PROTECTED]: I don't believe you need the HOME=$HOME/$EXT line. $HOME should point to the user directory containing Maildir. The first error was, that maildrop has forgotton the username. So HOME=$HOME/$EXT ends in the absolute path to the maildir for me. I've had problems with maildrop when I first set things up. It was like indentation had to be a certain way or something. Of course, it could just be that while changing indentation I fixed something else. I would put both commands on the same line. I've tried it with one line and other variants. I printed out the commands an tried it manually on the commandline - everything works fine. When I try to call these commands from inside the mailfiler - nothing happens even not, when I try to call TEST=`ls`. Again, here's the way I do it and it works. Not sure about the changes you made or why. You don't need the whole path when testing for the .SPAM folder. Everything can be relative to where the maildrop script is run from. I've allready tried it with relative paths. The same error shows up... Also, check your logs. Maildrop errors will show up. Yeah, I get the maildrop:_Unable_to_create_a_dot-lock. error because the target Maildir doesn't exists. Thanks for any help. Regards Christoph
