Re: Sieve & LMTP
Hi Ken,On Jul 16, 2005, at 8:01 PM, Ken Murchison wrote:Did you activate the script? If you look in your sieve directory (sievedir option in imapd.conf hashed by userid), you should see a 'defaultbc. link pointing to '.bc'Well, it was activated, but there was some end user error. I had a wrong condition on my test script, but my MUA still had a rule set that was causing it to filter weirdly. So, I have that all taken care of. However, my test script also used the "notify" command, which doesn't seem to be working -- not a big deal, I don't really need it, but I was expecting it to do something *shrug*You definitely do NOT want to use deliver unless you absolutely have to. Deliver is just an LMTP client anyways, and adds an extra (possibly expensive) process (fork() + exec()) to the pipeline.That's what I thought. I just incorrectly thought it might be the only way to get sieve filtering working.Anyway, thanks for the help Ken. It's nice to see your still active here as your contributions have always been great.-- Kevin
Re: Sieve & LMTP
Kevin Menard wrote: Hello all, It's been a few years since I've posted here, so I hope everyone is doing well. I'm running into a bit of a configuration issue that I hope someone might be able to help out with. I decided it was time to try letting sieve manage my filters and got avelsieve set up with squirrelmail this morning. I had to fight with timsieve for a bit in order to get it to use the correct SASL auth mechanisms, but that part is working fine now. So, I have the sieve server set up and a script on there, but nothing's getting processed. Did you activate the script? If you look in your sieve directory (sievedir option in imapd.conf hashed by userid), you should see a 'defaultbc. link pointing to '.bc' I normally use LMTP to deliver mail from Postfix to Cyrus. I tried to use deliver, since googling seemed to indicate this was the best way to do sieve filtering, but using deliver broke my virtdomain config (it strips the domain when delivering). So, what's the best way to get sieve working with LMTP? Is it even possible? Or is it possible to use deliver and preserve the full mailbox name? You definitely do NOT want to use deliver unless you absolutely have to. Deliver is just an LMTP client anyways, and adds an extra (possibly expensive) process (fork() + exec()) to the pipeline. -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Sieve & LMTP
Hello all, It's been a few years since I've posted here, so I hope everyone is doing well. I'm running into a bit of a configuration issue that I hope someone might be able to help out with. I decided it was time to try letting sieve manage my filters and got avelsieve set up with squirrelmail this morning. I had to fight with timsieve for a bit in order to get it to use the correct SASL auth mechanisms, but that part is working fine now. So, I have the sieve server set up and a script on there, but nothing's getting processed. I normally use LMTP to deliver mail from Postfix to Cyrus. I tried to use deliver, since googling seemed to indicate this was the best way to do sieve filtering, but using deliver broke my virtdomain config (it strips the domain when delivering). So, what's the best way to get sieve working with LMTP? Is it even possible? Or is it possible to use deliver and preserve the full mailbox name? Thanks, Kevin --- Cyrus Home Page: http://asg.web.cmu.edu/cyrus Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
Re: Debug sieve/lmtp
Len Smith wrote:
>
> I'm running Cyrus 2.0.7 on Solaris 8 but cannot seem to get sieve to
> work. The seive scripts are server-side, under /usr/sieve
> and the script is
>
> if header :contains "from" "mickey" {
> discard;
> } else {
> forward to [EMAIL PROTECTED];
> }
>
> The mail messages is deliverd to the user, as if it is ignoring this
> script. Is there anyway to get lmtpd to print out more info on what its
> doing, with regards to sieve?
You have a syntax error in your script which causes sieve to fail, and
as a result lmtpd drops the message in your INBOX. Your script should
look like:
if header :contains "from" "mickey" {
discard;
} else {
redirect "[EMAIL PROTECTED]";
}
Also, if you are trying to test against the address part of the "from"
header, you should use the 'address' test instead of the 'header' test.
Your current test WILL match something like "From: Mickey Mouse
<[EMAIL PROTECTED]>", which I don't think is what you want.
Ken
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key--http://www.oceana.com/~ken/ksm.pgp
Debug sieve/lmtp
I'm running Cyrus 2.0.7 on Solaris 8 but cannot seem to get sieve to
work. The seive scripts are server-side, under /usr/sieve
and the script is
if header :contains "from" "mickey" {
discard;
} else {
forward to [EMAIL PROTECTED];
}
The mail messages is deliverd to the user, as if it is ignoring this
script. Is there anyway to get lmtpd to print out more info on what its
doing, with regards to sieve?
thanx,
len
