How can I add an extension to Dovecot's Sieve implementation?
I would like to use 'editheader' and 'redirect'.
Thank you!
James
> On Fri, 2009-04-03 at 12:34 -0700, James Butler wrote:
>> How can I add an extension to Dovecot's Sieve implementation?
>>
>> I would like to use 'editheader' and 'redirect'.
>
> I'm not really sure what you mean. editheader isn
> On Fri, 2009-04-03 at 13:08 -0700, James Butler wrote:
>> - Dovecot v.1.2.beta4
>> - Sieve 0.1.4
>>
>> I am getting this in my sieve log:
>>
>> main script: line 7: error: unsupported sieve capability 'editheader'.
>
> Right, this isn&#x
And if it's not too much trouble, is there a way to include currently
un-included extensions, like 'editheader', into Dovecot/Sieve? How
complicated is it? I'm guessing that it is more complicated than simply
writing a Capability definition and generating a plugin ...
James
> On Fri, 2009-04-03 at 13:43 -0700, James Butler wrote:
>> And if it's not too much trouble, is there a way to include currently
>> un-included extensions, like 'editheader', into Dovecot/Sieve? How
>> complicated is it? I'm guessing that it is more compli
Hmmm. I'm having difficulty finding a good place for a global Sieve script.
The problem seems to be related to saving the compiled version
(xxx.svbin.tmp) in the same location as the script (xxx.sieve), which
happens using the credentials of the recipient user.
i.e.
drwxr-xr-x dovecoter dovecote
Thank you for your response, Mr. Bosch.
> James Butler schreef:
>> Hmmm. I'm having difficulty finding a good place for a global Sieve
>> script.
> First of all, you should start a new thread (i.e. don't reply on an
> existing message) if you have a completel
Is anyone here using a global Sieve file that handles messages for an
entire server with many users? I understand and use local Sieve files, but
I would like to learn more about how to set up Sieve to filter ALL
incoming messages using a single file. I would love to read about how you
managed to ge
Thank you very much for your reply, Mr. Bosch. Still trying to iron it out.
> If you are using the new Sieve implementation, you can use the new
> multiscript feature. It is not explained on the wiki yet (I should give
> the new Sieve its own page), but things are outlined in the
> configuration s
I've been messing with this for too long, now, and I'm blind to whatever's
wrong. Or I'm simply being dense. Either way, I need help with a common
issue.
I'm trying to get Postfix+Spamassassin+Dovecot going on Fedora 10. (I'll
get back to the global Sieve thingy soon, but I need to get this going,
ing problems with permissions on auth-master too. I solve them
> creating manually the folder /var/run/dovecot with correct permissions but
> i
> see you already did that :\
>
> On Sun, Apr 12, 2009 at 5:27 PM, James Butler
> wrote:
>
>> I've been messing with this for
er SWITCH that seems to be
> problematic.
>
> But then, my brain is all garbled, at this point, so I can't really trust
> any of my logic. I'll check back in, tomorrow.
>
> Thanks, again.
>
> James
>
>> Hi,
>>
>> I was having problems with permissions
> On Mon, 2009-04-13 at 15:48 -0700, James Butler wrote:
>> 1) User 'spam:dovecot' runs Smapassassin
>> 2) Hands off to deliver (root:dovecot)
>
> Have you set up some kind of setuid-root deliver, or why is it running
> as root:dovecot here instead of spam:
Thank you for your continued attention, Timo.
> On Tue, 2009-04-14 at 10:22 -0700, James Butler wrote:
>> > On Mon, 2009-04-13 at 15:48 -0700, James Butler wrote:
>> >> 1) User 'spam:dovecot' runs Smapassassin
>> >> 2) Hands off to deliver (root:d
Here is everything I could think of that might pertain to this, as
currently configured on my dedicated server. It's all fresh! :)
## SYSTEM ##
Fedora 10
Postfix 2.55
Dovecot 1.2.rc2
Spamassassin 3.2.5
SELinux (no SELinux restrictions. Testing done with SELinux=permissive.)
SASLAuthd (not requir
I have changed /usr/local/libexec/dovecot/deliver permissions as follows:
-rwsr-s--- 1 root dovecot 4044835 2009-04-03 13:52 deliver
Because of message returned to 'sen...@example-send.com':
"local configuration error. Command output:
/usr/local/libexec/dovecot/deliver must not be both world-exe
Oh, that was fun.
Making the change below resulted in mail getting deferred with "Fatal:
destination user parameter (-d user) not given" ... which apparently is
caused by running deliver as 'root'!
(http://archive.netbsd.se/?ml=dovecot-general&a=2008-02&t=6558196)
So I am back to:
-rwxr-xr-x 1 r
assin, which
seems a little unusual, considering the popularity of Spamassassin.
James
> On Tue, 2009-04-14 at 14:17 -0700, James Butler wrote:
>> Oh, that was fun.
>>
>> Making the change below resulted in mail getting deferred with "Fatal:
>> destination user pa
> On Wed, 2009-04-15 at 07:52, Timo Sirainen wrote:
>
>
>> Perhaps you shouldn't be using the pipe at all. Maybe you should just
>> put the command to mailbox_command and have it do all the work? Then
>> there's no need to worry about things like setuid-roots or whatever.
>
>
> Given what his conf
Well bust my buttons! Thanks, Timo! FUNCTIONING! Let Postfix figure out
the proper user. BTW, my 'deliver' is set to 755. Nothing special.
> I'm not all that good with Postfix configuration, but:
Clearly quite good enough.
> On Tue, 2009-04-14 at 13:05 -0700, James Butler
Not a problem ... sharing a solution (this time)! Please correct my
understanding of the process, if required.
"i_stream_read() failed: Permission denied" is an error message generated
when a large-ish file (>128kb in my case) is attached to a message that
has been passed to Dovecot's deliver prog
> On Wed, 2009-04-15 at 16:47 -0700, James Butler wrote:
>> "i_stream_read() failed: Permission denied" is an error message
>> generated
>> when a large-ish file (>128kb in my case) is attached to a message that
>> has been passed to Dovecot's deli
> On Wed, 2009-04-15 at 18:55 -0700, James Butler wrote:
>> > On Wed, 2009-04-15 at 16:47 -0700, James Butler wrote:
>> >> "i_stream_read() failed: Permission denied" is an error message
>> >> generated
>> >> when a large-ish file (>128k
> On Thu, 2009-04-16 at 17:01 -0700, James Butler wrote:
>> > But there's no dovecot.deliver anymore in v1.2:
>> >
>> > ~/cvs/dovecot-1.2/src/deliver% grep dovecot.deliver deliver
>> > ~/cvs/dovecot-1.2/src/deliver%
>> >
>> > It
Postfix 2.5.5
SpamAssassin 3.2.5 (under Perl 5.10.0)
ClamAV 0.95.1
Dovecot 1.2.rc2
works fine on Fedora 10.
Installed Dovecot and ClamAV from source and everything else using yum.
I'm using the ClamAV plugin for Spamassassin:
http://wiki.apache.org/spamassassin/ClamAVPlugin
I'm calling Spamass
Is there an alternative to the "redirect" Sieve capability?
For example:
if header :contains "Subject" "Listserv" {
redirect "list-us...@example.com";
redirect "list-us...@example.com";
redirect "list-us...@example.com";
stop;
}
How can I do the above without using "redirect"?
Unfortuna
> Is there an alternative to the "redirect" Sieve capability?
>
> For example:
>
> if header :contains "Subject" "Listserv" {
> redirect "list-us...@example.com";
> redirect "list-us...@example.com";
> redirect "list-us...@example.com";
> stop;
> }
>
> How can I do the above without using "
Egbert Jan van den Bussche wrote:
>> -Oorspronkelijk bericht-
>> Van: dovecot-bounces+egbert=vandenbussche...@dovecot.org
>> [mailto:dovecot-bounces+egbert=vandenbussche...@dovecot.org]
>> Namens James Butler
>> Verzonden: vrijdag 17 april 2009 20:5
missing, the message subjects when there are many messages are
actually more difficult to visually process, for me, even when all of
the messages within a directory are from the same list.
My 2 cents.
James Butler
IT Director
United Defense Group, LLP
usic for Humans, Burbank California
- Internet Society - Los Angeles Chapter, Los Angeles, California
- MyPhotoDiet.com, Providence Rhode Island
James Butler
30 matches
Mail list logo
