OK, this is working perfectly. Thanks for the help Aaron. How that setup
was ever working before is a mystery best left for the ages I think.
Aaron Stone wrote:
Yep, exactly. Good luck!
On Wed, May 16, 2007, Blake Mitchell <[EMAIL PROTECTED]> said:
OK, I think I see what I have to do. I need to remove the keep from my
redirect rule, and instead, put an explicit keep that matches anything
at the end of my ruleset. (After all my fileinto,stop rules for
sorting.) To make sure that anything that falls through all rules is
kept, because the redirect will cancel the implicit keep.
Aaron Stone wrote:
I'm not sure I understand what you mean.
If you redirect a message, it cancels the implicit keep. The only copy of
the message is the redirect, there will be no inbox copy.
If you fileinto another mailbox, it cancels the implicit keep. The only
copy of the message is in the other mailbox.
If you explicitly keep a message, it puts a copy into the inbox and
cancels the implicit keep. In other words:
keep;
discard;
keeps the message.
keep;
keep;
discard;
probably keeps the message twice. I bet I should fix that! :-P
Processing only stops at the keyword 'stop' or the end of the script.
Aaron
On Wed, May 16, 2007, Blake Mitchell <[EMAIL PROTECTED]> said:
So then the question is this: How does one have a rule to send a copy of
a message to another address (redirect), but still have the message
continue on to the next rule for processing?
Aaron Stone wrote:
Ah, yes, an explicit keep is the same as a fileinto "inbox".
On Wed, May 16, 2007, Blake Mitchell <[EMAIL PROTECTED]> said:
I think I've found the culprit, this rule:
# forward a copy of everything to gmail, unless it came from there
if not anyof ( header :contains "X-Forwarded-For" "[EMAIL PROTECTED]"
, header :contains "From" ["MAILER-DAEMON@",
"bankofamerica.com"] ) {
redirect "[EMAIL PROTECTED]";
keep;
}
Based on the trace output, it is my assumption that the "keep" on this
rule that is causing the INBOX delivery. After glancing through
sieve.info, it is unclear to me if this is actually the correct behavior
or not. http://wiki.fastmail.fm/index.php/BasicSieve#Actions seems to
indicate that a "keep" will always deliver to INBOX, instead of just
being a fall-through as it has in the past.
For now I have removed this rule from my sieve script, and confirmed
that this does correct the issue.
Aaron Stone wrote:
There are two very telling lines, they look like "action is FILEINTO,
mailbox is [...]" and the first one is INBOX, the second one is Work. So
we have to figure out where that first fileinto action came from.
I haven't had a chance to dig into this yet, but will have time probably
on Thursday. Thanks for the trace!
Aaron
On Wed, May 16, 2007, Blake Mitchell <[EMAIL PROTECTED]> said:
Aaron,
Here is a trace of a sample message insert, my sieve script, etc. Let me
know if anything else I can provide will be of use to you.
Thanks,
Blake
Aaron Stone wrote:
Oh that's not good, the implicit keep should be canceled after a
fileinto. I'll check this out.
Aaron
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
_______________________________________________
Dbmail-dev mailing list
Dbmail-dev@dbmail.org
http://twister.fastxs.net/mailman/listinfo/dbmail-dev
