* CJ Keist, 2008-08-07 22:58
Just to wrap this up.
[...]
Off-topic: CJ, unless you publish your PGP key on a public keyserver,
signing your e-mails is pretty much pointless. Without the public
part of your key, noone is able to verify that the signature is
actually correct. -> http://pgp.mit.e
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Just to wrap this up.
I think I found my problem. I'm running this on a test mail server in
engr.colostate.edu domain, but configuring the mail server to think it's
in engr2.colostate.edu. So the sieve plungin was trying to see if the
message was fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay,
Trying to do some debugging of the sieve code. So I have found that
it is failing on sending the reply in the following code area:
bc_eval.c
Line: 324
/* ok, we're willing to respond to the sender.
but is this message to me? that
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Timo,
I removed the ${1} variable but still no luck. I read the reasons
why deliver would not send a reply but I don't think any should be true.
Below is the header of one of the messages, let me know if you see
something that is causing sieve no
On Aug 6, 2008, at 1:57 PM, CJ Keist wrote:
My .dovecot.sieve file:
require ["vacation"];
if header :matches "subject" "*" {
vacation
:days 30
:addresses "[EMAIL PROTECTED]"
:subject "Automatic response to: ${1}"
"I'm away -- send mail to foo in my absen
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry if this comes in twice, I sent this first from my test account.
- -
Guys, I'm running out of hair to pull out ;).
Can anyone out there say that this does work?? To me this is looking
like a bug and I'm not sure whether it's the sieve
Guys, I'm running out of hair to pull out ;).
Can anyone out there say that this does work?? To me this is looking
like a bug and I'm not sure whether it's the sieve plugin or the dovecot
deliver program. I have also had no luck the the "reject" sending any
reply back to the sender.
My setup:
O
