Filters: catchall forwarding filter

[Baylink]

I want to put a catchall filter at the end of my list that automatically carbons anything that made it through out to my Blackberry -- until I get a better answer to the 'getting mail on your Blackberry' issue; my 7100i won't even run the generic zme client -- but I can't find a way to do it.

I know how to write the rule, but there's no TRUE condition on the pulldown menu in the top half of the rule-builder.

Should I say "From" "Contains" "@"? That looks like it would work, but it seems inelegant.

Should I feech an "Always" choice for that pulldown menu?

Alternatively, I see that, in Preferences->Mail->Receiving, there's a way to autocarbon everything, and while I assume that that it's post-AV, post-spam, I am not clear on whether it's post-filtering or not; the documentation doesn't seem to say. A quick test suggests that it carbons *first*, which means it won't help me.

So, what's the recommended solution to this?

Self-thread-jack: who does filtering? The webclient? Or the LMAP delivery server? IE: if you set up filters using the webclient, will IMAP see the messages delivered there if you never again fire up the webclient?

[mmorse]

Don't forget to also file it locally - if you don't choose 'keep in inbox' or 'file into folder' in the filter rule, you might accidentally loose that mail from Zimbra: Bug 9181 - Filters: forward with 'retain original' option

Likewise zimbraPrefMailLocalDeliveryDisabled (the 'don't keep a local copy of messages' checkbox under preferences > mail > 'forward a copy to' ie zimbraPrefMailForwardingAddress (additional with multi zimbraMailForwardingAddress) works exactly like it sounds. (Well in LMTP anyways not SMTP - bug 7474 & bug 7449 to cut down on extra cpu cycles.)

Now that that warning about forgetting local in filters is out of the way, some notes to explain why I would personally not use the zimbraPrefMailForwardingAddress feature to send mail to my phone address - stick with a rule(s) in sieve filters (or at end of filters in your case).

Re the first few questions: You could use a wildcard condition like * (Though I prefer to only fwd things with my address in to/cc, you seem to have a serious set of rules above this to handle your mail.)

Hate to burst your 'post-junk' bubble a tiny bit: zimbraPrefMailForwardingAddress still includes junk greater than zimbraSpamTagPercent, but is thankfully post anti-virus & post anti-spam greater than zimbraSpamKillPercent. It's like that because forwarding is done by postfix based on address resolution rules, and not by any piece that has an opportunity to examine content. Also the destination may need to know about false positives.

So in short using zimbraPrefMailForwardingAddress: Any spam that would end up in your 'junk' folder is forwarded. Anything dropped on the floor by ClamAV/Spamassassin is not forwarded.

Some use a 2nd MTA to catch outgoing mail that's already tagged with junk headers (X-Spam-Flag, X-Spam-Score, X-Spam-Level, or X-Spam-Status) for users doing the 'forward all mail approach' - so they don't become a sender of possible junk themselves & thereby get on an another organizations negative list. Nothing like a tarnished sender reputation.

Out-of-office replies aren't sent to junk: Bug 17561 - autoreply / forward and junk

if filters move a message to spam or trash, we do not out of office auto reply to it.
> If a message in moved to "junk" by zimbra spam is it office auto reply'ed ?
> No out of office message is sent in this case also.

The good news/+1 for rules - using sieve filtering is now post junk sorting:

In ZCS 5.0.1 and earlier, user filters were run before the spam filter check was run. This meant that if the user filtered mail into a folder, spam would not be identified and sent to the Junk folder.
Beginning with 5.0.2, spam check is completed first and messages identified as spam are moved to the Junk folder. With this change, users cannot write a filter to move false positive spam out of the Junk folder.

Two options:

A) If you prefer ZCS 5.0.2+ to use the spam filter function as it works for 5.0.1 and earlier, you can set the zimbraSpamApplyUserFilters option to True.

This can be done by COS:
zmprov mc COSname zimbraSpamApplyUserFilters TRUE
or for individual accounts:
zmprov ma user@domain.com zimbraSpamApplyUserFilters TRUE

B) You can create a spam white list for individual accounts that allows an account to identify email addresses that should not be marked as spam: zmprov ma user@domain.com +amavisWhiteListSender someone@example.com
RFE to bring this into the end-user UI: Bug 6953 - Per user white & black lists in the UI

Also an interesting RFE: Bug 7776 - Auto-forward -- should have option for Inbox only

[Baylink]

Ok, Got it.

Yes, I filter all my mailing list mail into folders, and the trickle that's left is entitled to bounce to my blackberry.

Of my thousand messages a day, 600 were spam, 395 were mailing lists, and 5 personal mail.

So I'll set up a rule that says "From" "Contains" "@", which ought to work, and put it last.

So here's a question: how would one go about generating and submitting patches against *NE*? The traditional fashion? I know guys don't quite run the standard FOSS development environment...