Re: [Dovecot] sieve redirect envelope address problem [solved]
submission_host directive solved problem for me. Thanks! -- С уважением, Костырев Александр администратор Linux-систем -Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Ben Morrow Sent: Wednesday, May 08, 2013 1:58 PM To: Костырев Александр Алексеевич Cc: dovecot@dovecot.org Subject: Re: [Dovecot] sieve redirect envelope address problem At 12PM +1100 on 8/05/13 you (Костырев Александр Алексеевич) wrote: > > I have a problem with mail redirection through sieve rules. > I've configured sieve rule that redirects any mail coming to user to > gmail mailbox (or whatever external mail system there is). > But when sieve redirects any mail it puts vmail@%dovecot_hostname% > into envelope address, gives it to my exim for delivery and gmail > rejects my mail because user vmail@%dovecot_hostname% do not exist. > Please, advice for what can be done about this behavior. Sieve should be submitting the mail to the outbound SMTP with the same envelope address as it had coming in (that is, this is a true SMTP redirect, not an SPF-compatible resending-from-a-new-address). I think your SMTP server must be rewriting this based on the uid of the LDA process; this is not something Dovecot can do anything about. To test this you can run sendmail(8) with the -f switch as the vmail user: if the address you specify is rewritten, then the problem is not with Dovecot. You need to fix this in your SMTP configuration, somehow. Decide what your policy is about the envelope sender of outbound mail: are you going to rewrite to @your.domain, which is SPF-compatible but messes up bounces; or are you going to leave it alone, which is what a sieve redirect is supposed to do but which can cause problems if the original sender publishes an SPF policy and the final recipient checks it (neither of which you can control)? There are a number of other variously-unpleasant alternatives, like SRS (which attempts to preserve the original sender while still only sending mail from @your.domain), but basically none of this is specific to sieve or Dovecot. Find out what happens if mail is forwarded in the ordinary way by your MTA, and then work out how to get the MTA to do that for any mail submitted by the 'vmail' user. Ben
Re: [Dovecot] sieve redirect envelope address problem
At 12PM +1100 on 8/05/13 you (Костырев Александр Алексеевич) wrote: > > I have a problem with mail redirection through sieve rules. > I've configured sieve rule that redirects any mail coming to user to > gmail mailbox (or whatever external mail system there is). > But when sieve redirects any mail it puts vmail@%dovecot_hostname% > into envelope address, gives it to my exim for delivery and gmail > rejects my mail because user vmail@%dovecot_hostname% do not exist. > Please, advice for what can be done about this behavior. Sieve should be submitting the mail to the outbound SMTP with the same envelope address as it had coming in (that is, this is a true SMTP redirect, not an SPF-compatible resending-from-a-new-address). I think your SMTP server must be rewriting this based on the uid of the LDA process; this is not something Dovecot can do anything about. To test this you can run sendmail(8) with the -f switch as the vmail user: if the address you specify is rewritten, then the problem is not with Dovecot. You need to fix this in your SMTP configuration, somehow. Decide what your policy is about the envelope sender of outbound mail: are you going to rewrite to @your.domain, which is SPF-compatible but messes up bounces; or are you going to leave it alone, which is what a sieve redirect is supposed to do but which can cause problems if the original sender publishes an SPF policy and the final recipient checks it (neither of which you can control)? There are a number of other variously-unpleasant alternatives, like SRS (which attempts to preserve the original sender while still only sending mail from @your.domain), but basically none of this is specific to sieve or Dovecot. Find out what happens if mail is forwarded in the ordinary way by your MTA, and then work out how to get the MTA to do that for any mail submitted by the 'vmail' user. Ben
Re: [Dovecot] sieve redirect envelope address problem
Because it should be optional for users (to use or not to use filters). -- С уважением, Костырев Александр администратор Linux-систем -Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Reindl Harald Sent: Wednesday, May 08, 2013 12:30 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] sieve redirect envelope address problem Am 08.05.2013 03:24, schrieb Костырев Александр Алексеевич: > Good day! > > I have a problem with mail redirection through sieve rules. > I've configured sieve rule that redirects any mail coming to user to gmail > mailbox (or whatever external mail system there is). > But when sieve redirects any mail it puts vmail@%dovecot_hostname% into > envelope address, gives it to my exim for delivery and gmail rejects my mail > because user vmail@%dovecot_hostname% do not exist. > Please, advice for what can be done about this behavior if you say "any mail coming to user" why do you implent the forwarding in dovecot/sieve instead directly on the MTA? i am using postfix, so no idea how to implement it in exim but i have on asverer 9000 forwarders which never touch the LDA at all and directly forwarded from the MTA
Re: [Dovecot] sieve redirect envelope address problem
Am 08.05.2013 03:24, schrieb Костырев Александр Алексеевич: > Good day! > > I have a problem with mail redirection through sieve rules. > I've configured sieve rule that redirects any mail coming to user to gmail > mailbox (or whatever external mail system there is). > But when sieve redirects any mail it puts vmail@%dovecot_hostname% into > envelope address, gives it to my exim for delivery and gmail rejects my mail > because user vmail@%dovecot_hostname% do not exist. > Please, advice for what can be done about this behavior if you say "any mail coming to user" why do you implent the forwarding in dovecot/sieve instead directly on the MTA? i am using postfix, so no idea how to implement it in exim but i have on asverer 9000 forwarders which never touch the LDA at all and directly forwarded from the MTA signature.asc Description: OpenPGP digital signature
Re: [Dovecot] sieve + redirect + as attachment
On Thu, 22 Oct 2009 12:38:45 -0400 Charles Marcus wrote: > On 10/22/2009, Stephan Bosch (step...@rename-it.nl) wrote: > > What is your exact application? I can take this issue to the Sieve > > mailinglist. > > One use case I would need is for a spam bucket. > > We have an out-sourced anti-spam service, and I have more than a few > ancient email addresses that get nothing but spam, and I'd like to be > able to forward all inbound messages (server side, as they come in) > to a designated address(es), but our provider requires them to be > forwarded as an attachment. Interestingly enough, that is one of reasons that I would benefit from sieve having the ability to forward-as-attachment; possibly with the ability to use multiple addresses in the process. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | One way to stop a run away horse is to bet on him.
Re: [Dovecot] sieve + redirect + as attachment
On 10/22/2009, Stephan Bosch (step...@rename-it.nl) wrote: > What is your exact application? I can take this issue to the Sieve > mailinglist. One use case I would need is for a spam bucket. We have an out-sourced anti-spam service, and I have more than a few ancient email addresses that get nothing but spam, and I'd like to be able to forward all inbound messages (server side, as they come in) to a designated address(es), but our provider requires them to be forwarded as an attachment. -- Best regards, Charles
Re: [Dovecot] sieve + redirect + as attachment
On Thu, 22 Oct 2009 14:01:59 +0200 Stephan Bosch wrote: > What is your exact application? I can take this issue to the Sieve > mailinglist. Cool. I will elaborate more fully then. Since this is not a dovecot specific problem, I will reply to you directly. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | genlock, n: Why he stays in the bottle.
Re: [Dovecot] sieve + redirect + as attachment
Jerry wrote: On Wed, 21 Oct 2009 23:01:14 +0200 Stephan Bosch wrote: Jerry wrote: Is it possible to use the 'redirect' function in 'sieve' to forward a message as an attachment rather than in-line? Unfortunately, no. I thought the (draft) enclose extension could provide this new feature, but the specification explicitly excludes redirect from being affected: http://ietfreport.isoc.org/idref/draft-ietf-sieve-mime-loop/#page-11 I am not sure exactly why. To my knowledge this is not provided by any other Sieve feature/extension. Regards, Stephan Honestly, I get confused reading RFCs. Since there is an 'enclose' extension, exactly how is it intended to be used? In any case, sieve seriously needs a way to forward a message as an attachment. What is your exact application? I can take this issue to the Sieve mailinglist. Regards, Stephan
Re: [Dovecot] sieve + redirect + as attachment
On Wed, 21 Oct 2009 23:01:14 +0200 Stephan Bosch wrote: > Jerry wrote: > > Is it possible to use the 'redirect' function in 'sieve' to forward > > a message as an attachment rather than in-line? > > > Unfortunately, no. I thought the (draft) enclose extension could > provide this new feature, but the specification explicitly excludes > redirect from being affected: > > http://ietfreport.isoc.org/idref/draft-ietf-sieve-mime-loop/#page-11 > > I am not sure exactly why. To my knowledge this is not provided by > any other Sieve feature/extension. > > Regards, > > Stephan Honestly, I get confused reading RFCs. Since there is an 'enclose' extension, exactly how is it intended to be used? In any case, sieve seriously needs a way to forward a message as an attachment. -- Jerry ges...@yahoo.com |=== |=== |=== |=== | I THINK MAN INVENTED THE CAR by instinct. Jack Handey, The New Mexican, 1988
Re: [Dovecot] sieve + redirect + as attachment
Jerry wrote: Is it possible to use the 'redirect' function in 'sieve' to forward a message as an attachment rather than in-line? Unfortunately, no. I thought the (draft) enclose extension could provide this new feature, but the specification explicitly excludes redirect from being affected: http://ietfreport.isoc.org/idref/draft-ietf-sieve-mime-loop/#page-11 I am not sure exactly why. To my knowledge this is not provided by any other Sieve feature/extension. Regards, Stephan
Re: [Dovecot] Sieve: redirect and keep action, possible bug (solved, but curious)
On Saturday 26 September 2009 16:21:34 Stephan Bosch wrote: > Andreas Ntaflos schreef: > > As explained, in the user's sieve script the "keep" after the > > redirect action is ignored when the backup mails script uses an > > explicit "keep" after "fileinto", but not when "fileinto" is used > > with "copy". > > > > Why? > > Because you have tripped a bug that is fixed in the repository, but > not in the final release: > > http://www.dovecot.org/list/dovecot/2009-September/042591.html [...] > Due to persisting headaches since last week I haven't had the ability > nor the motivation to make a new release. Now that I am better I > should release new Sieve and ManageSieve(s) in the next few days or > so. Hi Stephan, thanks for the reply and explanation and confirmation of this bug. Great to hear you are feeling better. Looking forward to testing the next releases. Andreas -- Andreas Ntaflos GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4 signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Sieve: redirect and keep action, possible bug (solved, but curious)
Andreas Ntaflos schreef: As explained, in the user's sieve script the "keep" after the redirect action is ignored when the backup mails script uses an explicit "keep" after "fileinto", but not when "fileinto" is used with "copy". Why? Because you have tripped a bug that is fixed in the repository, but not in the final release: http://www.dovecot.org/list/dovecot/2009-September/042591.html Your script executes as follows in the latest release (wrong): == $ sieve-test -s before.sieve user.sieve message.eml ## Executing script: /home/stephan/before.sieve Performed actions: * store message in folder: Backup/received-backup + add IMAP flags: \seen * keep Implicit keep: (none) ## Executing script: /home/stephan/frop.sieve Performed actions: * redirect message to: f...@example.org Implicit keep: (none) Info: final result: success == In the latest repository version it executes as follows (ok): == $ sieve-test -s before.sieve user.sieve message.eml ## Executing script: /home/stephan/before.sieve Performed actions: * store message in folder: Backup/received-backup + add IMAP flags: \seen * keep Implicit keep: (none) ## Executing script: /home/stephan/frop.sieve Performed actions: * redirect message to: f...@example.org * store message in folder: INBOX Implicit keep: (none) Info: final result: success == Due to persisting headaches since last week I haven't had the ability nor the motivation to make a new release. Now that I am better I should release new Sieve and ManageSieve(s) in the next few days or so. Regards, -- Stephan Bosch step...@rename-it.nl
Re: [Dovecot] Sieve: redirect and keep action, possible bug (solved, but curious)
On Saturday 26 September 2009 02:40:40 Pascal Volk wrote:
> On 09/26/2009 02:27 AM Andreas Ntaflos wrote:
> > …
> > Funny thing is that it doesn't work here, even when I strip it down
> > to just the two lines:
> >
> > redirect "f...@example.org"
> > keep;
>
> Hm, sorry no idea what could be the reason for this behavior.
>
> > What version of Dovecot and Sieve are you using if I may ask?
>
> Tested with Dovecot v1.2.5 + Patch
> http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1 and Sieve from
> http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.12.tar.gz
Thank you for confirming that it should work correctly with the latest
versions of Dovecot and Sieve. I found the problem in my setup.
I found that one of my "before" scripts (sieve_before =
/etc/dovecot/sieve/before.d, [1]) had a fileinto action together with an
explicit "keep". It seems that was a problem for the redirect action
later in the user's own script.
I modified that "before" script to use
fileinto :copy "INBOX/foo/bar";
instead of
fileinto "INBOX/foo/bar";
keep;
and now the redirect action works as expected, like you tested and
posted earlier.
Still, I wonder why this is happening? In both cases there is a keep
action in effect, otherwise the user's script wouldn't get executed at
all. Could someone explain what I am missing here? More details follow.
The script in /etc/dovecot/sieve/before.d looks as follows (I use it to
keep a backup copy of all mail received in an extra, hidden namespace):
001-backup-mails.sieve:
# We only want to backup incoming mail if it is not marked as spam.
if header :contains "X-Spam-Flag" ["YES"] {
discard;
stop;
} else {
# This works
fileinto :copy :flags "\\Seen" "Backup/received-backup";
# This doesn't, as explained above
# fileinto :flags "\\Seen" "Backup/received-backup";
# keep;
}
This user's script is again only two lines:
user.sieve:
redirect "f...@example.org"
keep;
As explained, in the user's sieve script the "keep" after the redirect
action is ignored when the backup mails script uses an explicit "keep"
after "fileinto", but not when "fileinto" is used with "copy".
Why?
Thanks,
Andreas
[1] http://wiki.dovecot.org/LDA/Sieve/Dovecot
--
Andreas Ntaflos
Vienna, Austria
GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4
signature.asc
Description: This is a digitally signed message part.
Re: [Dovecot] Sieve: redirect and keep action, possible bug
On 09/26/2009 02:27 AM Andreas Ntaflos wrote: > … > Funny thing is that it doesn't work here, even when I strip it down to > just the two lines: > > redirect "f...@example.org" > keep; Hm, sorry no idea what could be the reason for this behavior. > What version of Dovecot and Sieve are you using if I may ask? Tested with Dovecot v1.2.5 + Patch http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1 and Sieve from http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.12.tar.gz Regards, Pascal -- The trapper recommends today: face1e55.0926...@localdomain.org
Re: [Dovecot] Sieve: redirect and keep action, possible bug
On Saturday 26 September 2009 02:17:34 Pascal Volk wrote: > Your script looks strange for me. I'm simply using: > > # sieve script start > redirect "u...@example.com"; > keep; > # sieve script end (no conditions) Hi, thanks for the reply. I know it looks strange but that is how Ingo (Horde's filter application) generates it. But essentially it is the same as your script (just ignore the "if true" parts). > All emails is forwarded to u...@example.com and will be saved in the > inbox. Funny thing is that it doesn't work here, even when I strip it down to just the two lines: redirect "f...@example.org" keep; Only the redirection is executed, the keep action seems to be ignored. If I again change it to a 'fileinto "INBOX";' it works as expected. What version of Dovecot and Sieve are you using if I may ask? Thanks, Andreas -- Andreas Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4 signature.asc Description: This is a digitally signed message part.
Re: [Dovecot] Sieve: redirect and keep action, possible bug
On 09/26/2009 02:01 AM Andreas Ntaflos wrote:
> Hi,
>
> Using Dovecot 1.2.4 and the new Sieve implementation in version 0.1.12,
> I ran into a problem that could indicate a bug in Sieve.
>
> The following is a simple script (as generated by Horde's Ingo
> application) to redirect incoming mail and also keep a copy of the
> message in the local inbox:
>
> if true {
> redirect "f...@example.org";
> }
>
> if true {
> keep;
> stop;
> }
>
> Problem is, it doesn't work as expected: no copy of the message is kept
> in the local inbox. However, if I explicitly tell Sieve to "fileinto" it
> works fine:
>
> require ["fileinto"];
>
> if true {
> redirect "f...@example.org";
> }
>
> if true {
> fileinto "INBOX";
> stop;
> }
>
> Is this a bug in Sieve or am I wrong about how "keep" works?
>
> Thanks in advance!
>
> Andreas
Your script looks strange for me. I'm simply using:
# sieve script start
redirect "u...@example.com";
keep;
# sieve script end (no conditions)
All emails is forwarded to u...@example.com and will be saved in the inbox.
Regards,
Pascal
--
The trapper recommends today: face1e55.0926...@localdomain.org
Re: [Dovecot] sieve redirect action
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 30 Jul 2009, Stephan Bosch wrote:
> How do you look at adding one more header, for example X-Sieve-Forward-From:
>
> Now, when redirect action is in use - mail forwards using sendmail command line interface. The problem that there is no suitable way to know which user's script has generate redirect. Received: header may contain envelope receiver but this is valid if only 1 "rcpt to:" command was specified on SMTP session.
> This invokes problem when forwarding mail to non-local domains, breaking such things
like SPF. I'd like to setup SRS for fixing this, but I don't know sender("sieve local
user") mail. Adding one header with valid local user e-mail address will fix this.
> Google add 2 headers for this - X-Forwarded-To: and X-Forwarded-For: .
>
> What do you think about this ?
I have no objection, but then again my experience on this subject is
pretty bleak. Does anyone else have comments?
Basically I like the idea.
I've seen
X-Resent-By: Forwarder
X-Resent-For: stef...@example.com
X-Resent-To: kai...@example.net
inserted by one of my hosters.
Pine adds RFC 2822 sec 3.6.6 style headers (RFC 4021 sec 2.1.14 ff.)
ReSent-Date: Thu, 30 Jul 2009 14:36:18 +0200 (CEST)
ReSent-From: re-sender
ReSent-To: new recipients
ReSent-Subject: new Subject
ReSent-Message-ID: New msgid
ReSent-User-Agent: New MUA id string
However, the section starts with: "Resent fields SHOULD be added to any
message that is reintroduced by a user into the transport system." Dunno,
if "by a user" applies to Sieve, too.
IMHO, it should be customizable.
Bye,
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iQEVAwUBSnGWi3WSIuGy1ktrAQLUYggAw/BXIWXFEPw4pKpKpTbvufnsXLpP4Qew
GGo/9URurlk1TXPHywvLpgvRIQsfpe8elfqWmpiwMi56uIdXcDTY0rQ1TQ5HvlP2
3hqTGmKPF9y33HikCTTR9ZxVf9aebHDAkLKWeFyKNR6it4KCc1L9y2b2ebxhmrWj
u8vSX2tzeghr5XMHoowz8JMo3VdGnti6SBjeIOVHFeyVZSuNlXitZwLdPmTG7WEz
sqkqEvPJv3tXppDOahyayTu4SG9PkfKIv/Oe0Rsl7eQg3Lg5UK+uRmiJlA1KZnt1
SqGoTnqnDs4vBS8x6w70YxL+7rHwtMW9rZv9RBVt8pC8Lr6RkRanEw==
=AN8H
-END PGP SIGNATURE-
Re: [Dovecot] sieve redirect action
Nikita Koshikov schreef:
Hello Stephan,
First of all, thank you for dovecot-sieve implementation.
I see that you are adding X-Sieve header to all outgoing e-mail in cmd-redirect.c
/* Prepend sieve version header (should not affect signatures) */
rfc2822_header_field_write(f, "X-Sieve", SIEVE_IMPLEMENTATION);
How do you look at adding one more header, for example X-Sieve-Forward-From:
Now, when redirect action is in use - mail forwards using sendmail command line
interface. The problem that there is no suitable way to know which user's script has
generate redirect. Received: header may contain envelope receiver but this is valid if
only 1 "rcpt to:" command was specified on SMTP session.
This invokes problem when forwarding mail to non-local domains, breaking such things like
SPF. I'd like to setup SRS for fixing this, but I don't know sender("sieve local
user") mail. Adding one header with valid local user e-mail address will fix this.
Google add 2 headers for this - X-Forwarded-To: and X-Forwarded-For: .
What do you think about this ?
I have no objection, but then again my experience on this subject is
pretty bleak. Does anyone else have comments?
Regards,
--
Stephan Bosch
step...@rename-it.nl
Re: [Dovecot] [SIEVE: Redirect] Double ">" in forwarded envelop sender address => Gmail syntax error
Timo Sirainen a écrit : Mail rejections were fixed to use -f parameter, but I guess forwards should too. Fixed: http://hg.dovecot.org/dovecot-1.1/rev/b217c085ba15 Thanks ;) -- Toorop http://www.flickr.com/photos/toorop/
Re: [Dovecot] [SIEVE: Redirect] Double ">" in forwarded envelop sender address => Gmail syntax error
On Mon, 2009-04-20 at 17:02 +0200, Stephan Bosch wrote: > http://hg.dovecot.org/dovecot-1.1/file/1.1.14/src/deliver/mail-send.c > > at line 178, the return path is not taken from the -f parameter for > forwarded messages. It is in stead extracted from the message itself and > the address is not normalized, meaning that any surrounding <> will > still exist. .. > BTW, this problem sounds familiar.. haven't we seen this one earlier? Mail rejections were fixed to use -f parameter, but I guess forwards should too. Fixed: http://hg.dovecot.org/dovecot-1.1/rev/b217c085ba15 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] [SIEVE: Redirect] Double ">" in forwarded envelop sender address => Gmail syntax error
Toorop wrote:
Plateform: gentoo + qmail
My deliver line is in a .qmail-USER file:
|/var/qmail/bin/preline /usr/libexec/dovecot/deliver -f ${SENDER:-<>} -d
u...@domain.tld
I notice that sieve implementation in Dovecot use double ">" for the
envelop sender when there is a redirect command in sieve script.
(i've tried preline -f, without -f ${SENDER:-<>},... but nothing change
for the the envelop sender syntax, alway the double ">")
And that fact breaks forwardin to Gmail.
Gmail reply that there is a syntax error probably due to the double "<<"
(<> and not ) as we can see in the log behind:
Dovecot logs:
deliver(steph...@): Apr 20 16:06:44 Info: Sending a forward to
with return path <>
deliver(steph...@x: Apr 20 16:06:44 Info:
msgid=<49ec816d.9090...@x.com>: forwarded to
By the looks of the deliver code in
http://hg.dovecot.org/dovecot-1.1/file/1.1.14/src/deliver/mail-send.c
at line 178, the return path is not taken from the -f parameter for
forwarded messages. It is in stead extracted from the message itself and
the address is not normalized, meaning that any surrounding <> will
still exist.
The only way I can see this could manifest is when your sendmail does
not normalize its -f parameter and tries to issue this address in the
SMTP MAIL FROM: command with additional '< >'. That is all I can think
of right now...
Timo, what's your opinion?
BTW, this problem sounds familiar.. haven't we seen this one earlier?
Regards,
Stephan.
Re: [Dovecot] Sieve "redirect"
James Butler schreef:
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"?
Unfortunately, "redirect" seems to be unsupported by Dovecot.
Thank you.
James
Here's why I posted this:
sievec global.before.sieve global.before.svbin
line 7: error: unsupported sieve capability 'redirect'.
error: validation failed.
Error: failed to compile sieve script 'global.before.sieve'
Ok, this error needs some clarification, since I, being the developer,
did not quite anticipate users 'require'ing Sieve core commands. :) The
redirect command is part of the main Sieve language and therefore it is
not known as a Sieve extension. This means that you can start using the
redirect command right away, but also that 'require'ing it causes an
error. So don't use 'require "redirect";' in this case.
I am going to clarify these errors, so that user's know right away what
they are doing wrong.
Regards,
--
Stephan Bosch
step...@rename-it.nl
Re: [Dovecot] Sieve "redirect"
maybe you need to include vacation?
require "vacation";
if header :contains "Subject" "Listserv" {
redirect "list-us...@example.com";
redirect "list-us...@example.com";
redirect "list-us...@example.com";
stop;
}
Re: [Dovecot] Sieve "redirect"
> 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"?
>
> Unfortunately, "redirect" seems to be unsupported by Dovecot.
>
> Thank you.
>
> James
>
Here's why I posted this:
sievec global.before.sieve global.before.svbin
line 7: error: unsupported sieve capability 'redirect'.
error: validation failed.
Error: failed to compile sieve script 'global.before.sieve'
Sieve 0.1.4, Dovecot 1.2.rc2
James
